Published at: 2025-10-30

Configure Approval Flow Nodes

1. Approval Node Configuration

1.1 Approval Types

Type

Description

Standard Approval

In standard approval nodes, approvers can be selected from colleagues, departments, department heads, user groups, roles, process-related variables, data-related variables, or personnel object variables.

Countersign Approval

Countersign approval requires unanimous approval to pass. A single rejection will result in the entire approval being rejected.

Hierarchical Approval (Designated Level)

Follows the company’s predefined hierarchy levels. When the initiator’s department level matches or exceeds the selected level, options include process exception, designated approver, or automatic approval.

Step-by-Step Approval (Fixed Level)

Approval progresses to a fixed hierarchical level. Multiple consecutive levels can be assigned to the same approver for single approval. When the submitter’s level equals or exceeds the fixed level, options include approval by the immediate superior, process exception, designated approver, or automatic approval.

Step-by-Step Approval (Fixed Number of Levels)

Approval progresses upward by a specified number of levels. (Confirm the approval flow type before implementation)

1.2 Approval Types

1.2.1 Standard Approval

Single-approver scenario: Standard approval nodes are typically used for single-approver scenarios, such as when an operation requires approval from one person before proceeding.

1.2.2 Countersign Approval

Critical decision-making scenario: Countersign approval ensures all relevant stakeholders endorse important decisions.

  • When selecting “Countersign Approval,” you can configure the approval strategy: Unanimous Approval, Approval Ratio, or APL Code.

Countersign Strategies

  • Unanimous Approval: The node is marked as “Approved” only when all approvers agree. A single rejection marks the node as “Rejected.”

  • Approval Ratio: The node is marked as “Approved” when the ratio of approvers who agree meets or exceeds the configured threshold.

  • APL Code:

    • Custom approval strategies can be configured using functions.

    • Example strategies:

      • Mark as “Approved” only when all approvers agree.

      • Mark as “Approved” if any approver agrees.

      • Mark as “Completed” if any approver rejects.

      • Mark as “Completed” if some approvers agree and others disagree (configurable in the function).

Example function: groovy /* * Function parameters can include approval opinions for flexible strategy customization. * Return true for countersign approval, false for rejection, or null for node exception. */ log.info(opinions) log.info(taskId) log.info(name) return true;

1.2.3 Hierarchical Approval (Designated Level)

Sales Order Approval Scenario: For critical clients or high-value sales orders, designate a specific level (e.g., Sales Director) to ensure accuracy and compliance.

1.2.4 Step-by-Step Approval (Fixed Level)

Fund Approval Scenario: For large expenditures or investments, multi-level approval ensures compliance and accuracy.

1.2.5 Step-by-Step Approval (Fixed Number of Levels)

Purchase Request Scenario: For procurement requests, fixed-level approval (e.g., department head, procurement, finance) ensures authenticity and compliance.

picture coming soon:

picture coming soon:

1.3 Node Approvers

1.3.1 Select Personnel, Roles, or Variables

  • Approvers can be individuals, roles, approval roles (configured in business roles), user groups, process variables, or data variables. Multiple approver groups can be set conditionally.

  • Data variables support trigger object fields and lookup-associated object fields.

1.3.2 Based on APL Code

  • Complex approver logic can be configured using APL functions.

1.3.3 Based on Configuration Table

  1. Select Configuration Table Object:

    • Enable “Based on Configuration Table,” then add and select the configuration table object.

  2. Set Matching Conditions:

    • Left field: Select a field from the configuration table (field type determines right-field options).

    • Right field: Select a corresponding field from the trigger or associated object (supports personnel, departments, or external entities).

    • Multiple conditions can be combined with AND/OR logic.

  3. Sorting Rules:

    • Default: Created time (descending). Up to three fields can be sorted (ascending/descending).

  4. Specify Approver Field:

    • Select a personnel field (single/multi-select, including external personnel) from the configuration table.

1.3.4 Default Approver

  • If no approver is identified, a default approver (individual, role, user group, or variable) can be specified.

