Scenario: 2 Recipients, 2 Approvals where Task step is part of a multi-step containing 2 server events

To illustrate what happens in this scenario from an administrative perspective, you open the Task List in Management. Here you're able to see how the task status changes as the recipients open and action the task. This is also a convenient way to track, test, and confirm the behavior of how you configured the scenario.For more information on how to access Management see Accessing Sites.

The workflow starts and sends the Send Email - Task Assigned email to the Administrator. An email is sent for each recipient, which means the first email event executes the same number of times that there are users assigned a task. This email confirms that tasks were assigned to Codi and Bob.

The workflow then sends a task notification to all recipients. Nobody has opened the task and it is available to both to action. The Status for all tasks is Available.

Codi opens the task and takes one of the two available responses for the task. Notice the status for Codi is Open. The task is still available for the Bob.

Codi actions and approves the task and her name no longer shows on the Task List. Notice that Bob's task is still open.

As soon as Codi approves the task the Send Email - Task Completed email gets sent to the Administrator. This email confirms that she completed the task.

Bob opens the task and takes the second and final available response. Notice the status for Bob is Open.

As soon as Bob approves the task the Send Email - Task Completed email gets sent to the Administrator. This email confirms that he completed the task.

This completes the requirement for two approved responses and the task completes.

Select the Reports tab and scroll down to locate the All Instances section of the Process Overview report. Select the link for the task.

On the Process Instance Detail report, scroll down to locate the Activities section. Click the Task link.

In the Participants section of the Activities Instance Detail report, notice that Codi and Bob approved the task.

Configure the Task step for this scenario by matching your task with the examples:

Task Tab	Configuration Details
Task	On the Task tab add two actions: Approve and Reject. For additional information, see Task tab.
Recipients	On the Recipients tab add Codiand Bob as recipients. For additional information, see Recipient tab.
Task Result Rule	On the Result/Voting tab configure the following: Select Consensus for the Task Result Rule Expand Options and type 2 as the available responses   For additional configuration information, see Task Result Rule tab. For more information and scenario on Consensus rule, see Task Result Rule - Consensus Scenario.
Customized email subject	On the Send Email step, add the Task Participant Name to customize the Subject. For additional configuration information, see Context Browser and Workflow.

When working with this type of scenario keep in mind the following considerations:

• When you select a task from your task list in Workspace (Desktop), the status for the task changes from Available to Open. You take ownership of the task and it stays open in your name until you release, share, redirect, or action it. For more information see the Redirect and Release scenarios.
• If you don't action an open a task, remember to release it so it is available for other recipients. For more information on how to release a task, see Release in the Task Action Bar section of the My Tasks topic.
• All recipients can redirect the task. Two tasks can be completed because two responses are required to complete the task.
• When you redirect the task you no longer see it on your task list. The task shows on the other person's task list and they can action it..
• When you share a task, the task stays on your task list but also shows on the other person's task list. The first person to open the task can take action on it and the task is removed from the other person's task list.
• When you sleep a task, it pauses or suspends the task for a period of time. The task does not show on your task list until the time specified elapses. You have no option to release this task until the time has elapsed. The task is still open in your name as you are the owner of it.
• Additional responses may cause multi-step events to execute events multiple times that occur after the task event. This means when you combine a Task step and server events in a Multi-Step, the server event (in this scenario the Send Email step) executes based on the number of recipients of the task. Two emails are sent to the Administrator, one for Codi and one for Bob.

• At runtime, the steps within the multi-step executes from top to bottom, one after the other. If you have a combination of a User Task step and server events, the server events execute in serial for each recipient in the User Task step.

• If you assign tasks to groups and select to not resolve groups to individuals, the recipients within the group are not seen as individuals, which means the group is seen as one recipient. In this case, only one email would be sent for each Send Email event, and the task would complete when one person from the group actioned the task. To have two emails sent, you could use two groups as recipients, or a group and an individual. Note the impact on your recipient responses and any response rules you have specified in your task. For more scenarios on resolving or not resolving groups, see Scenario: 1 Recipient, 1 Group, 2 Responses, 2 Approved Actions - Do not resolve group to individuals and Scenario: 1 Recipient, 1 Group, 2 Responses, 2 Approved Actions - Resolve group to individuals.