Bot migration package
The Bot migration package enables you to migrate Enterprise 10 and Enterprise 11 bots to Automation 360 format. The package also enables you to convert Enterprise 10, Enterprise 11, or Automation 360 bots that use Internet Explorer to Microsoft Edge with IE mode. This package is used internally by the Bot Migration Wizard and the Update Bot wizard.
The Bot migration package does not migrate dependencies and other entities such as credential variables, AAApplicationPath system variable, and global values that are required to run the migrated bot.
Action in the Bot migration package
The Bot migration package includes the following action:
|Migrate legacy bot||Starting from Automation 360 v.24R2 release for IE EOL, the Migrate bot action is renamed as Migrate legacy bot.
Migrates the Enterprise 11 and Enterprise 10 and bot file to Automation 360 format and uploads the migrated file to the specified location in your private repository with the same name as .atmx and .mbot file. This action only migrates the bot you specify, but does not migrate its dependencies. Dependencies are the bots and other files that are required to run the bot. You must migrate the dependent bots separately and upload other files manually to Control Room.
All the bots migrated using the Bot migration package are stored in the Bots folder in Automation 360. If you have to migrate a parent bot and its child bots separately using the Bot migration package, you must create the same folder structure as in Enterprise 11 or Enterprise 10 and move the dependent bots to these folders for the parent bot to run successfully.
|Update bot||This action converts Automation 360 bots that are built using Internet Explorer browser to Microsoft Edge Chromium with IE mode. This action is internally used by the Update Bot wizard to convert the bots.
Nota: This action cannot be used manually in a new or an existing bot for bot conversion.