If Else
Description
This activity uses conditional or branching statements to execute different statements/branches based on whether a given expression is true or false. It includes a condition, a True branch, and a False branch. The Condition field must contain a Boolean expression that determines which branch to execute: True or False.
Using Process Data
You can dynamically configure activity properties by using variables from the Process Data drawer. This drawer is available in each activity's properties dialog. It provides access to variables from multiple sources within the workflow.
Process Data Categories
| Options | Description |
|---|---|
| Model Data | Process-specific data variables that you define for your workflow. |
| Form Data | Variables from forms associated with this process. |
| System Data | Predefined system variables (e.g., Process Initiator, Activity Name, Task ID). |
| Enterprise Variables | Enterprise variables created inside the AI Command Center. |
| Activities Outputs | Output variables from other activities in your workflow. |
Using Variables in Activity Properties
To use a variable:
- Drag and drop it from the Process Data drawer into any activity property that supports variable binding.
- Properties that support variable binding display a vertical ellipsis (⋮) icon.
You can also reference Process Data variables within JavaScript or Liquid expressions for advanced configurations.
For more information, see Process Data Drawer.
Design Time Configuration
Display Text
Specify the activity name that shows in your process.
Condition
Specify the condition expression. If the expression is true, the True branch executes; otherwise, the False branch executes. Click on the vertical ellipse to choose the following options.
| Options | Description |
|---|---|
| Default | When you select this option, specify the condition directly. |
| Javascript | Specify the condition using javascript expression. |
| Liquid | Specify the condition using a liquid expression. |
On Error
All activities support the common On Error handler to control behavior on failures (Fault, Continue, Suspend, Retry). See On Error Handler.
Wait All Incoming
The Wait All Incoming property defines how an activity behaves when it has multiple incoming execution paths. It controls whether the activity is triggered as soon as a path completes or whether the workflow engine must wait for multiple paths to complete before executing the activity.
| Options | Description |
|---|---|
| False | The activity is triggered whenever any incoming path completes. Each incoming completion can trigger a separate execution of the activity. |
| All Configured Incoming | The activity executes only after all design-time (configured) incoming paths have completed. If a path is skipped at runtime due to conditional logic, the activity may wait indefinitely. |
| All Active Incoming | The activity executes only after all runtime-active incoming paths have completed. Incoming paths that are not taken due to conditions are automatically ignored, preventing indefinite waiting and ensuring predictable execution. |