Setting a branch condition

  1. Select Enterprise Orchestrator > Symphonies.
  2. Select the symphony you want to edit.
  3. Click the switch construct on the symphony canvas.
  4. When the General tab opens, select the Action column, click on a pen icon in the Branch 1, and specify this information:
    Variable 1 Type
    Specify the source of the first operand used in the condition. Supported options include:
    • A symphony variable
    • An activity output variable
    Variable 1
    Specify the value of the first variable, based on the chosen variable type.
    Operator
    Defines how variable 1 is evaluated against variable 2. Common operators include: equals not equals, more than, less than, more or equal, and less or equal.
    Variable 2 Type
    Specify the source of the second operand.
    Note: Ensure both variables are of the same data type.
    Variable 2
    Specify the value of the second variable.
  5. Save the branch details.
    Note: This is useful information:
    • Each conditional branch must have a valid condition defined. The default branch does not require a condition, and is executed when no other branch conditions evaluate to true.
    • The maximum number of conditional branches is three.
    • You must define a condition for the current branch before adding a new branch. If you click the Add Branch button before defining a condition for the current branch, the system blocks the action and displays a validation error: Please define the condition for the current branch before adding a new branch.
    • Before you can define a switch branch condition, a symphony must have at least one symphony variable or an activity with output variables in the flow before switch.
    • Cross‑branch output variable references are not allowed.
    • These are the output variable scoping rules within the switch construct:
      • Output variables from activities inside a switch branch can only be referenced within the same branch. You cannot reference output variables from one branch in another branch (including the default branch).
      • Output variables from activities inside a switch branch cannot be referenced by activities outside the switch construct. Downstream activities placed after the switch cannot use outputs generated inside a branch.
      • The Variable Reference picker shows only in-scope output variables to prevent invalid references.
      • You cannot map an error path from an activity in one switch branch to an activity in a different branch, or from an activity before the switch to an activity inside a switch branch.
    • A switch conditional branch must have at least one element included. Additionally, the default branch can't have the first element added before the conditional branch.
    • When you delete a branch that contains activities, a confirmation warning is displayed informing you that the branch activities will also be removed.
    • When you delete a switch construct that contains branches and activities, a confirmation warning is displayed before deletion.
  6. Optionally, click Add Branch (+) next to the switch construct name to add more branches.
    Note: When the maximum of three conditional branches is reached, the Maximum number of branches reached message is displayed as a tooltip and the Add Branch (+) button is disabled.