Unsupported features for migration

Review the features that are not supported for migration from Enterprise 11 or Enterprise 10 to Automation 360.

Features not yet supported

The following features are not yet supported for migration:

  • Migration of audit logs from Enterprise 11 is not supported on Cloud deployments.
  • In Enterprise 11, if bots were using the Before-After string operation with the OR logical operator and operation output resulted in an empty string, then the output displayed as an empty string.

    However in Automation 360, if the output of such an operation results in an empty string, the value used in the End before text string operation is ignored and the result displays in the output.

    For example, in the text email:user@outlook.com, if the value in the Before operation is email: and the value in After operation is user, the results differ based on product version:
    • Enterprise 11 displays an empty string as the output.
    • Automation 360 displays user@outlook.com as the output.
  • In Enterprise 11, if users select internal variables for the window titles; but not used in the bot, after migration, these internal variables are also migrated to Automation 360.
  • In migrated bots, if you are using OLE DB Driver version 18 or later and when you export SQL Server Database with bit columns to a CSV file, the bit value of -1 is returned instead of 1 for string value TRUE.

    Fixed in: v.27

  • When you migrate bots using SAP > Select item by index command, incorrect index is displayed in the migrated bot.

    Fixed in: v.26

  • Bots that include the Terminal Emulator package are migrated only to Advanced Technology and not to Legacy Technology.
  • When you migrate a bot that was using the Manage Window Controls action, the last digit of the height value is not available after migration. However, the bot will execute successfully.

    Fixed in: v.26

  • When an Excel session is active in SAP, a corresponding Excel process starts in the background. In such a scenario, Automation 360 uses the same Excel process that SAP started. When you run a bot to automate spreadsheet data, Automation 360 processes the first request successfully. However, during execution, if the Excel is closed and a subsequent request is sent for automating the spreadsheet data, Automation 360 does not process the request because the Excel process is still being accessed by SAP. Therefore, the correct window is not activated for automating the spreadsheet data.

    Fixed in: v.26

  • If a bot is using the Structured text type field in the PDF > Extract text action, some of the characters might not be extracted correctly.

    Fixed in: v.25

  • After migration, the Before, Before and/or after, and After options in the String > Extract text action does not match the case in a string.

    Fixed in: v.25

  • After migration, bots that were using the Get text > All lines action in Enterprise 11 will display only 24 rows of lines in the Terminal Emulator.

    Fixed in: v.26

  • Migrating bots with Get Total Rows command in SAP GUI returns values as Float string type instead of an Integer type after migration.

    Fixed in: v.26

  • If you are a Bot Creator or a Bot Runner user, you might not be able to view the Review messages displayed in the Bot Assistant without having the View migration permission.

    Fixed in: v.26

  • When you use counter as a variable in a nested loop, the parent loop functions properly but the child loop does not run as expected.

    Fixed in: v.27

  • Bots with SAP packages cannot pick and convert window titles that include "*" (asterisk) character. These window titles are not converted to currently active window names after migration.

    Fixed in: v.26

  • Bot deployment might fail when you run migrated bots with the SAP > Get Property command. This issue occurs because of the following reason: In Enterprise 11, property name is case in-sensitive. During migration, property name is changed to being case sensitive, so bot deployment fails when the case of property name does not match.

    Fixed in: v.26

  • When you send an email through Exchange Web Services (EWS), the format of the email output do not have line breaks , the content appears tampered, and the entire content of the email appears in a single line.

    Fixed in: v.26

  • The Enterprise 11 or Enterprise 10 Bot Runner and Bot Creator devices are not included in the migration process and are therefore not migrated to Automation 360.

    The Automation 360 Bot Agent replaces the Enterprise 11 and Enterprise 10 Enterprise Client. Use the Bot Agent to connect a device to the Automation 360 Control Room and run bots on the connected devices.

  • When you run a migrated bot with the option Validate if attachment is missing option checked, and if the attachment is missing when you send the email, the bot might not run successfully.
  • Workflows, triggers, version control history of bots, and file system logs.
  • Migration of Enterprise 11 bots that uses Subversion Version Control for version control.
  • Migration of Enterprise 11 On-Premises Control Room to Automation 360 Cloud service on GCP using the Cloud Migration Utility is not supported.
  • Migration of Bot Insight data and other entities such as users, roles, schedules and credential variables when Automation 360 is installed using a fresh database.
  • Cut, copy, paste, and Ctrl+A functions on the terminal screen when using Terminal Emulator.

    Fixed in: v.27

  • Use of a variable within a variable (except value type variables) in a bot.

    For example, if a bot contains $variable1$, where $variable1$ contains $variable2$, and $variable2$ contains the actual value, this bot cannot be migrated.

  • Use of a fixed value and a variable to specify the index position, for example, $v_ArrVar(1$RowIndex$,1)$.
  • The capability to capture images from the runtime window when a bot is being executed.
  • Enterprise 11 or Enterprise 10 bots that use a string value in a variable that is used in the If command along with '<' or '=' operator are migrated to Automation 360. However, these bots encounter an error when they run in Automation 360.
  • The If command or the Loop command that use <, >, <=, or >= operator with variables that contain a string value encounters an error after migration.

    For example, if you have a bot that contains a variable with the value abcd and uses the > operator, the bot encounters an error when it is run after the migration because string type variables are not suppose to use the <, >, <=, or >= operator.

  • Object Cloning command that automates the following applications:
    • Flash applications
    • Web application running on Edge-Legacy browser
  • Enterprise 11 or Enterprise 10 bots were able to run a Microsoft Excel macro from the Microsoft Excel file available in the XLSTART folder when the that macro is called from another Excel file that does not contain that macro. After migration, these bots are not able to run the macros which are available in another Excel
  • The arrow symbol is not displayed in the Automation 360 Bot editor.

    When the arrow symbol is used in Enterprise 11 or Enterprise 10 bots, the Bot editor does not display any symbol after migration, with one exception. The exception is that when the symbol is used in multiple IF/ELSE commands, the Bot editor displays the $String:FormFeed$ variable instead of the arrow symbol.

