Business Actions
Digital Workers can query and analyze data and change values through chats or Skills. Business users often need to go further: “The customer has signed. Mark this opportunity as won.” These critical changes need clear controls over which fields can change, how they change, what conditions must be met, and who can act. The rules must be consistent and reusable.
A business action (Action) turns an established procedure into an executable standard workflow. In Capability Center → Business Actions, administrators define the object, whether to create, modify, or delete it, the required inputs, validation conditions, and changes to execute. Once published, chats and automation tasks use the same definition.
Create and Maintain Actions
Click New Business Action and select an ontology space. Describe the business goal in natural language to generate a draft, or choose Create Manually. Review the generated inputs, target object, and write operations before publishing.
Prepare Inputs
Inputs specify the information users must provide when invoking an action. Two types are available:
- Add Object Selection: Identify the business object to operate on. All attributes of the selected object can be used in subsequent write operations.
- Add Information: Add a regular input with a name and data type. Values can use Auto Discover, Fixed Value, or Reference Object Attribute to recommend information from context, preset a value, or read an attribute of an object specified earlier.
An action supports up to 20 inputs. Required information must be supplied before execution. After configuration, use Preview to check that the input names, purposes, and requirements are clear.
Configure Writes and Validation
Select Create Object, Modify Object, or Delete Object. For modification or deletion, first select the target object and the input used to locate it, then configure the attributes to write or the call parameters.
Built-in Data Update Skill updates the data source or extended attributes associated with the ontology. Call App Connection executes operations in an external business system and requires a Tool and parameter sources. If both are enabled, they run in parallel and record their results separately. Cross-system consistency is not guaranteed; success in one does not imply success in the other.
Set the rules that must be met before writing under Execution Validation Conditions. If a condition fails, the action does not run. For operations that require users to review the inputs and target first, select Require Confirmation for Every Execution.
Publish and Control Availability
Actions have three states: Draft, Published, and Offline. Publish a configured action before business users can select it in a new chat. Taking it offline removes it from subsequent selections. Maintaining actions, publishing actions, and changing target business data are each governed by their respective permissions.
When an action calls an app connection, the user still needs their own valid authorization. An administrator's action configuration does not automatically grant everyone access to the external system.