Published at: 2026-09-17

Configure post-business process actions

Automatically Update data or Trigger follow-up operations after a Business Process Node is Completed, the Process ends, or the Process is terminated.

Overview

Post-Business Process actions automatically execute operations after a Business Process reaches a specified Node or result. These operations include Field changes, notifications, task creation, data Lock or Unlock, variable assignment, Initiate Business Process, or Execute APL code. You can turn follow-up work after manual handling into Automatic System actions, which reduces manual Data Maintenance and keeps Processing Results consistent.
Post actions are usually Configured on the After completion tab of a Node. You can also Configure Actions after Process termination in the Basic Info of the Process. Node post-completion actions handle local results for a Node. Actions after Process termination restore Status, remind related Personnel, or clean temporary data when the Process is terminated.

Before you begin

  • The Business Process is created, and you are on the process canvas configuration page.
  • The target Node is Configured, and you have Confirmed its completion conditions and routing path.
  • You have Confirmed the action Trigger Timing, such as after a Node is Completed, after Approval Pass, after the Process ends, or after Process termination.
  • If you need SMS, Email, External Notification, or notifications for External Apps, Configure the corresponding services first.
  • If you need Execute APL code, Conversion Rules, or variable assignment, Confirm that Object Fields, process variables, and code permissions are Available.

Post-action Types

Post-Business Process actions can be grouped by Trigger location:
Type Trigger location Typical use
Node post-completion action Runs after a Business Activity Node, Approval Node, Co-signature Node, Automatic Node, or another Node is Completed Update Fields, Send notifications, create tasks, or enter subsequent Automatic handling based on a single Node result
Action after Process termination Runs when the Process is terminated Restore record Status, Send a termination Reminder, Unlock Business Data, or execute cleanup logic
Before you Configure post actions, Confirm whether the action should run only when a specific Node is Completed or only when the entire Process ends or terminates. If several Nodes need the same action, consider placing the action at Process completion to avoid Duplicate updates.

Supported execution actions

Post-Business Process actions Support these execution actions:
  • Field change.
  • SMS notification.
  • Initiate Business Process.
  • Email notification.
  • External Notification.
  • Execute APL code.
  • Change Owner.
  • Data Lock or Unlock.
  • New task.
  • New schedule.
  • New Sales Record.
  • Change team members.
  • Variable assignment.
  • Execute Conversion Rules.
Available actions vary by Node Type and Trigger location. Use the action list shown on the actual page.

Post-action list

Select a Node on the process canvas, and switch to the right-side After completion tab to View and Add post actions Supported by the Node.
Post-Business Process action list

Configure Field changes

Field changes automatically Update Business Object Fields after a Node is Completed, the Process ends, or the Process is terminated. For example, you can Update Process Status, Approval Decision, Account level, Owner, Date, or Amount. Field changes Support two update methods: Update current Object and Update Master/Related Object.

Update current Object

  1. On the After completion tab of the target Node, or in the action configuration area after Process termination, click Add.
  2. Select Field change.
  3. In Update method, select Update current Object.
  4. In Update the following Fields, select the current Object Fields to Update.
  5. In Change to, Configure the new Field value. You can use a fixed value, Object Field, process variable, or System variable.
  6. To Update multiple Fields, click Add Field change.
  7. Click Confirm to Save the Action Configuration.

Update Master/Related Object

  1. In Update method, select Update Master/Related Object.
  2. In Select data, select the Master Object or Related Object data to Update.
  3. In Update the following Fields, select the Fields under that Object.
  4. In Change to, Configure the new Field value.
  5. To Update multiple Fields, click Add Field change.
  6. Click Confirm to Save the Action Configuration.
Field changes are suitable when a Process result must be written back automatically. For example, after an Account grading Process Passes, Update the Account level to “Key Account”. After a Quote Approval Passes, Update the Quote Status to “Approved”.
[!NOTE] If the changed Field value violates rules or causes an exception, the Field is not changed. Examples include changing a required Field to Empty, changing Field A to Field B divided by Field C when Field C is 0, an integer calculation exceeding the maximum digits, a Field formula logic exception, or a single-select or Multi-Select Field result that does not Match option values. When you Configure Field changes, avoid having multiple post actions or Nodes Update the same Field at the same Time.
Post-Business Process Field change action

