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

What's changed

Migration of new formatting capabilities in the XML package (Service Cloud case ID: 01886455, 01925386)
  • When you migrate bots from Enterprise 11 to Automation 360 that are using the Start session action, the Remove text nodes that contain only white space check box is selected by default.
  • When you migrate bots from Enterprise 11 to Automation 360 that are using the Save session data action, the Use Prettyprint check box is selected by default.

Start session action in XML | Save session data action in XML

Fixes

You can migrate bots with filenames that contain up to 160 characters, and might use an action with an encrypted value or Credential Value (CV) type variable.

Previously, these bots failed when migrating to Automation 360.

Service Cloud case ID: 01813733
You can successfully run the migrated bots in the following scenarios:
  • If there is more than one xmlns (default XML namespace) defined in the XML document.
  • If the root element does not have a namespace and the child element of the XML package has a default namespace.

Service Cloud case ID: 01798339
You can migrate the MetaBots that are using Microsoft.Exchange.WebServices.dll as the dependency DLL, use the Get DLL details option during bot design, and then execute the DLL Run function action without encountering an error.

Previously, an error was encountered when the Microsoft.Exchange.WebServices.dll was used a dependency DLL of a bot.

Service Cloud case ID: 01819485, 01857278
You can migrate MetaBots that are using multiple logics without using the overwrite option even if some of the logics already exist in Automation 360.

Previously, such MetaBots encountered an error during migration.

Service Cloud case ID: 01905986
You can migrate MetaBots which include logic that calls another logic whose file name includes a dollar sign ($).

Previously, such MetaBots were displaying a review message on the migration results page.
If you set the Set production version permission in Enterprise 11, after migration to Automation 360, the Label bots permission is selected and replaces the previous Set production version permission. If you are upgrading from a previous Automation 360 release to v.28 (or later release) and you selected the Set production version permission, then the Label bots permission is selected as the default.

Service Cloud case ID: 01868097
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.
Note: This fix is currently not available in Automation 360 v.28 and v.29. The fix is available in the Automation 360 v.30 release. For more information, see Migration updates for v.30 release.
In Enterprise 11, if a bot was using the Normal, Gray-Scale, or Monochrome comparison mode in the Image Recognition command, after migration, the performance of the bot run is improved.

Previously, the performance of such a bot was impacted during a bot run.

Service Cloud case ID: 01889347, 01922609, 01920990
In Enterprise 11, if bots are using the recorder commands, some unused hidden properties remain in Enterprise 11 only after you migrate to Automation 360.

Previously, some unused hidden properties were migrated.

Service Cloud case ID: 01608928
You can migrate a bot that contains a Database with a Loop command and run it successfully in Automation 360.

Previously, when you ran the bot in Automation 360 using the Read from action with append and UTF-8 encoding with the loop, after the first iteration, the retrieved data would show a double quote for the first cell value in the CSV file.

Service Cloud case ID: 01911654
When you migrate a bot that contains the XML > Get single node command , after migration, when you run the bot in Automation 360, it retrieves the value of a single node and no longer displays an error on execution.

Previously, if the XPath started with open brackets, and you ran the bot in Automation 360, the bot encountered the following error: No node found at XPath while executing the Get Single node command.

Service Cloud case ID: 01854326
You can migrate bots that are using the If Variable command with the following conditions:
  • Includes multiple Excel Cell variables.
  • Includes one or more AND or OR operators for comparison.
  • The Excel Cell variables are compared with array type variables.

Previously, such bots failed to migrate.

Service Cloud case ID: 01856986
You can migrate bots that are using commands that include the Session Name field that contains the year ($year$) system variable.

Previously, such bots failed to migrate.

Service Cloud case ID: 01867380
When you migrate bots that are using Table type variables and then call those migrated bots from another Task Bot, the input variables are displayed on the Set input variables window.

Previously, when migrated bots containing Table type variables were called from another Task Bot, the input variables did not display.

Service Cloud case ID: 01920824, 01931439, 01945917, 01910787, 01930540, 01923133, 01931439, 01923133, 01934727
You can successfully migrate bots when you provide a clipboard value as a parameter to a VBScript file without any issues.

Previously, if you provided a clipboard value as a parameter in a bot, the bot migration failed with an error message indicating there was no proper variable selection for the clipboard.
In Automation 360, when you use the SOAP Web Service command in a bot, you can access the specific XML node from the XPath expression which has a namespace declaration from the SOAP response.

Previously, XPath expressions containing a namespace could not be parsed.

Service Cloud case ID: 01907999
When you migrate a bot that uses the Send Email command with the HTML option and run the migrated bot in Automation 360, the output is displayed in the appropriate format.

Previously, if you had used a variable in the HTML code section of the email body and ran the migrated bot in Automation 360, the code was not converted to HTML format. As a result, the output was displayed in an incorrect format.

Service Cloud case ID: 01908010
The Review Required count in the Bot Scanner report and Bot Assistant display consistent information.

Previously, there was inconsistency in the count.

Service Cloud case ID: 01816554, 01856822