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

Cancel work after committing work triggers 'pyWorkPage' error

SA-14286

Summary



Commit a work object and, while it is processing, Cancel the work.
Get the error message.
The
 remaining operations performed on the work object do not work.


Error Messages



ERROR: posted transaction id '9ddc078ebbe06382b15f29a829f61190' for frame 'pyWorkPage' DOES NOT match record '32735efd597725ee878525c07f6c45d1'.


Steps to Reproduce



1. Configure a button that calls an activity to commit the work object. 
2. Configure another button to cancel the work object. 
3. Run the work object. 
4. Click the first button to commit the work object changes.
5. Click the second button to cancel the work object.


Root Cause



An issue in the custom application code or rules 
pyWorkPage using the Commit method was used instead of Obj-Save with write-now parameter enable.

Resolution



Perform this local-change:
In the application design, replace pyWorkPage using the Commit method with Obj-Save with the Write-Now parameter enabled.

 

Suggest Edit

Published September 23, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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