You can quickly update bots to a secure, stable, and default package version across multiple bots.

Ensure that only Control Room administrators perform the bulk package update process.
Note: Automations and the corresponding details such as such as status, name start time, end time, duration, reason why the automation failed, skipped or stopped, and so on will be deleted automatically after 30 days from the Bot updates table that is available in Administration > Bot update page. For information on data retention and cleanup policy, see Data retention policy.

However, you can view audit log details for bulk package updates and automations. See View audit log for bulk package updates.

Prerequisites

  • To update bots to the default package version, ensure you have the View packages permission and the permission to edit bots .

    When you begin the bulk update process, this action updates the bots in a Public workspace for which you have check-out permission, and any bots using the non-default version of the specific package.

  • To view the Bot update page in the Control Room and to view the bulk update reports, ensure that you have the View bot update permission.
  • To perform the bulk package update action, ensure that you have the Manage bot update permission.
  • Verify the bots are compatible with the current default version of the package.
  • Navigate to Administration > Settings > Bots > Bot validation to turn on the bot validation.
  • When you update the bots to the default package version, ensure that the bots are not checked out until the process is completed.
  • Do not disable the package while the bulk update process is running.

Procedure

  1. Navigate to Administration > Bot update.
    Bot update list page provides a comprehensive view of the following:
    • Update status, including the number of completed, failed, skipped, and stopped bots.
    • Details such as status, name, start and end time, duration required for the update.
    • User details (such as username) who initiated the package update.
  2. Click Update Bots > > Package Version.
    Update - Package Version page is displayed.
  3. On the Settings page, update the following:
    1. Name: Shows a system-generated name for the update function.
    2. Description (optional): Add a description for the update package version function.
    3. Optional: Select the Downgrade version if the current version is greater than default check box if the current package version is higher than the default version.
      Note: If you downgrade the packages, then the bot might show an error. This happens because the higher version of the package might have additional attributes that are not available in the lower version.
    4. In the Available packages table, select the required packages and click the right arrow (→) to add your selection.
    5. Click Next. is displayed.
  4. On the Select bots to update page, update the following:
    1. Use the Update bots and dependencies using field to select one of the following tabs:
      • Latest version: To select the latest version of the bot.
      • Production label: To select the labeled version of the bot.
        Note: If you select the Production label option for the parent bot, then 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, then the latest version of the bot is selected.
    2. Select one of the following check boxes:
      • Update all bots: To update all the bots and dependent files that require an update and use these packages.
      • Custom: To update specific bots.
        Note: By default, the Bots folder is selected.
        1. From the Available files table, select a Task Bot for which you want to update the package version.
          Tip: You can use the search field to find a Task Bot quickly.
          Note: You can select a maximum of 1000 bots with the dependencies for bulk package update.
        2. Click the right arrow (→) to add your selection.
        3. Click Next.
  5. Use the Review bots and dependencies for update page to review the selected bots and dependencies that you have selected for the update.
  6. Click Update-Package Version.
    The system starts updating all the selected bots and dependencies in the Control Room repository which contain the selected packages. If any of the bots are not using the default version of the packages, those bots are updated. The Bot updates table is now updated and displays the updated bots.
    Note: When you update the bots to default package version, and if the process fails in between, the system will continue to update the remaining bots without any disruption.

    Consider a scenario where you are updating a large number of bots, say 1000, and a batch of 100 fails due to an issue. Despite this, the system allows the remaining 900 bots to continue processing, demonstrating its scalability.

  7. In order to view the update summary of a bot that you have update, hover over that bot in the Bot updates table, and click the ellipses (three dots) and click the View update bot details icon.
    A report is displayed with the following tabs:
    • Summary: Summary of the package update process with selected bots and dependencies.
    • Settings: Settings defined in the package update process with selected packages.
    • Results: Result of the package update process with these details such as status, type of bot, name of the bots and dependent files, folder path, name of the Bot Runner, and reason why the bot skipped or failed status.
    Note: Click Stop activity to cancel a bulk package update activity that is currently in progress. You can use this option to stop the bulk update process for any reason, such as the process run takes longer time than expected. When you stop the process, a confirmation message displays the total number of bots selected to use the default package version and the number of bots that have been updated so far.

    As the bots are being processed in batches of 100, stopping the process in between might take some time. When you stop the process midway, it will finish processing the currently running batch before stopping.

    For example, consider you selected 200 bots to update the package version and immediately clicked the Stop button to cancel the bulk update process. As the bulk update process was initiated and you stopped it halfway, it will stop after it completes updating one batch of 100 bots.

For an example of this procedure, see Example of updating default package version across bots .