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

Resolved work object still have assignments in workbasket



Due to a bad data manipulation several WorkObjects have been resolved even when assignments remain open . How can these be cleaned up?

Error Messages

No error message presented but when reviewing the broken WorkObjects, the users can clearly see the remaining assignments.

Steps to Reproduce

Following is the deployment scenario:
  1. Create a WorkObject.
  2. Create two assignments for the above created WorkObject.
  3. Now force the status of the WorkObject to be “Resolved-Completed”.
  4. The WorkObject will be closed but both assignments are still open.

Root Cause

The root cause of the issue is due to an incorrect data manipulation within the environment. The broken cases were updated manually to modify their status and this generates inconsistencies


An Activity has been created to open the broken cases and set the “Resolved” ticket. Setting the ticket has automatically resumed the remaining assignments. In the Activity the following methods have been used:
  • Obj-Open-By-Handle: To open the broken case
  • Obj-Set-Ticket: To set the “resolved” ticket
  • Obj-Save: To save the previous changes
  • Commit: To commit the operation
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