Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

pyApprovalResult is not persisted between assignments



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

  1. Create Flow with two assignments.
  2. Configure the first assignment with flow action Work-.pyApproval.
  3. 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.


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:

Published March 9, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us