Workflow issue with Form inside of Loop

[kbende03 (Kenneth Bender)]

I’m currently working at implementing some basic workflows to move away from scripts handling some basic tasks inside of SailPoint.

A very simple workflow that I have designed is currently doing the following:

1. Triggers on a Scheduled Trigger each day at a set time.

2. Performs API search to find entitlements that were created in the last 1 day, on our Active Directory Source, within a specific OU.

A foreach loop then starts the following steps:

1. Checks to see if a description is set for this new entitlement. If so, enables the entitlement as requestable within the “Request Center” using the Patch API method.
   This part is currently working.

2. If there is not a description set, then a different path of the workflow is followed. That path looks like this

   • A custom form is created
   • The patch Entitlement API method is called using a variable from the form to update the description with the value submitted in the form, as well as mark the entitlement requestable.

Currently when this workflow runs if an entitlement is missing a description, the form is created and sent off, however once the form is submitted, the rest of the workflow is never completed.

My question is this: For forms within Loops of workflows, does the remainder of the workflow finish after the form is completed, or does workflow just end upon sending a form out?

I know that I could create a seperate workflow using a “Form Submitted” trigger as the initiator, but I don’t want to clutter our workflows up if preventable.

[RAKGDS (Rakesh Bhati)]

Hey,
I doubt this will be achieved currently in your workflow. So once you form is submitted we have a different trigger for the same. The remainder of the workflow won’t be called once you form is submitted.

Thanks

[mesahassel]

Are you putting the logic for the rest of your workflow in the loop or outside of it? I just tested this to see if I could do a post to change a lifecycle state after a form was submitted. It worked with the HTTP Request action inside of the loop after the Form action and before the end step operator.