Task Results Rule Scenarios - Overview
This topic provides some common result rule scenarios, including standard and custom rules.
When using the custom Voting Rule, you can make your workflow go into an infinite wait-state due to too many responses required for the number of people assigned the task, and other misconfiguration. Make sure to inspect group membership and the number of responses you require, and make sure there are enough people to reach the amount of responses desired.
The table below contains commonly used results rule scenarios:
| Scenario | Description |
|---|---|
| Task Results Rule: First Response |
Only one person needs to action the task. The action taken by the first person is used to determine the path that the workflow follows. For example, as soon as the first recipient submits the Approve action, the workflow goes down the Approved path. The workflow does not wait for other recipients to action the task, and their tasks are removed from their worklists. |
| Task Results Rule: Consensus |
Consensus is required among the task recipients. In other words, all (or a subset of) the task recipients must choose the same action for consensus to be reached. For example, all recipients must approve the request before the workflow follows the Approved path. The workflow waits for all task recipients to action the task, and only follows the Approved path if all recipients submit the Approve action. |
| Task Results Rule: Custom Voting Rule |
A voting-style result is required. In other words, you want a certain number of people to select the same action. For example, for the workflow to follow the Approved path, at least two recipients must approve the task and none should reject the task. For the workflow to follow the Rejected path, more than one recipient must reject the task. |
| Task Results Rule: Custom Voting Rule with Task step Result |
Creating a voting rule on a task, and in the rule make decisions based on actions taken by recipients on other tasks within the same workflow. For example, for the workflow to go down the Approved path, the result of another task must be Passed (instead of Failed). |