Understand the MetaBot Designer

Well designed MetaBots are key to efficient and reliable reuse of all the Master Bot components and functionality.

MetaBot Designer features

  • Specify folders in an existing MetaBot,
  • Add DLL's to create low level operations of an application by circumventing GUI
  • Create simple independent yet functional Logic blocks.
  • Also, create MetaBots and upload them to Control Room to create a repository for using/reusing MetaBots in automation tasks.

MetaBot Designer Decoded

The work space in the MetaBot Designer allows you to work with multiple MetaBots at the same time. Keep MetaBots open in the form of tabs to sanctimoniously work on different MetaBots.

Once you create a MetaBot, you are taken to Assets tab by default where in you can start by adding new assets (Screens/DLLs).

Understanding Assets

The following explains the options available within an Assets view:

MetaBot Tab
The MetaBot opens in its own tab. This tab is dedicated to the Assets and Logic for that particular MetaBot.
Assets Tab
When highlighted it indicates that the view is open in 'Assets'; it displays all the Screens, DLLs and Folders inherent to this particular MetaBot. It is selected by default for a new MetaBot.
Add Folders*
You can organize your MetaBot using 'Folders'. This will enable you to easily manage all your screens and DLLs that are to be uploaded/have been uploaded.
Add Screen*
Use this feature to capture a single screen for an application. Start the application screen you are adding before using this feature. Also, if the application is closed, you will be prompted to open the required application.
Note: MetaBot Logic has been updated to refer to the Screen Title value to identify applications. Command titles are no longer used. Existing Logic that refers to command titles needs to be updated to use the Screen Title value.

To know more about adding a screen to MetaBot using OCR, see Add a Screen using OCR.

Record Screen
When you need to capture multiple screens of the related application/web page at one go, use Record Screen.
Tip:
  • Use Record Screen to record all the Screens/UI elements (Menu item / Pop-up / context menu etc.) as you interact with the application in a work flow mode. These UI elements cannot be captured using Add Screen.
  • If an application has multiple exe files, you are required to create a separate MetaBot for each.
  • * If your Screens are set at lower resolutions; for example 1024 X 768, the Add Folder and Add Screen options can be accessed from the Edit menu.
Add DLL
If you need to use an 'Application Programming Interface' (DLL) within your MetaBot, you can add it to the MetaBot using 'Add DLL'. Remember though, you cannot include special characters in DLL names, see Workbench and creating Logic
Note: The Screens, DLLs and Folders are displayed in the order they were added.
Configure
Use this to edit properties for the recorded/added screen. Here you can provide aliases such as a 'Screen Name' and a 'Screen Title'. You can also select an object to define its properties such as Name, Path, Value, ID, Class, Index, States etc and the 'Play Mode' to be used when running tasks. Some of these properties help to uniquely identify an object during playback. You can thus use configure to improve the reliability of your automation, see Object properties configuration
Calibrate
Applications are continuously updated with improvements and newer features, your captured screen and its object properties often need a re-look after every update of the application. In the MetaBot Designer you can use Calibrate to instantly compare an existing screen with a newer screen to identify changes. For more details, see Calibrate screens.
Upload
The MetaBots can be uploaded to the Control Room, which acts as the central library from where fellow MetaBot Designers can pick up the MetaBots necessary to their task(s). With MetaBot privileges you can upload and deploy the MetaBots to the server, see Upload considerations for MetaBots.
Delete

Use this to delete MetaBots that are no longer required.

Note: Deleting a MetaBot from the MetaBot Designer does not delete it from Control Room.

Understanding Logic

Once you have captured the desired assets, move on to create Logic using those assets.

A Logic is an independent yet functional unit of a process that represents a part navigational flow of an application and can be integrated into automation tasks as and when required.

You can use Assets (Screens and DLL's) to design a Logic block. Subsequently, you can upload the Logic to Control Room. Logic Blocks can be shared with and reused by other bots with appropriate MetaBot privileges.

The following explains the options available within a Logic view:

MetaBot Tab
The MetaBot opens in its own tab. This tab is dedicated to the Assets and Logic for that particular MetaBot.
Logic Tab
When highlighted it indicates that the view is open in 'Logic'; it displays all the Logic Blocks and Folders inherent to this particular MetaBot.
Add Folder
Similar to Assets; for instance, you can add Logic Blocks that are functionally similar to a folder.
Add Logic
Use this to create your navigational flows in the Logic Editor, see Workbench and creating Logic.
Record Logic
Use this to record the logic flow and automatically save Screens in Assets, see Record Logic.
Edit
Use this to edit an existing navigational flow.
Upload
Use this to publish (upload) your (new or edited) Logic to the Control Room, see Upload considerations for MetaBots.
Delete
Use this to delete obsolete Logic.
Note: The Logic and Folders are displayed in the order they were added.
Note:

You can convert existing bots created in Internet Explorer to Microsoft Edge with Internet Explorer mode using the Bot conversion utility. With Internet Explorer mode enabled, you can now run your automation in Microsoft Edge. Additionally, you can create bots as the system now supports the Microsoft Edge browser.