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.
To define variables in your activities via the administrative interface if necessary, please complete the steps below:
- Navigate to {your_instance_url}/list/wf_activity
- Choose the activity you are going to edit and click on it (or click New to create a new activity);
- Fill in the fields and click Save.
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.
Input variables
| Field | Description |
|---|---|
| Event | Choose the event instance on the basis of which the activity will create events. All the event instances (they also can be called event registers are listed in the Event Registers (sys_event_register) table). |
| Param 1 | Specify the first event parameter if it is required for this event. If this parameter is a string value, then it must be within quotes (" "). |
| Param 2 | Specify the second event parameter if it is required for this event. If this parameter is a string value, then it must be within quotes (" "). |
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.
Input variables
| Field | Description |
|---|---|
| Condition | A condition to meet for taking the Yes transition. |
| Advanced | Select this checkbox to specify a script to evaluate. |
| Script | Enter a script that must be evaluated in this field. If the script sets the variable answer to yes, then the Yes transition is taken; otherwise, the No transition will be chosen. |
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
- Add it to the canvas using the Workflow Editor;
- Connect the exits of the activities you need to join to the Join activity;
- Then connect its exits to the exit activities: Complete and Incomplete.
Exit activities
| 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.
If both the Wait for condition complete and Advanced checkboxes are selected, then they both must evaluate for this activity to choose the Yes transition; otherwise, the No transition is chosen.
Input variables
| Field | Description |
|---|---|
| Name | Displayed activity name. |
| Description | Type a brief description for the activity. |
| Task type | Select the task type to create. You can make a selection from the corresponding task table. |
Task values from | The values used to create the task may either come from:
|
| Wait for condition complete | If selected, then the activity waits for the condition to be met (and the task to be completed) before continuing. Yo can specify more than one condition; in this case, all of them have to be met before continuing. |
| Completion conditions | Specify the conditions to meet before completing. |
| Advanced | Select this checkbox to specify a script to evaluate. When you select this checkbox, a text box appears where you can enter the script. |
| Script | Set values for the task in this script. Use the variable 'new_task' when setting additional values. For example: |
| Task values from group | |
| Template | 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 | 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.
Input variables
| Field | Description |
|---|---|
| Name | Displayed activity name. |
| Description | Type a brief description for the activity. |
| Script | The script to execute. |
Set Values activity
The Set Values activity set values on the current record when the workflow freezes or ends. These values determine the activity behavior.
Input variables
| Field | Description |
|---|---|
| Set values | 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.
When creating this activity, specify a Field or Custom value to perform the check against the conditions for a matching value. When the field matches the value defined, the workflow progresses through the condition.
Input variables
| Field | Description |
|---|---|
| Type | Select Field or Custom as the type of the value to check against for. |
| Column | This field appears when you have selected the Field option. In there, you can specify a column containing options for a condition. These options will become exits of the activity. For example: if you are building your workflow basing on the Incident table and you have chosen the State column, your Switch activity may look like this:
|
| Script | This field appears when you have selected the Custom option in the field above. In there, you can specify a custom condition to meet. |
Subflow activity
This activity allows running workflow from the parent workflow.
Input variables
| Field | Description |
|---|---|
| Workflow | The workflow to run. You can choose any preferred workflow created earlier from the list. |
Timer activity
This activity pauses the workflow execution for the specified period of time.
Input variables
| Field | Description |
|---|---|
| Description | Brief activity description. |
| Timer based on | This is how the timer duration is calculated. Available options:
|
| Duration | This field appears when the option A user specified duration is selected in the field above. In this field you can specify the duration of time to wait before proceeding to the next activity (from days to seconds). This field is mandatory. |
Wait for 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.
Input variables
| Field | Description |
|---|---|
| Name | Displayed activity name. |
| Description | Type a brief description for the activity. |
| Condition | The workflow is paused at this activity until the record meets the condition specified. |
| Advanced | Select this checkbox to specify a script to evaluate. When you select this checkbox, a text box appears where you can enter the script. |
| Condition script | If specified, the workflow is paused at this activity until this script sets the answer variable to true. Select the Advanced checkbox to show this field. |
If both Condition and Condition script are specified, then both of them must execute successfully to transition to the next activity; otherwise, if the Condition will not meet or the Condition Script will not return true, the workflow will stay paused.
