Updating to v.32 release

Review requirements and support information about updating your Control Room and Bot Agent for the v.32 release.

Bot Agent updates

Note: This release includes an optional Bot Agent update. You can continue to run your existing bots without updating the Bot Agent. However, if you want to use the new features in Automation 360 v.32, you must update the Bot Agent available with this release.

While the Bot Agent update is optional in most of the updates rolled out for Automation 360, in environments where auto-update is enabled but auto-deploy is disabled for triggers, you need to log in to the browser session after the update is rolled out to activate the trigger listener.

For more information on updating to this release, see these resources:

Certified Control Room builds for direct update

You can update to the latest version of Automation 360 from the previous three releases (that is, from n−3 releases, where n refers to the latest release).

The following previous releases are certified for update to Automation 360 v.32:
  • v.31 (Build 21094, 21023)
  • v.30 (Build 19700, 19688, 19678, 19621)
  • v.29 (Build 18399, 18381, 18371, 18345)

If you are on one of these previous releases, for information about updating, see Update Automation 360 to latest version. If you are not on an n−3 release, update Automation 360 to one of the n−3 releases before updating to Automation 360 v.32.