Unsupported features with workaround

You can migrate bots with the following features if you update them based on the specified workaround:
  • The output of the String Length action is different in Automation 360 when compared to Enterprise 11 because Automation 360 considers the line feed character whereas Enterprise 11 considers both carriage return and line feed characters when calculating the string length.

    Workaround: Calculate the number of line feed characters used in the string and add it to the string length.

  • If you have created triggers, indexes, views and such custom Database objects in addition to the existing standard objects created in the Enterprise 11 Control Room, you might not be able to restore the exported data to Cloud using the Cloud Migration Utility. If you need help to identify such objects, contact Automation Anywhere support: Open a support case (A-People login required).

    Workaround: Disable the additionally created Database objects before exporting data to the Cloud.

  • In Enterprise 11, if bots were using a window title value or variable that contained leading spaces, after migration, the bots will be unable to select the corresponding window.

    Workaround: Remove the leading spaces from the window title value or variable and then run the bots.

  • When you use the Recorder to capture an object, select HTML Tag, HTML InnerText, and HTML type properties in Search Criteria, or migrate a bot with similar properties selected in Search Criteria, the bot fails to identify or locate the object and perform the selected action.

    Workaround: Modify the DomXpath according to the controls you capture or add more properties in Search Criteria.

  • When your bot has some error, you add the Try/Finally block around those actions and insert one more action in the Finally block. When you save and run the bot, you will see the Bot error dialog shows the wrong error line number within the Finally block.

    Workaround: If you are using Try and Finally without using Catch action, the Bot error dialog will not show the correct line number. Instead, use Try/Catch, the Try action handles the error and sends execution to Catch with line number and description. This would give the correct line number within the Finally block.

  • Note: Issue applies only to v.22 and earlier (as this is fixed in v.23, see Migration of non-credential vault variables). The Run Logic command that uses credential variables as input for a logic of a MetaBot

    Workaround: Bots that use the Run Logic command that passes Credential Vault attributes from a Task Bot to a MetaBot logic can be migrated to Automation 360. The credential name and attribute name are displayed in the fields in the corresponding line of the migrated bot.

    If you have migrated using the restored Enterprise 11 database, an equivalent locker is created in Automation 360 for the credential variables used in the Enterprise 11 bot.

    Choose one of the following options to run the migrated bots successfully:
    • Option 1: Pass the credential type variables.
      1. Create a credential type variable in the child bots as input variables.
      2. In the Run action of the Task Bot package of the parent bot, update the input value fields to use the Credential Vault attributes for the credential type variable created for the child bot (corresponding to MetaBot logic).
    • Option 2: Pass the credential values as a global value.
      1. Create the Global value in Automation 360 for the credentials use in the Run Logic command in Enterprise 11.
      2. In the Run action of the Task Bot package of the parent bot, update the Input value fields to use the Global values for the credential type variable created for the child bot (corresponding to MetaBot logic).
    If you have not used the restored Enterprise 11 database when installing Automation 360, you must first create the required locker for the credential variables used in the Enterprise 11 bot, before performing the preceding steps.
    Note: Automation 360 provides enhanced security by allowing you to assign Credential Vault attributes only to the credential type variables. This restricts any nonsecure handling of Credential Vault attributes where they might have been assigned to non-credential type variables.

  • When you create DLLs with different functions, if you use the same filename for DLLs and add them to multiple MetaBots, after migration, if a Task Bot is using the Logic of these MetaBots, an error occurs during execution.

    The error occurs because the DLL sessions are based on the DLL filenames, and only the session of the first DLL will be active during execution. Any function called from subsequent DLLs will not be present in the first DLL session that is active.

    For example, consider that MetaBot1 is using a DLL that has function1 and MetaBot2 is using a DLL that has function2, and both the DLLs have the same filename test.dll. After migration, when you run a Task Bot that uses MetaBot1 Logic and MetaBot2 Logic, the DLL session of MetaBot1 Logic is activated and function1 runs successfully. However, when the MetaBot2 Logic is run, the corresponding DLL is not activated because the session with the same DLL filename is already active, and function2 is not present in the DLL of MetaBot1 Logic, which results in an error.

    Workaround: Depending on your requirements, you can perform one of the following workarounds:

    • Before migrating the bots, ensure that you rename the DLL filename of one of the DLLs, update the references to the DLL function in MetaBots Logic, and then migrate the bots.
    • After migrating the bots, change the session name in the Create DLL session box of the Open DLL action and then update the same DLL session name in the related If action for the DLL Session does not exists condition and the Run DLL action.
  • In Enterprise 11, if a MetaBot was using Microsoft.Exchange.WebServices.dll to use Microsoft Exchange services, after migration, when you use the Get DLL details option in the DLL Run function, an error is encountered. The error is because, in Automation 360, the Microsoft.Exchange.WebServices.dll is not automatically installed in the global assembly cache (GAC) on your device.

    Workaround: You must manually install the Microsoft.Exchange.WebServices.dll in GAC on your device and then use the Get DLL details option.

    See How to: Install an assembly into the global assembly cache .

  • In Enterprise 11, if a bot was using the Log To File action and you entered text greater than 1000 characters in the Enter text to log field, then after migration, the bot will encounter an error.

    Workaround: Ensure that the you configure the text as a variable, and then use this variable in the Enter text to log field instead of entering the static text.

  • In Enterprise 11, if a bot uses the Text file > Read Variables action to read values of variables from a text file and uses the If > String condition to execute actions based on the value of the specified source string, when you run the bot after migration, the bot might fail if the key value added to the mapped variable does not match the value in the text file.

    Workaround: To pass null values successfully perform the following steps:

    1. Use the Text file > Read Variables action to add a dictionary variable.
    2. Use the Dictionary > Get action to find and save a specific key value.
      Note: If the key value does not match with the value in the text file, an empty string is returned to the string variable.

    Alternatively, use the If > Dictionary > Check key condition to validate if the key is present in the text file. You can then assign the value to the string variable.

  • PD-50108In Enterprise 11, if you used the Loop action to open the same Excel sheet multiple times without closing it, after migration, an error occurs. The error occurs because, in Automation 360, only one Excel session can be active at a time.

    Workaround: In the Loop action, ensure that you use the Close action to close the Excel session before opening the Excel sheet again with the same session name.

  • 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.

  • After migration, bots that were using the Log To File action to log files are using the LF character instead of the CRLF character for new lines.

    Workaround: Use the $String:Newline$ variable to use the CRLF character in the migrated bots.

  • If a MetaBot Logic (for example, Logic A) is referenced to a Task Bot or another MetaBot Logic and if Logic A was renamed or moved from one logic folder to another within the same MetaBot, after migration, the Task Bot or MetaBot Logic does not work when it calls for Logic A.

    Workaround: In the Task Bot or MetaBot Logic which calls for Logic A, update the name or path to reference to Logic A.

  • If a bot is using the Browser > Download files action to download files from a URL, some files whose URLs have special characters or require Windows native authentication access might not download properly.

    Workaround: Use the Browser > Open action instead.

  • When you insert XML > Insert node as an attribute using a variable, the bot migration might fail.

    Workaround: Insert the attribute by providing the direct value instead of a variable.

  • When you run migrated bots that open URL without the protocol information (such as http, https, or file), the web page might not open properly.

    Workaround: Ensure that you add the appropriate protocol information to the URL.

  • If a MetaBot Logic was using a DLL file that used classes without a namespace, after migration, any Task Bot that uses the MetaBot Logic will not work.

    Workaround: Manually update the DLL file to include namespace for classes.

  • After migrating bots, an error is seen when using FTP actions on bots that are using comma in the filenames and when using the Delete files and Delete folder FTP actions on bots that are using colon in the filenames.

    Workaround: Ensure that you remove comma in the filenames before using the FTP actions and colon in the filenames before using the Delete files and Delete folder FTP actions.

  • If a bot was using the Send action to send an email with attachments where the path for the attachments were variables, the bot will either fail to execute or ignore the attachment.

    Workaround: Replace variables with the paths for the attachments.

  • Enterprise 11 or Enterprise 10 bots encounter an error after migration when these bots use the Run Logic command to run a MetaBot logic and the location of the logic is specified up to the folder that contains that logic. For example, consider you want to run Logic1 that is available in D:Metabots\Logics\Finance location. If you specify only D:Metabots\Logics\Finance instead of the complete path (D:Metabots\Logics\Finance\Logic1) of the logic, an error is encountered.

    Workaround: Update the path of all the MetaBot logic to the complete path in Enterprise 11 or Enterprise 10 bots before migration.

  • Enterprise 11 or Enterprise 10 MetaBots that use the credential variable to pass a numeric value as an input to a DLL function.
    Workaround:
    1. Update the DLL function to use the input parameter of type string.
    2. Delete the commands from the MetaBots that pass the numeric type input parameter to the DLL function.
    3. Add the commands in the MetaBots to pass the string type input parameters to the DLL function.
    4. Migrate the relevant Task Bots and MetaBots.
  • If you are migrating to Automation 360 Cloud and you have configured SAML as the authentication type in Enterprise 11, the migration process changes the authentication type to the Control Room database authentication type for the migrated Automation 360 Control Room.
    Workaround: To configure SAML as the authentication type for the Cloud Control Room after migration, perform these steps:
    1. Delete the user that was used to configure SAML in Enterprise 11 from Automation 360.
    2. Create another user with the required permissions and use that user to configure SAML in Automation 360.
  • Applicable to v.24 and earlier:Migration from Enterprise 10 to Automation 360 Cloud.

    Workaround: Migrate to an Enterprise 11 version that is supported for migration to Automation 360 Cloud and then migrate to Automation 360 Cloud.

  • Enterprise 11 bots that use the Exchange Web Service (EWS) to send email using the Send Email command encounters an error after they are migrated to Automation 360
    Workaround: Create the following global values in Automation 360 and update the migrated bots to use EWS in all the actions:
    • AAE_EmailSettings_auth
    • AAE_EmailSettings_host
    • AAE_EmailSettings_port
    • AE_EmailSettings_ssl
    The values for these global values must be as specified in Enterprise 11.
  • The Loop command or the If command that use date conditions to compare dates in different formats encounters an error after migration. For example, a date with MM/dd/yyyy format does not work with a date with MM/dd/yyyy hh:mm:ss format.

    Workaround: Update dates with the different format to the same format.

  • A bot cannot use a variable or an object that contains data larger than 64 KB. For example, if you have captured a table from a website using the Object Cloning command and the captured object contains data larger than 64 KB. Bots containing such objects encounters an error after migration.

    Workaround: Remove unwanted data or copy the data in a CSV or a text file and uses the Read action of the CSV/TXT package.

  • Migration fails for action from which the Credential Vault value is missing in the Control Room.

    Workaround: Create the Credential Vault value in the Automation 360 before migration and start the migration again using the Bot Migration Wizard.

