Migration updates for v.29 release

Review what's changed and fixed in Automation 360 v.29.

What's changed

Migrate bots with greater than 10 nested loops

You can successfully migrate bots than contain more than 10 nested loops without any issues. The maximum number of nested loops supported is 97.

Service cloud case ID: 01936674

Fixes

When you migrate MetaBots that include large content variables using the Bot Migration Wizard, a new text file is generated and the filename for the text file is correctly displayed in the Target Name field on the migration wizard Results page.

Previously, the filename was not displayed.
You can successfully migrate an Enterprise 11 bot created using the nested email loop condition (the first loop is not commented, whereas the second loop action is commented or vice versa), having an Email Automation command.

Previously, migration of such bots showed nested email loop conditions (first and second loop), as commented.
You no longer encounter issues when you run an Enterprise 11 bot in Automation 360 containing the SAP Standard BAPI command. The scalar parameter now maps to Automation 360 variables even if you have not enabled the Write to CSV check box in the SAP Standard BAPI command.
You can successfully migrate an Enterprise 11 bot when it is using an array variable within a Loop While condition and the index position of the variable is greater than the size of the array.

Previously, such a bot encountered an error if the index position of the variable was greater than the size of the array.
After updating to this release, errors are no longer displayed when you select the Excel contains charts check box in the Open action of the Excel advanced package to open an Excel file that contains a graph sheet.
After updating to this release, actions from the App integration package that uses Windows SDK will timeout when the target application stops responding or is in 'Not responding' state.
When you migrate a bot from Enterprise 11 that contains the Run standard workflow action from the SAP BAPI package, the scalar parameters are assigned to the corresponding variables correctly.
When you migrate an Enterprise 11 bot that uses the Loop action with File exists condition and if the variable value inside the condition changes, then the bot picks up the latest value of the variable with every loop iteration.
When you migrate an Enterprise 11 bot that uses the Comment action, the action will always remain in the enabled state even if it consists of variables as the variables will now be represented as $. For example, when you add $vArray$ variable in the Comment action and migrate the bot, after migration it will be represented as $vArray$.
You can migrate bots that use the Delay package in a loop where the delay value is set to 0.

Previously, such bots encountered an error during bot execution.
When you migrate an Enterprise 11 bot which has Object Cloning command with Image play mode, the migration no longer fails for the currently selected active window. Also, it does not generate any error message.

Service Cloud case ID: 01947195
When you use the String > Before or after command in Enterprise 11 and if the number specified in the No. of characters to be extracted field is greater than the actual number of characters available before or after the specified text, the output shows consistent results. Additionally, it does not generate any error message.
When you migrate a bot that contains disabled if-else commands inside any active if-else block, the entire code in the bot is migrated without any issues.

Previously, when you opened the migrated bot in Automation 360, some lines of code were found missing. This issue occurred because when you migrated the bot, the disabled if-else code in the bot was skipped, and no error or warning was displayed in the migration wizard.

Service Cloud case ID: 01885648