Vote-based routing
In many cases, a single task can require action by a number of users collectively. These users can be identified explicitly or implicitly by using workflow groups.
It is vital in such cases that group actions be carried out in parallel rather than in sequence to minimize processing time. If the response of each user is to have an effect on the flow, it is necessary to be able to evaluate the responses as a whole to derive a consensus.
- All responses are of a specific value (example: all users select Approve).
- Any of the responses are of a certain value (example: any one user selects Reject).
- None of the responses are of a certain value (example: no users select Reject).
- The count of responses of a certain value (example: more than one user selects Reject).
Vote-based routing criteria can also be combined with more conventional data-based decision criteria (for example, the document type is Press Release and all users selected Approve). Users carrying out parallel tasks can also be made aware of the responses of other users by ensuring that the task they are carrying out has the View Status flag set in Process Designer. This capability allows for collective decision-making and ensures that the appropriate level of control over the process is always maintained.