Add a Bot task to a process automation to launch a bot that automates repetitive tasks. A Bot task is a building block that executes individual,repetitive tasks within a process.
Procedure
-
Drag the Bot Task element from the left panel onto the
editor.
-
In the Task: Bot properties panel, enter a unique identifier
in the Element ID field.
This value is used only as an internal reference during design and must be unique within the process. Example: InvoiceProcessing_BotTask or DataExtraction_Bot.
-
In the Task name (optional) field, enter a display name
for this task.
This name appears as a reference during process execution. Example Extract Invoice Data.
-
Select the Hide this task from users check box.
After the task completes, the task does not appear to the user in the web interface.
-
In the Bot field, click Choose to
browse and select the bot to run.
Example, browse to \Bots\Finance\ and select
InvoiceExtraction. - After selecting the bot, configure the input variables in the Input values section. Input variables appear after you select the bot. Map each variable to a value or variable from the current process.
-
In the Execution mode field, you can select how the bot task executes; locally on the request creator's desktop or
remotely.
From the Execution mode drop-down, you can select the following modes:
- Remote execution: (default) When selected, the local bot executes remotely based on your Global/Process Scheduler settings and generates a corresponding entry in the Audit log. With remote execution, automations can run independently while users work on other tasks and are notified in Automation Co-Pilot when the automations have completed.
- Local execution (main window): When selected, the local bot executes on the main window of the request creator's device and generates a corresponding entry in the Audit log. The request must be created by a user with an attended license and have selected a default device; otherwise, the Bot Task execution mode defaults to Remote execution. Local execution enables sensitive data to remain On-Premises and incur no queue times on local desktops.
- Local execution (child window): When selected, the local bot executes on a child window of the request creator's device and generates a corresponding entry in the Audit log. The request must be created by a user with an attended license and have selected a default device; otherwise, the Bot Task execution mode defaults to Remote execution. Local execution enables sensitive data to remain On-Premises and incur no queue times on local desktops. The automation execution occurs in the child window, so the user's machine is still available for use.
Note:- When creating variables, Execution mode is considered a String variable source.
- The user executing the automation locally with main or child window must have attended Bot Runner license with Run my bots permission.
-
In the Queue timeout section, set the maximum time to wait
for the bot to start. Enter values in the hours, minutes, and seconds fields.
Minimum is 1 minute; maximum is 24 hours. For example: 4 hours, 30 minutes,0 seconds. If the bot does not start within this time, the task times out.
-
In the Data privacy tag (optional) field, enter text or a
variable to tag this task for data privacy searches. This is an additional hidden
field used to search for data privacy purposes. Variables are populated at runtime.
For example, enter
PII_InvoiceData, or select (x) to use a process variable such as $PrivacyTag_Variable$. -
In the Annotation section, select Add
annotation to add context, assumptions, or references for this step.
Example: This bot task extracts line items from scanned invoices. Requires
InvoiceExtractionbot version 3.2 or higher. For more details about annotations, see About annotations. -
Click Save.
You have now configured the Bot Task in your process automation.