Migrating bots with N/A status

The Bot Scanner reports shows the status of bots that contain unsupported commands and cannot be migrated as N/A. You can migrate such bots by modifying them in your Enterprise 11 or Enterprise 10 machine as specified in the following table:
Message

Migration of bots not yet supported due to child bots using unsupported commands.
Description

A child bot that uses a command that is currently unsupported for migration cannot be migrated. As a result, parent bots that use this child bot also cannot be migrated.
Action

To migrate these parent bots, remove references to the child bot from the parent bot and then migrate that parent bot.

To view the unsupported commands used in the child bots, go to the list of bots that cannot be migrated and click the child bot name.
Message

Migration of "Object Cloning" with "HTML (Edge)" is not yet supported
Description

The Microsoft Edge Legacy browser is not supported in the Automation 360, so the migration of bots configured with this browser in not supported.
Action

Update the Enterprise 11 bots using other supported browsers such as Google Chrome, Firefox, Internet Explorer, or Microsoft Edge Chromium browser.
Message

Migration of MetaBot is not supported. The screen file does not exist. Please fix the bot and try again.
Description

MetaBot Logic refers to a screen that does not exist in the MetaBot.
Action

To migrate the MetaBot, either add the screen again or remove references to the non-existent screens.
Message

Migration of "Variable Operation" command where variable types do not match is not supported. Please fix the bot and try again.
Description

