Package mapping for migration

Automation 360 has a new package called Legacy automation. This package provides the additional support needed during migration. The Legacy automation package is for use during migration only; we do not recommend using this package for new bot development. Legacy Automation package

You can migrate bots when the user doing the migration is using an authenticated proxy server.

Note: For a list of packages and actions that support migration and conversion of Internet Explorer bots from Enterprise 11 or Enterprise 10 to Automation 360 with Edge with IE mode, see Packages and Actions.

Active Directory

Respective Active Directory commands are migrated within the Connect and Disconnect actions. Each command is migrated as follows:


Enterprise 11 or Enterprise 10 commands	Equivalent Automation 360 actions and packages
Create user	Create user
Modify group command with the Rename group option selected	Rename group
Modify group command with the Delete group option selected	Delete group
Modify group command with the Add users to group option selected	Add users to group
Modify group command with the Remove users from group option selected	Remove users from group
Modify group command with the Set property option selected	Set group property
Modify group command with the Disable user account option selected	Disable user account
Modify group command with the Update user details option selected	Update user details
Modify user command with the Rename user option selected	Rename user
Modify user command with the Delete user option selected	Delete user
Modify user command with the Enable user account option selected	Enable user account
Modify user command with the Update Account Options option selected	Update account options
Modify user command with the Change Password option selected	Change Password
Create object command with the Computer object option selected	Computer object
Create object command with the Organizational unit object option selected	Create organizational unit
Search command with the Run Query option selected	Run Query
Search command with the Get all users of a Group option selected	Get all users of a group
Get property command with the User option selected	Get user property
Get property command with the Group option selected	Get group property
Get property command with the Computer option selected	Get computer property
Get property command with the Organizational unit option selected	Get organizational unit property
Modify Object command with Computer object type and the Rename Object option selected	Rename computer
Modify Object command with Computer object type and the Delete Object option selected	Delete computer
Modify Object command with Computer object type and the Move Object option selected	Move computer
Modify Object command with Computer object type and the Set Property option selected	Set computer property
Modify Object command with Organizational Unit object and the Rename Object option selected	Rename organizational unit
Modify Object command with Organizational Unit object and the Delete Object option selected	Delete organizational unit
Modify Object command with Organizational Unit object and the Move Object option selected	Move organizational unit
Modify Object command with Organizational Unit object and the Set Property option selected	Set organizational unit property

See Active Directory package.

App Integration

App Integration in Automation 360 does not have actions for each technology, unlike in Enterprise 10/Enterprise 11. In Automation 360, all actions are divided into individual actions.


Enterprise 11 or Enterprise 10 commands	Equivalent Automation 360 actions and packages
App Integration commands that capture text from a window	Capture text from window action of the App Integration package
Modify group command with the Rename group option selected	Rename group
Modify group command with the Delete group option selected	Delete group
Modify group command with the Add users to group option selected	Add users to group

Enterprise 11 bots that resize the application window when they are deployed can be migrated to Automation 360.

See App Integration package.

Clipboard

All commands of Clipboard are migrated to equivalent actions of the Automation 360 Clipboard package. There is no change in behavior or command name.

See Clipboard package.

Comment

Comment is migrated to Automation 360 Comment action.

If the Comment command contains a variable or a $ symbol, the command gets disabled after migration.

Database

Enterprise 10/Enterprise 11 uses ODBC drivers and Automation 360 uses JDBC drivers.

The SQL Query action is called Read from in Automation 360.

The following table shows the commands that currently can be migrated.


Enterprise 11 or Enterprise 10 commands	Equivalent Automation 360 actions and packages
Connect	Migrates to the Connect command. If you encounter an unsupported connection string in Automation 360, the reasons might vary based on your environment. More details are available as part of the migration process. Contact Technical Support if you need assistance resolving the issue. 0 is not a valid time out value in Automation 360. The migration process replaces 0 with an empty value.
Run Stored Procedure	The parameter name and output parameter are mandatory fields in Automation 360. Important: After you migrate the bot, you must provide the parameter name and output parameter type in the Run stored procedure action.

See Database package.

Delay

Delay command is migrated to the Delay action in Automation 360. "Delay in Milliseconds" and "Delay in Seconds" options (Enterprise 11) have changed to radio options within the Time unit area (Automation 360). See Delay package.

Email

There are no sessions for Email commands in Enterprise 10 or Enterprise 11. However, Automation 360 includes Connect and Disconnect actions to ensure email sessions are started and closed. Therefore, during migration, the Connect action is placed before the respective email action and the Disconnect action after the respective email action.

The Save attachment option of the Get All Messages command is now a dedicated action called Save attachment in the Email package in Automation 360.

For bots created to automate email-related tasks on the Exchange Web Services (EWS) server, the Get All Message command is migrated to the Loop action with the iteration set to For all each mail in mailbox. Similarly, the Delete and Delete all commands are migrated to Delete and Delete all actions.

When you migrate Enterprise 11 bots that contain the Email package with Authentication type set to OAuth2, most of the parameters included in the package migrate to the same values in Automation 360. However, the following parameters migrate with different values:

The IMAP and POP3 protocols migrate to the corresponding Email server in Automation 360.
The Use Local timezone migrates to the Loop action as a Boolean value in Automation 360.

See Email package.

Error Handling

Disabled Error Handling commands are not migrated to Automation 360.

Begin Error Handling and End Error Handling is migrated to the Try/Catch block of the Error handler package in Automation 360. Many options available in Begin Error Handling are migrate to respective Automation 360 actions.

Note: To avoid an exception error when you use the Try/Catch block in a Loop, we recommend that you validate all the command inputs.

In Enterprise 11, if a bot was using the following conditions or features, after migration, a Try/Catch block is added in Automation 360 to prevent failure in the bot execution:

When the bot is using an Error Handling statement.
When the bot is using an Excel System Variable.

Refer the below table for details:


Enterprise 11 or Enterprise 10 commands	Equivalent Automation 360 actions and packages
Continue	By default, execution continues after executing the Catch block in Automation 360.
Stop	Stop action of the Task package is added in the Catch block.
Take Snapshot	When the Take Snapshot option is selected and the location is provided in the File Path field of the Enterprise 11 bot, the migrated bot contains: The Capture desktop action of the Screen package to capture the error screen. The Log to file action of the Log To File package to capture the error message in a text file. The To string action of the Datetime package to convert the datetime value to string that will be stored in the text file along with the error message. The above actions are added in the Catch block of the migrated bot and the captured image and the error message are stored at the location provided in the File Path field of the Enterprise 11 bot. When the Take Snapshot, Send Email, and Attach Sanpshot options are selected and the location is not provided in the File Path field in the Enterprise 11 bot, the migrated bot contains the following: The Create action of the Folder package to create a temporary location to store the captured image and the text file that contains the error message. The Capture desktop action of the Screen package to capture the error screen. The Log to file action of the Log To File package to capture the error message in a text file. The To string action of the Datetime package to convert the datetime value to string that will be stored in the text file along with the error message. The Send action of the Email package to send an email notification with the image and text file attached. The Delete action of the File package to delete the image and text file stored in the temporary location. The above actions are added in the Catch block of the migrated bot.
Run Task	Run action of the Task package is added in Try block. When a child bot encounters an error, the bot continues with the execution of the next action of the parent bot.
Log Data into File	Log to File action is added in Catch block.
Send Email	Send action from the Email package is added to the Catch block. The Task Bot variables and variable values sent as email attachment using the Attach Variable option are also migrated.
Variable Assignment	Assign action of the String package is added with respective the condition in the Catch block.

