Enterprise 11: Export bots

As a Control Room user with BLM Export module permission and download privileges for Tasks, Docs, Workflows, and Reports and execute permission for MetaBots, you can export bots and dependent files in different automation environments to help manage your organization's Bot Lifecycle Management.

The exported package can then be imported into another Control Room environment. See Import bots.

Export bot files - version control disabled

  1. Go to the Bots > My Bots page.
  2. Click Export bot files.

    This opens the Select Bots page where you must select the bots that you want to export.

  3. Select Task Bot from the list of Available items.

    You can choose either all the files by selecting the check box in the header row or certain files by selecting the check boxes beside each file.

  4. Select the check box for the bots you want to export, and then click the right arrow icon.
    Note: The Selected bots panel will be available either below the Available items list or on the right of the list based on your screen's resolution. If it is below, the down arrow is displayed, and if it is on the right, the right arrow is displayed for bot selection.
  5. Click Next.
  6. In the Summary page that opens, provide the Export package name and choose to exclude a bot or dependency file from the list.
    1. Rename the package if you want to change the default export package name assigned by the system.
    2. Optionally, provide a password that will be used to import the package.

      The password should be set based on the Control Room password policy and one that can be easily remembered.

      Note: The provided password is not stored anywhere in the Control Room. If you provide a password, the package is encrypted with AES 256-Bits and cannot be accessed outside of the Control Room.
    3. Select the Exclude MetaBots option if you do not want to include the MetaBot associated with the task in the package.
      If the Task Bot comprises of dependent bots (Task Bots, MetaBots) and files, they are also automatically selected for export. The dependency type for these bots is shown as User selected if the bot or file was added by a user manually or as Supports <bot path>/<bot name> if it was included automatically by the system. This allows you to include or exclude a bot from the export package based on your automation flow.
      Note: If any dependent file appears more than once, it is included in the package only once.
  7. Click Export.

    The package is successfully exported to the default folder for downloads.

    For messages related to export, see the section Export bot files - Validations

Export bot files- version control enabled

Before you use export bot files in a Control Room that has version control, ensure that the production version of bots and their dependencies is already set.

To export bot files:

  1. Go to the Bots > My Bots page.
  2. Click Export bot files.

    This opens the Select Bots page where you must select the bots that you want to export.

  3. Select TaskBot from the list of Available items. You can choose either all the files by selecting the check box in the header row or certain files by selecting the check box beside each file.
  4. Select the check box for the bots you want to export, and then click the right arrow icon.
    Note: The Selected bots panel is displayed either below the Available items list or on the right of the list based on your screen's resolution. If it is below, the down arrow is displayed, and if it is on the right, the right arrow is displayed for bot selection.
  5. Click Next.
  6. In the Summary page that appears, provide the Export package name and or choose to exclude a bot or dependency file from the list.
    1. Rename the package if you want to change the default export package name assigned by the system.
    2. Optionally, provide a password that will be used to import the package.

      The password should be set based on the Control Room password policy and one that can be easily remembered.

      Note: The provided password is not stored anywhere in the Control Room. If you provide a password, the package is encrypted with AES 256-Bits and cannot be accessed outside of the Control Room.
      • Only those Task Bots and MetaBots are available for selection for which production version is set. Hence, if the production version is not set for Task Bots and MetaBots, they cannot be exported. For other types such as Docs, Workflows, and Reports, the files with the latest version are allowed for export.
      • If the Task Bot comprises of dependent bots (Task Bots, MetaBots) and files, they will also be selected for export. The dependency type for these bots is shown as User selected if you select the bot manually or as Supports <bot path>/<bot name> if it is included automatically because it is a dependency. This allows you to include or exclude a bot from the export package based on your automation flow.
        Note: If any dependent file appears more than once, it is included in the package only once.
    3. Select the Exclude MetaBots option if you do not want to include the MetaBot associated with the task in the package.
  7. Click Export.
    • Click Cancel if you do not want to proceed.
    • Click Back to go to the previous page.
    Note: You can export bots without having the AAE_ADMIN role. However, the dashboard related information will not be exported. To export dashboards, you must have the AAE_ADMIN role assigned to you.
    The package is successfully exported to the default folder for downloads.

    For messages related to export, see the section Export bot files - Validations

Note: If the Email settings are enabled for export and Import operations of a Bot Lifecycle Management package, an email notification is sent to the user who performs the export whether the action succeeded or failed.

Export bots - validations

When you export bot files, the system checks for the following validations during export:

  • Whether the bot or dependent file is available in the Control Room
  • Whether you have download permission (Execute permission for MetaBot) on one or more bot or dependent files of the selected bots
  • Whether the production version is set for all the selected bots or dependent files

If any of the validation fails for one or more bot, those are automatically excluded from the package and shown in the Items not allowed to export section. You can choose to either fix those error messages and come back to export or you can export the rest of the bots shown in the Items to export section.

Audit logs

An audit entry is logged in the Control Room audit log page when you export bots.