Bot Migration package updates

Review the updates in released versions of packagesuch as new and enhanced features as well as fixes and limitations. The page also lists the release dates of each version, and the compatible Control Room and Bot Agent versions.

Versions summary

The following table lists the versions of Bot Migration package released either with an Automation 360 release or as a package-only release (in descending order of release dates). Click the version link for information about updates in that package version.

Version Release date Release type Control Room build Bot Agent version
10.11.3 27 September 2024 With Automation 360 v.34 (Sandbox) release 21.220 or later 15224 or later
10.9.1 21 March 2024 With Automation 360 v.32 (Sandbox) release 21.220 or later 15224 or later
10.8.2 20 October 2023 With Automation 360 v.31 (Sandbox) release and periodic package update 21.220 or later 15224 or later
10.7.0 6 September 2023 and 21 September 2023 With Automation 360 v.30 (Sandbox) release and periodic package update 21.220 or later 15224 or later
10.6.2 6 June 2023 With Automation 360 v.29 (Sandbox) release 21.220 or later 15224 or later
Note:
  • To download an individual package (updated in an Automation 360 release where you want only the package), use this URL:

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

  • For Bot Migration package, the naming convention is: bot-command-migrate-<version.number>.jar

    For example, bot-command-migrate-10.9.0.jar

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

10.11.3

  • Compatible Bot Agent version: 21.220 or later
  • Compatible Control Room version: 15224 or later
Fix
You can successfully migrate a bot containing an Excel command with an Error Handling from Enterprise 11 to Automation 360.

Previously, when you migrated a bot that contained an Excel command with an Error Handling command, an extra try-catch block was added. This extra exception message would override the original error and the description.

10.9.1

  • Compatible Bot Agent version: 21.220 or later
  • Compatible Control Room version: 15224 or later
Fix
You can now migrate bots that are using the PGP Create key action.

Previously, you were unable to migrate such bots.

Service Cloud case ID: 02004364

10.9.0

  • Compatible Bot Agent version: 21.220 or later
  • Compatible Control Room version: 15224 or later
Note: This package version is also available in the Automation 360 v.32 release.
Fix
When you migrate a bot that is using the Recorder package version 2.15.2-20231004-180246, you will no longer see an error in the Set system time out option.

Previously, you were seeing an error in such a scenario.

Service Cloud case ID: 02087598
When you are migrating a bot that is using the Recorder package version 2.15.2-20231004-180246 using the Bot Migration package version 10.8.2, you will no longer see a session UI error.

Previously, you were seeing a session UI error in such a scenario.

10.8.2

  • Compatible Bot Agent version: 21.220 or later
  • Compatible Control Room version: 15224 or later
Note: This package version is also available in the Automation 360 v.31 release.
Fix
You can migrate a bot that is using an array or dictionary variable in the session field of the Database Connect command without encountering an error.

Previously, you were unable to migrate such a bot.

Service Cloud case ID: 00743352, 01938224, 01946530

Fixed security vulnerability issues. For more information, click the release download link and view the Security & Compliance reports at A-People Downloads page (Login required).
You no longer encounter any issue when you migrate a bot that contains multiple Email dictionary variable (EmailSentDate) key and run the bot in Automation 360.

Previously, it displayed an error on execution.

10.7.0

  • Compatible Bot Agent version: 21.220 or later
  • Compatible Control Room version: 15224 or later
What's changed
In Enterprise 11, if a bot was using the FTP / SFTP commands, after migration, the respective FTP / SFTP actions are assigned a local session in Automation 360.

Service Cloud case ID: 01274780

Package mapping for migration
Fix
After migration, you can successfully execute the action that is set in the DefaultAction object property of the Recorder action in a bot.

Previously, such a bot was unable to execute the action and displayed an error.

Service Cloud case ID: 01961896
You can migrate MetaBot with screens with 'play mode as image for linked objects' and 'play mode as text for main objects'.

Previously, migration of such a MetaBot was not supported.
When you migrate a MetaBot Logic that contains linked object (static text and combo box) of UI Automation technology and used in a Recorder command to Automation 360, the bot now executes successfully.

Previously, such a bot was failing to identify the combo box.
Using the Bot Migration package version 10.7.0, you can migrate and execute a bot successfully that is using the Database package version 5.1.0 and FTP / SFTP package version 2.11.0.

Service Cloud case ID: 02000852

10.6.2

  • Compatible Bot Agent version: 21.220 or later
  • Compatible Control Room version: 15224 or later
What's changed

Help Center for bot developers

Help Center: We have added an in-app help for bot developers to get contextual information about actions and packages when building automations.

In-product user assistance
Fix
Fixed security vulnerability issues.