[bok-callout]For information about the design and implementation of the Approval Process workflow go to: Voting Sub-Process Design and Implementation[/bok-callout]
The Voting Sub-Process is an out-of-the-box sub-process that can be called by other workflows when a vote between or more users is needed. It is used within other out-of-the-box workflows such as:
- Approval Process
- Simple Approval
- Issue Management
It can also be used in new custom workflows. The result is a simple true or false that is provided to the parent workflow.
Which roles are involved?
To make the Voting Sub-Process reusable, it does not have specific role assignment. A list of users is provided to the sub-process. Each user will get a vote regardless of their role. They are referred to as Voters.
Who can start the workflow?
This sub-process will be automatically called within the parent workflow.
What status transformations happen in this workflow?
No status transformations happen within this sub-process
Each voting user is prompted with a new task to vote.
Starting the task will prompt the following form for the Voters to post their comments:
If a Voter does not start the task and vote within five business days (B5D; by default), the process will move on to a result without the vote. This ensures that the voting process will take no longer than five days. The amount of time can be configured in the Configuration Variables.
After the process is completed, an email notification of the result is sent to each Voter.
Settings > Workflows > Definitions > Voting Sub Process
Settings > Workflows > Definitions > Voting Sub Process > Description
This is a voting process used as sub process in a wide range of processes. It is very configurable and is not intended to be used standalone. If you want to configure how voting is handled in the application, this is the process to configure.
This Workflow Definition applies at the Asset level and for no specific asset types
Settings > Workflows > Definitions > Voting Sub Process > Applies To
Applies To: Asset
The Configuration Variables can be edited directly from the settings page.
Settings > Workflows > Definitions > Voting Sub Process > Variables
The start label is configured in the upper right corner of the page.This is the label that is shown to the users when they are allowed to start the workflow. The name can be changed by pressing the Edit button and filling in a new label.
Settings > Workflows > Definitions > Voting Sub Process > Start Label
Start Label: Vote
There are currently no start events for this Workflow Definition. This workflow is a sub-process and needs to be called within another workflow.
Settings > Workflows > Definitions > Voting Sub Process > Start Events
Start Events: None
There are currently no roles assigned. They do not need to be assigned for this sub-process.
Settings > Workflows > Definitions > Voting Sub Process > Roles
|Stop Workflow||Community Manager, Business Steward|
|Reassign Tasks||Community Manager, Business Steward|
There are currently no users assigned in this section either. They do not need to be assigned for this sub-process.
Settings > Workflows > Definitions > Voting Sub Process > Other
|Any guest user can start the workflow||No|
|Any signed in user can start the workflow||No|
|Demand exclusivity on resource||No|
|Perform candidate user check on workflow start||Yes|
|This workflow can only run once at the same time on a specific resource||Yes|
|Show in global create||No|
You have to login to comment.