Published at: 2026-09-17
Configure approval nodes
Configure approval types, assignees, approval content, and node rules.
Overview
An Approval Node lets specified assignees Approve, Reject, or complete Joint Approval. It is the core node in an Approval Process.
Before you begin
- The Approval Process is created.
- You have identified the approval type.
- You have identified the assignee source.
- You have identified the approval content and rejection content.
Configure Node Settings
In Node Settings, configure the node name and node description. The node name appears on the process canvas, in the to-do list, and in approval records. Use a clear business name, such as Commercial and legal review comments.
The Node Settings page also includes tabs such as Entry Conditions and Completion Conditions. Configure them as needed.
Configure the approval type
| Type | Description |
|---|---|
| Standard approval | Applies to approval by one user or users in a Specified Range |
| Joint Approval | Requires multiple users to approve together and supports pass policies |
| Hierarchy approval (specified level-one approval) | Specifies level-one approval by company hierarchy |
| Step-by-step approval (approval to fixed level) | Approves step by step to a specified department level |
| Step-by-step approval (fixed number of levels) | Approves upward for a fixed number of levels |
Joint Approval supports pass policies such as all approve, approval ratio, and APL code.
Standard approval applies to scenarios with one owner, a fixed role, or assignees resolved by variables. Joint Approval applies to important decisions that require confirmation from multiple users. Hierarchy approval and step-by-step approval apply to expenses, orders, contracts, and other scenarios that require organizational control.
Configure the Joint Approval policy
Joint Approval supports:
- All approve.
- Approval ratio.
- APL code.
When you use APL code, you can define policies such as pass when all users approve, pass when any user approves, complete when any user rejects, or let a function decide.
An APL Joint Approval policy can read approval comments, task ID, and node name. The function returns
true when Joint Approval passes, false when Joint Approval fails, and null when the node has an exception.log.info(opinions);
log.info(taskId);
log.info(name);
return true;
Configure node assignees
Assignees support:
- Select users, roles, or variables.
- Based on APL code.
- Based on configuration table.
- Group assignees.
When you select Select users, roles, or variables, you can add the process initiator, roles, users, process variables, and other values as assignees.
Select assignees based on a configuration table
- In Node Assignee, select Based on Configuration Table.
- Click Add.
- Select the configuration table object.
- Set matching conditions.
- Configure sorting rules.
- Select a user field in the configuration table as the assignee field.
Matching conditions support AND and OR. Sorting rules use Created On in descending order by default and support up to three sorting fields.
Configuration table assignee selection applies to scenarios such as finding approvers by region, product line, or account level. Fields on the left come from the configuration table object. Fields on the right come from the trigger object or related objects. User, department, External Personnel, and external department fields can be used as matching conditions.
Configure the default assignee
When the node assignee is empty, you can specify a default assignee. The default assignee supports users, roles, approval roles, user groups, process variables, and data variables.
[!WARNING] Dynamic assignees can resolve to empty. Configure a default assignee for key nodes.
Configure automatic pass rules
An Approval Node supports these rules:
- After rejection, jump to the current node after resubmission or after a specified node is processed.
- Allow the current node approver to operate on data. This applies when data is locked.
- Automatically pass when the current node approver is the same as the process initiator.
- Automatically pass when a historical node has the same approver.
- Merge handling when consecutive nodes have the same approver.
Nodes with configured approval content cannot pass automatically.
Configure approval content
| Method | Description |
|---|---|
| No Content | The approver directly approves or rejects |
| Custom Form | Configures trigger object fields and supports required or read-only settings |
| Process Layout | Supports editing fields from the main object and child objects together |
After you configure Custom Form or Process Layout, select Allow editing of configured node content. Otherwise, the configured content does not appear during approver handling.
When you select Process Layout, you can click Configure Process Layout and maintain the custom layout used by the current node.
Date range fields can be configured only through Process Layout.
Custom Form only configures trigger object fields. It does not support child object fields of the trigger object. Process Layout can configure fields from the main object and child objects at the same time, and supports layout rules. If an object field is required, it is required in node content by default. If an object field is not required, you can set it as required in the node as needed.
Configure rejection content
Rejection content supports No Content, Custom Form, and Process Layout. Custom Form and Process Layout apply when approvers must add fields or detailed explanations during rejection.
When rejection content is configured as Custom Form or Process Layout, the system requires the assignee to fill in the configured fields. This configuration is commonly used to require approvers to add rejection reasons, correction requirements, or next-step instructions.
Configure required approval comments
Required approval comments support global configuration, approval, and rejection. Node configuration takes priority over global configuration. You can set whether comments are required for approval and rejection separately.
Configure buttons
Buttons support display, hide, sorting, and custom names. Among displayed buttons, the first three appear directly, and the other buttons move under More.
Common buttons include Approve, Reject, Change Handler, Recall Approval, Retrieve, Read, and Pre-assign.
Button names affect assignee understanding. Keep core verbs such as Approve and Reject. Change names only when the business meaning is clear, such as Approve contract or Return for supplement.
Configure duration, timeout, and reminders
| Configuration item | Description |
|---|---|
| Node residence duration | Controls the maximum time that the node can stay. Supported units are minutes, hours, and days |
| Expiration Strategy | Runs custom actions through a function after timeout |
| More reminders | Supports CRM reminders, email reminders, to-do reminders, and Cc reminders |
Pre-timeout reminders are useful for urging users to act. Post-timeout reminders are useful for escalation. Node residence duration controls only the current node, not the deadline of the entire process.
Configure completion conditions
Completion Conditions limit the Approve operation. They support fields on this object, Lookup object fields, owner’s primary department, users, and user attributes.
Completion Conditions constrain only the Approve operation. If an approver does not meet completion conditions, the system blocks handling based on the configured prompt.
Expected result and verification
- Use a test record to trigger approval.
- Check whether assignees are correct.
- Check whether approval content appears.
- Test Approve, Reject, and timeout reminders.