Workflow Steps
Workflow Steps
Workflow steps are divided between:
- Workflow step
- Workflow Step System
The key difference between these two is – Workflow steps are used to create tasks for System users (workflow performers) while Workflow Step system is used for automated actions. Every workflow step may have one or more users designated to act on it.
Workflow Step Parameters
Voting Policy
Voting policy is a parameter in Workflow steps which sets what amount of workflow performers are required to take action on it (finish the task / Approve it / Reject it) before any further automated actions are made, before the document Process moves to another step.
Voting policy parameters:
-
Requires one approval. The task is rejected on the first rejection
- Previously named „Requires all". Workflow steps with this parameter only requires one Performer to take action. I.e.: If 3 Users received a task – only 1 of them Marking it as complete (for non-approval tasks) or Approving/Declining (for Approval tasks) is enough.
- Previously named „Requires all". Workflow steps with this parameter only requires one Performer to take action. I.e.: If 3 Users received a task – only 1 of them Marking it as complete (for non-approval tasks) or Approving/Declining (for Approval tasks) is enough.
-
Requires all approvals
- Previously named „Requires all". Workflow steps with this parameter requires all Performers to take action. I.e.: If 3 Users received a task – all 3 of them have to Mark it as complete (for non-approval tasks) or Approve/Decline (for Approval tasks) before the task is considered finished or declined.
-
Requires one approval. The task is rejected only if all performers reject it.
- Workflow steps with this parameter only requires one Performer's action to move forward, but all performers to Reject it. I.e.: If 3 Users received a task – 1 of them has to Mark it as complete (for non-approval tasks) or Approve (for Approval tasks) before the task is considered finished or declined. All of them have to Decline to Reject the Approval.
Delegation / Personal Task

Personal task is a boolean type Workflow Step parameter which regulates if a task is allowed to be transferred (aka delegated) to another system user. Delegation action is made by pressing the button on a received task named „Forward“.
If the parameter is marked – such action is not allowed and the button is not visible for the user.
Delegation properties:

„Forward to person“ – here you choose a person to delegate the task to. „Note for the performer“ – a free text area to write a comment to the person receiving this task. Note is optional. Delegation parameter:
- Delegate task ('do it instead of me') – the task will be sent to the person chosen in „Forward to person". You will no longer have the task.
- Delegate on behalf of all ('do on behalf of all assigned participants') – Only available when Voting Policy is Requires one approval. The task is rejected only if all performers reject it. – the task will be sent to the person chosen in „Forward to person". You and all other people added to the task will no longer have the task.
- Forward for additional approval - – the task will be sent to the person chosen in „Forward to person". You and all other people will still have this task in our system task list.