Conceptually, it is very simple, in very un-Outsystems notation it looks like this:
The Examples in Executing Multiple Instance Activities use a human process to initiate each iteration of Interview.
But when I create a Process Flow:
I cannot iterate through ExecuteProcesses
I cannot pass an array between AutomaticActivities (ok, I can pass a JSON list)
I cannot Initiate an ExecuteProcess from within an AutomaticActivity
But this ProcessFlow approach opens multiple Conditional Starts...
An alternative might be to use a Server Action to handle the iteration through the ExecuteProcess fails to use BPT to manage the overall process:
If a ServerAction is called from within a ProcessFlow the Executions are spawned independently and they need to be tracked.
I am reviewing the option to use a Light Process to launch on the creation of each chunk stub.
If there is a preferred pattern, I would be happy to hear about it....