Read and Review Automation Anywhere Documentation

Automation 360

Close Contents

Contents

Open Contents

Update bots to default package version

  • Updated: 2022/06/22
    • Automation 360 v.x
    • Manage
    • RPA Workspace

Update bots to default package version

You can perform a bulk update to existing bots in the Control Room repository to set the default version for any package. This feature enables a quick update to a secure, stable package version across bots.

Prerequisites

  • Ensure you have an AAE_Admin role or Manage packages to update bots to the default package version.

    When you begin the bulk update process, this action will update bots for which you have check-out permission and bots using the non-default version of the specific package.

  • Verify the bots are compatible with the current default version of the package.
  • When you updating bots to the default package version, ensure the bots are not checked out until the process is complete.
  • Do not disable the package when the bulk update process is running.
Note: Updating bots in bulk to use the default package version might affect the performance of the Control Room repository or other Control Room features.

Procedure

  1. Navigate to Manage > Packages.
  2. Search for the package that you want to update across bots.
  3. To set the default package version in all the bots in the public workspace, click Update bots to default package version.
  4. In the Update bots to default package version window, enter the following information:
    • Activity name: Name of the initiated process for bulk updating package version across all the bots.

      On the Audit log page, when you select Update default package to bot requested or Update default package to bot completed to view the details of the item name, the activity name is displayed as a request name with its value.

    • Description: Optionally provide a description for this activity.
    • Check-in comments: This field is already populated with the version details of the package you are updating.

      You can enter a meaningful comment that helps with any future reference. This check-in comment can be viewed on the View history page. For example, navigate to Automation > Public > Folder > Task Bot. Click the vertical ellipsis and select View history Task Bot to view the bulk check-in message for new versions of the bots created through the bulk update.

    Note: Running the bulk update process will not impact any existing schedules or bot runs. For schedules, the bots with Production label applied will continue to deploy the production version and not the latest version.
  5. Click Update Bots.
  6. Click Yes, continue.
    The system starts updating all the bots in the Control Room repository that uses the package. If any of the bots are not using the default version of the packages, these bots will be updated.
  7. Navigate to Administration > Audit log.
  8. On the Audit log page, search by the event type Update default package.
    View information such as start of the requested process, individual bots that are being updated with the default package version, and the completion of the requested process. You can also view the following item names in the Audit log for this information:
    • Update default package to bot requested
    • List of bots that are being updated, for example, Payrollprocess2022 bot
    • Update default package to bot completed
  9. To view details about all the bots that were updated to use the default package version, copy the Request ID from the Update default package to bot requested page. On the Audit log page, search by Request ID filter and enter the value.
    For example, use d6adb0724340666e. The Audit log page displays all the bots that are successfully updated through the Update bots to default version process. The list also includes bots that failed the update process.
  10. To view the details of each item name on the Audit log page, perform the following steps:
    1. Click Update default package to bot requested and view the following details:
      • Event details: Displays information such as details of the user who submitted the request, the user's device details, the request ID number, date and time of the initiated request, and the package version details that will be updated across all the bots.
      • Update default package details: Displays information such as the name of the request, change in package version, name of the package being updated, and the version of the package you are currently on.
      Depending on the package, all bots using the selected package will be updated one by one.
    2. Click any bot to view the following information:
      • Request name: Displays the name of the initiated request.
      • Bot path: Displays the file or folder path where the bot is located.
      • Package name: Displays the name of the package.
      • Old package version: Displays the version the package was on previously.
      • Target package version: Displays the version to which the package is being updated.
      • Old bot version: Displays the older version of the bot.
      • New bot version: Displays the current version of the bot that is being updated.
      During the bulk update process, some bots might fail to update the default package version. The failed bot displays an unsuccessful status on the Audit log page. For example, if the bots are checked out during the update package process, the package version update is not performed for these bots and they fail.
    3. Click Update default package to bot completed to view the information after the bulk update process is completed:
      • Number of bots that are successfully updated.
      • Number of bots that failed to update due to compile-time errors or bots that were checked-out during the update package process.
      • Number of skipped bots.

        If the bots are using the same package version, they will display as skipped during the update process.

      • The old package package number and the target (default) package version number.
For an example of this procedure, see Example of updating default package version across bots.
Send Feedback