Configure SMS notifications

SMS notifications Send SMS messages to process-related Personnel, phone numbers on related Objects, or specified mobile numbers after a Process Node is Completed or the Process ends.
  1. In After completion or the post-action configuration area, select SMS notification.
  2. In SMS notification Personnel, click Add option and select recipients.
  3. To Send messages by phone numbers in Business Data, click Add option in Related Object mobile number and select the mobile number Field.
  4. To specify numbers directly, enter them in Specified recipient mobile number. Separate multiple mobile numbers with semicolons.
  5. In SMS Content, select SMS template.
  6. Select an Approved SMS template from the dropdown. To create a template, click Create template.
  7. Click Confirm to Save the Action Configuration.
[!NOTE] SMS notification requires the SMS Service to be purchased and enabled. When you use an SMS template, Confirm that the template is Approved and that template variables Match Process Object Fields, process variables, or Node variables.
Post-Business Process SMS notification action

Configure Initiate Business Process

Initiate Business Process automatically triggers another Business Process after the current Process Node is Completed or the Process ends, so you can chain processes.
  1. In After completion or the post-action configuration area, select Initiate Business Process.
  2. Select the Trigger Object for the Process.
  3. Select the Business Process to start automatically.
  4. Configure the Initiator, Related Data, and variable mapping as needed.
  5. Click Save.
This action is suitable when the result of one Process is the starting point of another. For example, after an Account filing Process is Completed, automatically start an Account grading Process. After a Work Order repair Process is Completed, automatically start a Satisfaction Follow-Up Process.
[!NOTE] The target Business Process must be Available or Enabled. The current data must meet the target Process Trigger Object, initiation scope, and trigger-condition requirements.
Post-Business Process Initiate Business Process action

Configure Email Notifications

Email Notifications Send Process results, To-Do Reminders, or handling notices to specified Users, user groups, or Email addresses after a Process Node is Completed or the Process ends.
  1. In After completion or the post-action configuration area, select Email notification.
  2. In Sender, select the System Email account that sends the message.
  3. In Specified recipient employee or user group, click Add option and select the Users or user groups.
  4. To specify Email addresses directly, enter them in Specified recipient Email. Separate multiple Email addresses with semicolons.
  5. To Cc or Bcc Designated Personnel, click Add option in Cc Personnel or Bcc Personnel.
  6. In Email Template, select an existing Email Template.
  7. To View the template Effect, click Preview. To Add a template, click New.
  8. Click Confirm to Save the Action Configuration.
[!NOTE] Before you use Email Notifications, Configure an Available sender mailbox in System mailbox management and maintain Email Templates in template management. Variables in Email Templates must Match Process Object Fields, process variables, or Node variables. Separate multiple direct recipient Email addresses with semicolons.
Post-Business Process Email notification action

Configure External Notification

External Notification notifies External Personnel, External Roles, or Downstream Enterprise Personnel in External Apps. It is suitable for connected processes that synchronize results to Agents / Distributors, Service Providers, order mall users, or other External collaborators.
  1. In After completion or the post-action configuration area, select External Notification.
  2. In External Apps, select the connected app to notify, such as a Service Provider portal.
  3. In Reminder Personnel, Configure recipients. You must select at least one recipient source:
    • Personnel data-related variables: click Add, and select personnel variables such as External related teams or External Users.
    • External Role Personnel of Downstream Enterprise: select a Downstream Enterprise External Role, and click Add option to select specific Role Personnel.
  4. In Jump link, select the page that opens from the notification, such as the Object detail page.
  5. In Notification Content, Add or Edit the notification message.
  6. On the Create notification message page, Configure the notification template:
    • Select notification Channel: for example, Mini Program message.
    • Select Mini Program: select the Mini Program that carries the message.
    • Select message template: select a created message template.
    • Template message notification: Configure variables for template Fields, such as Process Initiator, Work Order Title, related Product, Appointment start Time, or Current Approver. Click Insert variable to Insert Process Object Fields, process variables, or Node variables.
  7. In the message Preview, check whether the notification Title, Fields, and values meet expectations.
  8. Click Confirm to Save the notification message, and then click Confirm to Save the External Notification action.
[!NOTE] The current template message is also sent to Chats. Before you Configure External Notification, Confirm that External Apps, Mini Programs, and message templates are Available and that Reminder Personnel can Match valid External Personnel. Otherwise, the notification may not be delivered.
Post-Business Process External Notification action

Configure Execute APL code

Execute APL code runs automation logic in a Process post action, such as cross-Object validation, External System synchronization, advanced Field calculations, or Custom data processing.
  1. In After completion or the post-action configuration area, select Execute APL code.
  2. Select a historical function or create a function.
  3. When you create a function, enter the code Name.
  4. Enter the API Name, namespace, or other code identifier.
  5. Select the return value Type.
  6. Bind the Object.
  7. Enter a Description that explains the function purpose and Trigger scenario.
  8. Click Save.
Execute APL code is suitable for complex scenarios that standard post actions cannot cover. Before production Enablement, validate the function with test data and Configure Abnormal Reminders for key functions.
Post-Business Process Execute APL code action

Configure Change Owner

Change Owner automatically changes the Owner of Business Data to specified Personnel after a Process Node is Completed or the Process ends. It is suitable for Account grading, Account filing, Opportunity advancement, Service Work Order handling, and other Processes that hand over Accounts, Opportunities, Work Orders, or other Business Data according to the Process result.
  1. In After completion or the post-action configuration area, select Change Owner.
  2. Select the target data whose Owner must be changed, such as the current Object, Master Object, or Related Object.
  3. Select the new Owner. You can Configure by colleague, personnel variable, or data-related Personnel Field.
  4. Click Save.
[!NOTE] Change Owner affects subsequent data ownership, Visibility, and collaboration responsibility. Before configuration, Confirm that the new Owner has permission to View and handle the data, and avoid conflicts with other Field changes or team member change actions.
Change Owner

Configure new tasks

New tasks automatically create follow-up tasks and Assign them to specified Personnel after a Process Node is Completed or the Process ends.
  1. In After completion or the post-action configuration area, select New task.
  2. In Content, enter the task Title and task Content. The Title limit is 50 characters, and the Content limit is 10000 characters. Both Support Insert variable.
  3. In Deadline Date, enter or select a variable to set the task Deadline.
  4. In Assign to, click Add option and select Executors.
  5. In Reminder, select the Reminder method or Reminder recipients.
  6. In Cc, click Add option and Configure the Cc scope.
  7. In Trigger Object, select the Business Object associated with the task.
  8. Click Confirm to Save the Action Configuration.
In the Content editor, click Insert variable to reference Process Object Fields or process variables and dynamically generate the task Title and Content. For example, you can write the Process Initiator, Work Order Title, Account Name, or Node result into the Task Description for follow-up.
New tasks are suitable for arranging follow-up after a Process is Completed, such as creating a “Send Quote” task after Quote Approval Passes or a “Customer follow-up” task after a Service Work Order is Completed.
Post-Business Process new task action

Configure new schedules

New schedules automatically create a schedule after the Process is Completed and invite related Personnel.
  1. In After completion or the post-action configuration area, select New schedule.
  2. In Content, enter the schedule Content. The limit is 10000 characters and Supports Insert variable.
  3. In Participants, click Add option and select Personnel to participate.
  4. In Start Time and End Time, enter Time, or select variables as the Time Source.
  5. To create an All Day schedule, select All Day schedule.
  6. In Reminder, select the Reminder method or Reminder Time.
  7. In Trigger Object, select the Business Object associated with the schedule.
  8. Click Confirm to Save the Action Configuration.
In the Content editor, click Insert variable to reference Process Object Fields or process variables and dynamically generate schedule Content. Start Time and End Time can also use Object Fields or process variables. This is suitable for creating schedules based on Work Order appointment Time, Account Visit Time, or Delivery Confirmation Time.
New schedules are suitable for converting Process results into Time arrangements, such as Account visits, on-site Service, contract review Meetings, or Delivery confirmation Meetings.
Post-Business Process new schedule action

Configure New Sales Record

New Sales Record automatically creates a Sales follow-up record after the Process is Completed and synchronizes the Process result to follow-up history for Accounts, Opportunities, Work Orders, or other Business Data.
  1. In After completion or the post-action configuration area, select New Sales Record.
  2. In Content, enter Sales record Content. The limit is 10000 characters and Supports Insert variable.
  3. In Type, select the Sales record Type.
  4. In Cc, click Add option and select the Personnel or scope that needs synchronized View access to the Sales record.
  5. In Trigger Object, select the Business Object associated with the Sales record.
  6. Click Confirm to Save the Action Configuration.
In the Content editor, click Insert variable to reference Process Object Fields or process variables and dynamically generate Sales Records Content. For example, you can record the Process Initiator, Work Order Title, Account Name, Processing Result, or Current Handler.
This action is suitable for automatically generating Sales process records after Account grading, Quote Approval, Opportunity advancement, Service Work Order handling, or Account filing Processes, so follow-up review and tracking are easier.
Post-Business Process New Sales Record action

Configure change team members

Change team members automatically adds members to a Business Data team or removes members from it after a Process Node is Completed or the Process ends, and controls member access permissions.
Configuration item Description
Change operation Select Add or Remove team members
Internal members Add colleagues, departments, user groups, Roles, Approval Roles, data-related variables, process variables, or personnel Object variables
External members Add External Personnel Fields, External Owner, or other External member sources
Permission When adding members, set Read Only or Read/Write
Configuration steps:
  1. In After completion or the post-action configuration area, select Change team members.
  2. In Change operation, select Add or Remove.
  3. To change internal Enterprise members, click Add option in Internal members, and select colleagues, departments, user groups, Roles, Approval Roles, data-related variables, process variables, or personnel Object variables as needed.
  4. To change External members, click Add option in External members, and select External Personnel Fields or External Owner as needed.
  5. Select Permission. You can set it to Read Only or Read/Write.
  6. Click Confirm to Save the Action Configuration.
  7. After you return to the process designer, click Save in the upper-right corner to Save the Business Process.
[!NOTE] When adding members, Confirm the permission scope at the same Time. If members only need to View Process-related data, select Read Only. If members need to continue editing or maintaining the data, select Read/Write. When you use Remove Member, Confirm that the change does not affect subsequent data collaboration.
Post-Business Process change team members action

Configure data Lock or Unlock

Data Lock or Unlock controls whether Master Object or Related Object data can be edited after a Process Node is Completed, the Process ends, or the Process is terminated.
  1. In After completion or the post-action configuration area, select Data Lock or Unlock.
  2. Select the Operation Type: Lock or Unlock.
  3. Select target data, such as the current Object, Master Object, or Related Object.
  4. Click Save.
Common uses include locking a Quote after a Process starts to prevent changes during Approval, and unlocking Account, Quote, or Work Order data after Approval Passes or the Process is terminated. Confirm the Usage Object before you Save the action.
[!TIP] If both Lock and Unlock actions are Configured in the Process, check their Trigger Nodes and Trigger conditions. Avoid unlocking data too early or leaving it uneditable after the Process ends.
Post-Business Process data Lock or Unlock action

Configure variable assignment

Variable assignment Updates process variables while the Process runs. Subsequent Nodes, Branch conditions, notification templates, or APL code can reuse these variables.
  1. In After completion or the post-action configuration area, select Variable assignment.
  2. Select the target process variable.
  3. Configure the assignment Content. You can use a fixed value, Object Field, Node result, or another variable.
  4. Click Save.
Variable assignment is suitable for calculating or recording results in the first half of the Process and reusing them in subsequent configuration. For example, record the Account grading result, Approval conclusion, External System return value, or next Node Handler.

Configure Execute Conversion Rules

Execute Conversion Rules automatically runs business conversion logic after the Process is Completed. Examples include Convert to Account from Lead, Convert from Quote to order, or generating target Business Data according to Enterprise configuration.
  1. In After completion or the post-action configuration area, select Execute Conversion Rules.
  2. Select the Conversion Rules to execute.
  3. Configure Source data, target data, and Field mapping according to rule requirements.
  4. Click Save.
Execute Conversion Rules is suitable for converting Process Approval results into formal Business Data. Before configuration, Confirm that the Conversion Rules are Enabled and that the current Process Object meets the execution conditions of the Conversion Rules.
Post-Business Process Execute Conversion Rules action

Configure actions after Process termination

Actions after Process termination run only when the Process is terminated. They do not run when the Process completes normally. Use them to restore Business Data Status or notify related Personnel after Abnormal Termination.
  1. In Basic Info or the action configuration area after Process termination, click Add.
  2. Select an action Type, such as Field change, Execute APL code, CRM Reminder, or Data Lock or Unlock.
  3. Complete action parameter configuration.
  4. To Add multiple post-termination actions, continue adding them and drag to adjust Execution Order.
  5. Save the Process configuration.
When you Configure post-termination actions, focus on these items:
  • Whether the Process Status must be Updated to “Terminated”.
  • Whether data locked during the Process must be Unlocked.
  • Whether the Process Initiator, Current Handler, or Process admin must be notified.
  • Whether Execute APL code is needed to clean temporary data or synchronize an External System.

Configuration recommendations

  • Check the Enable Status of related Processes or rules before relying on post actions.
  • First Confirm the post-action Trigger Timing, and then select the action Type.
  • Configure empty-Handler Reminders or post-action Abnormal Reminders for key Nodes to prevent stuck Processes or unattended Automatic operation failures.
  • Let only one post action Update the same Field where possible, to avoid results being overwritten by Execution Order.
  • Notification actions must use Content that business users can understand. Include the Process Name, Business Object, and Processing Result where possible.
  • For External Notification, Email, SMS, or APL code actions, validate the full flow with test data before Enablement.
  • For Lock, Unlock, Conversion Rules, and other actions that affect data Status, verify results in a test environment first.

Expected result and validation

  1. Run the target Business Process with test data.
  2. Complete the Node that has post actions Configured, and check whether post actions Trigger at the expected Time.
  3. Check whether Fields, variables, Lock Status, and conversion results meet expectations.
  4. Check whether SMS, Email, External Notification, and CRM Reminders are Sent Successfully.
  5. Check whether new tasks, schedules, and Sales Records are generated, and Confirm that Owner, Time, Related Object, and Content are correct.
  6. Check whether the initiated Business Process starts, and Confirm that the Initiator, Related Data, and variable mapping are correct.
  7. If actions after Process termination are Configured, manually Terminate the test Process, and Confirm termination Reminders, Field restoration, data Unlock, and APL code execution results.

FAQ

Why did the post action not execute?

Check whether the target Node is Completed, the post action is Saved Successfully, Trigger conditions are met, the Process follows the expected path, and the required Service or permission for the execution action is Available.

Why was the Field not Updated?

Check whether the Field is in the updatable Data Range, whether the Field value complies with Field Type and validation rules, whether the current User or System action has Update permission, and whether another post action overwrote the Field.

Why was the notification not delivered?

Check whether SMS, Email, or External Notification services are enabled, recipients, mobile numbers, or Email addresses are valid, template variables Match, and External Personnel are within the notification scope.

When should I use variable assignment?

Use variable assignment when subsequent Nodes, Branch conditions, notification templates, or APL code need to reuse Processing Results from earlier Nodes. Save the result first, and then reference it later.

When should I Configure an action after Process termination?

Configure an action after Process termination only when the action must run after the Process is Terminated. Examples include unlocking data, restoring Status, notifying the Process admin, or cleaning temporary data.

Related topics

Submit Feedback
Previous
01-create-a-business-process.md
Next
Manage business processes