Decision

The Decision node enables you to evaluate conditions and route the integration flow through different execution paths based on the evaluation result. It allows you to automate conditional processing by executing different activities when specified conditions are met or when no conditions are satisfied.

The Decision node evaluates the configured conditions and executes the corresponding branch; if no conditions are met, the Otherwise branch (if configured) is executed, with each branch containing one or more activities.

Figure: Decision node

Note

A Decision node supports multiple conditional routes.

Benefits

• Automates conditional routing within integration flows.

• Supports multiple execution paths for different business scenarios.

• Reduces the need for separate integration flows

Configure Decision Node

Configure the Decision node to define the conditions that determine which execution path the integration flow follows during runtime.

To configure Decision node, perform the following steps:

1. Click (Add Step) and select Decision from the Control Nodes category.
   The list of Control Nodes are displayed.
   
   Figure: Component list
   

2. Click Decision node to display the parameter section.
   The Decision parameter is displayed.
   
   Figure: Decision Parameter
   

3. Configure the following conditions and click Save Changes to save the configured parameters.
   

   If

   The If branch is a mandatory and defines the condition to evaluate. If the condition is met during runtime, the activities in the branch are executed. At least one If condition is required.
   
   Figure: If - Condition

   Otherwise (Else)

   The Otherwise branch defines the default execution path when none of the If conditions are met. This branch is optional.
   
   
   Figure: Otherwise (Else)

   Route

   A Route defines a conditional execution path within a Decision node. Each route includes a condition and the associated activities to execute when the condition is met. By default, a Decision node provides four routes, with support for up to eight configurable routes.

   Note

   By default, a Decision node provides four routes, and it can be configured to support up to eight routes.

   
   
   Figure: Route

   Actions

   Use the available route actions to configure, organize, and manage the conditions within a Decision node.

   Field	Description
   + Rule	Specifies the condition to evaluate for a route within the Decision node. A Rule defines the condition that is evaluated within a route. If the rule evaluates to True, the activities associated with that route are executed. Multiple rules can be configured across different routes to control the execution path of the integration flow.
   + Group	Organizes related rules within a route for condition evaluation.
   Remove route	Removes the selected route from the Decision node.
   AND	Evaluates to True only when all grouped rules are satisfied.
   OR	Evaluates to True when at least one grouped rule is satisfied.
   Group	Group combines multiple rules into a logical group and evaluates them using the selected AND or OR operator.
   Ungroup	Ungroup removes the logical grouping and restores the selected rules as individual conditions