You can delete older package versions from the Control Room if these packages are not being used in any public repository automations.

Important: When you use Delete unused versions feature, it might result in the deletion of some packages that are used by automations in the public repository under specific conditions.

If package versions are deleted and you want to re-download a specific package into the Control Room, you can use this URL to download it:

https://aai-artifacts.my.automationanywhere.digital/packages/<package-file-name>-<version.number>.jar.

For example, if you want to download Application package 3.8.0, then use this URL: https://aai-artifacts.my.automationanywhere.digital/packages/bot-command-application-3.8.0.jar

For detailed steps on downloading a package and manually adding it to the Control Room, see Add packages to the Control Room

Overview

Automation 360 On-Premises users can now delete unused package versions. This helps users delete package versions that do not meet their security policies. Removing old package versions that are not used in any of the automations also saves storage costs and simplifies infrastructure.

Use the Delete unused package versions feature to delete package versions in a controlled manner, ensuring that only necessary and up-to-date versions are retained.
Note: The Delete unused package versions feature is available only for On-Premises deployments.

The following image shows the process of removing older versions:


Deleting unused package versions process
  • New package versions are installed in the Control Room through Automation 360 release updates and periodic package updates.
  • The system scans every hour to identify which package versions are used in automations.
  • After the scan is complete, the packages page displays unused versions of specific packages.
  • You can choose to delete specific versions that are not in use.

Benefits

Deleting older versions provides the following benefits:
  • Improves security by providing an option to delete older versions that can have potential vulnerabilities.

    This enhances maintenance by eliminating the need to store unused package versions.

  • Deleting older versions that are not used in any of the public repository automations can save storage costs and simplify infrastructure.
  • Selecting and deleting specific versions that are not in use gives you full control over your package maintenance.