Add Bot Task to a process automation

As a Bot Creator, you can create a Bot Task to execute inside a process automation.

Procedure

  1. Add a Bot Task to the process automation by dragging the element from the Element panel.
  2. From the Bot Task panel:
    1. Enter a name in the Element name field.
    2. Enter the task name in the Task name field.
      The task display name appears in the web interface as a reference. You can use a Reference ID such as ref ID = $RefId$.
    3. Optional: Select the Hide this task after completion check box.
      After task completion, the user does not see the Bot Task in the web interface.

      To display the hidden task, select the View hidden tasks check box in the tasks view page of the web interface.

    4. Browse and select the Task Bot in the Select Task Bot field.
    5. In the Run bot and dependencies using section, select a label version.

      You can select Latest version (default) or Production label.

      The bot deploys the version that you select.
    6. In the Bot priority section, you can review your bot priority level.
      Note: The bot priority level is a read-only label that shows Low, Medium, or High depending on the priority level that was set for the bot.
      Important: If the priority of a task bot was changed, you need to browse for the task bot again to reflect the correct priority status for an existing Process Composer process automation.
    7. As a Bot Creator, you can select how the Bot Task executes; locally on the request creator's desktop or remotely.
      From the Bot Task 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.
      Once the local bot task has been deployed, a progress bar along with controls display within the Automation Co-Pilot window showing the bot progress details and status in real time. Using these controls (start, pause, and stop), you can manage your automation execution. To manage these controls the user running the automation must have the View my activity and Manage my activity permissions.
    8. Optional: In the Data privacy tag field, enter a text or variable to generate hidden custom output.
      Select the Input values check box and specify a variable.
      The variable input expected by the bot is mapped with the variable that will be populated when creating the request.
      1. Select a task in the Process task field.
      2. Select a type in the Variable type field. You can select Input, Output, or Meta. When you select the Use as input check box, the process automation passes data into the input variables, and when you select the Use as output check box, the process automation retrieves data from the output variables after the bot execution. See Supported variable types in Process Composer.
      3. Specify your variable in the Variable field.
        Note: Reference ID is a Meta variable type.
      4. Click Apply.
  3. Click Save.
    You have now configured the Bot Task in your process automation.
Additional resource: Go to this learning course to learn about how to execute desktop automations in Process Composer: Executing desktop automations in Process Composer.