Updating FlowProblems / RetryProblemFlow for fixing mis-assignments
Here's a common process pattern of manual assignment, where in a flow action the user sets property X to a desired user, who will be the assignee for the next assignment.
This is easy to screw up, unfortunately -- if you use an AutoComplete, and don't select a listed name (see
), and submit... we'd like the next assignment, ToWorklist, to simply fail and go back to the prior assignment. But ToWorklist doesn't even validate this, so there's a failure later, and the FlowProblems flow is spunoff.This functionality I remember from the v4 days (or earlier) and hasn't been updated much. Are there any thoughts to update this -- to enable the workflow engine to intelligently rollback assignments that can't be assigned?
Within the action RetryProblemFlow, there's little we could do; this only works if, say, the operator ID were valid, and it weren't created yet.
Here's a common process pattern of manual assignment, where in a flow action the user sets property X to a desired user, who will be the assignee for the next assignment.
This is easy to screw up, unfortunately -- if you use an AutoComplete, and don't select a listed name (see
), and submit... we'd like the next assignment, ToWorklist, to simply fail and go back to the prior assignment. But ToWorklist doesn't even validate this, so there's a failure later, and the FlowProblems flow is spunoff.This functionality I remember from the v4 days (or earlier) and hasn't been updated much. Are there any thoughts to update this -- to enable the workflow engine to intelligently rollback assignments that can't be assigned?
Within the action RetryProblemFlow, there's little we could do; this only works if, say, the operator ID were valid, and it weren't created yet.
(RetryProblemFlow and associated ActionDisplayError are final). The only approach I can think of is to add a local action to FlowProblems to update each assignee property for that work class. This should be automatically generated, ideally -- assuming that, in each work class, there's a list rule of properties that impact routing.
Otherwise, we just have an admin go in, update the Clipboard Page, and then run the RetryProblemFlow.
Is there a better way?
***Updated by moderator: Marissa to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.