Support Article
pyApprovalResult is not persisted between assignments
SA-45412
Summary
The 'pyApprovalResult' property is not being persisted. It gets reset when the next assignment is routed to a different user than the one who approved or rejected the previous assignment.
Error Messages
Not Applicable
Steps to Reproduce
- Create Flow with two assignments.
- Configure the first assignment with flow action Work-.pyApproval.
- Configure the second assignment with flow action to view the property 'pyApprovalResult' in read-only mode.
Root Cause
An issue in the custom application code or rules:
The 'pyApprovalResult' is a transient property and it is to be used in a fork shape to progress the flow based on its value. It is not supposed to be persisted in the database.
Resolution
Here’s the explanation for the reported behavior:
The 'pyApprovalResult' is a transient property that is not supposed to be persisted to the database.
Transient properties can have non-null values on the clipboard, but when a clipboard page containing transient properties is saved to the PegaRULES database, the values are removed from the Storage Stream column.
Similarly, when an instance containing a transient property is retrieved from the database and opened on the clipboard, the transient properties have no initial values on the clipboard:
Refer to the following link for details:
https://pdn.pega.com/sites/pdn.pega.com/files/help_v73/procomhelpmain.htm#definitions/t/transientproperty.htm
Published March 9, 2018 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.