Configure a Condition activity

Use the following procedure to configure a Condition activity for a simplified configuration of a Synchronization activity with branching rules. Paths from the activity properties are added as activities to the process. The destination activities are automatically displayed as you configure paths.

This activity is only available when configuring a decision tree.

  1. Add an activity to the map. See Add an activity.
  2. Change the default Name of the activity to something meaningful.
  3. On the Type list, select Common > Condition.
  4. Configure the properties for this activity, as required. See Activity properties.

    The After processing tab under Properties is not available for a Condition activity.

  5. Configure the branching rule, add destination nodes, and define their paths in either way.

    Add activity Description

    Add activities from the Satellite

    1. Select the Condition activity and select the Activity icon on the Satellite.

      An activity is added to the condition activity.

    2. To update the path, do the following:

      1. Double-click the first activity on the Path column or select the activity and then select on the header.

        The Edit path dialog box is displayed.

      2. The Activity name is displayed as read-only.

      3. Add a Description for the activity.

      4. Right-click on the rule editor and define a rule using the process/server variable or business data. See Additional information on creating rules for a Condition activity.

      5. Select Validate to validate the rule.

        If the rule is not valid, a message appears stating that branching rule is invalid. Select OK in the error message, correct the expression, and validate.

      6. Select Update.

        The activity description appears in the When column of the Path table.

    3. Similarly, add other activities to the Condition activity, as needed.

    4. By default, the first activity under the Condition activity appears as the default path. You can change the default path by selecting a different activity on the Default path list.

    5. To delete an activity, select the activity and select on the header.

    6. You can use expressions in decision-making processes to evaluate conditions and determine outcomes. Using expressions, you can define criteria at each decision node and ensure that decisions follow defined business rules and provide clarity on what actions to take based on varying conditions. You can enhance the evaluation process using functions in expressions.

    7. To validate the expression, select Validate.

    8. Similarly, update the path for other activities, as needed.

    Add activities directly when defining the rule path

    1. Select the Condition activity and select for Path on the Configuration tab.

      The New path dialog box is displayed.

    2. Enter the Activity name.

    3. Enter a Description for the activity.

    4. Right-click on the rule editor and define a rule using the process variables, server variables, predicates, and/or business data.

    5. To validate the rule, select Validate.

      If the rule is not valid, a message appears stating that branching rule is invalid. Select OK in the error message, correct the expression, and validate.

    6. Select Add.

      The activity name appears on the Take path column and the activity description appears on the Description column of the Path table.

    7. Similarly, add the other activities as needed to the Condition activity by defining the path.

  6. By default, the first activity under the Condition activity appears as default path. You can change the default path by selecting a different activity on the Default path list.
  7. To delete an activity, select the activity and then select on the header.
  8. Add the end nodes.
  9. Release the Decision tree business rule.

Additional information on creating rules for a Condition activity

When creating a rule for the Condition activity, you can set the value of one or more variables using free text (place the value under quotes), variables, operators, and functions in the rule editor.

Literal strings automatically support special characters such as \ and ". At runtime, the rules are updated to prefix the literal strings with @ symbol, but only when required. You can still use a prefix for the literal string with @ symbol, such as @"abc\123" or by escaping the characters, such as "abc\\123".

Supported variables

See the following table for the variables supported in a condition.

Bool (Boolean) Folder
Byte JSON expression
Currency Long
Data object Nullable date
Date Nullable string
Decimal Short
Document String
Double XML
Dynamic complex XML expression
Float