See Error handler package.

Excel

The Enterprise 10/Enterprise 11 Excel commands are migrated to respective Automation 360 actions of the Excel Advanced package.

In Enterprise 11, a bot can open a Microsoft Excel spreadsheet even when a file extension is not provided. In Automation 360, the migrated bots uses the Open action in the Excel advanced package to open a Microsoft Excel spreadsheet when a file extension is not provided.

In Enterprise 10/Enterprise 11, data returned by Get Multiple Cells and Get All Cells commands are returned to the Loop > Each Row in an Excel Dataset command. In Automation 360, the functionalities of Get Multiple Cell and Get All Cells are available in Loop > Each Row in an Excel Dataset action, so values from these commands are migrated to the loop instead of actual actions.

Bots that use the Get Single Cell command with the Specific cell and Get Cell Value options are migrated to the Get single cell action of the Excel advanced package with the Specific cell and Read cell value options selected after migration.

When you run a migrated bot with the Excel Advanced > Cell range option, ensure that you use a numeric value as the last character in the From cell and To cell fields (for example, testa1). The last character cannot be an alpha character.

The following table shows action name changes:


Enterprise 11 or Enterprise 10 commands	Equivalent Automation 360 actions and packages
Save Spreadsheet	Save workbook
Open Spreadsheet	Open
Close Spreadsheet	Close Note: When you migrate a bot with Excel: Close action, in Enterprise 10/Enterprise 11, the bot ignores the Save option for the read-only file, whereas in Automation 360, the following prompt is displayed: The File already exists.
Get Cells	Divided into Get single cell and Get multiple cells actions Note: The Get Cells action retrieves output in different formats for Enterprise 10/Enterprise 11 and Automation 360 for specific data types such as Boolean and Date.
Activate Sheet	Switch to sheet Note: In Enterprise 11, the bot containing the Activate Sheet command does not switch to and perform operations on a hidden worksheet. However, after migration to Automation 360, the bot containing the equivalent Switch to worksheet action switches to the hidden worksheet and performs operations on it. After the operations are completed, the worksheet remains hidden and is not activated.
Find/Replace	Divided into Find and Replace actions When you migrate a bot with the Excel > Find action and if the value is present at the beginning of a cell address, the migrated bot retrieves the same output results in a different sequence for the Find Text for Enterprise 11 and Automation 360. For example, if A2, B5, and D15 cell addresses have the value XYZ and you search for XYZ in the range A2:D15, the Enterprise 11 bot collects the result in the sequence: B5, D15, and A2. However, the migrated bot will collect the result in a different sequence: A2, B5, and D15, after migrating to Automation 360.

See Excel advanced package.

In Enterprise 11 or Enterprise 10 and in Automation 360, a session (used to open a Microsoft Excel spreadsheet) can be shared between the parent bot and a child bot. In Automation 360, you can close a shared session from the child bot.
Note: When you use more than one spreadsheet to automate an operation, you must use different session names for each spreadsheet. If you want to use the same session name to automate all the spreadsheets, you must first close the session of one spreadsheet before using the same session name for another spreadsheet.
In Enterprise 11 or Enterprise 10, when you try to save a read-only spreadsheet, an error is not displayed. However, in Automation 360, when you try to save a read-only spreadsheet, an error message that the workbook cannot be saved is displayed.
Workaround: Ensure that you have the Edit access for the file and retry the operation. If the issue persists, contact your system administrator. The Write action is not allowed on such files.

File and Folder

All commands of File/Folder have been split into File and Folder packages.

The following File related actions have changed in Automation 360:


Enterprise 11 or Enterprise 10 commands	Equivalent Automation 360 actions and packages
Copy Files	Copy action of the File package
Create Files	Create action of the File package
Create File Shortcut	Create shortcut action of the File package
Delete Files	Delete action of the File package
Open Files	Open action of the File package
Print Files	Print action of the File package
Rename Files	Rename action of the File package
Unzip Files	Unzip action of the Folder package
Zip Files	Zip action of the Folder package

The following Folder related actions have changed in Automation 360:


Enterprise 11 or Enterprise 10 commands	Equivalent Automation 360 actions and packages
Copy Folder	Copy action of the Folder package
Create Folder	Create action of the Folder package
Create Folder Shortcut	Create shortcut action of the Folder package
Delete Folder	Delete action of the Folder package
Open Folder	Open action of the Folder package
Rename Folder	Rename action of the Folder package

See File package and Folder package.

Enterprise 11 bots can use regular expressions in the Copy Files, Delete Files, Print Multiple Files, Rename Files, and Zip Files commands to search for files on which you want to perform an operation. The equivalent actions in Automation 360 too can use regular expressions to search for files on which you want to perform an operation.

FTP/SFTP

All commands of FTP/SFTP are migrated to equivalent Automation 360 actions of the FTP/SFTP package. There is no change in behavior or command name.

Get files and Get folder actions return runtime errors if they have additional criteria based on dates, which are provided as variables that have values in a format other than MM/DD/YYYY. You must fix such instances after bot migration. During the migration process, these two actions also add extra error handlers in the migrated bots when filtering is done on datetime.

In Enterprise 11, if a bot was using the FTP / SFTP commands, after migration, the respective FTP / SFTP actions are assigned a local session in Automation 360.

If/Else

Variables containing string condition

“ If ” with the following operators is migrated as a String condition in Automation 360:

=
< >
Include
Does not Include

For the Random variable of the String subtype, Automation 360 adds the Generate random string action of the String package to generate a random string above the If condition and assigns the value to the respective migrated variable.

Variable containing number condition

“ If ” with the following operators is migrated as a Number condition in Automation 360:

>=
<=
>
<

For the Random variable of the Number subtype, Automation 360 adds the Assign a random number action of the Number package to generate a random string above the If condition and assigns the value to the respective migrated variable.

Value type variable containing date

The system tries to evaluate if a condition on a variable has a date value. If found, it migrates If with the Datetime condition in Automation 360. Otherwise, the system migrates it as a string or number condition based on the operator used. In those cases, you must change it to a date condition after the bot migration if a date operation is involved.

