Published at: 2026-09-17
02-configure-business-activity-nodes.md
Configure Business Activity nodes for internal employees, so handlers can edit data, operate objects, maintain related objects, or add business information from process To-Do tasks.
Overview
A Business Activity node asks an employee to complete a specific business operation when the process reaches a step. Examples include Work Order confirmation, on-site work, Account grading, Account follow-up, and document completion. After you select a Business Activity node on the process canvas, configure Node Settings on the right, including node name, processing object, task, editable fields, button name, handler, default handler, and timeout rules.
Core configuration for a Business Activity node includes:
- Which object the current Business Activity targets.
- Which data record the task is executed on.
- What business action the handler must complete.
- Which fields the handling page displays and allows editing.
- Who handles the task, and how to provide a fallback when the handler is empty.
- Node completion conditions and post-completion actions.
Before you begin
- You have created a Business Process and opened the process canvas configuration page.
- You have confirmed the business object for the current node, such as Work Order, Account, Contact, Opportunity, or Related Object.
- You have confirmed the action the handler must complete, such as editing an object, operating on an object, or maintaining a Related Object.
- You have confirmed node handler rules, the default handler, and timeout requirements.
- If handlers need to edit fields, confirm field permissions, required rules, and page display requirements first.
Configure Node Settings
Select the Business Activity 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 Business Activity node on the canvas, in To-Do tasks, and in process records. Use an Action Name, such as Work Order confirmation or Account grading |
| Business description | Describes the node goal and helps the handler understand the task context. The limit is 500 characters |
| Which object this Business Activity targets | Selects the Affiliated Object of the Business Activity, such as Work Order, Account, or Opportunity |
| Which object to execute the task on | Selects the data that the handler actually operates on. Options can include current object, related data, or detail object |
| What needs to be done | Selects the action, such as edit object, operate object, select related object, or create related object |
| Set button name | Sets the main button label on the To-Do handling page, such as Fill in or Save and complete |
| Hide Complete button | Prevents the handler from completing the task directly. The process must continue through a configured editable-field page button or another action |
| Configure editable fields | Sets fields that handlers can edit in the node task. Options include no content, custom form, and process layout |
| Set the button name on the editable-field page | When you use a custom form or process layout, set the edit page button label, such as Save and complete or Save |
| Who handles this business task | Sets the node handler. 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 handler rules do not match valid users |
| Current Handler can specify the next-node handler when the node is completed | Allows the Current Handler to specify the handler of the next node at completion |
Configure the Business Activity object
A Business Activity node must first define which business object the node belongs to and which data record the handler operates on.
- In Node name, enter a task name that handlers can understand.
- In Business description, describe the node goal.
- In Which object this Business Activity targets, select the business object, such as Work Order.
- In Which object to execute the task on, select the data the handler operates on, such as related data / Work Order.
The main object defines the process context. The task execution object defines the data type that opens for the handler. These objects can be the same, or you can select a Related Object or detail object based on the Business Scenario.
Configure the handling action
What needs to be done defines the business operation that the handler completes in this Business Activity node.
Business Activity nodes support these handling actions:
| Action | Applicable scenario |
|---|---|
| Edit object | The handler must add or modify current object fields, such as Work Order confirmation information or Account grading results |
| Operate object | The handler must perform an operation on a single object record |
| Operate object (multiple) | The handler must select multiple records and run a batch operation |
| Edit related object | The handler must edit data that is related to the current process object |
| Select or create related object | The handler must associate existing data, or create and associate data |
| Batch Create related objects | The handler must create multiple related records at once |
| Create detail object | The handler must add detail records under the master object |
| Edit detail object | The handler must maintain existing detail records under the master object |
After you select a handling action, the system displays follow-up configuration items based on the action type. For example, if you select Edit object, you must configure editable fields. If you select Select or create related object, confirm the related object and creation rules.
Configure editable fields
When a node requires the handler to edit object fields, select a field display mode in Configure editable fields and configure editable fields.
| Field display mode | Description |
|---|---|
| No content | The handling page does not show editable fields. Use this when the handler only needs to click a button |
| Custom form | Manually select the fields displayed and edited in this node. Use this for a small number of key fields |
| Process layout | Uses a process layout to display fields. Use this to reuse a unified form layout |
When you configure a custom form, click Configure fields to edit to open the field configuration dialog:
- Select fields from the field list on the left.
- Add fields to the form area in the center, and arrange them in handling order.
- In field properties on the right, set Field Name, required status, and read-only status.
- To prevent handlers from changing specific fields, select Set as Read Only.
- To require handlers to fill in fields, select Set as required.
- Click Save to save field configuration.
Expose only the fields needed for the current node. Too many fields increase handling effort and can cause incorrect edits. For fields that handlers can view but cannot modify, set them to Read Only.
Configure editable-field page buttons
When a node uses a custom form or process layout, configure the button name on the editable-field page. Common buttons include:
| Button | Applicable scenario |
|---|---|
| Save and complete | The handler saves fields and completes the current node at the same time |
| Save | The handler only saves current input, and can continue editing or complete the node later |
If you select Hide Complete button, confirm that the editable-field page still has a button that can move the process forward. Otherwise, the handler cannot complete the task.
Configure handlers and routing
A Business Activity node handler determines who receives the node To-Do task. Handler configuration supports these methods:
| Method | Description |
|---|---|
| Select people, roles, or variables | Directly select colleagues, roles, process variables, or data-related personnel. Use this for common assignment rules |
| Based on APL code | Dynamically calculate handlers with code. Use this for advanced organization, region, or business rules |
| Based on configuration table | Match handlers by configuration table. Use this for product line, area, Account Type, and other rules that operations teams maintain |
Configuration steps:
- In Who handles this business task, select the handler configuration method.
- Select or add specific handler rules, such as process Initiator, service engineer, Account owner, or specified role.
- If the handler might be empty, add fallback users in Default handler when the handler is empty.
- If the Current Handler must specify the next-node handler, select Current Handler can specify the next-node handler when the node is completed.
Enable this option when frontline users must decide who handles the next step. If later nodes must be handled by fixed roles, do not enable it.
Configure timeout and reminders
A Business Activity node can set how long the task stays before timeout. Use this to remind handlers to complete tasks on time or to trigger exception handling.
- In Task timeout duration, set the node handling deadline.
- Use Select Time to select a time unit, such as hour or day.
- To configure timeout reminders or automatic handling, continue in related Reminder Settings or Expiration Strategy settings.
- Save the node configuration.
Timeout settings are suitable for Work Order SLA, Account follow-up deadlines, and data completion before approval. For key nodes, configure reminders or a default handler to prevent the process from getting stuck.
Configure completion conditions
Business Activity node completion conditions control whether the handler can complete the current node. Business Activity nodes support:
- Based on fields.
- Based on APL code.
You can configure custom Notice text to help handlers understand completion conditions. Field-based completion conditions work for rules such as required fields or status updates. APL-based conditions work for cross-object validation, advanced calculations, or combined rules.
Configure post-completion actions
After a Business Activity 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, Sales Records, change team members, variable assignment, and Conversion Rules.
For more post-action configuration, see Configure post-Business Process actions.
Configuration recommendations
- Use node names that handlers understand, such as Work Order confirmation or On-site work.
- Keep the handling action aligned with the node goal. Do not put too many business operations in one node.
- Expose only the fields needed by the current node. Set sensitive fields to Read Only or hide them.
- Configure a default handler for key nodes to prevent empty handler rules from blocking the process.
- If handlers can specify the next-node handler, confirm that later handler rules do not conflict.
- 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 handler account to open the Business Activity node task.
- Check whether Task Name, button name, editable fields, and Read Only or required rules match the configuration.
- Fill in or edit object data as required by the node.
- Check whether completion conditions restrict node completion as expected.
- After you complete the node, check whether post-actions take effect and whether the process enters the next node.
- If you configure timeout, default handler, or next-node handler assignment, validate each scenario.