Published at: 2026-09-17
03-configure-business-process-approval-nodes.md
Configure a business Approval Node that lets handlers approve business data and routes the process differently after approval, disapproval, or rejection.
Overview
An Approval Node asks a handler to confirm, approve, disapprove, or reject Business Data when the process reaches a specified step. After you select an Approval node on the process canvas, configure Node Settings on the right, including approval node name, business description, approval object, approval content, approval conditions, handler, default handler, button name, and timeout rules.
Core configuration for an Approval Node includes:
- Which Business Data to approve.
- Configure approval content or editable fields.
- Who approves the task, and how to provide a fallback when the handler is empty.
- Which path to enter after approval or disapproval.
- Whether the handler can edit node content.
- Whether the handler can specify the next-node handler when the node is completed.
Before you begin
- You have created a Business Process and opened the process canvas configuration page.
- You have confirmed the business object to approve in the current node, such as Work Order, Account, Opportunity, Quote, or Related Object.
- You have confirmed approver rules, the default handler, and timeout requirements.
- You have confirmed the routing path after approval and disapproval.
- If approvers need to edit content, confirm field permissions, required rules, and page display requirements first.
Configure Node Settings
Select the approval node on the process canvas. Then configure these items on the Node Settings tab on the right.
| Configuration item | Description |
|---|---|
| Node name | The name of the current Approval Node on the canvas, in To-Do tasks, and in process records. Use an action-oriented name, such as Work Order approval or Quote approval |
| Business description | Describes the approval matter and helps the handler understand the approval context. The limit is 500 characters |
| Which Business Data to approve | Selects the data approved by the current node. Options include current object, related data, and process-related Business Data |
| Configure editable fields | Sets content that the approver can edit in the node task. Options include no content, custom form, and process layout |
| Configure approval content | Sets the approval content to display or fill in, such as object fields, rich text, or collaborative rich text |
| Allow editing of configured node content | Lets the approver directly edit configured node content during approval |
| Approval conditions | Configures the routing path after approval and disapproval. Routing by Approval Decision is supported |
| Who approves this business task | Sets the node approver. You can select personnel, roles, or variables, or calculate by APL code or configuration table |
| Default handler when the handler is empty | Specifies a fallback handler when approver rules do not match valid users |
| Handler can specify the next-node handler when the node is completed | Allows the current approver to specify the next-node handler at completion |
| Set button name | Sets the main button label on the To-Do handling page, such as Approve, Reject, or Submit for approval |
| Hide Complete button | Prevents the handler from completing the task directly. The process must continue through approval results or conditions |
| Task timeout duration | Sets the node handling deadline for reminders or exception handling |
Configure the approval object
An Approval Node must first define which business object the node approves and which data record the approver handles.
- In Node name, enter an approval name that handlers can understand.
- In Business description, describe the approval goal.
- In Which Business Data to approve, select the data approved by the current node.
The approval object defines the process context. When the approver opens the To-Do task, the system displays the information that must be approved based on this object.
Configure approval content
An Approval Node can display or collect approval content. Common Content Type options include:
| Content Type | Description |
|---|---|
| No content | The approval page does not show extra approval content. Use this when the approver only needs to approve or disapprove |
| Custom form | Manually select fields to display and edit in this node. Use this for a small number of key fields |
| Process layout | Uses a process layout to display approval content. Use this to reuse a unified form layout |
In Configure approval content, select the content type to display and configure the related fields.
To let the approver directly modify approval content, select Allow editing of configured node content. If the approval content includes key fields, check field permissions and required rules.
Configure handling actions and routing
The core of an Approval Node is controlling which path the process enters after approval or disapproval.
- In Approval conditions, configure routing paths after approval and disapproval.
- If approval enters the next step, select the target node or path after approval.
- If disapproval must return for correction, select the target node or path after disapproval.
- To run different processing for different results, configure post-actions.
Use an Approval Node when the process should continue after approval and return or enter correction after disapproval. If multiple users must confirm together, use a countersign node.
Configure approvers
The Approval Node handler determines who receives the node To-Do task. Approver configuration supports these methods:
| Method | Description |
|---|---|
| Select people, roles, or variables | Directly select colleagues, roles, or process variables. Use this for common approval rules |
| Based on APL code | Dynamically calculate approvers with code. Use this for advanced organization, region, or business rules |
| Based on configuration table | Match approvers by configuration table. Use this for product line, area, Account Type, and other rules that operations teams maintain |
Configuration steps:
- In Who approves this business task, select the approver configuration method.
- Select or add specific approval rules, such as the process Initiator’s manager, Account owner, department head, or specified role.
- If the approver might be empty, add fallback users in Default handler when the handler is empty.
- To let the Current Approver specify the next-node handler, select Handler can specify the next-node handler when the node is completed.
- To change the To-Do page button label, enter a button name in Set button name.
If the process requires fixed-position approval, use roles or configuration tables. If it requires dynamic approver identification, use variables or APL code.
Configure timeout and reminders
An Approval Node can set how long the task stays before timeout. Use this to remind approvers to handle tasks on time or to trigger exception handling.
- In Task timeout duration, set the node handling deadline.
- To configure timeout reminders or automatic handling, continue in related reminder or Expiration Strategy settings.
- Save the node configuration.
Timeout settings are suitable for Work Order SLA, Account grading approval, Quote approval, and document completion approval. For key approval nodes, configure reminders and a default handler to prevent stuck processes.
Configure completion conditions
Approval Node completion conditions control whether the approver can complete the current node. Approval Node settings support field-based and APL-code-based completion conditions.
| Condition type | Description |
|---|---|
| Based on fields | Use for rules such as required fields or status updates |
| Based on APL code | Use for cross-object validation, advanced calculations, or combined rules |
You can configure custom Notice text to help approvers understand completion conditions.
Configure post-completion actions
After an Approval Node is completed, you can configure post-actions to update data or trigger later operations. Common post-actions include field update, SMS notification, Initiate Business Process, Email Notifications, External Notification, Execute APL code, Change Owner, data lock or unlock, create task, create schedule, New Sales Record, Sales Records, change team members, variable assignment, and Conversion Rules.
For more post-action configuration, see Configure post-Business Process actions.
Configuration recommendations
- Use Approval Node names that make the Approval Decision clear, such as Work Order approval or Quote approval.
- Keep approval content concise. Show only the information needed for this decision.
- Configure a default handler for key approval nodes to prevent empty approver rules from blocking the process.
- If different Approval Decision results enter different paths, check the approval and disapproval connectors first.
- If approvers can edit node content, check field permissions and required rules.
- After you configure completion conditions and post-actions, validate the full path with test data.
Expected result and validation
- Start a test Business Process.
- Use the approver account to open the Approval Node task.
- Check whether the node name, approval content, button name, and editable fields match the configuration.
- Test approval and disapproval paths separately.
- Check whether completion conditions restrict node completion as expected.
- Check whether post-actions run.
- If you configure timeout, default handler, or next-node handler assignment, validate each scenario.