Additionally, you might also have to change the date format to one that is compatible with your data. The default format used to convert a date to string is MM/dd/yyyy HH:mm:ss.

See If package.

Image Recognition

The If command with the Image Recognition condition in Enterprise 10/Enterprise 11 can become one of the following actions in Automation 360 based on the selected Enterprise 10/ options:

If > Image file is found in image file – Created if Image1 has the From File option selected and Image2 has the From File option selected in Enterprise 10 or Enterprise 11.
If > Image file is found in a window – Created if Image1 has the From File option selected and Image2 has the From Window option selected in Enterprise 10 or Enterprise 11.
If > Window is found in image file – Created if Image1 has the From Window option selected and Image2 has the From File option selected in Enterprise 10 or Enterprise 11.
If > Window is found in a window – Created if Image1 has the From Window option selected and Image2 has the From Window option selected in Enterprise 10 or Enterprise 11.

See If package.

Important: If a condition involves date, under certain situation, you must change the migrated information to a date condition after the bot migration.

The table below shows how various conditions are migrated to the respective Automation 360 conditions.


Enterprise 11 or Enterprise 10 commands	Equivalent Automation 360 actions and packages
Task Successful or Task Unsuccessful	Migrated to the equivalent If condition of Task Bot package.
Script Successful or Script Unsuccessful	Script successful/unsuccessful is migrated to respective If > Script Successful and If > Script Unsuccessful actions of the Legacy automation package.
Object Properties	Migrated to the If > Condition > Window Exists and Object conditions of the Recorder package.
Application Running or Application Not Running	Migrated to the equivalent If condition of the Application package.
File Exists, File Does Not Exist, File Date, File Size	Migrated to the equivalent If condition of the File package.
Folder Exists or Folder Does Not Exist	Migrated to the equivalent If condition of the Folder package.
Ping Successful Or Ping Unsuccessful	Migrated to the equivalent If condition of the Ping package.
Web Control Exists or Web Control Does Not Exists	Migrated to the equivalent If condition of the Legacy Automation package.
Window Exists/Window Does Not Exist	The following commands configured with the "Show child and hidden windows" option selected are migrated to the Automation 360 Legacy Automation package: If > Condition > Window Exists If > Condition > Window Does Not Exist
Logic Successful/Logic Unsuccessful	The If command is migrated to If > Task Successful and If > Task Unsuccessful respectively. The Else If command is migrated to Else If > Task Successful and Else If > Task Unsuccessful respectively. Bots that use the Logic Successful or Logic Unsuccessful condition and return an output variable to the parent bot, can be migrated to Automation 360. Bots that use Credential Vault variables are passed from one MetaBot Logic to another MetaBot Logic for both IF > Logic Successful and IF > Logic Unsuccessful commands. You can migrate a MetaBot with a Logic (parent) that includes a renamed Logic (child). If a child Logic is renamed after it is mapped to the parent Logic, this parent Logic mapping is migrated with the new name. Applies from v.25: Enterprise 11 or Enterprise 10 bots that use the If > Logic Successful or If > Logic Unsucessful command are migrated when a referred MetaBot Logic name is renamed or has changed the relative path after mapping. If a MetaBot Logic is renamed or changed the path after being mapped in the TaskBots, then the TaskBots are now migrated with the new MetaBot Logic name or path. For information about how a bot is migrated if the Logic Successful command passes a Credential Vault variable, see Run Logic.
Service is running/Service is not running	The If command is migrated to If > Service is running and If > Service is not running. The ElseIf command is migrated to Else If > Service is running and Else If > Service is not running.

Image Recognition

The Image Recognition command is split into Find file image inside window image and Find window image inside another window image actions in Automation 360.

In Automation 360, Advanced option is used as the default comparison mode. The other comparison modes (such as Gray-scale, Normal and Monochrome) that existed in Enterprise 10 and Enterprise 11, are hidden in Automation 360 but match the behavior with Automation 360 after migration. The migration process maps the information automatically and does not impact related bots.

When you run a migrated bot with Image Recognition that contains an If, IF/ELSE, or Loop action, an error displays when the window does not exist.

Migration of bots with the Image Recognition command might fail if the command is using any file type other than the following:

.jpg
.jpeg
.jpe
.jfif
.bmp
.gif

See Image Recognition package.

Insert Keystrokes

This command is called Simulate Keystrokes in Automation 360. The following keystroke conventions have changed:


Enterprise 11 or Enterprise 10 commands	Equivalent Automation 360 actions and packages
[PAGE UP]	[PAGE-UP]
[NUM LOCK]	[NUM-LOCK]
[SCROLL LOCK]	[SCROLL-LOCK]
[PAGE DOWN]	[PAGE-DOWN]
[CAPS LOCK]	[CAPS-LOCK]
[UP ARROW]	[UP-ARROW]
[LEFT ARROW]	[LEFT-ARROW]
[RIGHT CLICK]	[MENU]
[RIGHT ARROW]	[RIGHT-ARROW]
[DOWN ARROW]	[DOWN-ARROW]
[ALT GR DOWN]	[ALT-GR DOWN]
[ALT GR UP]	[ALT-GR UP]
[$]	[DOLLAR]

In Enterprise 11 or Enterprise 10, the delay time is divided by the total characters and applied between each character stroke. In Automation 360, the delay you specify applies to the time between each keystroke.

The legacy Get keystrokes delay action in Automation 360 supports migrated bots that include the Simulate keystrokes action. The legacy Get keystrokes delay action matches the duration of delay defined in Enterprise 11 bots for the Insert Keystrokes command and simulates the same value in Automation 360 for the Simulate keystrokes action. After migration, if keystrokes are typed faster (for example, keystrokes used to perform shortcuts in Microsoft 365 Excel), add the Delay action after the Simulate keystrokes action to ensure that the bots run without issues. The legacy Get keystrokes delay action provides similar delay, as seen in Enterprise 11, in the migrated bots to ensure that the migrated bots produce the same output as seen in Enterprise 11. However, this change leads to the command being split into multiple lines after migration.

If the Encrypt Keystrokes option is selected in Enterprise 11 or Enterprise 10 bots, after migration the value is stored in the Credential Vault. The migration process creates a locker in the Credential Vault with the following attributes:

Name of the locker created in Automation 360 is name AAE_<folder_name> (folder_name is the folder in which the migrated bot is available).
The migrated bot uses this locker. Users who have any permission for the folder that contains the bot can access the locker. The migration run-as user must have the Create standard attributes for a credential permission.
A locker contains only one credential for each bot. The name of the credential created is Keystrokes_<bot name> for the Task Bots and Keystrokes_<Metabot name>_<Logic name> for MetaBots.
Attributes for the locker are created with the name Encrypted_keystrokes.

