Question
Start Upon stage entry priority in a Case Type
Hello dear community,
I am working on Pega 7.31 and I have some troubles to configure steps order execution in a stage.
The scenario is : When I complete my stage 1, I go to stage 2.
In stage 2, there are 4 steps : A - B - C -D
In my application, when the user arrives to Stage 2, he should directly arrive on step A. However, he has the possibility to skip temporaly this part by going back on the review of the Case to go to Step B and complete the rest of the Stage (with Step A still opened = not completed).
To do that, I put steps A & B to "Start Upon stage entry" in my case type, otherwise I could not go out of Step A (without completing it) and go on Step B.
But the issue I meet is when I complete Stage 1,and I automatically move to stage 2, it's the Step B that's automatically open first and not Step A. For my customer needs, I have to let the order A - B - C - D displayed.
So do you have any idea why it's the Step B that's opening directly and not A ?
Thank you.
Best regards, Kévin.
@KévinG49
I am going off memory a bit here. I think this is because Pega does the work to create the assignment for A (because it is the first configured in the stage), and then subsequently does the work to create the assignment for B.
Once Pega realizes there is no more steps to start on stage entry, the case has reached an idle point. Once idle, if the most recently created assignment (B) is performable by the current user, it makes sense that B is the one shown given the clipboard already has B's assignment state in place.
Is it appropriate to swap A and B around? That is, have Stage 2 configured as B - A - C - D? This would have A in place at the idle point and be shown to the user.
Depending on what you need to happen once either A or B are performed (for example, in both cases they should go to C), you may want to investigate a Split Join subflow in the Flow rule, for which you may need to use Dev Studio. This is another technique for starting multiple flows at the same time, and having some rules around how to proceed once either (or both) are completed.
There is also the option to add A and B as Parallel Processes to your stage, but that's not much different to what you already have.
In all of the above though, I think the principle of "the last performable assignment created is the one shown" still likely takes effect.
Post back your findings - I have one other idea in mind too if none of the above work for you.