I am curious if there is a way to allow a user to initiate a business process that will stop an instance of another current business process. For example, we have a business process running that starts after a form is submitted from LF Forms. The business process kicks off a complex approval route. If a user makes a mistake in a field selection and the document is routed to the next (wrong) department, we need a way for the the initial user to stop this process. I have set up a second business process which resets the necessary fields and then starts the initial business process again. This works great except that the initial instance still has a “waiting” status. So each user is getting multiple shortcuts in their workflow folders (one for the first instance and one for the second). I do not want the initiator to have to use the Workflow Designer to terminate the initial instance. Is there another way to accomplish this?
Question
Question
Business Process Question
asked on April 8, 2013
•
Show version history
0
0
Answer
APPROVED ANSWER
replied on April 10, 2013
•
Show version history
While there’s no easy way to have one workflow terminate another, you can accomplish something similar using routing decisions and an additional field available to the initiator. The idea is to have a branch that looks for an “oops” field and terminates the workflow if it’s set. In the workflow below, I’ve set up a wait condition that is looking for either the approval or the “oops” field. The routing decision, making a decision using the approval or the “oops” field, invokes the clean-up business process (and doesn’t wait for it to finish) if the “oops” field is set, and then terminates the current workflow.
0
0
Replies
You are not allowed to reply in this post.
You are not allowed to follow up in this post.