If a locker, credential, or attribute with the same name is already available, the system appends the locker name, credential name, and attribute name with a numeric value. For example, AAE_<folder_name>_1, Keystrokes_<bot name>_1, and Encrypted_keystrokes_1 respectively. If name of the locker, credential, or attribute is longer than 50 characters, the system trims the characters at the end to limit the name to 50 characters.

Note: You cannot migrate a bot that is available on the local device and the Encrypt Keystrokes option is selected.

See Simulate keystrokes package.

Launch Website

This command is migrated to the Open action of the Browser package in Automation 360.

Commands with the Edge or Override default browser option deselected in the legacy product is automatically changed to use Default Browser after migration.

Enterprise 11 bots that open a website in a new window of all browsers supported by Automation 360 can be migrated. The Enterprise 11 bots that open the website in a new or an existing tab of the Internet Explorer browser can be migrated to Automation 360. The equivalent option to open the website in a new window, tab, or an existing tab is selected in the migrated bots.

Note: The support for the Microsoft Edge Legacy browser is no longer available, whereas the Microsoft Edge Chromium browser is supported. As a result, you cannot create new bots using the Microsoft Edge Legacy browser. However, the existing bots created in Microsoft Edge Legacy browser can be updated using other supported browsers such as Google Chrome or Microsoft Edge Chromium browser.

See Browser package.

Important: If you have created bots in Enterprise 11 or Enterprise 10 using the Microsoft Edge browser, you must first port these bots to another browser, and then you can migrate them.

Log To File

This command is migrated to Log to file action in Automation 360.

See Log To File package.

Loop

The following table shows how the Loop command is migrated to the equivalent Automation 360 actions and packages:


Enterprise 11 or Enterprise 10 commands	Equivalent Automation 360 actions and packages
Loop command with the Times option selected	Loop action of the Loop package with the For n times option selected.
Loop command with the List option selected	Loop action of the Loop package with the For n times option selected.
Loop command with the Each Row in an Excel Dataset option selected	Loop action of the Loop package with the For each row in worksheet option selected. The system variable $Excel Column$ used inside the loop is now a user defined variable specified in the same iterator.
Loop command with the Each Row In A SQL Query Dataset option selected	Loop action of the Loop package with the For each row in a SQL query Dataset option selected. The system variable $Dataset Column$ used inside the loop is now a user defined variable specified in the same iterator.
Loop command with the Each File In A Folder option selected	Loop action of the Loop package with the For each file in a folder option selected. The system variables $Filename$ and $Extension$ are now keys name and extension of a dictionary variable specified in the same iterator. In Enterprise 11, the bots does not encounter an error if the folder does not exist. In Automation 360, the migrated bots encounter an error if the folder does not exist.
Loop command with the Each Folder In A Folder option selected	Loop action of the Loop package with the For each folder in a folder option selected. The system variable $Folder name$ used inside the loop is now a user defined variable specified in the same iterator. In Enterprise 11, the bots does not encounter an error if the folder does not exist. In Automation 360, the migrated bots encounter an error if the folder does not exist.
Loop command with the Each Row In A CSV/Text File option selected	Loop action of the Loop package with the For each row in CSV/TXT option selected. The system variable $Filedata Colum$ used inside the loop is now a user defined variable specified in the same iterator.
Loop command with the Each Email Message On Mail Server option selected	Loop action of the Loop package with the For each mail in mailbox option selected. The system variables $Email Cc$, $Email From$, $Email Message$, $Email Received Date$, $Email Received Time$, $Email Subject$, and $Email To$ are now keys emailCc, emailFrom, emailMessage, emailReceivedDate, emailReceivedTime, emailSubject, and emailTo respectively of a dictionary variable specified in the same iterator.
Loop command with the Each Node In An XML Database option selected	Loop action of the Loop package with the For each node in an XML database option selected. The system variable $XML Data Node$ used inside the loop is now a user defined variable specified in the same iterator.

The following commands configured with the Show child and hidden windows option selected are migrated to the Automation 360 Legacy Automation package:

Loop > Condition > Window Exists
Loop > Condition > Window Does Not Exist

Variables containing string condition

“ If ” with the following operators is migrated as a String condition in Automation 360:

=
< >
Include
Does not Include

For the Random variable of the String sub-type, Automation 360 adds the Generate random string action of the String package to generate a random string above the If condition and assigns the value to the respective migrated variable.

Variable containing number condition

“ If ” with the following operators is migrated as a Number condition in Automation 360:

>=
<=
>
<

For the Random variable of the Number sub-type, Automation 360 adds the Assign a random number action of the Number package to generate a random string above the If condition and assigns the value to the respective migrated variable.

Variable containing date conditions

The system tries to evaluate if a condition on a variable has a date value. If found, it migrates IF with the Datetime condition in Automation 360. Otherwise, the system migrates it as a string or number condition based on the operator used. In those cases, you must change it to a date condition after the bot migration if a date operation is involved.

Additionally, you might also need to change the date format to one that is compatible with your data. The default format used to convert a date to string is MM/dd/yyyy HH:mm:ss.

List type variable

Loop on a variable condition of type List is migrated to either String or Number condition based on the operator used in the condition. The system uses the list index to validate the condition.

Web Control Exists or Web Control Does Not Exist

Loop with Web control exists and Web control does not exist conditions are migrated to Loop > While conditions Web control exists and Web control does not exist of the Legacy Automation package respectively.

See the following table to understand how various conditions are migrated to the respective Automation 360 conditions.


Enterprise 11 or Enterprise 10 conditions	Equivalent Automation 360 actions and packages
Web Control Exists or Web Control Does Not Exists	Migrated to the equivalent If condition of the Legacy Support package.
Object Properties	Migrated to the Object condition of the Recorder package.
Application Running or Application Not Running	Migrated to the equivalent If condition of the Application package.
File Exists, File Does Not Exist, File Date, File Size	Migrated to the equivalent If condition of the File package.
Folder Exists or Folder Does Not Exist	Migrated to the equivalent If condition of the Folder package.
Ping Successful Or Ping Unsuccessful	Migrated to the equivalent If condition of the Ping package.
Service is running or Service is not running	Migrated to the equivalent If condition of the Service package.

The following table shows the Loop commands supported for migration and their respective mappings in Automation 360.


Enterprise 11 or Enterprise 10 commands	Equivalent Automation 360 actions and packages
Exit Loop	Break
Continue

Message Box

This command is migrated to Message box action in Automation 360.

See Message box package.

Object Cloning

This command is migrated to the Recorder package > Capture action in Automation 360.

Migration is supported for applications using the following technologies (including when they are within a Citrix environment):

MSAA (Standard desktop technology)
Google Chrome browser
Internet Explorer browser
Java desktop
Web Java
UI Automation (advanced)
Firefox browser (object based on HTML technology only)
Microsoft Silverlight version 5