1.3.5 Other Options

Name

Description

Auto-approve if approver and initiator are the same

The node is auto-approved if the approver and initiator match.

Return to current node after resubmission or designated node processing

After rejection, resubmission returns to the rejected node without re-approval.

Allow approvers to edit locked data

Approvers can modify data even when locked.

Auto-approve if historical node approver is the same

Rejected nodes resubmitted are not considered “historical.”

picture coming soon:

1.4 Configure Approval Content

Options: No Content, Custom Form, Process Layout.

1.4.1 No Content

No content is configured. Approvers can directly approve without additional input.

1.4.2 Custom Form

Configure fields from the trigger object (sub-object fields are excluded). Fields can be set as required or read-only. Approvers can view/edit these fields.
Note: Enable “Allow editing configured node content” to display fields.

1.4.3 Process Layout

Select or create a process layout (only one allowed). Layouts can include primary and sub-object fields for unified editing.
Note: Enable “Allow editing configured node content” to display the layout.

1.4.4 Other Notes

  • Required fields in the object list are defaulted as required in forms/layouts.

  • Read-only fields can be overridden in approval nodes.

  • Date range fields are only configurable via process layouts.

picture coming soon:

picture coming soon:

1.5 Configure Rejection Content

Options: No Content, Custom Form, Process Layout.

1.5.1 No Content

Rejections require only comments.

1.5.2 Custom Form

Mandatory fields for rejection. “Allow editing configured node content” cannot be disabled.

1.5.3 Process Layout

For complex rejections (e.g., involving primary/sub-object fields).

1.6 Mandatory Approval Comments

Configure whether comments are required for approvals/rejections. Node settings override global settings.

1.7 Button Settings

  • Show/hide and reorder buttons. The first three buttons are displayed; others are under “More.”

  • Customize button labels.

picture coming soon:

1.8 Node Timeout

Set timeout durations (minutes/hours/days) to trigger CRM reminders.

1.9 Timeout Policy

Custom actions can be executed via functions after timeout.

1.10 Additional Reminders

Configure CRM/email reminders (pre/post timeout) and task/copy reminders.

1.11 Post-Approval/Rejection Actions

Options: Field updates, CRM reminders, emails, SMS, external notifications, APL code execution, variable assignment, or team changes.

1.12 Preconditions

Set conditions for approval (e.g., object fields, lookup fields, department, personnel attributes).

picture coming soon:

2. Multi-Branch Node Configuration

2.1 Description

Multi-branch nodes require at least two nodes. Entry depends on meeting branch conditions.

picture coming soon:

2.2 Condition Name

Customize branch names.

2.3 Condition Details

Set object fields as entry conditions.

picture coming soon:

picture coming soon:

3. Task Collaboration Node

3.1 Description

Collaborators complete assigned tasks before progressing.

picture coming soon:

3.2 Select Approvers

Same as approval nodes (personnel, roles, variables, APL code, or configuration tables). Default approvers can be set.

3.3 Configure Node Content

3.3.1 Approval Content

Configure object fields (required/read-only).

3.3.2 Process Layout

Copy or create layouts (based on object detail pages).

3.3.3 Editable Content

Enable/disable editing for approvers.

3.4 Button Settings

Reorder buttons (first three displayed; others under “More”). Customize labels.

3.5 Node Timeout

Control maximum node duration.

3.6 Timeout Policy

Define actions after timeout.

3.7 Additional Reminders

Configure task/CRM reminders.

3.8 Post-Approval Actions

Same as approval nodes.

picture coming soon:

picture coming soon:

4. Parallel Gateway Node

4.1 Description

Tasks are sent simultaneously to multiple nodes/approvers for parallel processing.

4.2 Other Configurations

Refer to Task Collaboration Node.

5. Wait Node

5.1 Delay Wait

Pause and resume the process at a future time.

5.2 Conditional Wait

Delay until conditions are met.

picture coming soon:

Submit Feedback
Previous
Approval Process Configuration
Next
Configuring Post-Approval Process Actions