Question
Virtusa Consulting Services Pvt. Ltd.
US
Last activity: 11 Apr 2017 12:30 EDT
Jump to previous step inside a stage
Hi,
I have a process with 3 stages and the last stage has 3 steps in it. The process moves to Stage 3, starts step 1, navigates to step 2 from step 1 naturally. But, I have to go back to step 1 from step 2 inside Stage 3 on a condition. Can this be achieved?
Thanks in advance
***Updated by moderator: Lochan to add Categories***
Accepted Solution
Pegasystems Inc.
IN
>>> If I restart the stage, I guess it will remove step 2
- yes. does if the parameter CleanUpProcesses is set to true
>>> we need to manage not to create that assignment again when it enters in step 2 / skip step 2 entirely when we come out of step 1.
- yes - checking the pxFlowPage - we need to skip the assignment creation.
>>> it will not do anything in step 2 second time
- it will create another assignment _2/_3 likewise...
>>> what do you think will be the behaviour of the system, does that still keep the step 2 alive?
- No
>>> If I restart the stage, I guess it will remove step 2
- yes. does if the parameter CleanUpProcesses is set to true
>>> we need to manage not to create that assignment again when it enters in step 2 / skip step 2 entirely when we come out of step 1.
- yes - checking the pxFlowPage - we need to skip the assignment creation.
>>> it will not do anything in step 2 second time
- it will create another assignment _2/_3 likewise...
>>> what do you think will be the behaviour of the system, does that still keep the step 2 alive?
- No
-
my preference ... but not certain on the exact OOTB behavior.../ Pankaj Rawal please share your inputs, Thank you!
- the recent saved updates on assignment 2 should be presented to user in any scenario...
- any scenario...
-
CleanUpProcesses is set to true
-
step will be deleted...
- but the data persisted on this step should be presented to user on newly created assignment...
-
step will be deleted...
-
CleanUpProcesses is set to false
-
creation of new step should be skipped automatically if the step is existing/already visited ...
- the data entered (not saved) and any saved data should be presented for user...
-
again, if step 2 is a conditional output of step 1
-
in pxChangeStage use case
- step 2 and the data saved at step 2 should be deleted.
- step 2 and the data saved at step 2 should be deleted.
-
in pxChangeStage use case
-
creation of new step should be skipped automatically if the step is existing/already visited ...
-
CleanUpProcesses is set to true
- any scenario...
- the recent saved updates on assignment 2 should be presented to user in any scenario...
PEGA
IN
May be you can use the Change Stage smart shape and give the 3rd Stage as input.
If the process goes to the 3rd stage, that means it starts from first step only right. So it will fulfill your requirement.
Virtusa Consulting Services Pvt. Ltd.
US
I am sorry I missed to mention this in the problem. But, I have to keep step 2 alive as well when process goes to step 1. So, If I restart the stage, I guess it will remove step 2
Virtusa Consulting Services Pvt. Ltd.
US
I understand where you are going Phani. If that param is switched off, it will not clear the assignments and keep that step alive and then, we need to manage not to create that assignment again when it enters in step 2/ skip step 2 entirely when we come out of step 1. Either way, it will not do anything in step 2 second time. what do you think will be the behaviour of the system at that point, does that still keep the step 2 alive?
Accepted Solution
Pegasystems Inc.
IN
>>> If I restart the stage, I guess it will remove step 2
- yes. does if the parameter CleanUpProcesses is set to true
>>> we need to manage not to create that assignment again when it enters in step 2 / skip step 2 entirely when we come out of step 1.
- yes - checking the pxFlowPage - we need to skip the assignment creation.
>>> it will not do anything in step 2 second time
- it will create another assignment _2/_3 likewise...
>>> what do you think will be the behaviour of the system, does that still keep the step 2 alive?
- No
>>> If I restart the stage, I guess it will remove step 2
- yes. does if the parameter CleanUpProcesses is set to true
>>> we need to manage not to create that assignment again when it enters in step 2 / skip step 2 entirely when we come out of step 1.
- yes - checking the pxFlowPage - we need to skip the assignment creation.
>>> it will not do anything in step 2 second time
- it will create another assignment _2/_3 likewise...
>>> what do you think will be the behaviour of the system, does that still keep the step 2 alive?
- No
-
my preference ... but not certain on the exact OOTB behavior.../ Pankaj Rawal please share your inputs, Thank you!
- the recent saved updates on assignment 2 should be presented to user in any scenario...
- any scenario...
-
CleanUpProcesses is set to true
-
step will be deleted...
- but the data persisted on this step should be presented to user on newly created assignment...
-
step will be deleted...
-
CleanUpProcesses is set to false
-
creation of new step should be skipped automatically if the step is existing/already visited ...
- the data entered (not saved) and any saved data should be presented for user...
-
again, if step 2 is a conditional output of step 1
-
in pxChangeStage use case
- step 2 and the data saved at step 2 should be deleted.
- step 2 and the data saved at step 2 should be deleted.
-
in pxChangeStage use case
-
creation of new step should be skipped automatically if the step is existing/already visited ...
-
CleanUpProcesses is set to true
- any scenario...
- the recent saved updates on assignment 2 should be presented to user in any scenario...
Virtusa Consulting Services Pvt. Ltd.
US
I agree. So, here is what I have done
1) Process when enters STAGE 3, enters step 1
2) On certain input in step 1, goes into step 2
3) After step 2, I tried to call pxChangeStage and gave STAGE3 as param. This has failed as pega has a validation when process tries to jump to same stage which it is currently in (No idea why this was put in the first place !! ). So, had to copy to rule to my application and removed the validation. Called the new activity ChangeStage with param CleanUpProcess set to false.
4) This re-started the stage leaving the step 2 assignment and the step alive which gives the ability to click on the step link to open the assignment
5) After step 1 when it enters step 2 again, like you mentioned it is trying to create another pxFlow page with _1 as suffix. Now I have placed a logic to skip assignment as there is an existing assignment. So, it skips assignment and ends the process.
Output,
Step 2 assignment still exists but the step is not alive (I mean no link for it in the stage navigation panel). The reason is, when it enters step again it is creating new flow page, takes the page subscript and copies it onto the step list in the stage page. So, the link tries to look for pxFlow page with this subscript and if it finds the assignment key on it, it will show the link. As we don't have that pxFlow page anymore, the link is not showing up.
So, I had to tweak that control a bit to show the link of previous existing assignment.