The following table lists the behavioral differences between Enterprise 11 or Enterprise 10 and Automation 360:


Enterprise 11 or Enterprise 10 behavior	Automation 360 behavior
GetAllChidrenName and GetAllChidrenValue commands return string type variable values	The equivalent actions in Automation 360 return list values. The migration process joins the list values and stores them into a string variable to maintain consistent bot behaviors across releases.
In Enterprise 11, the command is used to capture the control in an image	The entire window image is captured with the control highlighted using a red rectangle

Object Cloning with the Export to CSV action in Enterprise 10/Enterprise 11 is migrated into the following packages/actions combinations because the action does not exist in Automation 360:

The Capture action saves the captured data into a table variable.
The Write to file action of the Data table package is then used to save the data from the table variable to the CSV file.

The window title is copied from the source command to the destination action.

The X, Y coordinates and window title are also migrated to Automation 360.

The Coordinate and Image execution or play modes from Enterprise 11 are migrated as the following actions:

Play mode as coordinates:

Play mode as coordinates

Mouse click actions: The Click, Right Click, Left Click, Middle Click, and Double Click actions are migrated in the Mouse: Click action as a combination of Button and Events. The corresponding mouse buttons with events are migrated as shown:

Click changes to Left Button-Click
Right Click changes to Right Button-Click
Left Click changes to Left Button-Click
Middle Click changes to Middle Button-Click
Double Click changes to Left Button Double-Click

Get Text

The Get Text action is migrated as a combination of actions that include Mouse: Click with Left Button-Click, Clipboard: Clear, Delay, and Simulate keystrokes.

Set Text

The Set Text action is migrated as a combination of actions that include Mouse: Click with Left Button-Click, Clipboard: Clear, Delay, and Simulate keystrokes.

The following table shows the property name changes for the controls and objects captured using Object Cloning. The migration process automatically maps the name changes. However, if a property is used inside a variable, you must manually enter the new name in the variable.


Enterprise 11 or Enterprise 10 property name	Automation 360 property name
Object ID	ID
Type	Control Type
State(s)	States
Action	DefaultAction
Bold	IsBold
Italic	IsItalic
Underline	IsUnderline
Strike Through	IsStrikethrough
Super Script	IsSuperscript
Sub Script	IsSubscript
Background Color	BackgroundColor
Foreground Color	ForegroundColor
Font	FontFamily
Font Size	FontSize
First Line Indent	FirstLineIndent
Left Indent	LeftIndent
Right Indent	RightIndent
Line Spacing	LineSpacing
Space Above	SpaceAbove
Space Below	SpaceBelow
Item Name	ItemName
Item Value	ItemValue
Animated	IsAnimated
CapStyle	Cap
Font Weight	FontWeight
Horizontal Alignment	HorizontalAlignment
Hidden	IsHidden
Read Only	IsReadOnly
Bottom Margin	BottomMargin
Left Margin	LeftMargin
TopMargin	TopMargin
Right Margin	RightMargin
Overline Color	OverlineColor
Strikethrough Color	StrikethroughColor
Tabs Style	Tabs
Text Flow Direction	TextFlowDirection
Underline Color	UnderlineColor
HTML ID	IEID
HTML Name	IEName
HTML Alt	IEAlt
HTML Tag	IETag
HTML Class	IEClass
HTML InnerText	IEInnerText
HTML SourceIndex	IESourceIndex
HTML HRef	IEHref
HTML Value	IEValue
HTML Type	IEType
HTML ClassId	IEClassId
HTML Title	IETitle
HTML Tag Index	IETagIndex
HTML HasFrame	IEHasFrame
HTML FrameID	IEFrameID
HTML Frame Name	IEFrameName
HTML Frame Src	IEFrameSrc
HTML Width	IEWidth
HTML Top	IETop
HTML Left	IELeft
HTML Height	IEHeight
HTML Frame Path	IEFramePath
Item Collection	ItemCollection
OCR Engine	OCREngine
OCR Occurrence	OCROccurrence
Row Control Type	RowControlType
GetSelectedIndex	GetSelectedIndex
GetSelectedText	GetSelectedText

The migration process truncates the data to 64 KB if the Enterprise 11 or Enterprise 10 bots that use an object and any properties of that object contain data larger than 64 KB. This is to ensure that these bots do not encounter an error after migration.
In Enterprise 11, you can remove the control type of an object from the search criteria, but this option is not available in Automation 360. In Automation 360, the capture action executes only on objects with the same control types. If you want to use this action on objects with different control types, you must capture these control types in separate capture actions.

See Using the Capture action.

OCR

All commands of OCR are migrated to equivalent Automation 360 actions of the OCR package. There is no change in behavior or command name.

In Enterprise 11, ABBYY, MODI, TESSERACT,TOCR OCR options are available as OCR engines. In Automation 360, by default only ABBY OCR engine is used.

See OCR package.

Open Program/File

This command is migrated to the Open program/file action of the Application package.In Enterprise 10/Enterprise 11, this command does not throw an error if you provide an incorrect value in the Start In field. Automation 360 validates the value entered for the same field and throws an error during bot execution.

See Application package.

Important: Users must change the bot accordingly if they want to continue even if the Start In value field is incorrect.

PDF integration

The following table shows the PDF integration command and their equivalent actions and packages in Automation 360:


Enterprise 11 or Enterprise 10 commands	Equivalent Automation 360 actions and packages
Merge Document	Merge document
PDF to Image	Extract image
Extract Form Fields	Extract field
Extract Text	Extract text
Split Documents	Split documents
Encrypt Document	Encrypt document
Decrypt Document	Decrypt document

If the Enterprise 11 bot uses the Extract Form Fields command and stores values in the Credential Vault, the migration process migrates these values in the Automation 360 Credential Vault.

The output of an Enterprise 11 bot is mapped with multiple variables in the equivalent actions of the PDF package after that bot is migrated to Automation 360. This reduces the number of actions in the migrated bot because a separate action is no longer required to map output to a variable.

See PDF package.

PGP

All commands of PGP are migrated to equivalent Automation 360 actions of the PGP package. There is no change in behavior or command name.

See PGP package.

Play Sound

All commands of Play Sound are migrated to its equivalent actions of the Sound package in Automation 360.

Automation 360 supports only .mp3 and .wav file types in Play media file action.

See Play Sound package.

Printer

Default Printer, Remove Printer, and Select Default Printer are migrated to the equivalent actions of the Printer package in Automation 360.

See Printer package.

Prompt

All commands of Prompt are migrated to equivalent Automation 360 actions of the Prompt package.

The following table shows commands that can be migrated with name changes.


