Building on what was proposed by @Peter Bodelier solution is as follows:
Create a reusable "Gather Task Status" SubFlow which can be reused and will either 1) WAIT on an unfinished task if one exists, or 2) Return a flag indicating that all tasks were in fact completed. I added some integers also, to indicate how many Complete, Incomplete, and Skipped tasks there were, but that is icing on the cake, and could be skipped.
The overall subflow looks like this:
The inputs and outputs look like this:
Individual flow actions look as follows:
The subflow is used inside of a regular Catalog flow as follows:
The details of those Flow actions are as follows:
Then at runtime, after all tasks are closed Closed Complete, Closed Incomplete, or Closed Skipped, like this:
The Catalog Item will be closed, like this. Woohoo! ...
Optional updating of comment field looks as follows:
The End. Please mark helpful if this helped you in some way!
@VullankiL We haven't made a habit of doing this in Flow like we did in Workflow so it took awhile to find an example, but I think the following series of steps works as of Vancouver (we're now on Xanadu). In the first screen shot, note the 3 second Wait for, if I recall correctly that prevented an issue.
