Published at: 2026-09-17
Configure branch nodes
Configure a Business Process Node that routes records by condition, so the Process enters different paths based on Business Data or rules.
Overview
A Branch Node determines which Node the Process enters next based on Configured conditions. When the Process reaches the Branch Node, the System matches each Branch condition. If a condition is met, the Process enters the subsequent Node connected to that Branch. If none of the Configured conditions is met, the Process enters the default path.
Branch Nodes are suitable for these scenarios:
- Route different Work Order Types to different handling processes.
- Route by Approval Decision to a Co-signature, field service, or evaluation Node.
- Route by Account level, Amount, Area, Status, or other Fields.
- Decide whether the Process continues, Returns for correction, or ends according to business rules.
Core Branch Node capabilities include:
- Configure one or More Branch paths.
- Set a Branch Name for each path.
- Configure entry conditions for each Branch.
- Configure the default Node for records that do not meet the preceding conditions.
- Connect each Branch to the corresponding next Node.
Before you begin
- The Business Process is created, and you are on the process canvas configuration page.
- You have Confirmed which business conditions the Process uses for routing.
- You have Confirmed the next Node for each Branch.
- You have prepared a default path for data that does not Match any Branch condition.
- If Branch conditions depend on Field values, Confirm that the Fields are Updated before the Process reaches this Node.
Configure Node Settings
Select the Branch Node on the process canvas, and then Configure the following items on the right-side Node Settings tab.
| Configuration item | Description |
|---|---|
| Node Name | The Name of the current Branch Node on the canvas and in Process records. Use the decision target, such as “Determine service path” or “Determine whether Co-signature is required” |
| Business Description | Describes the decision purpose of the Branch Node and helps admins understand the routing rule. The limit is 500 characters |
| Branch Name | The Name of the current Branch path, such as “Co-signature” or “Field service” |
| Enter when the following conditions are met | Configures the conditions for entering the current Branch. When the conditions are met, the Process enters the subsequent Node connected to this Branch |
| Edit conditions | Opens the condition configuration page, where you can set Fields, operators, values, or combined conditions |
| Enter when none of the above conditions are met | Configures the default path. When all Branch conditions fail, the Process enters this Node |
Configure Branch paths
A Branch Node requires at least one conditional Branch. We recommend that you also Configure a default path.
- Add a Branch Node and select it.
- In Node Name, enter a Branch Node Name, such as “Branch”.
- In Business Description, describe the Branch decision purpose.
- In the Branch configuration area, enter Branch Name, such as “Co-signature”.
- Click Edit conditions and Configure the condition for entering this Branch.
- Connect the Branch to the corresponding next Node, such as the Co-signature Node.
- To Add other Branches, continue to Configure new Branch names and entry conditions.
- In Enter when none of the above conditions are met, select the default Node.
- Save the Node configuration.
In the screenshot example, the Branch Node has two Branches:
| Branch Name | Entry condition | Next Node |
|---|---|---|
| Co-signature | Meets the “Co-signature” Branch condition | Co-signature Node |
| Field service | Meets the “Field service” Branch condition | On-site Standard Operation Node |
| None of the above | Does not meet the first two Branch conditions | Enters the Co-signature Node by default |
Configure Branch conditions
Branch conditions determine whether Business Data enters a specified path. Click Edit conditions to Configure condition rules.
When you Configure conditions, focus on these items:
| Configuration focus | Description |
|---|---|
| Decision Field | Select the routing Field, such as Work Order Type, Status, Account level, Amount, or Area |
| Decision rule | Configure operators such as Equals, Not Equal To, Include, Greater Than, or Less Than, depending on what the page Supports |
| Condition combination | If multiple conditions must be evaluated together, Configure AND or OR logic |
| Condition result | Confirm that the next Node entered after the condition is met is correct |
Branch conditions must be clear and stable. Avoid overlapping conditions that cause a record to Match multiple Branches and produce unexpected routing.
Configure the default path
Enter when none of the above conditions are met is the fallback path of a Branch Node. When Process data does not meet any Configured Branch condition, the System enters the default path.
Always Configure a default path to prevent the Process from being unable to continue when no condition is matched.
Common uses of the default path include:
- Enter a manual review Node.
- Enter a general handling Node.
- Return to the previous step to complete information.
- Enter an end Node or Abnormal handling Node.
Configuration recommendations
- Use a Branch Node Name that describes the decision purpose, such as “Determine service mode” or “Determine whether Co-signature is needed”.
- Use Branch names that express business outcomes, such as “Co-signature”, “Field service”, or “Return for correction”.
- Make Branch conditions mutually exclusive where possible. Avoid having the same data Match multiple Branches.
- Always Follow the default path to ensure data that does not meet conditions can continue.
- Connect each Branch to a clear next Node.
- If conditions depend on an Automatic Node or a previous manual Node to Update Fields, verify that the Field value is written before the Branch decision.
Expected result and validation
- Start the Process with test data that meets different Branch conditions.
- Check whether the Process enters the corresponding Branch.
- Use test data that does not meet any Branch condition, and check whether the default path is Available.
- Check whether each Branch connection enters the correct next Node.
- View the Process Log and Confirm that the Branch decision result is as expected.