Enterprise 11 or Enterprise 10 commands	Equivalent Automation 360 actions and packages
Prompt For Value	Converts to the For value action. In addition, Simulate keystroke action is added below the For value action to perform the keystrokes on the specific window title. This is to retain the execution behavior of old bots.
Prompt for File	For file
Prompt for Folder	For folder
Prompt For Yes/No	For yes/no

See Prompt package.

Read from CSV/Text

The Read from CSV/Text is converted to Open, Read, and Close actions in the Automation 360 CSV/TXT package.

If your Enterprise 10/Enterprise 11 bot is using a variable as a session name and the Loop action used to read all rows of the CSV/TXT is using a hard-coded session name instead of a variable, then you must review the migrated bot and set the output variable of the CSV/TXT > Read action in the respective loop. Otherwise, you will get a UI error when you edit the Automation 360 bot.

In Automation 360, if the CSV/TXT file is not present in the specified file path, the bot returns an error message, whereas in Enterprise 11, the bot does not return such message.

Important: Review the migrated bot and set the output variable of the CSV/TXT > Read action in the respective loop.

REST Web Service

The Save Header To option in Enterprise 11 is migrated to Automation 360. This option enables you to store the response header in the array and dictionary variables with the response header name as key and its header value as the value of the dictionary.

In Enterprise 11, the failure response is captured by default. In Automation 360, enabling the Capture failure response option captures the errors and adds to the response dictionary variable. When you migrate an Enterprise 11 bot to Automation 360, the Capture failure response option is enabled by default to capture the failure response of the migrated bot.

The time-out value configured in Enterprise 11 to send REST request is migrated to Automation 360 as part of global values (AARestTimeOut). The default time-out value is set as 60000 ms in Automation 360. You can update this value if the REST Web Service is taking more time to receive a response.

See REST Web Service package.

Run Logic

Run logic command is migrated to the Run action of the Task Bot package in Automation 360.

Additionally, Error Handling with the Run Logic command is migrated to the Try and Catch block.

Applies from v.25: Enterprise 11 or Enterprise 10 bots that use the Run Logic command are migrated where a referred MetaBot Logic name is renamed or has changed the relative path after mapping. If a MetaBot Logic is renamed or changed the path after being mapped in the TaskBots, then the TaskBots are now migrated with the new MetaBot Logic name or path.
Changing the relative path is applicable in the following scenarios:
- Logic is moved from one folder to another.
- Logic is moved from a MetaBot root-level folder to a subfolder.
- Logic is moved from a subfolder to a folder at MetaBot root level.
- The folder that has the Logic is renamed.
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.
Applies from v23: Enterprise 11 or Enterprise 10 bots that use the Run Logic command are allowed to pass Credential Vault type variables from the parent bot to a MetaBot non-Credential Vault type variable. However, in Automation 360, Credential Vault variables are passed only to credential type variables (and not to non-Credential Vault type variable) for enhanced security. Therefore, the migration process first converts the Credential Vault type variable to the string type variable using the Convert credential to string action of the Credential package so that the migrated bot can run successfully. The string variable is then assigned to a temporary variable that is used as an input parameter in the Task > Run action to call the MetaBot Logic.
Bots that use Credential Vault variables are passed from one MetaBot Logic to another MetaBot Logic for the Begin Error Handling > Run Logic command.
When you perform a Begin Error Handling > Run Logic command, you can migrate a MetaBot with a Logic (parent) that includes a renamed Logic (child). If a child Logic is renamed after it is mapped to the parent Logic, this parent Logic mapping is migrated with the new name.

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.

Run Script

The Run Script command is migrated to the Run Script action of the Legacy automation package.

When you use the Legacy automation package with the Run Script action after migration, you might run into issues in some scenarios, so review the cause and how to resolve the issue:

Cause: In the Run Script action > Input Parameters field, if the value of the argument (passed by String > Assign action) contains double quotation marks followed by a backslash at the end of the argument and the variable value contains a space, the string breaks where the first space occurs (this is due to upgrade changes in openJDK).
Example: Consider a folder path as the argument value that is passed using String > Assign action, "\\fwus129ns.ny.fw.gs.com\mahatb\home\My Documents\Test Adhoc Request\". When you migrate this Enterprise 11 bot to Automation 360, this single argument value is considered as four different argument values in Automation 360, as follows:
- \\fwus129ns.ny.fw.gs.com\mahatb\home\My
- Documents\Test
- Adhoc
- Request\
Solution: Edit the Enterprise 11 bot and remove the double quotation marks in the variable value in String > Assign action.

SAP Integration

This command is migrated to the Recorder package > Capture action in Automation 360. All object properties in the Enterprise 11 bots are mapped with the equivalent properties in the migrated bots.

Note: If the Enterprise 11 bot with the SAP Integration command is using SAP GUI 740 or earlier versions, perform additional steps in the Bot Agent machine to run the migrated bot successfully in Automation 360. For more information, see Failed to capture SAP application using SAP GUI 740 (A-People login required).

If you run migrated bots with the SAP GUI option selected but the SAP GUI window is closed, an exception error is displayed. This occurs because, the Recorder package uses the Window title during runtime and, in Automation 360, SAP Integration is migrated to Recorder package.

The following table provides a list of SAP objects and the actions that can be migrated to Automation 360.


Object	Action
Text box	Set Text, Append Text, Left Click, Right Click, Double Click
Combo box	Select Item By Text, Select Item By Index, Get Total Items, Get Selected Item Text, Get Selected Item Key, Get Property, Set Focus, Left Click, Right Click, Double Click
Check box	Check, Uncheck, Toggle, Get Status, Get Property, Set Focus, Left Click, Right Click, Double Click
Button	Click, Get Property, Left Click, Right Click, Double Click
Radio button	Select, Get Status, Get Property, Set Focus, Left Click, Right Click, Double Click
Menu bar	Select Item By Text, Get Property, Set Focus, Left Click, Right Click, Double Click
Tree	Get Property, Set Focus, Left Click, Right Click, Double Click, Get total items, Get selected index, Get selected text, Select item by index, Select item by text
Label	Click, Get Property, Set Focus, Left Click, Right Click, Double Click
Tab	Get Property, Set Focus, Left Click, Right Click, Double Click, Get total items, Get selected index, Get selected text, Select item by index, Select item by text
Rest of the control (It includes controls such as: `GuiMainWindow`, `GuiBox`, `GuiUserArea`, `GuiTitlebar`, and `GuiStatusbar`)	Get Property, Set Focus, Left Click, Right Click, Double Click

The following table shows the actions performed on the main window object and their equivalent actions in Automation 360:


Enterprise 11 action	Equivalent Automation 360 action
Activate Window	Activate action of the Window package.
Close Window	Close action of the Window package.
Execute Script	Append SAP session and Run function actions of the Legacy Automation package.
Maximize Window	Maximize action of the Window package
Restore Window	Restore action of the Window package

