Update bots to default package version

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

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.

<span>Video showing bulk package updates for multiple bots and dependent files</span>

Procedure

Navigate to Administration > Bot update.
Click the Update Bots drop-down and click Package Version.
On the Update - Package Version page, define the settings.
1. Name: Shows a system-generated name for the update function.
2. Optional: Description: Add a description for the update package version function.
3. If the current version is higher than the default version, then downgrade the current version by selecting the Downgrade version if the current version is greater than default option.
4. View and search the list of available packages by the Status, Name, and Version.
5. Select the required packages and click the right arrow (→) to add your selection.
6. Select the required packages from the selection list and click Next.
You are redirected to the Bots section.
On the Select bots to update page, update bots and dependencies.
1. Select a Task Bot to process in the queue from the list.
  - Latest version: Click the Latest version tab to select the latest version of the bot.
  - Production label: Click the Production label tab to select the labeled version of the bot.
  By default, the Bots folder is selected.
  Tip: Use the search field to find a Task Bot quickly.
  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 a Task Bot to process in the queue from the list.
3. From the list of available bots, select the required bots for which you want to update the package version.
  
  Note: You can select a maximum of 100 bots with the dependencies for bulk package update.
  You can select bots based on the following parameters:
  - Type: Select one of these values: Folder, Task Bot, .ATMS Task Bot, .MBOT Task Bot, Form, and Process.
  - Name: Search the required bot by its name.
  - Code Analysis results: Select one of these values: N/A, Not scanned, No violations, Low severity, and High severity.
4. Click the right arrow (→) to add your selection.
5. Select the required bots from the selection list and click Next.
You are redirected to the Bots and Dependent Bots section.
Review the selected bots and dependencies that you selected for the update.
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 update list page displays status, name, start and end time, and duration required for the update. It also displays the number of completed, failed, skipped, and total items with last modified time, and user details (such as username) who initiated the package update.
On the Bot update list page, click the three dot icon next to the required update and click View update bot details to view a detailed report.
A report displays the following information:
- 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.

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

Automation 360