Export bots - You can export a bot from one Control Room to another.

Automation 360

You can export a bot from one Control Room to another.

Before you begin

  • You can export automations and files from either the Private or Public workspace. To export from your Private workspace, ensure that you have the Export bots permission. You can export automations that you created in your Private workspace. Citizen Developers with the required permission can also export supported automations from their Private workspace.

  • Ensure that you have the View package permissions.
  • Ensure that you have the View content rights at the folder level from which you want to export the bots.
  • Ensure that the Control Room builds and packages in the source and target Control Room instances are the same for export as well as import.
  • Ensure that the default maximum size for individual bot is 50 MB. However, the total export (zip/bundle) file can be up to 1 GB in size.

About this task

Review the guidelines before you export bots.

Guidelines for exporting and importing bots

Procedure

  1. On the left pane, click Automation.
    A list of available bots and forms is displayed.
  2. Select the Private or Public workspace that contains the automations or files that you want to export.
  3. Start the export using one of the available options:
    • Select Manage bots > Export> .
    • Select one or more items and use the table-level Export option.
    • For an individual item, open the actions menu and select Export.
  4. Select the automations and files to export, and then click Next.
    • Latest version: Click Latest version tab to select the latest version of the bot.
    • Labeled version: Click Production version tab to select the labeled version of the bot.
    When exporting from the Private workspace, the export page displays the items from your Private workspace. You can add or remove items from the export selection.
    Note:

    The Latest version and Production version options are not available when exporting from the Private workspace.

  5. Click Next.
    The bot dependencies are displayed in the Select dependencies window. If the production label option is selected for the parent bot, the corresponding dependent bots with the production label are also automatically selected. If any of the dependent bots do not have the production label applied, the latest version of the bot is selected.
  6. Select the dependencies to export and click Next.
    All related packages are displayed.
  7. Select the necessary packages associated with the automations to export.
    Select Exclude bot packages to remove all packages from the export.
  8. (Optional) Use the Global values to select the Include global values check box if you want to include any available global values with the bot.
    Note:
    • Only the users or roles associated with the View and manage global values permission can select the option to include global values while exporting a bot.
    • Only the global values associated with Task Bots and API Tasks are included.
    • When you export a bot with global values, it includes the global value with changeable scope across the Control Room (both source and target).
    • The option to include Global values is available only when exporting from the Public workspace. It is not available when exporting automations and files from the Private workspace.
  9. Optional: Create and confirm a password.
    Password enhances the security for your bot or file when exporting from one Control Room to another.
  10. Click Export bots and files.
    All the selected bots are exported into a zip file.

    Based on the result (failure or success) of the export bot functionality, a notification is also displayed in the Control Room Notifications icon. For more information, see Automation events event notification.

    Note: If you have analytics bots in your Control Room, all the Bot Insight dashboards (default, custom, and published) associated with the bots are also exported into the zip file.
    If you have configured SMTP, an email is sent that contains a link to the zip file of the exported package.
    If you have not configured SMTP, perform the following steps to access the link to the zip file of the exported package:
    1. Navigate to Activity > Historical.
    2. Search and view the historical activity of the exported package.
    3. Click Download exported zip file.
      A link to download the zip file is displayed.
  11. Use the link to download the zip file and save it to a location for importing it to another Control Room.
    Note:
    • If you are exporting a large size bot or dependency, there might be a delay in the download of the export zip file from the Activity > Historical page.
    • All the exported zip files older than 30 days will be automatically deleted.

What to do next

You can import the exported ZIP file into either the Private or Public workspace of the target Control Room. For more details, see Import bots.