SAP commands that support BAPI features in Enterprise 11 are migrated to equivalent actions of the SAP BAPI package in Automation 360.

The following table shows the Enterprise 11 command and its equivalent action in Automation 360:


Enterprise 11 command	Automation 360 action
Connect	SAP BAPI > Connect You must create the JcoDllPath and JcoJarPath global values. Update the JcoJarPath global value with the location of the SAP Java connector package and the JcoDllPath with the location of the SAP Java connector DLL.
Create Function	SAP BAPI > Create function
Get Data command with the Field option selected	SAP BAPI > Get field
Get Data command with the Table option selected	SAP BAPI > Get table
Get Data command with the Structure option selected	SAP BAPI > Get structure
Set Data command when the Fields, Table, or Structure option is selected	SAP BAPI > Set field
Invoke Function	SAP BAPI > Run function
Run standard workflow	SAP BAPI > Run standard workflow
Run custom workflow	SAP BAPI > Run custom workflow

Send Email

In Enterprise 10/Enterprise 11, the Send Email command uses user-specific email settings stored as credential attributes within the system locker. When the first bot is migrated, we create a custom locker called AAE_Email and add the AAE_EmailSettings credential with the Username and Password attributes to it. Additionally, we create Global Values for the non-credential attributes, such as Server host, port, SSL and authentication, which correspond to the same Email Settings. Enterprise 10/Enterprise 11 Email Settings credentials are split into Credential Variable and Global Values in Automation 360, so during the migration process, email settings are migrated as follows:


Enterprise 10/Enterprise 11 Email Settings	Automation 360 Email Settings	Automation 360 Storage Type
Host	AAE_EmailSettings_host Global Value of type String
Port	AAE_EmailSettings_port Global Value of type Number
Use secure connection (SSL/TLS)	AAE_EmailSettings_ssl Global Value of type Boolean
My server requires authentication	AAE_EmailSettings_auth Global Value of type Boolean
Username	userName Credential attribute within AAE_EmailSettings credential assigned to AAE_Email locker
Password	password Credential attribute within AAE_EmailSettings credential assigned to AAE_Email locker

Services

All commands of Services are migrated to equivalent Automation 360 actions of the Service package. There is no change in behavior or command name.

SOAP Web Service

This package behaves the same in Automation 360.

If a SOAP web service is configured to call REST APIs, then we migrate them to the REST web service action instead of the SOAP web service action. Based on additional XML operations, we add actions from the XML package to make sure the migrated bot gives same result as the legacy bot.

The time-out value configured in Enterprise 11 to send SOAP request is migrated to Automation 360 as part of global values (AASoapTimeOut). The default time-out value is set as 60000 ms in Automation 360. You can update this value if the SOAP Web Service is taking more time to receive a response.

Example of using the SOAP web service action

Enterprise 11 provides options to select the URI type for execution such as Default, Static, and Dynamic. However, in Automation 360, no option is available to select the URI type for execution. The Enterprise 11 URI types are migrated in Automation 360 as follows:

Default and Static: If your Enterprise 11 bot is configured with the Default or Static URI type, it is migrated as static and the Address location field is automatically populated.
Dynamic: If your Enterprise 11 bot is configured with the Dynamic URI type, it is migrated as dynamic and the Address location field is empty.

See SOAP Web Service package.

String Operation

The Enterprise 11 or Enterprise 10 String Operation command is migrated to equivalent actions of the String package.

The following table shows the String Operation commands and their equivalent actions in Automation 360.


Enterprise 11 or Enterprise 10 commands	Equivalent Automation 360 actions and packages
Before-After	Extract
Compare	Compare
Find	Find
Length	Length
Lower Case	Lowercase
Replace	Replace
Reverse	Reverse
Split	Split
Substring	Substring
Trim	Trim
Upper Case	Uppercase

In Enterprise 11, if you are using carriage return (CR) (\r) in regular expression in the String Find command, after migration, the output displayed in Automation 360 is different from the output in Enterprise 11.

Workaround: In Automation 360, use \r|\R instead of \r for carriage return.

In Enterprise 11, both carriage return (CR) and newline (LF) were enumerated to calculate the total length of String Operation. However, in Automation 360, only newline (LF) is considered for the length of String Operation. Hence, the length count in the resulting output in Automation 360 is lesser.

Enterprise 11 bots can use regular expressions in the Find and Replace commands to search for the string on which you want to perform an operation. The equivalent actions in Automation 360 too can use regular expressions to search for the string on which you want to perform an operation.

In Enterprise 11, the system considers the new line character (/n) used in the variable when you use the Find and Replace commands. However, in Automation 360, the system does not consider the new line character when you use the Find and Replace commands.

When you migrate a bot to Automation 360 with the string operation set to Before or After action, the output is retrieved correctly and the operation is successful. The matching output is displayed even if no characters are present before the matched string. In Enterprise 11, bots with Before or After action do not retrieve output correctly and therefore retrieve the source string itself. If no characters are present before the matched string, the output is displayed as no match is found.

Example:

