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

Assignment saved to DB for temporary work object



A custom configuration has been created where a WorkObject is created as “temporary”. This process is handled by a flow creating an assignment and finally resolving the WorkObject.
Unfortunately, at the end of explained process, an assignment has been generated and is presented on the WorkList without any ID associated with it. 
If a user is trying to open the invalid assignment an error is generated

Error Messages

 A new page cannot be locked; it must be saved first.

Steps to Reproduce

  1. Create a temporary WorkObject
  2. Create an assignment for previous created WorkObject
  3. Finish the assignment and resolve the case
  4. An assignment is still remaining on WorkList

Root Cause

A custom Activity has been identified. The activity is using an “Obj-Save” method on the “newAssignPage” and this is generating an unexpected “pzInsKey” for a temporary WorkObject.


A local-change has been implemented and the “Obj-Save” method removed from the custom activity.

Published June 12, 2015 - 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