Support Article
Assignments still remain even after transfer or process
SA-22546
Summary
Assignments with errors remain on user's worklist after a work object has been transferred or processed.
Error Messages
The flow this assignment corresponds to has been removed
The work object references a different assignment than the current one
Steps to Reproduce
Normal case processing.
Root Cause
An issue in the custom application code or rules where explicit commits were made to assignments and work objects during flow processing via the Obj-Save method's "Write Now" option.
Resolution
Perform the following local-change:
Remove any explicit commits to the work object or assignment and allow flow processing to handle them, to avoid the potential for assignments and work objects to get out of sync.
Published April 30, 2016 - 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.