Enterprise 11 or Enterprise 10 bot uses the Variable Operation command where the variable types of the variables used are not the same.
Action

Update the Variable Operation command in the Enterprise 11 or Enterprise 10 bots to ensure that the referenced variables are of the same type.
Message

Migration of "Variable Operation" command where the variable does not exist is not supported. Please fix the bot and try again.
Description

Enterprise 11 or Enterprise 10 bot references a non-existent variable in the Variable Operation command.
Action

Either create a variable with the same name and type, or remove the command that references the non-existent variable.
Message

Migration of "If" command where the variable does not exist is not supported. Please fix the bot and try again.
Description

Enterprise 11 or Enterprise 10 bot references a non-existent variable in the If command.
Action

Either create a variable with the same name and type, or remove the command that references the non-existent variable.
Message

Migration of "ElseIf" command where the variable does not exist is not supported. Please fix the bot and try again.
Description

Enterprise 11 or Enterprise 10 bot references a non-existent variable in the Else If command.
Action

Either create a variable with the same name and type, or remove the command that references the non-existent variable.
Message

Migration of "Loop" command where the variable does not exist is not supported. Please fix the bot and try again.
Description

Enterprise 11 or Enterprise 10 bot references a non-existent variable in the Loop command.
Action

Either create a variable with the same name and type, or remove the command that references the non-existent variable.
Message

