In Pega Constellation, the case status (pyStatusWork) is initially set to “Assigned-Review not started”.
The requirement is to update the status to “Assigned-Review in progress” when the user enters the Review Start Date and clicks on Save for Later, and to have this update reflected on the Case Summary view.
Currently, the status does not update upon clicking Save for Later. The updated status is only reflected after clicking GO (Submit) and re-opening the assignment.
It appears that Save for Later performs a partial save and does not trigger assignment processing or flow actions where the status update logic is configured.
Query:
Is this the expected behavior in Constellation? What is the recommended approach to update pyStatusWork on Save for Later so that the status is immediately reflected on the Case Summary view without requiring assignment submission?
Hi @DaminiC5 , In constellation we cannot change the behavior of buttons. The significance and use of Save For Later button is to save the data for now and user might come later and change it again or submit it. No assignment or anything action is triggered when you click on it.
So to answer your question. No, we cannot refresh pyStatusWork on Save for Later action. This is expected behavior of pega constellation build applications.
There is an extension point named “pyAssignmentSaveDefaults“ which can be extended for your requirement with specific conditions in your application ruleset based on the assignment you are currently working on and also the specific save action parameter.
Mind that, you should specifically run the UpdateStatus on the work case context using a parameter page name “workPage“ (Work-) declared in the parameters and pages & classes.
Also, you can’t save as the above activity in your specific case type work class as its not getting invoked. So you are forced to keep in Work-.
If you can do this change, then the work object status will be updated on the save for later button and case will refresh to show the updated status. No other custom needed.
Try to run the tracer and kindly do more research on this approach and if you have any other constraints or issues, please let us know.
Thanks @JayachandraSiddipeta for your response. I tried your approach but I am not able to find this activity in pega. Could you please help me on this.
In Constellation we will be not able to perform any button actions.
For your scenario, you could monitor the Review Start Date field by using Declarative Rule (On-Change/Trigger) and in the declarative rule logic you can call pega OOTB updateStatus activity and update the status explicitly.
