Scenario: 6 Recipients, 5 Responses, and using a variable in the voting rule to wait for 2 Approvals

In this scenario, a task is sent to Codi and the Finance group that has five people, namely Bob, Anthony, Blake, Mike, and Rick. They can either Approve or Reject the task, which completes when two of the recipients respond with Approve or when someone rejects the task.

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

If you want to know how to configure the rest of the workflow for this scenario, skip ahead to How to configure related steps in the workflow.

Task list behavior for Recipients

The workflow start after you complete and save the form.

In your workflow you configure the voting rule to set the number of Approvals required for a task based on a dollar amount for this Travel Expense Claim scenario. The Total Amount variable calculates values from a SmartObject and is the sum of Accommodation, Transportation and Miscellaneous expenses. Amounts less than or equal to 3000 require one approval. If it's more than 3000, two approvals are required.

In this scenario, the amount is 3567.25 which means the task needs to be approved by two 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. Because you checked the Resolve groups to individuals box, the task is sent to each person in the Finance group.

Codi opens the task and takes ownership of it. This means that Codi takes one of the two available responses for the task. The task is still available for any of the remaining five recipients and shows in their inbox.

Bob, who is a member of Finance, opens the task and takes ownership of it. He takes the second and final available response. In this scenario, you specified that only two responses are needed which means that the task is no longer available for the remaining recipients (even though Codi and Bob have not yet actioned it).

In this scenario, you configured the custom voting rule to wait for two approved actions or one reject action. Codi approves the task and this is the first Approve response. Bob then approves the task and this is the second Approve response. The workflow continues because two people chose the Approve action.

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