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
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
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.
0% found this useful