I am working on implementing an Approve/Reject stage after the “Enrich Data for Due Diligence” step in my case lifecycle. I have run into an issue and would appreciate some guidance.
Current Behavior:
When the Approve Data task is rejected, it triggers `pxRestartStage` (configured in the flow of the Approve Data task).
This results in a new sub-task being created with the same name (e.g., “Enrich data for due diligence”) instead of reopening the previously completed task.
As seen in the screenshot below, multiple sub-tasks with the same name are being generated, which is not the desired behavior.
Is this Pega’s OOTB behavior where, when a task is already completed and we restart the stage using `pxRestartStage`, it creates a new sub-task with the same name instead of reopening the completed one??
This is generally expected behaviour when pxRestartStage is used after a task has already been completed. In Pega, restarting a stage does not “reopen” the exact completed assignment instance.. it re-enters the stage and creates a new assignment/sub-task for the stage steps that are configured to run again.
When a case re-enters a stage, Pega follows the stage flow again. If the step is configured to run on stage re-entry, it will be launched as a new assignment rather than restoring the old completed one. Pega’s stage re-entry model is designed to restart the process path, not to resurrect a finished work item
If the requirement is to reopen the exact previous assignment, that would need a different design approach because stage restart and assignment reopen are different behaviors in Pega
