We launched BotVisions this month, a monthly webinar series offering insights into robotic process automation and, and chose this as the first topic because we believe if it is not fast and easy to use, it is not RPA.
In our webinar we shared what makes SMART record different from web record, and shared how Automation Anywhere is innovating to save customers hours of time, increase their RPA adoption, automate their most complex processes, and reduce errors.
The recording of this webinar is available here.
Major customers like a large telecommunications provider and a major Australian bank (both examples in the webinar) are using Record successfully within their enterprises.
We had over 30 questions asked and we will attempt to cover a few here.
What is the difference between the recording options you offer?
We have three recording options to satisfy any specific organizational need.
- Smart Recorder captures the UI controls/objects for a variety of frameworks. This allows it to be more resilient to automation obstacles such as screen resolution changes. It offers more flexibility while recording tasks that use different technologies – Silverlight, Java, html, and Flex to name a few. It can also be used to record tasks for legacy as well as web-based applications.
- Web Recorder is used to automate pattern-based tasks for web- based applications, e.g. automatically extracting web data spread across multiple pages with just a few clicks.
- Standard Recorder (now Screen Recorder) can be used to build simple tasks for processes that involve mouse clicks and keyboard operations, and when you plan to run the recorded task on the same computer on which it was recorded.
Is there a need for special training in order to make changes, once processes are automated with Record functionality?
Recorded automation can be easily altered to address unique business needs or exception scenarios, making training requirements minimal. Record functionality lets you make the basic skeleton of a process faster, so you can spend more time adding exceptions and testing the bot. Once you have a process recorded, you can use that code to update as needed without having to re-record the entire process.
Can results be deployed to production right away after recording?
We have designed the functionality such that it is powerful yet easy to use. Recorded automation just works—even without any changes—and can be deployed to production straightaway. It is advisable to first test the recorded automation.
For straightforward use-cases, you can deploy to production as-is, or by making minimal adjustments. For complex use-cases with multiple exceptions, you can add the appropriate logic to the already-created bot and deploy to production. (Which can mean the difference between POCs taking days or weeks rather than months).
Is the recorder good with attended automation (playing nicely with humans)?
Once you have recorded a process or use case, you can insert logic into the already-created bot to interact with humans via message and prompt dialogs. Bots can communicate key information to humans and even change course based on human input in the middle of the process. This “human in the loop” interaction is a key feature of our Enterprise RPA platform.
Can a bot be exported to other users?
Yes, this is a key feature for several of our customers. Users can upload their bots to our Control Room, and using Role Based Access Control (RBAC) can share their bots with other users. This ensures central policy management and better auditability rather than ad-hoc sharing. From there, users can easily modify the bots as needed to work on other related automations.
How do you handle decision-making as process steps are recorded?
Decision-making can be handled while editing the recorded automation or using Automation Anywhere workflows. We have standard constructs such as “if-then-else,” messages, and prompts to handle decision-making.
How does the Recorder handle navigation purely by image recognition, such as on systems like Citrix or virtual/remote machines?
Automation Anywhere Smart Recorder creates the automation of Citrix/Virtual Desktop Infrastructure (VDI), just like any other application. To address such specific cases, the Automation Anywhere platform has specific execution modes to deliver optimal results.
Does the Smart Recorder make your MetabBots obsolete? Will there still be any advantage in using MetaBots?
The Recorder is a quick, intuitive, and secure way of creating automation, not intended to replace MetaBots, but rather to work alongside them. MetaBots are automation building blocks that deliver automation scalability and unique benefits of extensibility of the Automation Anywhere RPA platform. You can use Meta Bots as black box building blocks making them perfect for re-use and protecting IP.
Does the Recorder work on mainframe systems?
Automation Anywhere does automate mainframe emulators. Most of the actions performed on the emulator window (clicking of menu items, buttons, etc.), can be captured by the Recorder, which supports accessing mainframes from virtual machines and desktops. Our inbuilt Terminal Emulator command connects with most mainframes (vt-100s, 3270s and 5250s).
How is the Recorder different than QTP (automated testing)?
QTP is limited in use for testing automation whereas Automation Anywhere Smart Recorder automates business processes leveraging rich toolset and execution frameworks available in the Automation Anywhere platform.
Watch the entire webinar ‘Record’ Is Critical for Enterprise-Grade RPA” here.
To view a demo or for more information on this and any other Automation Anywhere product please contact us as email@example.com