Workflow activities

This exit is taken when all joined activities have finished running, but at least one of them has not proceeded to this activity, that is, another path was taken bypassing the Join activity.

Example:

In this case, the If activity bypassed the Join activity; therefore, the Incomplete exit was taken.

Select the field whose value you want to change when the workflow freezes or ends, and define the new value.

Click the leftmost field to open the drop-down list of available fields. Click the rightmost field to open the drop-down list or enter the value (depending on the type of the selected field).

Select the task type. You can make a selection from the corresponding task table. Click the magnifier icon  to see the list, or start typing the table name in the field to select from autosuggest.

Specify an existing template related to the selected task table.

Specify an existing template related to the selected task table.

Specify conditions for the created task. The process will not proceed to the next activity until the task meets all conditions.

Set values for the task in this script. Use the variable 'new_task' when setting additional values. This field is displayed when the Advanced checkbox is selected.

For example:

new_task.parent_id = current.sys_id;
new_task.caller = current.getValue('caller');

A condition to meet in order to proceed with the Yes transition. 

This field is displayed when the Advanced checkbox is selected. If the script is executed, the result of the script will be added with the AND operator to the results of the Condition specified. To proceed with the Yes transition, the script should return the true value.

const uc = new SimpleUserCriteria();
const isUserLocal =
  uc.userAcceptanceByCriteria(ss.getUserID(), '165470191717512124'); // true or false
return isUserLocal; 

Type 

Specify a column containing options for the condition. These options will become exits of the activity. Click the magnifier icon  to see the list, or start typing the column name in the field to select from autosuggest.

In the example below, the Switch activity takes options from the Type field.

The option name. If the Type field is equal to Field, the name is taken from the Column. If the Type field is equal to Custom, specify the name you like.

This field appears when the Advanced checkbox is selected. If specified, the workflow is paused at this activity until this script returns true.

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.

The published workflow to be performed by the activity. Click the magnifier icon  to see the list, or start typing the workflow name in the field to select from autosuggest.

Specify the duration of time to wait in days, hours, minutes and seconds to wait before proceeding to the next activity.

Specify the script implementing the duration calculation logic. Here, you can use the SimpleOne API methods.

Select a timezone from the list. Click the magnifier icon  to see the list, or start typing the schedule name in the field to select from autosuggest.

Select a schedule from the list. Click the magnifier icon  to see the list, or start typing the schedule name in the field to select from autosuggest.