Condition node in Agentic Process

The Condition node lets you define decision points in Agentic Processes, from which one or more paths can continue.

You can add a Condition node from any existing node in the Agentic Process. To do so, hover over one of the node's anchor points and click the + icon. This opens a context menu with options such as Task, Event, Finish, and Condition.

You can also add a Condition by dragging it directly from the Toolbox.

Condition types

Agentic Processes support three types of Condition nodes:

• Agentic
• Parallel
• Exclusive

Agentic

The Agentic condition allows you to delegate the decision about which path to follow to an Agent. The Agent evaluates the current state of the Agentic Process instance and selects one or more paths based on the available information.

When you select a Condition node of Agentic type, the Properties panel becomes available with the following options:

• Condition name: Enter a descriptive name to identify the condition in the Agentic Processes.
• Type: Defines the type of condition. In this case, it is set to Agentic, which means an Agent will decide which path to follow based on the state of the Agentic Processes.
• Condition instructions: Enter custom instructions to guide the Agent’s decision. Use this optional field to limit the choice to a single path, prioritize certain steps, or include specific conditions.

Elements considered in the Agent's decision

The Agent's decision is based on three elements that are automatically included in the prompt:

• The subject of the Agentic Process and the variables assigned up to that point. Note that if the Agentic Process starts with an artifact event, no variables are retained.
• The process history, including the list of executed tasks, their statuses, and start and end times. Task content, results, and generated files are not included.
• Information about the tasks available after the Condition node, including task names, descriptions, and the Agents that will execute them.

If no Condition instructions are provided, a default prompt is generated that automatically includes this information.

The prompt has the following structure:

This is a workflow process, here is what has happened so far: 
The instance subject is: {{PROCESS_INSTANCE_SUBJECT}} 
The information about the process that we have so far is as follows:
### START HISTORY
  {{PROCESS_HISTORY}}
### END HISTORY
  {{GATEWAY_EXPRESSION}}

You must choose one of the following next-steps to call:
{{NEXT_STEPS}}

Any text you enter in Condition instructions will be inserted in the {{GATEWAY_EXPRESSION}} space.

Parallel

The Parallel condition allows the Agentic Process to continue through multiple paths simultaneously. Use this condition when different tasks can run in parallel.

When you select a Condition node of Parallel type, the Properties panel is enabled with the following options:

• Condition name: Enter a descriptive name to identify the condition in the Agentic Process.
• Type: Defines the condition type. In this case, it is set to Parallel, which means the Agentic Process will continue through multiple paths at the same time from this point forward.

Unlike the Agentic type, the Parallel node does not evaluate any conditions or require instructions. All outgoing paths are triggered simultaneously, with no need for a decision.

Considerations

After a Parallel node, you can define a new node for the process to converge once all branches are completed. This convergence point must be located one step away from the Parallel node.

Exclusive

The Exclusive condition evaluates predefined logical rules to determine which path the Agentic Process follows. Unlike the Agentic type, it does not delegate the decision to an Agent. Instead, it applies strict deterministic criteria, and only the first path whose condition evaluates to true is executed.

When you select a Condition node of Exclusive type, the Properties panel becomes available with the following options:

• Condition name: Enter a descriptive name to identify the condition in the Agentic Process.
• Type: Defines the condition type. In this case, it is set to Exclusive, which means the process follows the path determined by formal logical rules.

Each time you connect a new node to the Exclusive node on the canvas, a new entry appears in the Properties panel: Condition 1, Condition 2, and so on.

To view or configure a condition, open the Properties panel by clicking the Exclusive node (1) or one of the condition lines on the canvas (2).

After opening the Properties panel, expand the condition using one of the following options:

• Click the expand icon (3) to open it in a dialog box.
• Click the down arrow (4) to expand it inline in the panel.
• Click Expand all conditions (5) to expand all conditions at once.

In all cases, two fields become available:

• Condition Description: Enter the logical rule in plain language (for example, "num is greater than 23").
• Condition Expression: The formal syntax evaluated by the system (for example, &num.GreaterThan(23)).

An integrated Agent automatically keeps both fields synchronized, allowing you to work in either format.

Considerations

• The process engine evaluates conditions sequentially and executes the first path that evaluates to true.
• The Condition node of Exclusive type must include one path marked as Default. If only one condition exists, it is automatically set as Default and cannot be cleared. If two or more conditions exist, you can manually choose which path acts as the default fallback.
• To learn more about the expression syntax supported in Condition Expression, see Condition Expression Language.