Migration updates for v.30 release

Review the fixes for migrating from Enterprise 11 and 10 versions to Automation 360 v.30.

Fixes

After migration, the In progress activity page displays correct information for activities.

Previously, there was a delay in displaying activities after migration.

Service Cloud case ID: 02096061, 02097079, 02097465
In Enterprise 11, if a bot was using the Send Email command in a loop to send attachments to email address that was using username as a variable, you can migrate such a bot and execute it to send email with the correct attachment.

Previously, such a bot was sending additional attachment with each iteration.

Service Cloud case ID: 01947234
You can migrate a bot that uses the Database command to read data from excel and execute it successfully.

Previously, such a bot was reading data from excel with additional newline characters at the end of the line.

Service Cloud case ID: 01953984
When you migrate a bot that uses variables in expressions, the variables are no longer tagged as unused variables.

Previously, such variables were tagged as unused variables.

Service Cloud case ID: 01972750
In Enterprise 11, if a bot is using the Image Recognition commands along with the If, Else if, and Loop commands, you can migrate the bot using the Bot Migration Wizard without encountering error.

Previously, such a bot encountered an error during migration.

Service Cloud case ID: 01966636
In Enterprise 11, if a bot is using the String Operation command and includes a backslash (\) in the Replace string, after migration, the bot executes properly.

Previously, such a bot encountered an error when a backslash (\) was used in the Replace string.
Using the Bot Migration Wizard, you can now migrate bots to a repository that is hosted on Network-attached storage (NAS).

Previously, an error encountered is such a scenario.

Service Cloud case ID: 01977429

Limitations

The Cloud Migration Utility will be unavailable to order or use from October 11, 2023, until the middle of February 2024.
Workaround: Perform one of the following actions: