Overview
Paths connect elements within a workflow template to determine the flow of an execution. Paths direct the execution based on system-evaluated conditions or user-selected resolutions. This article explains how to configure and manage paths to ensure predictable routing.
Prerequisites
- The workflow template must be created and a Context must be defined.
- Elements (such as a Rule node or Task node) must be added to the canvas before paths can be configured.
Required Permissions
- Admin permissions with Workflow configuration access.
Technical Considerations and Limitations
- Evaluation Order: Paths are evaluated in order, and the first match is triggered. If two conditions are both true, only the first one fires.
- Fixed Order: Path order is fixed at creation and cannot be changed. Paths can be added and deleted, but never reordered. Combined with first-match logic, overlapping conditions produce behavior that cannot be corrected without deleting and recreating paths.
- Exclusive Conditions: Designers should write mutually exclusive path conditions to prevent overlapping logic.
- Condition Requirements: Every path on a starting rule requires a condition. There is no catch-all path. If no paths are added to the starting rule, the rule uses a default path that fires immediately.
- No Match Behavior: If no path condition matches on a starting rule, no execution is created. This is the expected behavior, not an error.
Configuration Steps
Configuring Condition Paths
Condition paths are evaluated by the system. They are used on the starting rule and intermediate rules to route the execution based on field values or events.
- Select the starting rule or intermediate Rule node on the canvas.
- Add a new path in the configuration sidebar.
- Define the conditions for the path.
- Ensure the conditions do not overlap with other paths on the same rule.
Configuring Resolution Paths
Resolution paths behave differently from condition paths. Resolution paths are used on a Task node and are selected by a person, not evaluated by the system.
- Select the Task node on the canvas.
- Navigate to the Resolution Paths section in the configuration sidebar.
- Add the required resolution codes to the path. The assignee picks an outcome code from a flat list, and the system maps that code to the corresponding path.
-
Do not factor path order into the design, as order does not affect resolution paths.
Adding a Custom Name to a Path
A custom name can be added to label the path in the configuration sidebar.
- Click the Write a custom name text next to the path identifier.
- Enter the custom name.
- Click Save.
Deleting a Path
- Click the Delete icon next to the path identifier.
- The path is deleted automatically.
Validation
To validate path configuration, verify that paths are connected to the intended destination nodes. When the template is published and an execution runs, the visual canvas displays taken paths in green and untaken paths in light gray.
Troubleshooting
Problem: An execution stalls or stays in a running status indefinitely.
Possible Causes:
- A branch reached a path that connects to nothing.
- A Rule with ALL convergence is waiting for a branch that can never arrive due to exclusive paths upstream.
Resolution Steps:
- Review the canvas for unconnected paths.
- Trace the logic of upstream paths to ensure all required branches can reach the Rule.
Problem: The workflow routes down the wrong path automatically.
Possible Causes: Path conditions overlap, and a path created earlier in the sequence matched the criteria first.
Resolution Steps: Review the condition logic. Delete and recreate the paths to enforce the correct order, and rewrite the conditions to be mutually exclusive.
Problem: No execution is created when a record is updated.
Possible Causes: No path condition on the starting rule matched the data of the record.
Resolution Steps: Verify the conditions on the starting rule paths. If an execution is expected, adjust the conditions to capture the intended event.