Read and Review Automation Anywhere Documentation

Automation 360

Close Contents

Contents

Open Contents

How MetaBots are migrated

  • Updated: 12/06/2021
    • Automation 360 v.x
    • Migrate
    • RPA Workspace

How MetaBots are migrated

When you migrate a MetaBot to Automation 360, equivalent bots are created for the various logic available in the MetaBot, except for application screens. After successful migration, each logic in a .mbot file is converted to a TaskBot file.

A MetaBot contains assets and logic. Assets are the application screens or DLLs that are used to automate a task on an application. Logic is a set of commands to perform an operation and interact with other logic and bots.

The migration process performs the following actions:
  • Converts MetaBot logic to corresponding TaskBots.
  • Maintains the folder structure of the MetaBots after it is migrated. The new folders created in Automation 360 contain the TaskBots for each logic migrated to Automation 360.
  • Updates the TaskBots that use MetaBot logic to refer to the new TaskBots that are created for the migrated MetaBot logic.

    You do not have to update the TaskBots manually.

Features such as use of DLLs, input and output variables, and Execute permission which were available only for MetaBots are now available for all TaskBots.

We will use the following MetaBot to explain how it is migrated to Automation 360:
  • MetaBot name: MetaTask
  • Assets:
    • Login screen
    • General.dll
    • DLL\Binary.dll
  • Logic:
    • Common
    • Process1\Connect
    • Process1\Disconnect
    • Process1\Operations\Numeric

Benefits of reusable TaskBots in Automation 360

The following table lists the benefits of using resuable TaskBots in Automation 360 compared with MetaBots in Enterprise 11:
Automation 360 reusable TaskBots v11 MetaBots
You can navigate to a child bot through fewer clicks using the Finder component, thus saving time. Navigate to Editor > Finder to reach the child bot. You must navigate through the TaskBot > Run action to reach the child bot.
You can search the child bots from the private workspace as well as public workspace to use them in TaskBots. You must download the MetaBots to the local repository to use a child bot in the TaskBots.
Only a specific Logic is deployed when it is used in a task, which saves time and bandwidth. Entire MetaBot is deployed to the Bot Runner machine even if only one Logic is used in the Task.
Provides better RBAC, which enables you to customize permissions. MetaBots forces all Logic to have the same permissions even if multiple Logic are spread across different folders.

MetaBot migration process

The system creates a folder with the same name as the MetaBot within the My MetaBots folder available in the Bots folder, and the same folder structure as Enterprise 11 is retained. For example, if the folder structure in Enterprise 11 is Accounts/Tax/MetaTask.mbot, the system retains the folder structure as Accounts/Tax/MetaTask.mbot. All the components of a MetaBot are stored in the folder created for that MetaBot. In this example, the system creates the MetaTask folder in the Bots\My MetaBots folder and stores all the components the MetaBot in that folder.

Enterprise 10 bots that directly call DLLs and screens in a MetaBot without using MetaBot logic are migrated to the equivalent TaskBots and actions in Automation 360. In Enterprise 10, if a DLL that returns a list or array type parameters and the output of that DLL is mapped with a value type parameter, an extra space is added at the start of the output value. The extra space is not added to the output value after the bot is migrated.

10.1 MetaBots that use DLL functions that accept one-dimensional array and list type input parameters and is mapped with the array type parameter. In such cases, row index and column index are required as input to specify the value to be returned. After migration, the row index is considered as column number.
Note: For bots that are upgraded from 10.1 to 10.3.5 and then migrated to Automation 360, the Bot Migration Wizard does not show the dependency on the Bot and Dependent Bots page. For such bots, you must migrate the MetaBots before migrating the TaskBots that are calling those MetaBots.

Migration of DLLs

The system does not maintain the folder structure for assets in order to maintain the references between the DLLs. For the above example, General.dll and Binary.dll are stored in the MetaTask folder although the Binaary.dll is stored in the DLL subfolder.

Migration of screens

Each screen in a MetaBot is converted to a windows variable and the actions performed on the screen are migrated to the equivalent actions in Automation 360.

The following table lists the screens that can be migrated to Automation 360:
Browser Internet Explorer

Google Chrome (for object play type only)

