Workflow Activities

The Workflow supports a set of activities of various types to configure a process that fits your needs.

Find more about the functionality in the Workflow Editor.

Available activities:

• Run Script activity
• Join activity
• Set Values activity
• Record Generator activity
• Create Event activity
• Wait Condition activity
• If activity
• Switch activity
• User-approval activity
• Subflow activity
• Timer activity

Activity states

The activity state tells the workflow engine what to do with the activity. The states listed below are standard for all the types of activities implemented in SimpleOne.

Navigate to Workflow → Workflow Executing Activity to see the states of activities in published workflows.

Activities States

Basic activities

Utilities

The activities included in this category execute scripts, change and update records.

Run Script activity

The Run Script activity executes the defined script.

Activity fields

Join activity

The Join activity combines several activity exit transitions, so that they turn into one transition. This activity is useful for synchronizing several activities, so that the next activity does not start until the previous ones are finished.

In the example below, the Join activity waits for the results of processing of the If, Subflow, and Wait activities. If all three transitions from these activities lead to the Join activity, the Complete exit that leads to another activity named Insert is taken. If one of the activities bypasses the Join activity (in this case, it is the No exit of the If activity), then the Incomplete exit is taken.

How to use the Join activity

1. From the left side menu, open the Utilities tab and drag the Join activity onto the canvas.
2. Connect the exits of the activities you need to join with the Join activity.
3. Create transitions from the Join activity exits (Complete and Incomplete) to the next activities.

Activity fields

Activity exits

Set Values activity

The Set Values activity sets specific values to the current record. These values determine the activity behavior when the workflow freezes or ends.

Activity fields

Record Generator activity

The Record Generator activity creates records in any table extending from the Task table.

Activity fields

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

Create Event activity

The Create Event activity puts an event from the Event Register (sys_event_register) table in a queue. Later, this event can execute specific scripts or send notifications. When the Create Event action runs, a new event record is created in the Event (sys_event) table.

See the System Events article to learn more.

Activity fields

Conditions

The activities included in this category set conditions to continue the processing and define further transition of the workflow. The selected transition depends on the conditions set and the activity outcome.

Wait Condition activity

The Wait Condition activity pauses the workflow until the defined conditions are met. The activity checks if the record meets the conditions after every record update.

Activity fields

const isUserManager =
  ss.hasRole('process_manager'); // true or false
return isUserManager;

If activity

This activity checks a condition to determine if a Yes or No transition should be taken.

Activity fields

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

Switch activity

The Switch activity manages transitions by checking the field values against the defined case values (one or more). This activity works like the switch statement.

The activity checks against conditions specified in the Column field or in manually defined exits and, based on the outcome, selects the next transition.

Activity fields

To create additional exits, perform the following steps:

1. Right-click the Switch activity and select Add exit.
2. Double-click the exit to open the exit form fields.
3. Fill in the fields.
4. Click Save.
5. Repeat to add more exits if needed.

Activity exit fields

Approvals

With the User-approval activity, configure the approval processing: creating approvals, setting approval rules and conditions.

User-approval activity

The activity evaluates the result depending on the following factors:

• the decision made by the approvers.
• the conditions specified in the Approved When or Approval Conditions and Reject Conditions fields.
• (optional) the conditions specified in scripts.

The activity can be completed with one of two results: Approved or Rejected.

Activity fields

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');
  }
}

(() => {
  let isFirstGroupApprove = false;
  let isSecondGroupApprove = false;

  const docID = ss.getDocIdByIds(current.sys_db_table_id, current.sys_id);

  const rejectedApp = new SimpleRecord('sys_approval');
  rejectedApp.addQuery('item', docID);
  rejectedApp.addQuery('state', 'rejected');
  rejectedApp.setLimit(1);
  rejectedApp.selectAttributes(['sys_id']);
  rejectedApp.query();
  if (rejectedApp.next()) {  // One of tickets rejected
    answer = 'rejected';
  }

  const approvedApp = new SimpleRecord('sys_approval');
  approvedApp.addQuery('item', docID);
  approvedApp.addQuery('state', 'approved');
  approvedApp.selectAttributes(['approver_id']);
  approvedApp.query();

  const uc = new SimpleUserCriteria();
  while (approvedApp.next()) {
    let approver = approvedApp.getValue('approver_id');

    if (!isFirstGroupApprove) {
      isFirstGroupApprove = uc.userAcceptanceByCriteria(approver, '167416106197358457'); // First Group Member
    }
    if (!isSecondGroupApprove) {
      isSecondGroupApprove = uc.userAcceptanceByCriteria(approver, '167416108994075219'); // Second Group Member
    }
  }

  if (isFirstGroupApprove && isSecondGroupApprove) {
    return 'approved';
  } else {
    return 'waiting';
  }
}
)()

Subflows

Use the Subflow activity for complex workflows that include other processes.

Subflow activity

The Subflow activity performs an existing workflow as part of the current workflow.

Activity fields

When a Subflow block starts, a workflow context is created for the current record. Until the context is finished, another Subflow block with the same workflow cannot start, because only one workflow context  can exist for the current record at a time.

For example, the Subflow block related to the "Request 2nd phase" workflow is configured in the main workflow. After the main workflow starts, the "Request 2nd phase" subflow starts too. The execution context of the subflow is paused. If the main workflow attempts to run the "Request 2nd phase" subflow again, the subflow is created in a canceled state.

Timers

The Timer activity pauses the workflow. This activity is useful when a process requires waiting for a certain period.

Timer activity

The Timer activity defines a period of time when the current workflow does not run. The logic is the following:

• If the workflow context is not finished and the block following the Timer block has the Finished state – the block processing is restarted.
• If the workflow context is not finished and the block following the Timer block has the Waiting state – the block processing is not restarted.
• If the workflow context at the moment of running of the Timer block is finished – processing of the block following the Timer block is not started.

Activity fields