We have a few Onboarding/Offboarding catalog items that have specific back end tasks that need to be completed before tasks for application access and IT equipment tasks are created.
We built these a few years back and created Workflows to do this type of operation using the Branch/Join on the additional tasks after the first few tasks are completed. This works great, because there is no set due dates or requirements on when the additional tasks are to be completed and, most important, the Request/RITM does not go to Closed Complete state until ALL the tasks are closed.
How can this type of action be recreated using Flow Design. I put a "wait for condition" after the first initial tasks before the additional tasks are created, which works just fine, but using another "wait for condition" on the last additional task is not working because sometimes that task is completed before other additional tasks, so the Request/RITM goes to closed complete state with open (orphan) tasks. I even tried checking the "wait" box on the last task, but it still creates with all the other tasks instead.
I have tried parallel flows and sub flows, but still getting the same result.
Any suggestions?
