Published at: 2026-09-17

06-configure-automatic-nodes.md

Configure business nodes that the system runs automatically, so the process can complete field updates, notifications, Business Process initiation, code execution, and similar actions without manual handling.

Overview

An Automatic Node runs one or more preset actions automatically when a Business Process reaches a specified step. Unlike manual nodes such as Business Activity, Approval Node, and Co-signature nodes, an Automatic Node does not generate a To-Do task for manual handling. The process continues after the system actions are completed.

After you select Automatic Node on the process canvas and drag it to the canvas, configure Node Settings on the right. Settings include node name, business description, business object, task execution object, and automatic execution actions.

Core configuration for an Automatic Node includes:

Which business object the current Automatic Node targets.
Which Business Data record the task acts on.
Configure one or more actions for automatic execution.
Adjust the Execution Order of multiple automatic actions.
Configure required parameters for CRM reminders, Designated Personnel, Initiate Business Process, APL code, External Notification, and similar actions.
Validate whether automatic actions run as expected, and check process logs.

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, Opportunity, Quote, or Related Object.
You have confirmed the actions the Automatic Node must run, such as field update, SMS notification, Initiate Business Process, Email Notifications, or Execute APL code.
To call external systems, send notifications, or run code, confirm that interfaces, templates, recipients, variables, and Data Permission settings are available.
If multiple automatic actions have dependencies, confirm their Execution Order first.

Configure Node Settings

Select the Automatic 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 Automatic Node on the canvas and in process records. Use an action-oriented name, such as Automatically Update Status for Work Order or Send Service Evaluation notification
Business description	Describes the purpose of the Automatic Node and helps administrators understand its goal. The limit is 500 characters
Which object this Business Activity targets	Selects the main business object handled by the current Automatic Node, such as Work Order
Which Work Order to execute the task on	Selects the data source actually handled by the node, such as related data / Work Order
What this task needs to do	Adds actions that the system runs automatically. You can add multiple actions and drag them to adjust Execution Order

Configure the business object and task data

An Automatic Node must first define the object it handles and the actual task data.

In Node name, enter an automatic node name that is easy to identify.
In Business description, describe the system action that the Automatic Node completes.
In Which object this Business Activity targets, select the object associated with the current Business Activity, such as Work Order.
In Which Work Order to execute the task on, select the data source for task execution, such as Related data / Work Order.

The business object determines which data the Automatic Node can read and update. Task data determines which record the automatic action affects. Ensure that the selected object matches the process context.

Configure automatic execution actions

In What this task needs to do, click Add and select the action that the system runs automatically. If you add multiple actions, drag them to adjust Execution Order.

Automatic actions shown in the screenshot include:

Automatic action	Description	Common use
Field update	Automatically updates target object field values	Update Status for a Work Order, write Processing Result, or modify a stage field
SMS notification	Sends SMS messages to specified recipients	Notify Accounts, engineers, or Service Providers about handling progress
Initiate Business Process	Automatically starts another Business Process	Create a later approval, supplemental process, or collaboration process
Email Notifications	Sends emails to specified recipients	Send handling results, service reports, or internal notices
External Notification	Sends notifications or callbacks to external systems	Synchronize Process Status or notify a third-party system
Execute APL code	Runs custom business logic	Advanced calculation, cross-object handling, or dynamic judgment
Change Owner	Automatically changes the owner of Business Data	Work Order handover or Account owner adjustment
CRM reminder	Creates CRM-related reminders	Remind sales, service, or operations users to follow up
Data lock or unlock	Locks or unlocks Business Data	Lock data during Approval Process handling, and unlock it after the process ends
Task	Automatically creates a task	Create a follow-up task or correction task
Schedule	Automatically creates a schedule	Arrange On-site Repair or follow-up plans
New Sales Record / Sales Records	Automatically creates a Sales Records entry	Record Account communication, service follow-up, or a sales action
Change team members	Automatically adjusts Business Data team members	Add collaborators, remove members, or adjust permissions
Variable assignment	Assigns values to process or business variables	Save intermediate results or pass parameters to later nodes
Conversion Rules	Runs business data conversion rules	Generate a target object or synchronize conversion results

