Serialloop - Workflow

[AllIT (Anirban Singha)]

Hello All,

inside the serialLoop get-identity does not with the loop variable $.serialLoop.loopInput

It works with loop variable $.loop.loopInput

Is this being an expected behavior?

Thanks,
Anirban

[ryan_toornburg]

Hi @AllIT can you test and post the json output of the step? Is $.serialLoop.loopInput coming from the variable selector list?

[ssowmya567 (Sangeetham Sowmya)]

Hi @AllIT,

There is a similar discussion around Serial Loop behavior in the thread below. It might be useful to compare your scenario and see if it helps

New Capability: Workflows with 1K Serial Loops

Description We are excited to announce a new set of Serial Loop operators in Workflows that support up to 1,000 iterations per loop. With these operators, you can process large lists one item at a time and repeat steps until a condition is met without hitting the 250-item limit of today’s Parallel Loop operator. What you need to know The new loop operators run in serial (one iteration after another). They do not replace the existing parallel Loop operator (250-item cap) - both will be availabl…

[punna0001 (harish Punna)]

Yes, $.loop.loopInput is the correct one to use inside a serial loop. That is the expected behavior.

The workflow operators docs specifically say this for serial loops: data within the loop’s steps must be referenced using a JSONPath expression beginning with $.loop.loopInput. Same syntax as the parallel loop. So regardless of what you name your serial loop step, inside the loop you always reference it as $.loop.loopInput.

I think the confusion around $.serialLoop.loopInput or $.<Loop_Name>.loopInput probably comes from the 1K Serial Loops announcement thread where there was some back and forth on this between community members and SailPoint. But going by the official docs, $.loop.loopInput is the correct and safe path to use.

So your workflow with $.loop.loopInput should be fine. I would stick with that.