OK we are running K2 Five (5.0001.1000.1).
In 4.7 we could call an IPC process as part of a loop or use plan per slot (no destinations).
The sub-workflow / IPC process would have a task in it and we could then add a succeeding rule to stop the parent process continuing before all the sub-workflow tasks were completed.
How the devil is this accomplished in the new workflow designer for Five?
I can see the loop activity and the sub workflow activity and see that you can stop the workflow continuing until the sub-workflow task has completed but if you check this then you cannot do the looping as it'll create the first task and then wait. I think this was the same feature as the synchronous option in 4.7.
Any ideas?