Screen type Standard
Technology Java, HTML, MSAA, .Net, UI Automation (for object play type only)
Play type Object, Image, Coordinate

You can also migrate MetaBots with screens that are captured in the Citrix environment from applications that are based on Java, UI Automation, and MSAA technologies.

The linked objects on a MetaBot screen that are captured using the object play type are migrated to the Capture action of the Recorder package. The source object is displayed in the Main tab and the linked object is displayed in the Anchor tab of the Capture action.

The following table provides information about the actions that are performed on an object play type object available on the screen is migrated to the equivalent actions in Automation 360:
Play type Enterprise 11 Action Automation 360 Action
Object Get Property, Get Total Items, Get Selected Index, Get Selected Text, Select Item by Text, Select Item by Index, Click, Left Click, Right Click, Double Click Migrated to the Capture action of the Recorder package.

The GetAllChidrenName and GetAllChidrenValue commands in Enterprise 11/Enterprise 10 return string type variable values. In Automation 360, they return list values. The migration process joins the list values and stores them into a string variable to maintain consistent bot behaviors across releases.

The Object Cloning command with the Export to CSV action in Enterprise 11/Enterprise 10 is migrated to:
  • The Capture action of the Recorder package.

    This action saves the captured date into a table variable.

  • The Write to file action of the Data Table package.

    This action saves the data from the table variable to the CSV file.

The following table provides information about the actions that are performed on an image play type object available on the screen is migrated to the equivalent actions in Automation 360:
Play type Enterprise 11 Action Automation 360 Action
Image Left Click Migrated to the Find window in window action of the Image Recognition package with the Left Click selected from the Action list.
Right Click Migrated to the Find window in window action of the Image Recognition package with the Right Click selected from the Action list.
Double Click Migrated to the Find window in window action of the Image Recognition package with the Double Click selected from the Action list.
Middle Click Migrated to the Find window in window action of the Image Recognition package with the Left Click selected from the Action list.
Set Text Migrated to:
  • The Find window in window action of the Image Recognition package with the Left Click selected from the Action list.
  • The Delay action of the Delay package with the Regular delay set to 500 milliseconds.
  • The Simulate keystrokes action of the Simulate keystrokes package.
Get Text Migrated to the Capture area action of the OCR package.
The following table provides information about the actions that are performed on a coordinate play type object available on the screen is migrated to the equivalent actions in Automation 360:
Play type Enterprise 11 Action Automation 360 Action
Coordinate Click Migrated to the Click action of the Mouse package with the Left Button and Click options selected.
Left Click Migrated to the Click action of the Mouse package with the Left Button and Click options selected.
Right Click Migrated to the Click action of the Mouse package with the Right Button and Click options selected.
Middle Click Migrated to the Click action of the Mouse package with the Middle Button and Click options selected.
Double Click Migrated to the Click action of the Mouse package with the Left Button and Double click options selected.
Set text Migrated to:
  • The Click action of the Mouse package with the Left Button and Click options selected.
  • The Delay action of the Delay package with the Regular delay set to 500 milliseconds.
  • The Simulate keystrokes action of the Simulate keystrokes package.
Get text Migrated to:
  • The Click action of the Mouse package with the Left Button and Click options selected.
  • The Clear action of the Clipboard package.
  • The Delay action of the Delay package with the Regular delay set to 500 milliseconds.
  • The Simulate keystrokes action of the Simulate keystrokes package.
  • The Delay action of the Delay package with the Regular delay set to 500 milliseconds.
  • The Copy to action of the Clipboard package.
The following table provides information about actions that are performed on a coordinate play type custom object available on the screen that is migrated to equivalent actions in Automation 360:
Play type Enterprise 11 action Automation 360 action
Coordinate Click Migrated to the Click action of the Mouse package with the Left Button and Click options selected.
Left Click Migrated to the Click action of the Mouse package with the Left Button and Click options selected.
Middle Click Migrated to the Click action of the Mouse package with the Middle Button and Click options selected.
Double Click Migrated to the Click action of the Mouse package with the Left Button and Double click options selected.
Set text Migrated to the following:
  • The Click action of the Mouse package with the Left Button and Click options selected.
  • The Delay action of the Delay package with the Regular delay set to 500 milliseconds.
  • The Simulate keystrokes action of the Simulate keystrokes package.
