Skip to main content

Configuring Transition Lines

Transition conditions define how workflows transition between activities based on success or error states. Each condition has a specific inverse condition that must be used for complementary scenarios.

Available Conditions and Corresponding Mappings​

  1. Success ↔ Error
    • If the user uses Success, they must use Error as its counterpart.
    • Similarly, if the user uses Error, they must use Success.
  2. Error Matching Condition ↔ Error No Matching Condition
    • If the user uses Error Matching Condition, they must use Error No Matching Condition as its counterpart.
    • Similarly, if the user uses Error No Matching Condition, they must use Error Matching Condition.
  3. Success Matching Condition ↔ Success No Matching Condition
    • If the user uses Success Matching Condition, they must use Success No Matching Condition as its counterpart.
    • Similarly, if the user uses Success No Matching Condition, they must use Success Matching Condition.

Steps to Configure Workflow Transitions​

1. Add Activities​

Incorporate required activities into your workflow based on the specific requirements.
Examples

  • Response Activities for returning outputs to the caller.
  • Rest Client Activities for interacting with external APIs.
  • Data Transformation Activities for manipulating workflow data.

2. Configure Transition Conditions​

  1. Select the Transition Line
    • Navigate to the transition line between activities.
    • Assign a descriptive name to the transition for clarity.
  2. Define the Condition
    • Use expressions starting with $ to define logic.
      Example
      • ($.RESTService.pathParams.num >= 10) ensures the transition follows only when num is greater than or equal to 10.
  3. Apply the Correct Inverse Condition
    • For Success
      • Use Error as the counterpart.
    • For Success Matching Condition
      • Use Success No Matching Condition as the counterpart.
    • For Error Matching Condition
      • Use Error No Matching Condition as the counterpart.

Example Scenarios​

Scenario 1: General Success Handling​

  • Primary Condition: Success
  • Counterpart: Error
  • Example Use Case
    • If a task is successful, the transition uses Success. If it fails, the counterpart transition uses Error.

Scenario 2: Success with Specific Matching Conditions​

  • Primary Condition: Success Matching Condition
  • Counterpart: Success No Matching Condition
  • Example Use Case
    • Use Success Matching Condition for specific success criteria, and Success No Matching Condition to handle success cases that don’t meet these criteria.

Scenario 3: Error with Specific Matching Conditions​

  • Primary Condition: Error Matching Condition
  • Counterpart: Error No Matching Condition
  • Example Use Case
    • Use Error Matching Condition for errors matching certain criteria (e.g., error codes). Use Error No Matching Condition to handle errors that don’t match those criteria.