This activity creates user approval(s) when executed, one or more, depending on the parameters specified.

The result value is the final approval disposition that depends on the actions taken by the approvers and the approval conditions specified in the When approved and When rejected 

The activity can be completed with one of two results:

Input variables 

NameDescription
NameCustomized activity name.
DescriptionBrief activity description. It is displayed on the activity block on the canvas if provided.
TableSelect a table to be processed by this activity.
Run Conditions

Specify conditions that must be met for generating approvals; whenever they are not met, then the activity is skipped.

Approval type

Specify the approval type (here you can define conditions of the block exit, i.e. activity completing). Available options:

  • Automatically - specify the conditions of the activity completing in the When approved field manipulating with approval tickets;
  • Manual - specify the conditions of the activity completing in the Conditions approved and Conditions approved fields manipulating with the object fields and their values.
Non-mandatory participantsSelect this checkbox to authorize the participants whose approvals are not mandatory to vote.
Mandatory participants tab
EmployeesSelect a responsible person or persons from the dictionary; these ones are recipients for the approvals.
GroupsSpecify a group or groups whose members will be the approvers.
RolesSpecify a role or roles whose owners will be the approvers.
AdvancedSelect this checkbox to specify a script to evaluate.
Script

If the Advanced checkbox is selected, then this script is called to determine if any additional approvals to be created.

The script needs to set the variable answer to a comma-separated list of user ids and group ids or an array of user and group ids to add as approvers.

For example:

answer = [];
       answer.push('id1');
       answer.push('id2');


When approved

This field is displayed when the Approval Type is chosen to "Automatically".

In this field, you can define the approval logic. Available choice options:

  • Anyone to approve - any user can approve; the first received approval causes the activity to complete with the result of Approved;
  • Everyone to approve - all the users must approve; otherwise, the activity will not proceed further;
  • The first response from anyone - when selected this option, the first response from any user will complete the activity;
  • Most answers - when selected this option, the activity will be completed with the Approved result if there were received more approvals than rejects;
  • Conditions based on script - Each time a user approves or rejects, the Script is called to determine if the activity should complete.
Conditions approved

This field is displayed when the Approval Type is chosen to "manual".

Specify the conditions to meet before the activity will complete with the result of Rejected. If you have specified more that one condition, then they will proceed downhill.

Non-mandatory participants tab. This tab appears when you select the Non-Mandatory Participants checkbox
Non-Mandatory: EmployeesSpecify the employees who are participants of the approval process but their approval is not mandatory.

Non-Mandatory: Groups

Specify the groups whose members are participants of the approval process but their approval is not mandatory.

Non-Mandatory: Roles

Specify the roles whose owners are participants of the approval process but their approval is not mandatory.

Non-Mandatory: Advanced

Select this checkbox to specify a script to evaluate.
Script

If the Advanced checkbox is selected, then this script is called to determine if any additional approvals to be created.

The script needs to set the variable answer to a comma-separated list of user ids and group ids or an array of user and group ids to add as approvers.

For example:

answer = [];
       answer.push('id1');
       answer.push('id2');


Consider Non-Mandatory Participants

When selected, non-mandatory participants are able to vote in approval tickets.


Unlike mandatory participants, approval tickets for non-mandatory participants do not contain the Approve action but only Reject.  So, participants of this kind can either tacitly approve the request or reject it.