Execute action
- Updated: 2025/09/19
Citizen Developers and Pro Developers have access to the AI Skills package in the Bot editor based on licensing and role.
The Automation Admin creates a custom role to assign access to AI Skills to the users based on their role and task. An AI Skill consists of a Model connection (connecting to a foundational model), Prompt (consisting of a fine-tuned prompt), and Prompt Input (values defined in the AI Skill by the Pro Developer when creating it). The prompt input values can be entered directly within the automation.
- Role: AAE_Basic, Pro Developer Custom role
- Permission: Bot Creator
- Setting: Administration Settings AI Data Management Data logging settings must be enabled. The Automation Admin can enable this setting for the Pro Developer
Other requirements:
Besides the roles and permissions the Pro Developer must be connected to a Bot Agent. As part of testing the Model connection, you would have to run the bot on your desktop. Hence ensure the Bot Agent is configured to your user. If you have to switch connection to a different Control Room, see: Switch device registration between Control Room instances.
- Log in to the Control Room and navigate to Automation Create new or ‘+’ icon and choose Task Bot. You can also edit an existing Task Bot by accessing it from the Automations tab.
- In the Bot editor, add the AI Skills Execute action to the automation.
- Click the Execute action in the automation flow to display the details panel.
- Click Choose and select an AI Skill from the list you have access to, in your repository.
- When you select an AI Skill, the Prompt field is
populated with the prompt text from the AI Skill.
- The AI Skill inputs field is enabled and displays the input values
defined in the selected AI Skill. For example, if the AI Skill has two input values defined, then you would see both
the input value fields.
You can define a variable for the AI Skills inputs field to pass information to the AI Skill and receive a response from the model. The AI Skill executes the prompt based on the value entered in this field and returns values for the following fields. These are optional fields and can be defined using ‘If’ variables as per your use case:
- Save the response to a variable (optional): Displays the response from the prompt execution (output value).
- Error (optional): Captures the error status. You can define an ‘If’ variable based on the Save the response to a variable output to show an error message.
- Success Status (optional): Captures the success status. Similar to Error, you can define an ‘If’ variable based on the response output to show a success message.
Note:- Prompt data details could contain PHI, PII, or other sensitive data you choose to enter in the Prompt. Be mindful of this when testing and executing a Prompt.
- When using Grounded by knowledge base and Grounded by data store
Model connections, additional fields display the
returned citations in a table format.
The response is saved to a SampleString variable, and a table variable is automatically selected to display the citations. Each citation includes a content segment (information chunk) and a URI (URL) to the referenced chunk in the knowledge base or data store.
- When you run the automation, messages show the referenced citations in message boxes.
- Save the automation. Run and test the automation.