Migrate legacy bot action in Bot Migration
- Updated: 2023/09/14
Migrate legacy bot action in Bot Migration
The Migrate legacy bot action enables you to migrate the Enterprise 11 and Enterprise 10 bot files to Automation 360 format.
Settings
Starting from Automation 360 v.24R2 release for IE EOL, the Migrate bot action is renamed as Migrate legacy bot .
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.
- Use the Control Room file, Desktop file, or Variable tab to specify the location of the bot you want to migrate.
- In the Output folder path field, specify the location
where you want to save the log files generated for the bot
migration. Note: Ensure that the location you have specified exists on the device.
The system does not upload the bot if it fails during the migration process. The system creates an XML report at the same location that provides information that helps you to troubleshoot if the system encounters an error during migrating the bot file.
- Select the Overwrite the file if exists check box to overwrite an existing bot file.
- Set a time-out value for migrating the bots within the range of 3 through 90 minutes (default value is 90
minutes).
If the migration of any specific bot is not completed within the set time, the bot will display a timeout message with the reason for the failure and the migration process will move on to the next bot.
- If you are migrating Enterprise 10 and Enterprise 11 bots that are built using Internet Explorer, select the Convert bots built using Internet Explorer to Edge with Internet Explorer mode option to convert them to Microsoft Edge with IE mode.