Packages lifecycle in Automation 360 Cloud
The Automation Anywhere software lifecycle policy aims to make the latest software (including new and enhanced packages) available to customers quickly for better change management.
- Predictability: With faster deployment cycles, you can get access to new and enhanced packages sooner than before.
- Deploy new features: With faster build cycles, you can test new features and deploy them at your own pace.
- Quality: With faster deployment cycles, you can use packages that include critical bug and security fixes.
- Nondisruptive access: You can update packages without disrupting your existing configurations.
- Backward compatibility: You now have the option to roll back to a previous version of a package.
The following image shows the advantages of using this package lifecycle:
Support policy for packages
Packages are compatible with all Control Room and Bot Agent versions that are released within 24 months of releasing a package version. Any bot using a package version can continue to use that version until 2 years from the release of that package version.
The following image shows the workflow of packages in Automation 360 Cloud:
- How a Control Room administrator manages packages
By default, Automation 360 Cloud is configured to enable you to use the latest build for packages when they are deployed. The latest build will then be the default build when users create new bots or when they edit existing bots. As the Control Room administrator, you can also disable this option so that the latest builds are not used.
- How bot developers use packages
When the automatic update of packages is enabled in the Control Room, a bot developer can use the latest version of a package to test the version before making it available to other users. The developer can nondisruptively test and enable the build without making any changes to the existing configuration of the bots.
If the bot developer does not want to use a specific build for a package, they can manually roll back to a previous build that they want to use. This option to roll back provides full control to the bot developer for choosing the appropriate versions for packages.註: This capability has no impact on existing bots. Existing bots continue to run unchanged. The new package versions are also backward-compatible with the existing platform version.
Configure default version for packages
By default, Automation 360 Cloud enables you to use the latest build for packages when they are deployed.
As an administrator, you can disable this option so that the latest builds are not used:
- Log in to the Control Room as an administrator.
- Navigate to .
- In the Automatically set the default version setting, select Off.
Roll back your package version
The latest package version is set as the default version.
If the Control Room administrator has enabled the option to use the latest version of the package as default, botdevelopers can test and enable newer versions before making it available for other users. The bot developer can also roll back to a previous version.
- Log in to the Control Room as a Bot Creator.
- Open a bot for which you want to change the package version in the Bot editor.
- Select the action for which you want to change the package version.
- Click the options menu on the top-right corner of the screen and click Packages.
- On the Packages settings page, click Bot Migration.
- Click the change version drop-down list and select the version that you want the action to use.
- Click Change version.