Decision (Beta) tool in Jitterbit Integration Studio

Introduction

The Decision (Beta) tool is a project component that is used as a step in an operation to create conditional logic with IF statements and nested IF statements. Each condition evaluates to true or false and routes processing to different operations or operation chains based on the evaluation results.

Create a Decision (Beta) instance

A new instance of a Decision (Beta) tool can be created from these locations:

• The project pane's Components tab using the Create New menu (see Components tab actions menu in Project pane Components tab).

• The design component palette's Tools tab (see Tools in Design component palette).

An existing Decision (Beta) tool can be edited from these locations:

• The design canvas (see Component actions menu in Design canvas).

• The project pane's Components tab (see Component actions menu in Project pane Components tab).

Configure a Decision (Beta) tool

The Decision (Beta) configuration screen includes these fields and actions:

• Name: Enter a name to identify the Decision (Beta) tool instance. The name must be unique for each Decision (Beta) instance and must not contain forward slashes (/) or colons (:).

• Add If: Click to add a new IF condition branch to the decision.

• Add Else: Click to add an optional ELSE condition branch that defines the outcome if none of the previous conditions evaluate to true. Only one ELSE condition branch can be configured.

• Move: Drag and drop to change the position of the condition branch relative to others.

Condition configuration

Each condition branch contains the following elements:

• Condition name: Enter a descriptive name for the condition (for example, Premium Customer High Value).

• Expressions: Define one or more expressions that evaluate to true or false.

  • Field: Enter the field to evaluate from variables or activity responses.

  • Operator: Choose from comparison operators (equal, not equal, greater than, or less than).

  • Value: Enter the value to compare against the field.

  • Remove: Removes the expression.

• Logical operators: Use the AND/OR selector to define how multiple expressions are evaluated.

  

  • AND: All expressions must be true for the condition to evaluate as true.
  • OR: At least one expression must be true for the condition to evaluate as true.

• Add expression: Adds a row to configure an expression for the condition.

• Add condition: Adds a nested condition structure.

• Remove: Removes the condition structure.

Processing logic

The following processing logic applies when running a Decision (Beta) tool:

• Sequential evaluation: Conditions are evaluated in the order they appear in the configuration. The first condition that evaluates to true is executed, and no subsequent conditions are evaluated.

• Condition sequence: The order of conditions can be modified by dragging them up or down in the configuration using the Move icon.

• ELSE branch: If configured, the ELSE branch executes when none of the IF conditions evaluate to true.

• Save Changes: After making changes to a new or existing configuration, click to save and close the configuration.

• Discard Changes: After making changes to a new or existing configuration, click to close the configuration without saving. A message asks you to confirm that you want to discard changes.

Define logic operations

Once you save the configuration, you return to the design canvas, where you define the operation or operation chain that runs based on the evaluation results.

• Y (Yes/true): Use the drop zone to add or configure an operation or operation chain that runs when the condition evaluates to true.

• N (No/false): If an ELSE branch is configured, use the drop zone to add or configure an operation or operation chain that runs when none of the conditions evaluate to true.

In this example, (continued from the example shown in Condition configuration), premium customers with high-value orders in North America get special processing and all other customers get standard processing:

Actions

The actions bar for a Decision (Beta) tool has these actions: