Introduction to Bot Insight

► In the fully functional RPA system, millions of units of data are flowing through bots each mili second.

► Any organization were require some thing or someone to analyze that data and turn that data into Business insights

► For the above issue, Automation Anywhere came with the unique solution,

► Introducing Bot Insight

Bot Insight

► A fully functioning software component used to analyze real-time data for operational and Business purposes.

► Bot Insights arms business executives in shared services and
operational departments with real-time content level data
they need to measure and assess the business value that RPA Program is generating.

► Bot Insight Immediately transmits the data captured by bots
into insights through Aggregated volumes, Transaction throughput,Failure rates, Trends,Events and changes.

► These are all through auto generated and customized dashboards.

► Other than bot insight delivers operational intelligence
by providing in the moment of historical information by 24/7 on the health and performance of the bots and machines.

► Actionable intelligence delivered by self measuring bots.

► Operational managers and practitioners can constantly manage the efficiency and effectiveness of the digital workforce.

► It also includes API's that enables the it professionals in centralized it groups and competent centers to easily
extract, load and transform RPA data into their data ware houses.
► It is packed with quick tagging, Instant and tailored dashboards, Interactive analysis and central management and
also it enables any operational organizations to derive revenue, customer satisfactions, reduce costs and error margins.

► And by positively impacting the organizations top and bottom lines by leveraging Business Insights and
Operational Insights.

► Only Bot Insight can perform this type of tasks and only Automation Anywhere has it.

Note:- I will be updating this blog frequently.✍

Thank you for visiting this blog☕️

“In the end, only three things matter: How much you loved, how gently you lived, and how gracefully you let go of things not meant for you”




To Learn Mainframe Modules (Cobol, Jcl, VSAM, DB2, CICS): Click here

For Latest Job Updates: Click here

For Online Shopping: Click here

Use Cases of Meta Bot with Explanation

First Use Case of Meta Bot

An Inventory Manager needs to add a new vendor to their Inventory Management System
every time a vendor is on boarded. Since this is a repetitive process and time consuming,
the inventory manager wants to automate it.

Solution

You can create a Meta Bot logic to automate such processes.

Process Step Flow

Open the Vendor Registration web page
↓
Capture screens of the web page to be automated
↓
Define MetaBot logic to the captured screens
↓
Save the logic.
↓
Define TaskBot logic.
↓
Save task--->Execute task.

Benefits of using this command

► MetaBots are highly re-usable; create once, use everywhere. They can be leveraged by any automation task.

► Enterprises can leverage MetaBot library to standardize org-wide automation in a rapid manner.

► MetaBots ensures systematic, accelerated automation ROI.

► MetaBots help to eliminate common navigational errors in complex automation tasks.

► MetaBots help to automate without requiring access to live application.

► MetaBots can be easily calibrated to newer versions of applications to ensure compatibility.
Note:

► You will have to invoke the application screen before using the Add Screen feature.
Also, if the application is closed, you will be prompted to open the required application.

► When interacting with an application in a workflow mode, use Record Screen,
instead of Add Screen, to record all the Screens/UI elements.
These UI elements cannot be captured using Add Screen.

► Deleting a MetaBot from the MetaBot Designer doesn’t delete it from Control Room.

► If an application has multiple exe's, you are required to create a separate MetaBot for each.

I will be updating this blog with new use cases as soon as possible.

Thank you for visiting this blog☕️

“Believe nothing, no matter where you read it, or who said it, unless it agrees with your own reason and your own common sense.”

To Learn Mainframe Modules (Cobol, Jcl, VSAM, DB2, CICS): Click here

For Latest Job Updates: Click here

For Online Shopping: Click here

Explanation Of Meta Bots

-> Automating the process on a enterprise level requires automation process to be scaled effectively.

-> Automation Anywhere Provides hand-on solution this by providing Meta Bots.

-> Meta Bots are automation building blocks, which are reusable blue prints of a application.

-> Meta Bots are Application Resilient,
it means any time a application updates or changes,
the user can make minimal edits to the bot itself.
Then those will automatically apply to any process, utilizing that bot.

-> Meta bots can automate any task without requiring live access to an application and
these bots are easily calibrated to new versions of application to ensure compatibility.

-> Meta bots helps to eliminate common navigational errors in complex automation tasks.

-> These accelerate the deployment of digital workforce by providing scalability and
extensiblility to Automation Anywhere cognitive RPA Platform.

-> These also facilities maintainability and offline automation and
available in automation command in Automation Anywhere Enterprise.

-> These can be leveraged by any automation task bot and
used in the the place of scripting and VB macro's.

-> You can upload meta bots to the control room to use by other enterprise client users and
edit the meta bots that are created by other users (Reusable).

-> Important point while developing the meta bots is re-usability which

---> Shrinks deployment time.
---> Reduces operational costs.
---> In turn amplifies the ROI(Return of investment) from RPA initiates by more than 50 percent.


-> Meta bots are highly reusable automation building blocks and you can create multiple meta bots
and pick some meta bots to build one task bot.These are automation blue prints of the application.

-> A Bot creator user with Meta bots repository access permissions can

a) Create a new meta bot.
b) Record screens for a new meta bot
c) Upload the meta bots to the control room to enable other
bot creators to download for task bot integration.
d) Delete obsolete meta bots (or) ones that are no longer required.

-> If version Control is enable for controlled edits of meta bots,
a bot creator can check out the meta bot for editing and to view version history.

-> Meta Bots are automation blue prints of the applications.
These automation blue prints are created using meta bot designer
that are accessed by enterprise client application.

-> These Blue Prints can be constructed using three elements present in the Meta Bot Designer such as

1) Visual Captures
2) API (Application Programming Interface)
3) Navigational Flows

-> Existing meta bots can be leveraged or new meta bots can be created using Meta Bot Designer.

So, What do we need to build Meta Bots?
Ans: Meta Bot Designer

Explanation of Meta Bot Designer

-> With Meta Bot Designer, you can conceptualize, Manage and Create Meta Bots.

-> Meta bot designer comes pre-installed with Automation Anywhere Client and
to ensure meta bot designer is installed and working fine,
check if you can locate meta bots under AUTOMATE on left panel.

-> If yes, click on meta bots to launch the enterprise client- Meta Bot Designer.

-> You will need the required access privileges provided by control room administrator to access the meta bots.

-> You will have to exit and restart Automation Anywhere Client for the changes to take effect.
If you have upgraded to the current version.

-> Once the meta bot designer is launched, you can see two views in the work space of meta bot designer.

1) Assets View and
2) Logic View

1) Assets View

-> Assets are the collection of visual captures as well as application API's or DLL's.

-> In meta bot designer, the required application screens to be automated are captured and placed under the assets tab.

-> The Application DLL's added using the add DLL option, are displayed in this tab.
This view is selected by a default for a New Meta Bot(Assets View).

2) Logic View

-> Logic is a navigational flow that is developed based on the available assets,
which includes visual captures or Application DLL's or Both.

-> It is also a independent functional unit of a process
that represents part navigational flow of an application that can be integrated into automation tasks as and when required.

-> Workbench commands can be used to build the navigation flow that is placed under the logic tab.

1)Visual Captures

These are referred has screens and are capable of performing visual captures that include GUI components of the desired application,
to be used for front-end automation.

2)API (Application Programming Interface)

The most common API's such as dynamic link libraries or DLL's are supported.
These are capable of integrating application API's(DLL- dynamic link libraries) that can be used for back-end automation,
by passing GUI and by creating black boxes of automation.

3) Navigational Flows

Screen's and DLL's forms the assets using which you can define or pre-configure any use in case of target application
to create navigational flow known as logic.
In corporate logic that helps in standardizing navigational flows,
to leverage multi-level integrations and create repeatable,
system to system automation in conjunction with task bots.

These bots allow automation at all levels including

1) API
2) Front End automation.
3) Back End automation.
4) Image Recognition.

This work space allows to work with multiple meta bots at the same time.

Let's explore the options available within an Assets view

-> Meta Bot tab open each meta bot in its own tab.
This tab is dedicated to the assets and logic for that particular meta bot.

-> The Add Folder option organizes your meta bot using 'Folders'.
This enables you to easily manage all your screens and DLL"S that are to be uploaded (or)
have been uploaded.

-> The Add Screen option captures a single screen for an executable application,
that is running.

Note:
a) If your screens are set at lower resolutions.
Example:- 1024X768, the 'Add Folder' and 'Add Screen' option can be accessed from the 'edit menu'.

b) You will have to invoke the application screen before using this feature.
Also, if the application is closed, you will be prompted to open the required application.


-> The Record Screen option captures multiple screens of the related application or
web page at one go. Every screen or menu item or pop-up or context menu
that you interact with during the recording gets captured.

-> The Add DLL option adds the API or DLL within your meta bot.
Also you can't include special characters in DLL names.

-> The Configure option edits properties for the recorded or add screen
such as name,path,value-- etc.
Thus improving the reliability of your automation.

-> The Calibrate option instantly compares an existing screen
with a newer screen of an application to identify any changes,
when the application has been updated with improvements and newer features.

-> The Delete option removes the meta bots that are no longer required.

Note:

a) Deleting a meta bot from the meta bot designer doesn't delete it from the control room.

b) The screen, DLL's and Folders are displayed in the order they were added.

Let's explore the options available within an Logic view

-> The Add Folder option is similar to that under assets.
It organizes your logic using 'Folders'.

-> The Add Logic option allows to create the navigational flows in the logic editor.

-> The Record Logic option records the logic flow and
automatically saves the screens in assets.

-> The edit option makes changes to an existing navigational flow.

-> The Delete option deletes obsolete logic.

Note: The logic and folders are displayed in the order they were added.

-> Also you can use the Automation Anywhere Workbench to create simple,
manageable and independent navigational flow.

-> This means creating logic that can be integrated into other automation
task bots or meta bot logic's as and when required.

->It is also used to save and play the meta bot logic to see if it works as required.

I will be updating the information regarding Meta bots in this blog frequently.


Thank you for visiting my blog.

“Each morning we are born again. What we do today is what matters most”


To Learn Mainframe Modules (Cobol, Jcl, VSAM, DB2, CICS): Click here

For Latest Job Updates: Click here

For Online Shopping: Click here