In Pega, I had a requirement where users should only be allowed to move a case back to a previous stage and not jump forward to future stages using the Change Stage option.
To achieve this, I have a plan to be implemented like this:
• UI-level filtering to display only previous stages
• Server-side validation to prevent forward stage transitions
• Conditional logic using When rules and stage sequence checks
This approach helped maintain process integrity while still allowing controlled backward navigation in the case life cycle.
Has anyone implemented a similar requirement differently or found a more optimized OOTB approach for restricting stage transitions in Pega?
@Debanjan_Seth I would target a certain stage specifically instead of providing a dropdown to choose a stage. The solution approach in your post feels overengineered.
Also - I would not go back to a previous stage. As a concept, that stage is completed. If you need to run that process again, I would instead go to an alternate stage to “step out of the happy flow” so to speak. And then return to whatever main stage the user was in before. For example - my main analysis stage is called “Analysis”. In the “Review” stage, the case is rejected. Instead of going back to “Analysis”, I would send the case to “Update analysis” alternate stage. And then send user back to “Review” stage, or possibly a “Re-review” alternate stage". That way you avoid the classic problem of “Hmm have I performed this stage before” type of validations you likely need to add.