When a user creates and checks in an automation or Task Bot, it is moved into the public workspace. Users with unattended Bot Runner license who have access to the folder can then run this automation.

Ensure that you have the Run my bots permission in order to run an automation from the public workspace.

Procedure

  1. Log in to the Control Room.
  2. Click Automation > Public.
    Available automations and forms is displayed.
  3. At the top right, click Run > Run now
  4. Click the Choose button to select the automation that you want to run.
    You can select an automation that is based on either Windows or macOS platform. If the automation is not displayed in the Find a file screen, enter the name in the search field or click Browse to find it.
  5. Use the Automation and dependencies tab to review or update the following:
    • (Optional) Click the Choose button in the Automation file field to select a different automation.
    • In the Run automation and dependencies using field, select one of the following options:
      • Latest version: To select the most recent version of the automation.

        This is the default option.

      • Production label: To run the selected automation and its dependencies using any of the available production labels.
      Note: If the Production label option is selected for the parent automation, the corresponding dependent automation with the production label are also automatically selected. If any of the dependent automations does not have the production label applied, the Latest version of the automation is selected.
    • Dependencies: Available dependencies for the selected automation are displayed.
  6. Click Next.
  7. Use the Run-as users tab for the following:
    • Select the users from the list of Available run-as users table and click the right arrow to add your selection.

      The users that you have selected are listed in the Selected table. You can use the left arrow to remove any of the selected users.

    • In the Define number of run-as users to use field, choose one of the following:
      • All run-as users: Select this option to specify all the users available in the Selected table as run-as users while executing the automation.
      • Custom number of run-as users: Select this option to provide a certain number of users from the Selected table that you want to use as run-as users.

        For example, if you have 5 users in the Selected table, and you only want to use 3 as run-as users, enter 3. The 3 users listed at the top of the table are used as run-as users while executing the automation.

  8. Click Next.
  9. Use the Device pools tab to select the following:
    1. Override default device: This option is disabled by default. Review the following considerations before enabling it:
      • Default setting where Override default device is not enabled:
        • If the default device platform of the selected run-as-user does not match the automation platform, system will ignore the default device and pick a compatible device from the device pool.

          For example, if the default device platform is macOS and the automation platform is Windows, then that default device is ignored.

        • If the default device platform of the selected run-as-user matches the automation platform, system uses the default device if it is available for deployment. Otherwise, a compatible device is selected from the pool.
        • Automation deployment is rejected if the selected device pool platform does not match with automation platform.
      • If you select the Override default device check box:
        • Automation is deployed on the next available device from the device pool if the default device of the selected run-as-user is unavailable.
        • Deployment is rejected if the automation platform does not match the platform of the selected device pool.
    2. Available device pools: Select an available device pool from the list.
      Note: If you select a device pool with a platform (Windows or macOS) that is not compatible with the automation platform, the deployment will fail.
  10. Click Next.
  11. Optional: Use the Resiliency settings tab to change the following options:
    Note: The resiliency settings are not supported for macOS based automations.
    • In the Pop-up handling field, clear the Ignore unexpected pop-ups check box if you do not want to avoid any pop-ups during the automation runtime.

      This option is enabled by default. If you disable this option, any unexpected pop-ups that occur during the automation run can impact the automation or delay the runtime.

    • In the Bot execution recording field, change the following options:
      • Store bot execution recording: Clear this check box if you want to prevent the automation execution from being recorded.
      • Recording preferences: If you have opted to record automations, you can further select one of the following options for recording automation executions:
        • Only failed executions: Recording will be stored only when the automation execution fails.
        • All bot executions: Recording is stored irrespective of whether the execution is successful or failed.
  12. Optional: Use the General settings tab to change the default settings for the following options:
    • Name: Edit or rename the automation.
    • Automation priority: Click the drop-down menu to set the automation priority.

      While Medium is the default automation priority, you can change it so that automations are processed for deployment accordingly.

    • Clear the Hide bot run window check box.

      This option is enabled by default and hides the automation run progress window from view. If you disable this functionality, progress window is displayed when the automation starts.

  13. Click Run now.
    Note: If you have not set the device credentials from the My settings page, you are prompted to provide the device credentials to run the bot.
    The selected automation is deployed and a runtime window that indicates the progress is displayed at the bottom of the screen.
If you encounter issues in running a bot, refer to the following articles: