Configuring Approval Processes

1. Approval Node Types

1.1 Standard Node

1.1.1 Description

A Standard approval node represents a basic approval step in the workflow. Use it for straightforward approval actions and routine flow control.

1.1.2 Use Cases

Single-approver scenarios: Standard nodes are commonly used when one person must approve an action before the workflow proceeds to the next step.

1.2 Multi-branch Node

1.2.1 Description

A Multi-branch node allows multiple parallel approval paths within the same step. Each path can have different approvers or conditions. The node is considered passed when any one branch’s conditions are satisfied.

1.2.2 Use Cases

Sales Order approval: In a CRM, Sales Order approval may require reviewers from different Departments or hierarchy levels (for example, Sales, Finance, and Operations). Multi-branch nodes enable parallel approvals so departments can review simultaneously and improve overall efficiency.

1.3 Task Collaboration Node

1.3.1 Description

A Task Collaboration node requires any one of the assigned handlers to complete the specified task or action for the workflow to move to the next node.

1.3.2 Use Cases

Account data update: When modifying an Account’s record, multiple teams may need to collaborate — sales enters the data, finance verifies accuracy and completeness, and customer service confirms contact details. Task Collaboration nodes let teams work according to the predefined flow, enhancing efficiency and data quality.

1.4 Parallel Gateway Node

1.4.1 Description

A Parallel Gateway node permits multiple operations to execute concurrently. The workflow continues only after all parallel branches finish.

1.4.2 Use Cases

Customer service request handling: When a customer submits a service request, multiple teams (e.g., technical support, customer service, after-sales) may need to work in parallel. Parallel Gateway nodes allow simultaneous handling to speed up response time and improve customer satisfaction.

1.5 Wait Node

1.5.1 Description

A Wait node pauses the workflow until specific conditions or events occur. Use it to control sequence and timing, ensuring subsequent actions only run when required conditions are met.

1.5.2 Use Cases

Approval delays: In a CRM, you may add a Wait node to pause until a manager or other stakeholder provides their approval or feedback. The workflow remains suspended at the Wait node until the necessary approval is received.

1.6 Action Node

1.6.1 Description

An Action node performs concrete operations or tasks within a workflow step, such as approvals, notifications, or data processing.

1.6.2 Use Cases

Data processing: Action nodes execute data updates, calculations, or other processing tasks in a workflow — for example, updating Account records or calculating sales totals.

1.7 Subprocess Node

1.7.1 Description

A Subprocess node embeds and composes more complex business flows within the main workflow.

1.7.2 Use Cases

Nested Business Process: In a CRM, you may need to nest or combine processes. For example, a Contract approval may call a Sales Order process or an invoice handling process. Use a Subprocess node to orchestrate these nested flows.

picture coming soon:

1.8 Branch Condition Settings for Multi-branch Nodes

• Condition scope: Branch conditions support fields from the same object only.
• Manage condition priority: Drag the condition name to adjust its priority.

Note:

• Supports up to 10 branch conditions.
• If multiple branch conditions are satisfied, the branch with higher priority is taken.
• Default branch supported: If no branches match, the workflow enters the default branch.

picture coming soon:

2. Additional Grouping Features

• If the 10-branch limit for a Multi-branch node does not meet your requirements, click the More Groups button to add additional groups.
• Standard nodes, Task Collaboration nodes, and Action nodes also support the More Groups feature.

picture coming soon:

picture coming soon: