Support Article
Assignment saved to DB for temporary work object
SA-9084
Summary
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
- Create a temporary WorkObject
- Create an assignment for previous created WorkObject
- Finish the assignment and resolve the case
- 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.
Resolution
A local-change has been implemented and the “Obj-Save” method removed from the custom activity.
Published June 12, 2015 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.