Voting Sub-Process configuration
Access the workflow configuration via 
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.
Applies to
This workflow applies to assets.
Configuration Variables
You can edit the configuration variables directly from the workflow definition page by clicking 
in the upper-right corner of the variables table.
| Variable | Description | Default value |
|---|---|---|
| names | Email Template Names | resultTemplate,reminderTemplate |
| defaults | Defaults | result,reminder |
| voteDueDate | The due date expressed in duration for task 'vote'. | B1M |
| voteTaskNotificationEnabled | Send notification emails for task 'vote'. | true |
Start label
The start label is the name of the workflow when it is visible as a button on a resource page or in the drop-down list when you add it as a button on a dashboard. You can find the Start Label section in the upper-right corner of the workflow definition page.
Default value: Vote
Click Edit to edit the label.
Start event
A start event is an event that triggers the workflow, for example starting the workflow when an asset is created.
There is no packaged default value.
Roles
The roles define the permissions to manage the workflow. For example, if a certain tasks must be urgently executed but the responsible person is on sick leave, a user with the defined role can reassign that task to somebody else.
You do not have to define any roles to start the workflow for this sub-process.
| Action | Roles |
|---|---|
|
Start workflow The button with the start label is available to users with these roles. |
There is no packaged default value. |
|
Stop workflow The option to cancel the workflow is available to users with these roles. |
|
|
Reassign tasks The option to reassign the task is available to users with these roles. |
|
Other
The settings in this section define global restrictions that apply to the workflow such as:
- Accessibility to guest or logged in users.
- Checking that the roles required by the workflow are not empty.
- Preventing the same worflow or other workflows from running on the same resource.
- Making the workflow available to be added to a dashboard.
| Setting | Enabled |
|---|---|
| Any guest user can start the workflow. | No |
| Any signed in user can start the workflow. | No |
| Perform candidate user check on workflow start. | Yes |
| This workflow can only run once at the same time on a specific resource. | Yes |
| Lock resource. | No |
| Show in global create. | No |