Is there any limitation to number of utilities we can call simultaneously in a flow shape?
I have a requirement to start multiple flows on submit of a screen based on its input. In a worst scenario, I have start three flows independent to each other. For some technical reasons, I cannot use spin-off or sub-process. They should behave like adhoc flows. So, I am calling this activity called "StartNewFlow" three times for three flows that I want to initiate.
But, at run time, it is initiating only two processes. As I had a look at the tracer it is ending the process after second utility
Say, I have Utility1, Utility2, Utility3. It is executing Utlity1, Utility2 and ending the flow. If I skip Utility1 then, Utility2, Utility3 are executed. I tried changing the order of utilities but no luck.
So, is there any limitation to number of utilities we can call simultaneously in a flow shape? What is the meaning of that highlighted flow message?
I am not aware of any limit to the number of utilities you can call in a flow. I can definitely confirm if there is a limit it is significantly higher than three. I suspect the limitation is within StartNewFlow or Wrapper_StartNewFlow, although I'm not actually aware of a limit. Have you tried using a single uitlity shape that calls an activity and the logic to spin off (or not) your new flows resides in there? That would certainly rule out there being any sort of limit on utilities and help highlight any limits of StartNewFlow. What is the technical reason you can't use a spin off? I would think that's exactly what you would want to use.
So, yeah. I have Step 1 with Flow A and Step 2 with Flow B in same order under a stage. Flow A and Flow B have a split-for-each in them on this page list ResponsesByParty calling Flow A1, Flow B1 respectively with join condition set as ALL. The standard Stage-step navigation bar in work object header doesn't support split-for-each or sub processes assignments for a step. We cannot see the link on the Step if the assignment is of a subprocess in the Step process. So, I had to change the step link configuration to consider even the assignments of sub-process by comparing the top flow property on the pxflow page of the sub-process with the process name of the step.
Now, if I use spin-off or sub-process for Flow B, it will treat the assignments in Flow B1 as part of Step 1 but, I want to show them as part of Step 2. Hence, I am trying to start the flows as an independent process.