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

Unable to resume the flow using SetTicket



User has a scenario where in they open the work object and click Edit to modify the users in the repeating grid list.
After the values are modified and Save is performed, the flow is resumed to a point by using "SetTicket" in the post processing activity.

But during the flow resume through ticket, an error is thrown and the resume does not happen.

Error Messages

trying to calculate the handle of a class whose instances may not be written to the database: Assign-: code: SQLState: M

Steps to Reproduce

1. Create a case.
2. Add few users and save in workshop later user for processing.
3. After saving case. open the case and Edit the case.
4. Modify the user details in the grid and try the save the updates to resume the flow using a ticket.

Root Cause

The issue is because there is no newAssignPage present for that case, there are no value entries for properties in newAssignPage after clicking on "Edit".

The changes that are made to the list are all directly posted to the pagelists configured in the section/harness and when the user is trying to process the case, since there is no assignment handle present, it is expected to throw an exception in such scenario.


To achieve the functionality, it is suggested to modify the application logic to adapt when the user clicks on Edit, if the current user has to process the case, then it is mandatory that the user should have the handle of the assignment like other users(from the repeating grid list) who had entries in Assign-Worklist table.

Published March 26, 2018 - Updated October 8, 2020

Was this useful?

100% 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