Question
World Bank
US
Last activity: 17 Jul 2018 1:32 EDT
Change Stage to Current Stage
Why does pega not allow to change to current stage in Pega 7.1.7?
We have 4 steps under one stage and when I try to use change stage from Step 4 I expected the case to start from Step 1 of the stage. But it shows me an error that I cannot use change stage to jump to current stage.
When I tweak the code in pxchangestage it works. Any leads on why Pega restricted it and what is the best way to implement this approcah?
***Updated by moderator: Lochan to update Categories***
Accepted Solution
Pegasystems Inc.
US
Hi Deepthi,
Commenting fourth step by itself wouldn't be sufficient. You'll have to set remove all assignments to true as well.
-Ravi.
Pegasystems Inc.
US
Change stage(pxChangeStage) to current stage is not possible. There is a different utility for that(pxRestartStage)
Cognizant
US
Thank you Ravi for answering. Is this utility(pxRestartStage) available in 7.1.7? I cannot find it.
Also, small change to pxchangestage worked for me to restart the current stage. Any idea on why we should use a different utlity?
Regards,
Deepthi
Pegasystems Inc.
US
Hi Deepthi,
pxRestartStage is only given as part of pega 7.1.9.
What is the change that you are talking about? Did you remove the error message on 4rth step and see that it's working?
-Ravi.
Pegasystems Inc.
US
Hi Deepthi,
I have gone through the code. While restarting it is must that we delete the existing flows(clean up processes), so if you want you can save as the pxChangeStage to reflect the restart behavior (hardcode the cleanup process boolean and remove validations). Then this must work for you.
Hope this helps.
-Ravi.
Pegasystems Inc.
IN
Hi Ravi/Deepthi-
A customer can override only py or available rules. px/pz and final rules cannot be overridden by customers.
Pegasystems Inc.
US
Hi Rekha,
Apologies, I should have been more clear. I meant Deepthi to save as the rule under a different name to use it for restart stage as there is no OOTB utility for the same in Pega 7.1.7
-Ravi.
Pegasystems Inc.
IN
Can you not reconfigure your steps/stage to support the use case.? Is upgrading to 7.1.9 an option?
Overriding FA , you will miss out on ootb enhancement. Instead try using Alternate stage to go back to previous stage via utility change stage as an alternative.
World Bank
US
Hi,
Thank you all for your prompt responses.
But the system is already in production and we cannot change to alternate stages approach or the upgrade to 7.1.9.
Ravi,
Yes if I remove the page level messages on step 4 it worked for me. I would save the rule with diff name in my implementation class.
Can I go ahead with the change? I understand we might miss OOTB enhancement.
But in future we have plan to upgrade to 7.3 and we would check to redevelop at that time.
Regards,
Deepthi
Accepted Solution
Pegasystems Inc.
US
Hi Deepthi,
Commenting fourth step by itself wouldn't be sufficient. You'll have to set remove all assignments to true as well.
-Ravi.