Decision Box Node
Updated
The Decision Box node allows an Integration Flow to branch into multiple paths based on defined conditions. Instead of routing every record through the same workflow path, the node evaluates the configured criteria and directs the workflow to the appropriate branch.
This is particularly useful when different scenarios require different processing. For example, one team may need a workflow to follow a specific path when certain conditions are met, while another team may require a different path based on a separate set of conditions. The Decision Box enables this type of conditional routing without requiring duplicate workflow logic.
By default, the node supports two paths. However, it is not limited to only two outcomes. If additional paths are required, click Add Another Path to create another branch. This allows a Decision Box to support three, four, or more paths, providing the flexibility to model complex decision-making processes within a single node.
Supported Fields
Field | Description |
Name | Enter a unique and descriptive name for the node. Clear naming conventions can make it easier to identify the node in workflows that contain multiple decision points. |
Path Name and Conditions | Define the execution paths available in the Decision Box and the conditions that determine when each path is followed. Conditions can be based on Custom Code, Predefined Variables, or Previous Button Actions. You can combine multiple conditions using AND and OR logic to create more specific routing criteria. |
Adding Paths | Click + Add Another Path to create additional branches beyond the default paths. Each new path can have its own name and set of conditions, allowing the workflow to support multiple routing scenarios. |
Default Path | Specify the path that the workflow should follow when none of the configured conditions are met. This ensures that every record continues through the workflow, even if it does not match any predefined rule. |
