Improved Rule Editor for Branching & Filter Logic in Flows

What It Is

 

This article explains the revamped Rule Editor in Celigo’s Flow Builder, which significantly improves how you define filters and branching logic. The new interface makes it much easier to build, review, and manage both simple and complex logic structures without relying on custom scripts.

 

 

 

Need to Use

 

Use this when you are building flows in Celigo that require conditional logic, branching (e.g., “if this, then that, else”), filters for data subsets, and you want a more intuitive, visual experience. It’s especially useful when logic is complex, nested, or needs maintenance by non-developers.

 

 

Key Benefits

 

Visual clarity: AND, OR, and NOT operators are clearly displayed and nested logic groups are collapsible for easier overview.

 

No scripting required: You can configure branching/filter logic without writing custom code.

 

Improved usability: Operands and fields are searchable; conditions and groups can be cloned, cleared or reordered via drag-and-drop.

 

Consistent experience: The rule editor works the same way for both filters and branching steps, reducing learning curve.

 

 

 

 

Steps Involved

 

1. Open your flow in Celigo’s Flow Builder and locate a filter or branching step.

 

 

2. Switch to the new Rule Editor UI.

 

 

3. Build rule logic by:

 

Selecting conditions (e.g., “Order Total > 100”, “Country == US”).

 

Combining using AND/OR/NOT operators.

 

Nesting groups if needed (e.g., “(ConditionA AND ConditionB) OR ConditionC”).

 

 

 

4. Use drag-and-drop to reorder rules or groups; clone individual rules or clear them without deleting the entire branch.

 

 

5. Search for operands/fields when building conditions to quickly find the right data item.

 

 

6. Deploy the flow and monitor branches executing based on the logic you configured.

 

 

7. Use this in use-cases like:

 

Filter orders by region before importing into ERP.

 

Branch logic for different payment gateways (e.g., flow branch A for PayPal, branch B for Stripe).

 

Applying different mapping logic based on order size or product category.

 

 

Leave a comment

Your email address will not be published. Required fields are marked *