I would like it to be that we not only have interrupt timer events to add to a task, but also the ability to point an arrow from another task, so if we need to, we can have a step in forms where three people might be able to approve a document, and once 1 person approves the document, we no longer need anyone else, so the forms process is able to continue. This would allow us to add a lot of sequencing capabilities.
Question
Question
Feature Request: Interrupt activity based on incoming arrow being satisfied.
Replies
Hi there,
Can you provide more business context for your use case? It sounds like a user task with three participants will meet your need. Once one of the participant finishes the task, it will go to the next step.
Well, we have a business process that requires unique approvals by 3 individuals from a group. This was one of the thoughts that came up in our brainstorming that seemed to be the simplest to implement and have widespread usage for a multitude of clients.
Hi there,
So all of these 3 need to approve? and you want process ended if one of them reject?
well, we just want it to be where, we assign 10 people, AKA everyone in a particular group, and the first to approve or reject causes no one else to be the first person. At this point, it will evaluate if it was an approval or rejection, and if its an approval, route the task to the same users, minus that first approver, now with the first approvers signature on the page or a field indicating their notes. This users are instructed to be the second approver or to reject the form.
This should be able to be repeated as many times as needed.
can you tell me more about the user story? what kind of business process is this? (eg. HR process) what's the relation of the people in the group? (eg. is there a person/role weight heavier than another?) how many rounds of approval needed?