In Boomi, the Decision Step is a logic shape used to route documents based on a true/false comparison between two values. Those values can be anything from field values in the current document (profile elements), static values, results of a database, an application query, and more.
What is the Decision Step?
The Decision Step evaluates each document that reaches it and determines whether it meets a specified condition. Based on the result, the document is routed down either the True or False path.
How It Works
- Comparison Logic: You compare two values using operators like Equal to, not equal to, Greater than, etc.
- Values Can Be:
- Profile elements (fields from the document)
- Static values
- Results from database queries
- Application connector responses
How to Add a Decision Step
- Drag the Decision Step onto the process canvas.
- In the Decision Properties dialog:
- Set a Display Name (e.g., “Does Order Exist?”)
- Choose the First Value (e.g., a profile element or query result)
- Select a Comparison Operator
- Choose the Second Value (e.g., a static value or another profile element).
3. On the Notes tab,
- Enter the title of the note in the Title field.
- Enter the note in the Note field.
4. Click OK to save or click Cancel to cancel configuring the step
5. Connect True and False paths to appropriate next steps.
Common Use Cases
- Checking for the existence of a record in the destination system to determine whether to create or update it.
- Database — The first value is the result of a SQL statement (often a simple SELECT COUNT(1) FROM SOME_TABLE WHERE ID=?), the comparison is “Equal to”, and the second value is a static value of ‘1’.
- Application — The first value is a profile element from a connector call response profile, the comparison is “Not equal to”, and the second value is a static value of ‘ ‘.
- Checking for the existence of value in a given profile element.
- The first value is a profile element, the comparison is “Not equal to”, and the second value is a static value of ‘ ‘.