Migration of "Run Task" with bot path defined using "AAApplicationPath" not followed by valid repository folder path is not supported. Please fix the task bot path in the 11.x bot and migrate again.
Description

Enterprise 11 or Enterprise 10 bot uses an invalid path in the Run Task command of the child bot.
Action

To migrate this bot, modify the Enterprise 11 bot to ensure a valid child bot path is provided after AAApplicationPath.
Message

Migration of "If - TaskSuccessful" with bot path defined using "AAApplicationPath" not followed by valid repository folder path is not supported. Please fix the task bot path in the 11.x bot and migrate again.
Description

Enterprise 11 or Enterprise 10 bot uses an invalid path within the If > Task Successful condition of the child bot.
Action

Update the Enterprise 11 or Enterprise 10 bot to ensure a valid child bot path followed by a proper folder structure is provided after AAApplicationPath.
Message

Migration of "If - TaskUnsuccessful" with bot path defined using "AAApplicationPath" not followed by valid repository folder path is not supported. Please fix the task bot path in the 11.x bot and migrate again.
Description

Enterprise 11 or Enterprise 10 bot uses an invalid path within the If > Task Unsuccessful condition of the child bot.
Action

Update the Enterprise 11 or Enterprise 10 bot to ensure a valid child bot path followed by a proper folder structure is provided after AAApplicationPath.
Message

