Question
Cornèr Banca S.A.
CH
Last activity: 30 Apr 2025 17:20 EDT
Change stage in Subprocesses
We have a change stage in a subprocess and the behaviour we observed is that the parent flow proceed as if the subprocess reached the end shape.
The automation "Change to a Stage" should clean up all the processes as "CleanUpProcesses" parameter is defaulted to true, but the result is that we have a new flow in the new stage and the parent flow in the old stage (when we have an assignment otherwise the parent flow follow its route and closes).
The same behaviour is observed when we force close the case (causing active assignment on closed cases or other unexpected behaviours).
In some old documentation (Pega 7 or 8) there is this phrase: "By default, the calling flow waits for the subprocess to finish running before it moves to the next shape in the sequence." But this isn't present in the new documentation.
Is this working as intended? Are we using subprocesses in a wrong way? Or we should open a SR?
HCA Healthcare
US
@FedericoC5373 In your scenario, using "Change Stage" within a subprocess can lead to unexpected behavior because the parent flow may treat the subprocess as completed even if the case has only switched stages, not actually finished the subprocess logic. This happens because the ChangeStage step with CleanUpProcesses=true exits all flows except the one for the new stage, including the subprocess, making the parent flow move forward. This is technically working as designed, but it can lead to issues like orphaned assignments or stage mismatches. To avoid this, it's better to avoid placing "Change Stage" in subprocesses if the parent flow expects a proper completion. Instead, move the change stage logic to the main flow or ensure the subprocess ends cleanly before stage transitions.