Scenario: 5 Recipients, 5 Responses using a rework action when someone rejects the task

In this scenario, a task is sent to five recipients, namely Codi, Bob, Dennis, Holly, and Erica. They can either Approve or Reject the task, which completes when five recipients respond with Approve. The rework path is followed if one of the recipients responds with Reject. This is sometimes referred to as a Veto scenario because one person can cause the workflow to stop at this task until full agreement is reached. This means that the task is resent to the same recipients until all five respond with Approve.

If you want to know how to configure the task step for this scenario, skip ahead to How to configure the Task step.

Task list behavior for Recipients

The workflow starts and sends a task to all recipients. The task shows in the My Task section in K2 Workspace (Desktop) for each of them because, at this stage, nobody has opened the task and it is available for everyone to open. Codi opens the task and takes ownership of it. This means that Codi takes one of the five available responses for the task. The task is still available for all of the remaining four recipients and shows in their inbox.

Bob, Dennis and Holly open the task and take ownership of it. They take the second, third, and fourth tasks of the available responses. In this scenario, you specified that five responses are needed which means the task is still available for the remaining recipient and shows in her inbox.

Codi, Bob and Dennis approve the task. These are the first, second and third Approve responses. In this scenario, you configured the custom voting rule to wait for five approved actions which means the task stays available for the remaining recipients.

Holly rejects the task. This is the fourth response as well as the first Reject response. In this scenario, you configured the custom voting rule to follow the rejected (rework) path. The workflow continues because one person chose the Reject action which follows the rework path and sends the task to all the recipients again. The task is available for everyone to open.

The animation below illustrates the path from when the task is assigned to the recipients to when it completes.