User-approval activity

Select responsible users. They will receive the approvals and make their decisions. Click the magnifier icon  to select from the list or start typing the user name to select from autosuggest.

Select responsible groups. Users included in this group will receive the approvals and make their decisions. Click the magnifier icon  to select from the list or start typing the group name to select from autosuggest.

Select roles whose owners will receive the approvals and make their decisions. Click the magnifier icon  to select from the list or start typing the role name to select from autosuggest.

Script 

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

The script is intended to set the answer variable to a comma-separated list of user IDs to add as approvers.

The code example below implements logic as described below:

1. Checks groups of the current caller.
2. Checks the value of the Responsible attribute of these groups.
3. If the group responsible was found, then his user ID is added to the answer array.

const caller = current.getValue('caller');
const callerGroup = new SimpleRecord('sys_user_group');
callerGroup.addQuery('user_id', сaller);
callerGroup.selectAttributes('group_id');
callerGroup.query();
while (callerGroup.next()) {
  if (callerGroups.group_id.getValue('responsible')) {
    answer = callerGroups.group_id.getValue('responsible');
  }
}

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

• Anyone to approve – the Approved exit will be taken if at least one responsible user approves the ticket.
• Everyone to approve – the Approved exit will be taken only if all responsible users approve the tickets; otherwise, the workflow will take the Rejected exit.
• First response from anyone – the exit to be taken depends on the first decision received: the first user who happens to make the decision defines the outcome.
• Most answers – the activity outcome depends on the number of approvals and rejections: if there are more approvals, then the Approved exit is taken and vice versa.
• Conditions based on script – the activity outcome depends on the Script that calculates the result every time it receives approval or rejection.

Specify the conditions to be met for the Approved exit. If there is more than one condition, they will be checked one after another.

Specify the conditions to be met for the Rejected exit. If there is more than one condition, they will be checked one after another.

Select responsible users from the Employee list. They will receive the approvals and make their decisions. Yet, their approval is not mandatory. Click the magnifier icon  to select from the list or start typing the user's name to select from autosuggest.

Select responsible groups. Users included in this group will receive the approvals and make their decisions. Yet, their approval is not mandatory. Click the magnifier icon  to select from the list or start typing the group name to select from autosuggest.

Select roles whose owners will receive the approvals and make their decisions. Yet, their approval is not mandatory. Click the magnifier icon  to select from the list or start typing the role name to select from autosuggest.

This script is called to determine if any additional approvals to be created.

The script is intended to set the answer variable to a comma-separated list of user IDs to add as approvers.

See an example and clarifications above.

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