Configure field updates

Field updates automatically update fields on the business object.

In automatic actions, select Field update.
Select the field to update.
Configure the new field value. You can use fixed values, variables, or expressions.
Save the action configuration.

Field updates are useful for automatically updating status, stages, Processing Result values, time fields, or flag fields. Avoid repeatedly updating the same field in multiple nodes, so one status does not overwrite another.

Configure notification actions

Notification actions include SMS notification, Email Notifications, External Notification, and CRM reminder.

In automatic actions, select the notification type.
Configure recipients, such as users, roles, variables, mobile numbers, email addresses, or external system addresses.
Configure notification content or a notification template.
If notification content references business fields, confirm that field variables return values correctly.
Save the Action Configuration.

Notification actions are suitable for automatically reminding related personnel at key process nodes, or synchronizing process status to external systems. For External Notification actions, confirm interface retry, failure records, and exception handling.

Configure Initiate Business Process

Initiate Business Process automatically creates another Business Process instance when the current process reaches the Automatic Node.

In automatic actions, select Initiate Business Process.
Select the target process to initiate.
Configure the business object, initiation data, and parameters required by the target process.
Save the Action Configuration.

Use this action when a main process triggers a subprocess, cross-team collaboration process, or supplemental approval process. Before configuration, confirm that the target process is enabled and that initiation data meets the target process start conditions.

Configure Execute APL code

Execute APL code handles advanced business logic.

In automatic actions, select Execute APL code.
Configure the code to run, or select existing code logic.
Confirm that code parameters can access the current business object, task data, process instance, and other context.
Save the Action Configuration.

APL code is suitable for cross-object calculation, advanced field processing, dynamic assignment, and data assembly before external interface calls. Before launch, use test data to validate code results and exception branches.

Configure data and collaboration actions

Data and collaboration actions include Change Owner, data lock or unlock, task, schedule, Sales Records, change team members, variable assignment, and Conversion Rules.

Action	Configuration focus
Change Owner	Confirm the new owner source, and whether team members or permissions must be synchronized
Data lock or unlock	Confirm the locked object, lock scope, and unlock timing
Task	Confirm task title, owner, Deadline, and associated data
Schedule	Confirm schedule time, participants, location, and Related to Business Data
Sales Records	Confirm record type, content, owner, and Account relationship
Change team members	Confirm added or removed members, member permissions, and data Visibility
Variable assignment	Confirm variable type, assignment source, and how later nodes reference it
Conversion Rules	Confirm the conversion rule, source object, target object, and duplicate-execution handling

Configure multiple-action Execution Order

An Automatic Node can contain multiple actions. Multiple actions run in the configured Execution Order.

Configuration recommendations:

Run data preparation actions first, such as variable assignment and field update.
Run data generation or collaboration actions next, such as Initiate Business Process, create task, or Conversion Rules.
Run notification actions last, such as SMS notification, Email Notifications, or External Notification.

If a later action depends on the result of an earlier action, check the action order carefully. For example, update the Work Order status first, and then send a status change notification.

Configuration recommendations

Use an Automatic Node name that directly describes the system action, such as Automatically update Work Order status or Auto Send evaluation notification.
Configure a clear business object and task data for each Automatic Node to avoid acting on the wrong record.
When multiple automatic actions have dependencies, arrange them in business order.
For External Notification, Initiate Business Process, APL code, and similar actions, configure troubleshooting methods or failure reminders.
Avoid updating the same field in an Automatic Node, manual node, Approval Node, or post-action at the same time.
For notification sending, use test accounts to validate recipients, template variables, and content format.
For data lock, Change Owner, or team member changes, also validate Data Permission effects.

Expected result and validation

Start a test Business Process.
Let the process reach the Automatic Node.
Check whether the process continues without manual handling.
Check whether field updates, notification sending, process initiation, APL code, task creation, and other actions run in the configured Execution Order.
View process logs or execution records, and confirm that automatic actions succeed.
If you configure External Notification or interface actions, check whether the external system receives the request.
If you configure data lock, Change Owner, or team member changes, check whether Business Data permissions and status match expectations.