Migration updates for v.26 release

Review what's new, changed, and the fixes and limitations to migrating from Enterprise 11 and 10 versions to Automation 360 v.26.

What's new

Enterprise 11 and Enterprise 10
Migrate parent bots independently, avoiding overwrites and loss of updates (Service Cloud case ID: 01258572, 01778107, 01275417, 01880168)

You can now migrate a parent bot independently even if it has associated child bots. You now have a choice to select whether you want to migrate a parent bot independently or along with its dependent child bots.

This helps in avoiding overwrites and loss of updates that might happen when child bots that are migrated to Automation 360 are updated after migration.

Migrate Enterprise bots

Migrate more bots with specific features

You can now successfully migrate bots in the following cases:

  • Bots that use spreadsheets residing in SharePoint by using the Excel advanced > Open action.
  • You can now migrate bots with REST commands with custom proxy configuration at the Action level. For custom proxy configuration support, in the Bot Migration Wizard, select the Include web service settings option.
    When you select this option, the REST commands are migrated with custom proxy configurations that use the following global variables:
    • AAProxyHost for Hostname
    • AAProxyPort for Port

    Migrate Enterprise bots

  • Bots in which the user interface or window extends beyond the screen on the top-left corner (truncated) for the following actions: Object Cloning, If, Loop, Web Recorder, and Manage Web Control.

    Now, migrated bots support windows with negative coordinates (truncated windows).
Enterprise 11 only
Migrate bots independent of Bot Insight migration

Before migration of legacy bots, you can now declare whether these bots were using the Bot Insight option in Enterprise 11 by selecting the Tag bots and variables for analytics option in the Bot Migration Wizard. The Bot Insight Open and Close actions are created only for such migrated bots where this option is selected.

Migrate Enterprise bots

What's changed

Assess migration readiness of processes with Bot Scanner
The Bot Scanner scans your repository for processes that can be migrated to Automation 360 and provides information under the following categories:
Note: A process is a bot that is not used in any other bot and can include child bots.
  • All: List of all the processes.
  • Action required: List of processes that require action after migration to Automation 360. A process is flagged as Action Required even if one of its child bot requires action.
  • Review required: List of processes that require review after migration to Automation 360. A process is flagged as Review Required even if one of its child bot requires review.
  • No review required: List of processes that can be migrated. All the bots in the process can be migrated.
  • Non Migratable: List of processes that cannot be migrated. All the bots in the process cannot be migrated.
Note: For generating processes summary report, the maximum repository size that is supported is up to 10 GB.

Analyze Bot Scanner report for migration

Direct link to migration resource portal and upgrade launchpad in Bot Scanner
Bot Scanner report now also contains direct links to:
  • Enterprise Migration Resources: Use the information on this page to plan for migrating to Automation 360.

    Enterprise Migration Resources | Cloud RPA | Automation Anywhere

  • Upgrade Launchpad: Use the information provided on this page for a self-guided experience that is customized for your migration requirements.

    Note that we'll be decommissioning the Upgrade Launchpad by August 2023.

Analyze Bot Scanner report for migration

Direct link to corresponding migration messages

With a direct link to migration messages in Bot Assistant, you now have quicker access to information about migrated bots that require action or review.
Validate letter case in window titles

You can now validate the letter case in window titles in window variables. By using the Case sensitive option, you can now decide whether to match or not match the letter case in window titles that have the same titles but differ in letter case.

With this option, you can ensure that the migrated bots produce the same output as that of their corresponding Enterprise 11 bots.
Review bots more efficiently with exact line number in Bot Scanner report

The Bot Scanner report now displays the exact line number in the bots that need review or action even in cases where some of the commands used in Enterprise 11 bots are not available in Automation 360.

Fixes

When you migrate bots with the Select item by index action of the SAP package, the index is now displayed correctly. The migrated bot selects items according to the correct index, and no error is displayed.
MetaBots that were captured using the following configurations will now be migrated to Legacy AISense in Automation 360:
Linked object play mode Main object play mode
Text Text
None Text

Previously, bots that used such MetaBot configurations failed to migrate.

Service Cloud case ID: 01774261
You can now migrate Task Bots that use MetaBot Logic whose DLL file contains classes without a namespace.

Previously, an error occurred when you ran such Task Bots.

Service Cloud case ID: 01765712
When you migrate from Enterprise 11 to Automation 360, capturing MetaBot screen commands is changed as follows:
Enterprise 11 Automation 360
  • Main objects captured with the Object play mode
  • Linked objects captured with the Coordinate play mode
 Record capture actions with the Object play mode
