We are implementing an emergency termination process using a form-based approach. To achieve this, we have created a custom form and an associated workflow.
Within the form, we select the active identity and provide an option to set the Out of Office flag to Yes or No for that identity.
Once the form is submitted, it triggers the workflow, which updates the lifecycle state of the identity from ActiveSF to TerminatedDisabled. ISC detects this attribute change and invokes the configured lifecycle workflow, which proceeds to disable the associated accounts.
However, within the custom workflow we created, we observed an issue with the Send Email step. The email template is expected to retrieve and display the Out of Office values captured in the form, but those values are not being populated in the email notification.
Can you show us how you’re referencing the form data from the send email step? My guess is there’s some small syntax related mix up on that step that’s causing the variable to return as null or just the variable name.
I also see that you’re putting all of this data inside a loop. To access data outside the loop, it needs to be passed in through the context of the loop or the loop input to be accessible by the steps inside.
So for example, if you’re passing the formdata inside the loop as context, you can reference the formdata by doing this $.loop.context.outofofficestatus to access your data inside the loop.
Most likely issue: the Out of Office value from the form is not automatically available as an identity attribute inside the email template.
The form captures that value at submission time, but unless your workflow stores it in a workflow variable or writes it back to the identity/account first, the email step has nothing to resolve.