Get text Migrated to the following:
  • The Click action of the Mouse package with the Left Button and Click options selected.
  • The Clear action of the Clipboard package.
  • The Delay action of the Delay package with Regular delay set to 500 milliseconds.
  • The Simulate keystrokes action of the Simulate keystrokes package.
  • The Delay action of the Delay package with Regular delay set to 500 milliseconds.
  • The Copy to action of the Clipboard package.
The following table provides information about actions that are performed on a text play type custom object available on the screen that is migrated to equivalent actions in Automation 360:
Play type Enterprise 11 action Automation 360 action
Text Click Migrated to the Find window in window action of the Image Recognition package with Left Click selected from the Action list.
Left Click Migrated to the Find window in window action of the Image Recognition package with Left Click selected from the Action list.
Double Click Migrated to the Find window in window action of the Image Recognition package with Double Click selected from the Action list.
Set text Migrated to the following:
  • The Find window in window action of the Image Recognition package with Left Click selected from the Action list.
  • The Delay action of the Delay package with Regular delay set to 500 milliseconds.
  • The Simulate keystrokes action of the Simulate keystrokes package.
Get text Migrated to the Capture area action of the OCR package.

Migration of logic

Each logic in a MetaBot is converted to a TaskBot and each command used in a logic is converted to the equivalent action in Automation 360. The variable used in a logic is converted to an equivalent variable in Automation 360. Credential variables used in the logic are migrated to Automation 360 and used in the equivalent actions in the migrated bots. If the Parameter Type of a variable is input or output, the same is maintained after that variable is migrated to Automation 360. For example, if the Parameter Type of the variable ABC is set as Input, the variable ABC created in Automation 360 has the Use as input option selected after it is migrated. The system retains the internal folder structure of the logics. For the above example, all the migrated logics are stored as listed in the following table:

Folder structure in Automation 360 Entry
MetaTask Common
MetaTask\Process1 Connect
MetaTask\Process1 Disconnect
MetaTask\Process1\Operations Numeric
The following table provides information about how the Import DataSet command used in the MetaBot logic is migrated to the equivalent actions in Automation 360:
Play type Enterprise 11 Action Automation 360 Action
Object Get Property, Get Total Items, Get Selected Index, Get Selected Text, Select Item by Text, Select Item by Index, Click, Left Click, Right Click, Double Click Migrated to the Capture action of the Recorder package.
Image Left Click Migrated to the Find window in window action of the Image Recognition package with the Left Click selected from the Action list.
Right Click Migrated to the Find window in window action of the Image Recognition package with the Right Click selected from the Action list.
Double Click Migrated to the Find window in window action of the Image Recognition package with the Double Click selected from the Action list.
Middle Click Migrated to the Find window in window action of the Image Recognition package with the Left Click selected from the Action list.
Set Text Migrated to:
  • The Find window in window action of the Image Recognition package with the Left Click selected from the Action list.
  • The Delay action of the Delay package with the Regular delay set to 500 milliseconds.
  • The Simulate keystrokes action of the Simulate keystrokes package.
Coordinate Click Migrated to the Click action of the Mouse package with the Left Button and Click options selected.
Left Click Migrated to the Click action of the Mouse package with the Left Button and Click options selected.
Middle Click Migrated to the Click action of the Mouse package with the Middle Button and Click options selected.
Double Click Migrated to the Click action of the Mouse package with the Left Button and Double click options selected.
Set text Migrated to:
  • The Click action of the Mouse package with the Left Button and Click options selected.
  • The Delay action of the Delay package with the Regular delay set to 500 milliseconds.
  • The Simulate keystrokes action of the Simulate keystrokes package.
The following table provides information about how the Export Dataset command used in the MetaBot logic is migrated to the equivalent actions in Automation 360:
Play type Enterprise 11 Action Automation 360 Action
Object Get Property, Get Total Items, Get Selected Index, Get Selected Text, Select Item by Text, Select Item by Index, Click, Left Click, Right Click, Double Click Migrated to the Capture action of the Recorder package.
Image Left Click Migrated to the Find window in window action of the Image Recognition package with the Left