You can update multiple packages to default version for multiple bots. This feature enables you to update multiple package versions across all available bots with one action thereby increasing the efficiency of a bulk package update. Additionally, you can review the bots and dependencies before a bulk update.

Overview

In an enterprise business, maintaining a large number of bots with default and up-to-date packages is a tedious and time-consuming process. You cannot update those packages manually because you need to check the latest released package version and then update them for any required bots.

The Bot update feature in the Automation 360 platform provides a multiple package version update for multiple bots with dependencies. With one action, you can update multiple packages, bots that contain selected packages, and dependent bots.
Note: The bulk update package feature is designed to function correctly. However, errors might occasionally occur (though these are not consistent occurrences). For example, when you edit a bot in the Bot editor after the bulk package update to the default package version, some actions might display an error due to missing input values. In such cases, you can update the package version manually or make changes in the bot to resolve the issue.

Bulk package version updates for multiple bots

Benefits

The Bot update feature provides the following benefits:
  • Ability to select more than one package

    You can view a list of all the available packages and select to update all the required packages instead of updating one package at a time. Also, you can update packages to their default versions for the required bots.

  • Ability to select only required and multiple bots

    You can select only the required bots that you want to update with default package version instead of selecting all bots for update. This decreases the time required to complete the update functionality.

  • Advanced reporting to view progress of bulk package updates
    The Automation 360 platform provides a comprehensive report to view the progress of a bulk update of a package with the user's information. It also provides the following details:
    • Number of packages considered for the update
    • Number of bots updated with default package version
    • Number of bots for which package version is updated successfully
    • Number of bots for which package version update is unsuccessful
    • Number of bots for which package version update is pending
    • Total time elapsed in bulk package version update
    • User who started the bulk package update operation
    • All packages, bots, and dependencies selected by the user
  • Enhanced compiler for accurate results

    With an upgraded compiler, the Automation 360 platform improves the overall accuracy and outcome of the bulk package version update processes.

Bot update types

When you start a bulk update process using Update all bots or the Custom option, the system efficiently updates the bots in batches of 100, allowing you to continue with all repository activities. Only the bots that are actively processed by the batch will not be available for repository operations. However, if you try to attempt a file that is being worked on, that will not be allowed. The system notifies through an appropriate error message.

For example, consider an On-Premises Control Room cluster consisting of three nodes. When you start a bulk update process using the Update all bots option, the bots are modified in batches of 100, processing a total of 300 files. The files being updated are the only ones for which you cannot perform repository operations. However, you can actively work on the rest of the files. If you attempt to work on the files being updated, an error message is displayed indicating that you cannot perform repository operations. You can continue to work with the entire repository, ensuring business continuity. The system performance is optimized to significantly reduce the time taken to complete the bulk update package process, thus improving performance.
Recommended: Ensure that only Control Room administrators perform the bulk package update process.

You can choose from the following options to update multiple package versions across all available bots to the default version:

  • Update all bots

    When updating multiple packages to their default versions, you can choose to update all bots and dependencies that use those packages and need an update. This feature empowers enterprise organizations with thousands of bots that need to be updated to the default package version and provides greater control over their bots.

    With a single click, you can update all the bots in your public workspace to the default package version, regardless of how many you have. This eliminates the need to select each bot manually and simplifies the process of updating multiple packages to the default version for multiple bots with dependencies.

    Updating package version using update all bots option

  • Custom

    With the custom option, you have the flexibility to manually select only the required bots and dependent files that you want to update with the default package version. This tailored approach reduces the time required to complete the update functionality, catering to your needs. You can select up to 1000 bots with the dependencies for bulk package updates. This significant increase in limit has improved the performance of the bulk update process, helping you quickly update your packages and saving you valuable time.

    Updating package version using custom option