3.48 Vote Outcome Dialog
Use to enter group voting details between two parallel participant types. The outcome for the final task is chosen based on the selected default outcome and consensus percentage.
Element | Description |
---|---|
Vote Outcome |
You can specify a voted-upon outcome that overrides the default outcome selected in the Default Outcome list. This outcome takes effect if the required percentage is reached. Outcomes are evaluated in the order listed in the table. |
Voted Outcomes table |
Click the Add icon to add additional columns. |
Voted Outcomes |
Select an outcome for the task (for example, Any, ACCEPT, REJECT, or any other outcome specified in the Outcomes dialog). The Any outcome enables you to determine the outcome dynamically at runtime. For example, if you select Any and set the outcome percentage to 60, then at runtime, whichever outcome reaches 60% becomes the final voted outcome. If 60% of assignees vote to reject the outcome, then it is rejected. |
Outcome Type |
Select a method for determining the outcome of the final task.
|
Value |
Specify a value based on your selection in the Outcome Type column.
|
Default Outcome |
Select the default outcome for this task to take effect if the consensus percentage value is not satisfied. This happens if there is a tie or if all participants do not respond before the task expires. The default outcomes that display are based upon your selections in the Outcomes dialog of the Human Task Editor. You can also select By Expression to use the XPath Expression Builder. |
Immediately trigger voted outcome when minimum percentage is met |
If selected, the outcome of the task can be computed early with the outcomes of the completed subtasks, enabling the pending subtasks to be withdrawn. For example, assume four users are assigned to act on a task, the default outcome is APPROVE, and the consensus percentage is set at 50. If the first two users approve the task, the third and fourth users do not need to act on the task, since the consensus percentage value has already been satisfied. This option is automatically selected. |
Wait until all votes are in before triggering outcome |
If selected, the workflow waits for all responses before an outcome is initiated. |
Share attachments and comments |
Select this checkbox if you want all group voters or workflow participants to share comments and attachments for this task. This option is typically used when users must collaborate, such as collectively producing a proposal or a design. This information typically displays in Oracle BPM Worklist. |
Related Topics
Creating Human Tasks in Developing SOA Applications with Oracle SOA Suite