Approval Process Configuration

1. Approval Node Types

1.1 Standard Node

1.1.1 Standard Node Description

A standard approval node in the workflow represents a basic approval step, designed for simple approval actions and process control.

1.1.2 Use Cases for Standard Nodes

Single-approver scenarios: Standard nodes are commonly used for individual approvals, such as when an action requires approval from one person before proceeding to the next step.

1.2 Multi-Branch Node

1.2.1 Multi-Branch Node Description

A multi-branch node allows multiple parallel approval paths in a workflow. Each path may involve different approvers or conditions, and the node is passed if any one of the paths meets its requirements.

1.2.2 Use Cases for Multi-Branch Nodes

Sales Order approval: In a CRM system, Sales Order approvals may involve multiple departments or hierarchical levels (e.g., Sales Dept., Finance Dept., Operations Dept.). Multi-branch nodes enable parallel approvals, improving efficiency by allowing simultaneous reviews.

1.3 Task Collaboration Node

1.3.1 Task Collaboration Node Description

This node requires any assigned member to complete a specific task or action before the workflow progresses to the next step.

1.3.2 Use Cases for Task Collaboration Nodes

Account data updates: When modifying Account details, collaboration across teams (e.g., Sales for data entry, Finance for accuracy checks, Support for contact verification) may be required. Task collaboration nodes streamline this process, ensuring efficiency and data integrity.

1.4 Parallel Gateway Node

1.4.1 Parallel Gateway Node Description

This node enables concurrent execution of multiple actions. The workflow proceeds only after all parallel branches are completed.

1.4.2 Use Cases for Parallel Gateway Nodes

Customer service request handling: When a service request is submitted, multiple teams (e.g., Technical Support, Customer Service, After-Sales) may need to act simultaneously. Parallel gateway nodes accelerate response times and enhance customer satisfaction.

1.5 Wait Node

1.5.1 Wait Node Description

A wait node pauses the workflow until a specific condition or event is met, ensuring proper sequencing and control.

1.5.2 Use Cases for Wait Nodes

Approval delays: If a workflow requires input from a manager or stakeholder, a wait node holds the process until the necessary approval is received.

1.6 Action Node

1.6.1 Action Node Description

This node executes specific tasks, such as approvals, notifications, or data processing.

1.6.2 Use Cases for Action Nodes

Data processing: Action nodes can update Account information, calculate sales figures, or perform other operations during the approval process.

1.7 Subprocess Node

1.7.1 Subprocess Node Description

Subprocess nodes embed complex workflows within a parent process, enabling modular and reusable Business Processes.

1.7.2 Use Cases for Subprocess Nodes

Nested workflows: For example, a Contract approval may trigger subprocesses like Sales Order validation or invoice processing, handled seamlessly via subprocess nodes.

picture coming soon:

1.8 Configuring Branch Conditions for Multi-Branch Nodes

• Condition details: Branch conditions only support fields from the current object.
• Priority management: Drag conditions to adjust their priority.

Notes:
- Maximum of 10 branch conditions supported.
- If multiple conditions are met, the highest-priority branch is followed.
- A default branch can be set for cases where no conditions are met.

picture coming soon:

2. Additional Grouping Features

• If the 10-branch limit is insufficient, click [More Groups] to add extra branches.
• Standard, Task Collaboration, and Action nodes also support this feature.

picture coming soon:
picture coming soon: