Published at: 2026-09-17
05-configure-extension-elements.md
Learn about extension elements in a Business Process, and use them to configure industry extension nodes.
Overview
Process extension elements are extensible component capabilities provided by the process platform. Business teams can register industry application capabilities as business nodes on the process canvas based on their business features and industry requirements. Then administrators can drag these nodes directly into process orchestration.
Extension elements enhance personalized process customization. With extension elements, you can connect order acceptance, dispatch, service, follow-up, evaluation, sign-off, and other industry business actions to a process without waiting for a process platform release. This makes Business Process design more aligned with real operations.
On the Business Process canvas, click Extension on the left to view connected industry extension nodes. After you drag an extension element to the canvas, configure the business object, task data, Operation Type, operation rules, operation interface, operation buttons, and Task Handler in Node Settings on the right.
Core values of extension elements include:
- Support business teams in connecting custom nodes by industry Business Scenario.
- Support unified orchestration of industry application capabilities on the process canvas.
- Support node rendering and task handling through configuration, without rebuilding the process platform for each scenario.
- Support different node types, such as manual nodes and Automatic Node entries.
- Support interaction with business objects, task instances, process instances, and extension configurations.
Application scenarios
Extension elements are suitable for scenarios where Business Process differences are significant, many industry handling actions exist, or business application capabilities must be connected flexibly.
| Scenario | Description | Example |
|---|---|---|
| Manufacturing | Optimizes after-sales service and on-site service processes, and improves Work Order handling efficiency and service quality | Service Work Order acceptance, Work Order assignment, On-site Repair, On-site Standard Operation, Service Evaluation |
| SFA in-sales business | Connects key actions in the in-sales process chain to improve process flexibility and collaboration efficiency | CPQ, contract signing, Sales Order, shipping order, outbound order, Payment Plan, receivables order, Invoice Application, Payment Collection |
| Healthcare | Customizes patient diagnosis and treatment processes, and connects business steps in the treatment journey | Registration, consultation, inspection, diagnosis, treatment, discharge |
| Finance | Orchestrates compliance, risk control, and Account Management processes | Risk assessment, loan approval, Account Management |
Available extension elements can vary by tenant or industry package. Use the actual page as the source of truth.
View extension elements
After you open the Business Process configuration page, click Extension in the left toolbar of the process canvas. The system opens the Extension elements panel.
The extension elements panel displays extension nodes connected by industry teams. You can search or browse by group, and then drag nodes to the process canvas.
In the screenshot, extension elements are grouped by Business Scenario. Common groups include:
| Group | Description | Example nodes |
|---|---|---|
| Service app | Internal business nodes for enterprise personnel to handle service-related business | Assign engineer, assign service group, assign Service Provider, Service Team Internal Assignment, engineer accepts order, On-site Standard Operation, inspection group, service report, Service Evaluation, service fee confirmation, service follow-up, service product consumption, repair part sign-off, repair part return |
| Service Provider portal | Nodes for External Service Provider collaboration, used by Service Provider users to handle process tasks | Assign Service Provider, engineer accepts order, On-site Standard Operation, Service Evaluation |
| Terminal user portal | External terminal user nodes, used by Accounts or terminal users to handle process tasks | Terminal user handling, terminal user task, Account sign-off |
Configure extension element nodes
After you drag an extension element to the canvas and select the node, configure node information on the Node Settings tab on the right. Configuration items vary dynamically by business capability.
| Configuration item | Description |
|---|---|
| Node name | The Name of the current extension node on the canvas, in To-Do tasks, and in process records. Use a specific business action, such as Service Evaluation (Service Provider) or Account sign-off |
| Business description | Describes the processing goal of the current node and helps handlers understand the task context. The limit is 500 characters |
| Which object this Business Activity targets | Selects the main business object handled by the current extension 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 |
| Operation Type | Selects the industry business action that the node runs, such as order acceptance, dispatch, service, follow-up, or evaluation |
| Operation rules | Configures execution rules for the business action. Some nodes can redirect to an industry configuration page for further configuration |
| Operation interface | Selects the interface used by the handler, such as process layout, template, or industry application page |
| Who handles the task | Sets the Task Handler. You can select personnel, roles, variables, Service Provider Engineer, service group, or another business source |
| Set operation button names | Sets button labels on the handling page, and hides some buttons as needed |
| Auto-complete node | Sets whether the node automatically completes after a specified time to prevent long process stays |
| Change Business Status when the node starts | Sets the Business Status written automatically at node start, such as changing Work Order status to Service Evaluation |
| Task timeout duration | Sets the node handling deadline for reminders or exception handling |
Configuration example: Service Evaluation node
The extension element selected in the screenshot is Service Evaluation (Service Provider). This node lets a Service Provider Engineer or related handler complete a Service Evaluation task.
Configuration steps:
- In Node name, enter a node name, such as Service Evaluation (Service Provider).
- In Which object this Business Activity targets, select Work Order.
- In Which Work Order to execute the task on, select the data source for task execution, such as Related data / Work Order.
- In Select Service Evaluation method, select a method, such as QR code evaluation.
- In Select Service Evaluation template, select a template, such as On-site Repair.
- In Who handles the task, confirm the handler rule, such as Work Order.Service Provider Engineer. To adjust it, click Edit.
- In Set operation button names, configure button labels, such as Evaluation QR code and Skip evaluation.
- To hide a button, select Hide next to it.
- To allow multiple evaluation submissions for the same task, select Allow multiple evaluation submissions.
- To complete the node automatically after a specified time, select Auto-complete evaluation node and set the auto-completion duration.
- In When the node starts, change Work Order status to, select the Work Order status after the node starts.
- Save the node configuration.
The page prompt states that some Service Evaluation capabilities require object layouts for external terminal users. During configuration, also check the evaluation template, object layout, and Data Permission for external users.
Element capability notes
Extension elements are usually registered to the process platform by business teams or industry applications. The platform displays, renders, and executes elements based on element configuration information.
Business elements
A business element is the base definition of an extension element. It usually includes:
| Capability | Description |
|---|---|
| Basic Info | Includes element name, ApiName, node type, related object, and other metadata |
| Node type | Supports manual nodes and Automatic Node types, and determines whether handlers participate |
| Invocation method | Supports calling business capabilities by REST API or Function |
| Idempotency requirement | The execution interface for the extension element must support idempotency to prevent duplicate business results during process retry |
| Input parameters | Can include element definition information, extension information, object ID, object ApiName, task or node ID, instance ID, process Name, and other context |
When the invocation method is REST, you usually configure URL, Header, Result Body, and related information. When the invocation method is Function, the platform usually calls custom logic by FunctionApiName.
Groups and plugin group strategies
Extension elements can be managed and displayed by group. A group usually includes a group name and ApiName. When an element is registered, its group, node type, and related object can be specified. This helps administrators find nodes by Business Scenario on the left side of the canvas.
Element rendering and execution
Extension element rendering and execution usually have two layers:
| Type | Description |
|---|---|
| Element rendering | The platform displays draggable nodes in the extension elements panel based on element definitions and extension configuration information |
| Node rendering | After a node is dragged to the canvas, the platform displays configuration items in the right panel based on element configuration information and current node Basic Info |
| Node execution | When the process reaches the node, the platform calls the industry business capability based on node configuration and passes object, task, node, and process instance context to the business side |
Configure completion conditions
Extension node completion conditions control whether the handler can complete the current node. Configure rules on the Completion conditions tab on the right.
Common completion conditions include:
| Condition type | Description |
|---|---|
| Based on fields | Use for rules such as Evaluation result must be filled in, Sign-off status must be confirmed, or Service report must be uploaded |
| Based on APL code | Use for cross-object validation, advanced calculations, or combined rules |
Configure clear prompts for key completion conditions so handlers understand which information to add.
Configure post-completion actions
After an extension node is completed, you can configure post-actions on the After completion tab on the right. Use 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 node names that include the business action and processing object, such as Service Evaluation (Service Provider) or Account sign-off.
- Before selecting an extension element, confirm whether the task is handled by internal personnel, a Service Provider, or a terminal user.
- Validate portal accounts, Data Permission settings, and object layouts before you use external Service Provider or terminal user nodes.
- For template-based nodes, confirm template content, field permissions, and applicable scenarios.
- For Automatic Node or interface-call nodes, confirm idempotency to prevent duplicate execution from causing data exceptions.
- If the node might have no handler, configure timeout, reminders, or auto-completion to prevent the process from staying too long.
- After you configure completion conditions and post-actions, validate the full path with test data.
Expected result and validation
- Start a test Business Process.
- Check whether the extension node enters the pending state in process order.
- Use the corresponding handler account to open the task, such as an internal employee, Service Provider Engineer, or terminal user.
- Check whether the node name, business object, task data, template, button name, and Task Handler match the configuration.
- Execute the node task, such as submitting an evaluation, accepting an order, completing on-site work, or signing off as the Account.
- Check whether the process continues routing as expected.
- If you configure auto-completion, Business Status changes, completion conditions, or post-completion actions, validate each scenario.
- If the node runs business logic through an interface or Function, check whether it returns success and whether repeated execution avoids duplicate data.