You can now use commas in the filenames of bots that use FTP actions and use colons in the filenames of bots that use Delete files and Delete folder FTP actions.

Previously, such bots encountered an error during bot run.

Service Cloud case ID: 01772186
When you migrate bots that use the same window titles but have different letter case in window variables, the bots now run successfully.

Previously, bots that used the same window titles but had different letter case in window variables failed to run successfully after migration.

Service Cloud case ID: 00825181
You can now successfully run migrated bots that use the Email Received Date variable twice in subactions inside the Email Loop action.

Previously, a parse error occurred in such cases.

Service Cloud case ID: 01275815
In migrated bots, when you use the Recorder package, you can now use the Click action on Client Control in HTML technology without any issues.

Previously, the Click action button on Client Control did not work as expected.

Service Cloud case ID: 01713357
You can now successfully re-edit a migrated bot with the Record > Dataset variable.

Service Cloud case ID: 01807170
When you want to open web pages, in the Browser package, when you use the New window option of the Open action, you can now specify a URL without the protocol information, such as http, https, or file.

Previously, when protocol information was not provided in the URL, some web pages did not open properly.
You can now successfully migrate Enterprise 11 bots with analytics flags.

Previously, migration failed when variables with analytics flags were checked.

Service Cloud case ID: 01768545
When you click the Back button in the migration details page for a migration run, you are now redirected to the Migration runs tab.

Previously, when you clicked the Back button, you were redirected to the Overview tab.

Service Cloud case ID: 01816558
When you migrate a bot that uses the Manage Window Controls action, the height value is now set correctly after migration.

Previously, after migration, the last digit of the height value was not available.

Service Cloud case ID: 01756996
When you run a bot to automate spreadsheet data, all the requests are now processed successfully in the following scenario:

When an Excel session is active in SAP and a corresponding Excel process starts in the background, Automation 360 creates a separate Excel process other than the one that SAP started, and the correct window is now activated for all the subsequent requests.

Previously, only the first request was processed successfully because the correct window was not activated for automating the spreadsheet data for the subsequent requests.

Service Cloud case ID: 00815159
When you migrate bots from Enterprise 11, the automation priority of each bot is now adjusted to match its equivalent priority level in Automation 360, as follows:
  • In Enterprise 11, if the automation priority for a bot was set to low, after migration, the automation priority for the bot is changed to medium.
  • In Enterprise 11, if the automation priority was set to medium, the automation priority in the migrated bot is set to high.
Note: There is no change in automation priority when it is set to high.

Previously, the automation priority of migrated bots remained the same as in Enterprise 11.
You can now migrate bots even if the properties value of the Manage Window Controls action is set to 65536 or more.

Previously, when the properties value was set to 65536 or more, the bots encountered an error during bot run.

Service Cloud case ID: 01768555, 01825071
After migration, you can now get all the lines of text from the Terminal Emulator by using the Get text > All lines action.

Previously, you could get only 24 lines of text from the Terminal Emulator.

Service Cloud case ID: 01609467
In the Bot migration wizard, the Bot Scanner and the Bot migration report now display the correct status for bots that are flagged for the R134 migration message.

Previously, in the Bot Scanner and the Bot migration report, the status of bots that required review was incorrectly displayed as No review required.

You can now successfully migrate bots whose queue category name contains a space.

Previously, migration of such bots failed because Enterprise 11 bots whose queue category name contained a space went into an infinite loop until the loop timed out at 90 minutes.

Service Cloud case ID: 01850864
After you migrate a bot that uses the Terminal Emulator package, when you run the bot, the terminal window is now activated and remains in the front. This is because the Show terminal window in the front option in the Connect action is now enabled by default.

Previously, when you ran such a bot, the terminal window was not activated and remained minimized because the Show terminal window in the front option was not present in the Connect action.
When you run a bot with the Database package, the bot no longer becomes stuck at the Insert or the Update command when run for a long duration.

Previously, in such cases, the bot became stuck intermittently.

Service Cloud case ID: 01836733

Limitations

In Enterprise 11, if bots were using the String > Replace action to find a carriage return line feed (CRLF) character and replace it with another character, after migration, the output might not be the same as the output seen in Enterprise 11.

Workaround: In the Find string option, instead of the Enter (LF) variable, use the Newline (CRLF) variable.

Service Cloud case ID: 01808878
In Enterprise 11, if bots were using the If, IF/ELSE, or Loop While command in Windows Control and if the Application window does not exist, after migration, the bots will encounter an error during bot run.

Service Cloud case ID: 01846262
When the Select query is used inside a Loop command and its result set is further iterated, if the query returns no record, the result set Loop reiterates the previous record.

Service Cloud case ID: 01799961