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

Code-Pega-PDF-AttachToWork activity fails



User encounters issue after Code-Pega-PDF-AttachToWork activity gets called and with the following user interaction an error on screen occurs and in the log files.

Error Messages

On screen: "This action is not allowed as it is outside the current transaction"
In PegaRULES log: "ERROR: posted transaction id 'dcd3c782a71b457b062c2772bac895cb' for frame 'pyWorkPage' DOES NOT match record 'b0218c0569fd66601ebe6094bc97623b'"

Steps to Reproduce

Perform UI action after Code-Pega-PDF-AttachToWork activity runs.

Root Cause

The root cause of this problem is a defect in customer application code/rules. Configuration in use is calling the AttachToWork activity with skipCommit parameter set to false, this activity is called from the preprocessing activity of the flowaction. 
However if skipCommit option set to true, the then the error goes away but the PDF does not get attached to workitem.


This issue is resolved through the following local-change:
Call the preprocessing activity as a utility shape prior to the flowaction and also use the skipCommit parameter set to true.

Suggest Edit

Published January 31, 2016 - 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