Configuring a Decision Split control

Use the Decision control (Decision split) to add conditions to the Entry Source data. The records which fulfill the condition will flow in the YES path and the remaining records will flow in the NO path.

About this task

Use conditions to automate the behavior of touchpoints with some business requirement conditions. Business requirements can include filtering a list of customers based on age, salary, etc.

To configure a Decision Split control, perform the following steps:

Procedure

  1. From the Journey Palette, drag-and-drop the Decision Split control.
    Note: If you drag-and-drop the Decision Split between the existing elements on a canvas, a confirmation dialog appears. Confirm whether you want the remaining flow to be added in the YES flow or the NO flow.
  2. To configure the Decision Split control, double-click the control on the Canvas.
    The Decision Split page appears.
  3. To configure the Decision Split control, complete the following steps:
    1. Enter an appropriate Name. A name is mandatory.
    2. Enter an appropriate Description. The description is optional.
    3. Use the toggle button to set the condition as OR or AND. By default, the condition is set to AND. The selection applies to all the rules within a group. The selected condition is applicable only if you add more than one rule in a group.
    4. Note: A group contains one or more rules. A rule has a field, a condition, and a value for the condition to verify. It is mandatory to configure at least one group and a group must contain at least one rule.
      Create a rule by selecting the data field (same as the Data Definition field) in the first drop-down box, the condition in the second drop-down box, and entering the value in the third text box.

      When configuring Decision Split, the available operators will be shown based on the data type of the field in the data definition. String, Numeric, and Date fields have different operators.

      For configuring a date in Decision Split, the format of date field should match the Data Definition date format. Decision Split configuration will be unsuccessful if the date formats do not match.

    5. To add more rules in a group, select + Add Rule. To delete a rule, select the X succeeding the rule.
    6. To add a group, select + Add Group, and perform Step c to Step e.
      A parent group allows five levels of nesting in the sub-groups. However, any number of groups can be added at the same level.
    7. To delete a group, select Delete Group.
      Note:
      • You can delete a group only if there are more than one groups. By default, Decision split control should contain at least one group with at least one rule.
      • When a group has nested sub groups and if you select the parent group for deletion, a confirmation box appears warning you that the sub-groups will also be deleted.
    8. Set one of the following evaluation periods for customers to wait for a condition to be satisfied:
      • Duration - Set the duration in days, hours, or minutes. By default, the minimum duration for Decision valuation period is 5 minutes.
      • Wait till date - Set the duration to a specific future date. By default, the next day's date is selected.

        Once the Duration or Wait till date elapses, Journey will assume that there are no data that satisfies the configured condition the selected decision split and the audience in the Journey will move to the NO path.

        Audiences satisfying the condition will be moved to Yes path immediately.

    9. To save the Decision Split, select Done.
    Note: When user input the date in Journey entry source and date - year is mentioned in two digits then Journey consider this year in the current century, for example if you send the date as in format DD/MM/YY - 10/12/22 - then year is considered as 2022. If you need to send any date for processing Journey from previous century - for example - 04/031982 - then it needs to be explicitly specified in YYYY format.
    Note: Journey is not interpreting the data value for non-required fields and it is always considered as string for any value. Hence, null will be considered as null in the database and is null milestone condition will be evaluated only if that field is absent in input. Same is applicable for Milestone and Milestone analysis.