Migration of "ElseIf - TaskSuccessful" with bot path defined using "AAApplicationPath" not followed by valid repository folder path is not supported. Please fix the task bot path in the 11.x bot and migrate again.
Description

Enterprise 11 or Enterprise 10 bot uses an invalid path within the Else If > Task Successful condition of the child bot.
Action

Update the Enterprise 11 or Enterprise 10 bot to ensure a valid child bot path followed by a proper folder structure is provided after AAApplicationPath.
Message

Migration of "ElseIf - TaskUnsuccessful" with bot path defined using "AAApplicationPath" not followed by valid repository folder path is not supported. Please fix the task bot path in the 11.x bot and migrate again.
Description

Enterprise 11 or Enterprise 10 bot uses an invalid path within the Else If > Task Unsuccessful condition of the child bot.
Action

Update the Enterprise 11 or Enterprise 10 bot to ensure a valid child bot path followed by a proper folder structure is provided after AAApplicationPath.
Message

Migration of "Variable Operation" command resetting system variable "$WorkItemResult

quot; will not be supported.
Description

Resetting the system variable $WorkItemResult$ is not supported for Variable Operation command.
Action

Use the String > Assign operation and assign an empty string to the $WorkItemResult$ system variable instead of resetting it.
Message

Migration of "Windows - Close All Open Windows" is not yet supported.
Description

If you have used the Close command with the All open windows option selected in a bot, you cannot migrate that bot.
Action

Update the Enterprise 11 or Enterprise 10 bot so that it does not use the All open windows option before you migrate it
Message

Migration of "If - ObjectProperties" with field "OCObjectPlay_PropertyInfo_ReviewMessage" of type "String" is not yet supported.
Description

Enterprise 11 or Enterprise 10 bot uses an object in the If > Object Properties command that has one of the properties with size larger than 64 KB.
Action
To migrate this bot, you can perform one of the following actions:
  • Delete the property value that is larger than 64 KB in size, in the If > Object Properties command.
  • Store the property value which exceeds 64 KB into a text file. Then, create a variable which reads the value from this file. Assign this new variable to the corresponding property in the If > Object Properties command.
Message

Migration of "ElseIf - ObjectProperties" with field "OCObjectPlay_PropertyInfo_ReviewMessage" of type "String" is not yet supported.
Description

Enterprise 11 or Enterprise 10 bot uses an object in the Else If > Object Properties command that has one of the properties with size larger than 64 KB.
Action
To migrate this bot, you can perform one of the following actions:
  • To migrate this bot, delete the property value that is larger than 64 KB in size, in the Else If > Object Properties command.
  • Store the property value which exceeds 64 KB into a text file. Then, create a variable which reads the value from this file. Assign this new variable to the corresponding property in the Else If > Object Properties command.
Message

Migration of "Loop.Condition - ObjectProperties" with field "OCObjectPlay_PropertyInfo_ReviewMessage" of type "String" is not yet supported.
Description

Enterprise 11 or Enterprise 10 bot uses an object in the Loop while > Object Properties command that has one of the properties with size larger than 64 KB.
Action
To migrate this bot, you can perform one of the following actions:
  • To migrate this bot, delete the property value that is larger than 64 KB in size, in the Else If > Object Properties command.
  • Store the property value which exceeds 64 KB into a text file. Then, create a variable which reads the value from this file. Assign this new variable to the corresponding property in the Else If > Object Properties command.