Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
The Workflow supports a set of activities of various types to configure a process that fits your needs.
See the Workflow Editor article to familiarize yourself with the functionality.
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
Image Added
Note |
---|
Please keep in mind that all mandatory fields should be populated in order for a workflow element to work fine. |
Begin activity
This activity, along with the End activity, is initial and appears when a new workflow is created. It's a logical start of every workflow.
End activity
This activity, along with the Begin activity. is initial and appears when a new workflow is created; it's a logical conclusion of every workflow.Info |
---|
To define variables in your activities via the administrative agent interface if necessary, please complete the steps below:
|
Create Event activity
The Create Event activity primary function is to add events in the event queue that may later perform a trigger function for any action or notification or something else. After creating an event, it is written down into the Event (sys_event) table. In parallel, the event processor handling the event within the period specified in the system properties.
Activity fields
See the Creating a new activity article to learn more. |
Basic activities
Section | ||||
---|---|---|---|---|
|
Utilities Anchor utilities utilities
utilities | |
utilities |
The activities included in this category execute scripts, change and update records.
Run Script activity
The Run Script activity executes the defined script
If activity
This activity checks a condition to determine if a Yes or No transition should be taken.
If both the Condition and Advanced checkboxes are selected, then they both must evaluate for this activity to choose the Yes transition; otherwise, the No transition is chosen.
Activity fields
Field | Mandatory | Description |
---|---|---|
Name | N |
Activity name. A good practice is to make the name descriptive for clarity. | ||
Run Script | N | Specify the script to execute. |
Description | N | Type a brief description |
of the activity. |
Enter a script to evaluate in this field. This field is displayed when the Advanced is set true.
Join activity
This activity joins multiple execution paths from several activities exits into one transition.
The possible case to use this activity is when you need to cause a workflow to wait for more than one activity in multiple paths to finish before continuing.
How to use the Join activity
Note | |||||||||
---|---|---|---|---|---|---|---|---|---|
This activity type causes the update of the current target record after execution. The activity logic is defined by the Immediately value in the When to Run field within the Workflow Activity Type (wf_activity_type) table. Also, the Immediately option and the related activity behavior allows to avoid the update of records within Run Script scripts, as follows:
It will be done automatically. |
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 path of the Complete exit is taken (to the activity named Insert). 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.
Image Added
Warning |
---|
Never join multiple exits from an activity to a single Join activity, otherwise, the Join activity works incorrectly and never selects the Complete transition. In the example below, both exits from the If activity lead to the Join activity. Even though the condition of the If activity is met, the Join activity selects the Incomplete exit as the No exit from the If activity is inactive.
|
How to use the Join activity
- In the left side menu, open the Utilities tab and drag and drop the Join activityAdd it to the canvas using the Workflow Editor.
- Connect the exits of the activities you need to join to with the Join activity.
- Then connect its exits , create transitions from the Join activity exits (Complete and Incomplete) to the exit next activities: Complete and Incomplete.
Activity fields
Field | Mandatory | Description |
---|---|---|
Name | N | Descriptive activity name displayed on a canvasActivity name. A good practice is to make the name descriptive for clarity. |
Description | N | Type a brief description for the activity. |
Activity exits
Result | Description |
---|---|
Complete | The Join activity moves along this path when the system has determined that all activities joined have completed and transitioned to the Join. |
Incomplete | The Join activity moves along this path when the system has determined at least one activity joined have completed but transitioned along a path not followed by the Join. |
Record Generator activity
This activity creates records on any of the tables extending the Task table.
This exit is taken when all joined activities have finished running and proceeded to this activity. | |
Incomplete | 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.
|
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.
Note |
---|
This activity type causes the update of the current target record after execution. The activity logic is defined by the Immediately value in the When to Run field within the Workflow Activity Type (wf_activity_type) table. |
Activity fields
Field | Mandatory | Description |
---|---|---|
Name | N | Activity name. A good practice is to make the name descriptive for clarity. |
Description | N | Type a brief description of the activity. |
Table | Y | A table to be affected by this activity. This field is populated automatically. |
Set Values | N | 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).
|
Record Generator activity
The Record Generator activity creates records in any table extending from the Task table.
Info |
---|
If both the Wait For Condition Complete and Advanced checkboxes are selected, then they both must |
be evaluated for this activityto |
proceed with the |
transition. |
Note |
---|
Make sure that all mandatory fields are populated when using this activity; otherwise, the workflow will break its execution. |
Activity fields
Field | Mandatory | Description | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Name | N | Descriptive activity name displayed on a canvasActivity name. A good practice is to make the name descriptive for clarity. | |||||||||||||||||
Description | N | Type a brief description for of the activity. | |||||||||||||||||
Task Type | Y | Select the task type . You can make a selection from the corresponding task table. Click the magnifier icon | |||||||||||||||||
Task Values Fromfrom | N | The source of values used to create the task may either come fromfor a task to be created. Available options:
| |||||||||||||||||
Set Values | N | Specify an existing template related to the selected task table.
| |||||||||||||||||
Task Template | Y | Specify an existing template related to the selected task table.
| |||||||||||||||||
Wait for Condition Complete | N | If Select this checkbox to display Completion Conditions. When selected, then the activity waits conditions are mandatory for completing the condition to be met (and the task to be completed) before continuing. You can specify more than one condition; in this case, all of them have to be met before continuing. | |||||||||||||||||
Completion Conditions | NY | Specify conditions for the created task. The process will not proceed to the next activity until the task meets all conditions.
| |||||||||||||||||
Advanced | N | Select this checkbox to specify a script to evaluateexecute. When you select this checkbox, a the Script text box appears where you can enter the scriptfield appears. | |||||||||||||||||
Script | N | Set values for the task in this script. Use the variable 'new_task' when setting additional values. Note: This script is run This field is displayed when the Advanced checkbox is selected.
For example:
This field is displayed when the Advanced is set true. | |||||||||||||||||
Task Values From group | |||||||||||||||||||
Task Template | Y | This field appears only when the Template option is selected in the Task Values From field. In there, you can specify an existing template related to the selected task table. | |||||||||||||||||
Set Values | N | This field appears only when the Values option is selected in the Task Values From field. In there, you can specify an existing template related to the selected task table. |
Run Script activity
The Run Script activity runs a script in the scope of the workflow version.
|
Create Event activity
The Create Event activity establishes 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 Events article to learn more.
Activity fields
Field | Mandatory | Description | ||
---|---|---|---|---|
Name | N | Activity name. A good practice is to make the name descriptive for clarity. | ||
Event | Y | Choose the event instance on the basis of which the activity will create events. All the event instances (or event registers) are listed in the Event Registers (sys_event_register) table. Click the magnifier icon | ||
Param 1 ... Param 5 | N | Specify the event parameter. If this parameter is a string value, it must be enclosed in quotes.
| ||
Description | N | Type a brief description of the activity. |
Conditions
The activities included in this category set conditions to continue the processing and define further transition of the workflow. The transition taken 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
Input variablesField | Mandatory | Description |
---|---|---|
Name | N |
Activity name. |
A good practice is to make the name descriptive for clarity. | ||
Description | N | Type a brief description |
of the activity. |
Set Values activity
Table | N | A table to be affected by this activity. This field is populated automatically. | |||||||||||
Condition | Y | Define conditions mandatory for proceeding with the Yes transition. | |||||||||||
Advanced | N | Select this checkbox to specify a script to execute. When you select this checkbox, the Script field appears. | |||||||||||
Script | N | This field appears when the Advanced checkbox is selected. If specified, the workflow is paused at this activity until this script returns true. The result of the script execution will be added with the AND operator to the results of the Condition specified.
|
Note |
---|
If both Condition and Script are specified, then both of them must execute successfully to transition to the next activity. The workflow will stay paused until the Condition is met and the Script returns true. |
If activity
This activity checks a condition to determine if a Yes or No transition should be taken.
Info |
---|
If both the Condition and Advanced checkboxes are selected, then they both must be evaluated for this activity to choose the Yes transition; otherwise, the No transition is chosen |
. |
Activity fields
Field | Mandatory | Description |
---|---|---|
Name | N | Descriptive activity name displayed on a canvasActivity name. A good practice is to make the name descriptive for clarity. |
Description | N | Type a brief description for of the activity. |
Table | Y | A table to be affected by this activity. This table should contain columns for which you need to set new values. This field is populated authomaticallyautomatically. For example, if you need to set new values for the Master Incident field using this activity, then select the Incident table. |
Set Values | N | From the list on the left, select the current record field whose value you want to set when the workflow freezes or ends. In the input field to the right, enter the value to set. You can choose more than one parameter, in this case, all of them are applied. |
Switch activity
This activity checks the passed field values if they are equivalent to one or several case values. Its behavior is similar to a switch statement in Java.
Condition | Y | A condition to meet in order to proceed with the Yes transition.
| |||||||||||
Advanced | N | Select this checkbox to specify a script to execute. When selected, the Script field appears. | |||||||||||
Script | N | 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.
|
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 transitionWhen creating this activity, specify a Field or Custom value in the Type field to perform the check against the conditions for a matching value. When the field matches the value defined, the workflow progresses through the condition.
Activity fields
Field | Mandatory | Description | Workflow Version | Y | This field indicates the workflow version to which this activity instance related to. By default, it is populated with the current workflow name value that you are working on.||||||
---|---|---|---|---|---|---|---|---|---|---|
Table | N | A table to be affected by this activity. This | table should contain columns for which you need to set new values. Thisfield is populated | authomaticallyautomatically. | ||||||
Name | N | Descriptive activity name displayed on a canvas. | Activity name. A good practice is to make the name descriptive for clarity. | |||||||
Type | Y | Select Field or Custom as the type of the value to check against for. If you select the Custom option in the Type field you can customize your activity exits in the following ways: source of exit options for this activity. The workflow will perform check values against these conditions. Available options:
| ||||||||
Column | Y | This field appears when you have selected the Field option. In there, you can specifySpecify a column containing options for | a the condition. These options will become exits of the activity. Click the magnifier icon | |||||||
Fields specific for activity exits | ||||||||||
In the example below, the Switch activity takes options from the Type field.
|
To create additional exits, perform the following steps:
- Right-click the Switch activity and select Add exit.
- Double-click the exit to open the exit form fields.
- Fill in the fields.
- Click Save.
- Repeat to add more exits if needed.
Anchor | ||||
---|---|---|---|---|
|
Field | Mandatory | Description | |||
---|---|---|---|---|---|
Name | N | ||||
Table | N | A table to be affected by this activity. This field is populated automatically. | |||
Activity | Y | The activity to which this exit is related. This field is populated automatically. | |||
Description | N | Type a brief description of the activity exit. | |||
Condition | Y | Define conditions mandatory for proceeding | Condition | N | A condition to meet in order to proceedwith this specified transition. |
Advanced | N | Select this checkbox to specify a script to | evaluateexecute.When | you select this checkbox, a text box appears where you can enter the scriptselected, the Script field appears. | |
Script | Y | This field appears when | your have checked the Advanced checkbox is selected. | In there, you can specify the exit scriptIf specified, the workflow is paused at this activity until this script returns true. |
Note |
---|
If both Condition and |
Script are specified, then both of them must execute successfully to transition to the next activity |
. The workflow will stay paused until the Condition is met and the Script returns true. |
Note |
---|
In case of the Switch activity, every exit can be configured with a separate individual scripts. So the Advanced checkbox appears only when an the activity has more that one exit, and it is displayed on exits onlythan one exit. The checkbox appears only on exit forms. |
Approvals
The User Approval activity configures the approval processing: it creates approvals, sets approval rules and conditions.
User-approval activity
Excerpt Include User-approval activity User-approval activity nopanel true
Subflows
The Subflow activity performs another workflow. This activity is useful for complex workflows that include other processes.
Subflow activity
This activity allows running workflow from the parent The Subflow activity performs an existing workflow as part of the current workflow.
Activity fields
Field | Mandatory | Description | |
---|---|---|---|
Name | N | Descriptive activity name displayed on a canvasActivity name. A good practice is to make the name descriptive for clarity. | |
Workflow | N | Y | The published workflow to be performed by the activity. Click the magnifier icon . |
Description | N | Type a brief description for the activity. |
When a Subflow block is started, a workflow context is created for the current record. Until the context is finished, another Subflow block with the same workflow cannot be started, since at any given time only one workflow context can exist for the current record.
Timer activity
This activity pauses the workflow execution for the specified period of time.
For example, a Subflow block referring to the "Request 2nd phase" workflow is configured in the main workflow. After the main workflow starts, the "Request 2nd phase" subflow is started. The subflow execution context is paused. If another attempt to launch the "Request 2nd phase" subflow is made within the main workflow, the subflow is created in the canceled state.
Timers
The Timer activity pauses the workflow. This activity is useful when the process requires waiting for a certain period.
Timer activity
The Timer activity defines a period of time during which the current workflow does not run. It follows the logic below:
- 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
Field | Mandatory | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
Name | N | Descriptive activity name displayed on a canvasActivity name. A good practice is to make the name descriptive for clarity. | ||||||||
Description | N | Type a brief description for of the activity. | ||||||||
Timer, based on | Y | This is how The way the timer duration is calculated. Available options:
| ||||||||
Duration | Y | This field appears when the A user specified duration option is selected in the field above. In this field you can specify the duration of time Specify the duration of time to wait in days, hours, minutes and seconds to wait before proceeding to the next activity . | Script | N
| the Script
| selection
| ||||
Script | Y | Specify the script implementing the duration calculation logic. Here, you can use the SimpleOne API methods.
| ||||||||
The Schedule tab | ||||||||||
Timezone, based on | N | Specify a timezone source for this activity. Available options:
| ||||||||
Timezone | Y | Select a timezone from the list. Click the magnifier icon
| ||||||||
Schedule, based on | N | Specify a schedule source for this activity. Available options:
| ||||||||
Schedule | Y | Select a schedule from the list. |
User Approval activity
This activity creates user approval(s) when executed, one or more, depending on the parameters specified. For full information please refer to the User approval article.Wait Condition activity
This activity causes the workflow to wait until the record meets the condition specified. The workflow evaluates this activity each time the record updated. Use it to hold a workflow execution until a particular criteria is met by a record update.
Activity fields
Click the magnifier icon
|
|
Table of Contents | ||||
---|---|---|---|---|
|
...