Drag Before/After Action → (Inputs : [Source = (ABCZ)] → [Before = Z] → [assign to Prompt-assign] → Output : Empty("")

Drag Before/After Action → (Inputs : [Source = (ZABC)] → [After = Z] → [assign to Prompt-assign] → Output : ZABC

System

Lock computer, Logoff, Restart, and Shutdown actions are migrated to the equivalent actions of the System package in Automation 360.

See System package.

Task

The following table shows the different commands that are migrated to the respective actions of the Automation 360 Task Bot package.


Enterprise 11 or Enterprise 10 commands	Equivalent Automation 360 actions and packages
Pause	Pause
Stop Task	Stop
Run Task	Run. The output returned by the child bots is mapped to the respective variable in the parent bots.

Terminal Emulator

Encrypt text is not supported in the Send Text and Set Field actions for Automation 360. We recommend that you use Credential Vault instead of plain text.

In Enterprise 11 and in Automation 360:

Bots that use the following terminal model can be migrated to Automation 360:
- VT 220 model of the VT Series terminal type
- IBM 5555 B01 and C01 models of the TN 5250 terminal type
A session (used to establish a connection with the terminal server) can be shared between the parent bot and a child bot. You can close a session from the child bot instead of closing the session from the parent bot.
You can use the Default terminal in bots for the VT100 terminal type.
Bots that send Japanese text using the Send Text command in Enterprise 11 with the DBCS option from the Encoding list and the Japanese Shift-JIS (932) option from the CodePage list selected in the Connect command can be migrated to Automation 360.
Applies only to v.24 and earlier : In the Terminal Emulator, when you manually click the key in the keyboard, the main keyboard Enter is identified as {enter} in Enterprise 11, while in Automation 360, it is identified as {return}.
Ensure that you set the correct row value (use the Set row value as 24 to set the cursor at the last row) in the Set cursor position action for bots to execute successfully.

Automation 360 does not support legacy technology and by default supports all capabilities of Advance Technology of the Enterprise 10/Enterprise 11 bots.

The maximum index value in Automation 360 is 99999. The migration process automatically updates the value of Field index in the Set Field action to 99999 to meet the maximum value restriction. If the index value is higher that 99999 and is used in a variable, then you must change it manually.

The SSHI feature is not yet supported in Automation 360.

The Search field action enables you to search for field index or field name by using a text.

Bots created in Enterprise 11 no longer show the Trying... text after the bots are migrated to Automation 360.

See Terminal Emulator package.

Variable Operation

The following are the operations when a value is assigned to the variable:

Value type variables

The functionality for this command has been divided into multiple packages in Automation 360.

In Enterprise 10/Enterprise 11, this command was performing assignment operations for all the supported datatypes. Automation 360 has built a dedicated Assign action for each data type. The migration process handles the mapping of the corrected packages and action based on the assignment that the respective variable operation is performing.

For Enterprise 11 bots that use the Decimal configuration option, the To string action of the Number package is added in the migrated bots. In Enterprise 11, the system rounds off the value based on the value specified in the Decimal configuration field. For example, if the value that is assigned to the variable is 13.456 and the value specified in the Decimal configuration field is 2, the system rounds off the value in Enterprise 11 to 13.46. In Automation 360, the value is trimmed instead of rounded off. For example, the value 13.456 will be converted to 13.45 in Automation 360.

List type variables

Operations involving on list assignments are migrated to the Set item of the List package. If the operation has a fixed value, the system creates a temporary variable and stores the fixed value in it. You can then use this temporary variable in the Assign action of the List package to save it.

Array type variables

Operations involving on array assignment is migrated to Set value of a single cell action of the Datatable package to set a value for specific rows and columns.

Dictionary type variables

Operations involving dictionary assignment is migrated to the Put action of the Dictionary package to set the value for a specific key. If the key is a combination of a variable and fix value (for example $Dictionary(key-$id$)$), then the String package > Assign action is added to get the actual key.

System variable $Date$

The Enterprise 10/Enterprise 11 Variable Operation command that uses the $Date$ system variable is migrated to Automation 360 by adding new date actions based on the operation being performed using $Date$. The migration process also converts the date value to a default string format – mm/dd/yyyy HH:mm:ss.

Random variable of sub type string: We migrate and map this directly.

The following are the variable operations when a value of the variable is reinitialized:

List variable: For the Variable Operations command that reinitialize the list variable in Enterprise 10/Enterprise 11, the migration process creates a temporary list variable with new values and assign it to the destination list variable in Automation 360.
List variable declared by reading a Text file: This command is migrated to the Import list from text file action in the Legacy Automation package.
Note: In Automation 360, the bot encounters an error if the source file is empty or does not contain a key for initializing the list variable, unlike in Enterprise 10 or Enterprise 11.
Array variable declared by reading a Text file: The Array variable type is migrated as a Table variable type in Automation 360. The system uses the CSV/TXT package to read and load the respective data into the table variable in the bot.
Dictionary variable: The migration process creates a temporary dictionary variable to store all keys and values. Then the system uses the Dictionary package > Assign action to update the target variable with the keys and values from the temporary dictionary variable.
Dictionary variable declared by reading a Text file: The migration process addresses this use case by adding actions to read the CSV file using the CSV/Text package and storing the data in a table variable. Then it adds actions to perform a loop on the table variable and uses the Dictionary package > Put action to add keys and values into the dictionary variable.
Array variable declared by reading an Excel/CSV file: The migration process addresses this use case by migrating the Array variable type as a Table variable type in Automation 360. The system adds Open, Get Multiple Cells, and Close actions of the Excel Advance package and populates the table variable.

The following are the variable operations when a value of the system variable is reset:

Variable Operation (resetting system variables)

The following system variables are migrated as user defined variables in Automation 360. The system adds a respective action to clear the value of the equivalent variable created in Automation 360.

Email Cc
Email From
Email Message
Email Received Date
Email Received Time
Email Subject
Email To
Error Description
Error Line Number

Wait

Wait for window and Wait for screen change in Automation 360 throws an exception error if the respective window is not open/close in the specified time or the screen is not found in specified time. In these cases, the system adds try and catch block if the command was configured to stop the bot and adds the Stop task action in the catch block. This is to ensure that the execution behaviour of migrated bots is the same as Enterprise 10/Enterprise 11.

Because we are migrating commands with the Stop bot action is encapsulated with the try and catch block in Automation 360, the bot also stops if the action fails due to some other reason. During the migration process, the Stop bot action also adds extra error handlers in the migrated bots when the Stop the task option is selected.

The Wait for window action can have negative values for coordinates that are not supported in Automation 360. The negative values are changed to 0 during the migration process.

Web Recorder

All commands (except those mentioned below explicitly) of Web recorder are migrated to respective actions within the Legacy Automation package in Automation 360. The Legacy Automation package ensures that the migrated bots give the same results as Enterprise 10/Enterprise 11. However, it is not recommended to use the Legacy Automation package for new development.

Find broken links is migrated to Browser > Find broken links package. Additionally, Enterprise 10/Enterprise 11 has the "Find broken links timeout" and "Find broken links" options within the Tools > Options. Automation 360 has these options as part of the action and the timeout defaults to 10 seconds and the number of parallel threads value defaults to 10.

Download files is migrated to Browser > Download files package.

During the migration process, the Extract table action adds extra error handlers in the migrated bots when the On error continue with next action check box is enabled.

Window Action

All commands of Windows Actions are migrated to its equivalent actions of the Window package in Automation 360.

Enterprise 11 bots can use regular expressions in the Get Active Window Title, Activate Window, Maximize Window, Minimize Window, Close Window, and Resize Window commands to search for the window on which you want to perform an operation. The equivalent actions in Automation 360 too can use regular expressions to search for the window on which you want to perform an operation.

See Window package.

XML

All commands of XML are migrated to its equivalent actions of the XML package in Automation 360.

The following command names have changed:


Enterprise 10/Enterprise 11	Automation 360
End XML session	End session
Start XML session	Start session
Delete Node/Attribute	Delete node
Update Node/Attribute	Update node
Get nodes action with the "Single Nodes" option selected	Get single node action
Get nodes action with the "Multiple Nodes" option selected	Get multiple node action

In Enterprise 11, when you set the XML command to Get Node(s) with the Multiple Nodes option selected, the XPath Expression returns only the last element of the matching expression. In Automation 360, the XPath Expression returns all the matching elements.

Enterprise 11 bots that extract nodes that contain namespaces from an XML file can be migrated to Automation 360. If you add a namespace to a node in an XML file, you must save and reload the XML file to reflect the changes.

See XML package.