Automation Anywhere Reviews

We are currently using Automation Anywhere for a Master Card customer complaint bot that will log tickets on our top priority websites. When customers complain it can be logged directly or the agent logs it on one of our databases. The bot goes to the database and can pick up the ticket that was logged on a top priority website. It then becomes a role ID number to us for verification that has been locked properly. Third parties can take notes, then once locked, they can give the ticket to us.

We did this procedure manually before the use of Automation Anywhere.

Automation Anywhere is very simple to use. The features are very simple and the application light. Overall I love it.

I have been using Automation Anywhere(AA) for approximately five months.

Automation Anywhere is a very stable solution.

The scalability of Automation Anywhere is perfect.

I am the only one using the solution. However, I am going to create a team that can use it optimally.

The challenge we face is the response time of the Automation Anywhere support teams. They could be quicker to give support. However, the problem could be because of the time difference. When we do get in contact with the support their knowledge is very good.

I have used other BPM solutions previously, such as Optimus.

We decided to take processes away from Optimus and we now are using Automation Anywhere.

The initial implementation of Automation Anywhere regarding the elastic search and database set connection can be a little difficult. However, I am skilled enough to get through it. There were some balancing issues that my other team members had to manage. They are having difficulty in balancing when I checked the architecture properly. We determined later that there was no need for a load balance to be done on the servers. We didn't do any load balancing and then the elastic search was not done.

The first time we did the implementation took us some time because we had to set up the server based on the minimum server requirements that were sent to us. Then we had some load balancing issues which took some days because we did not have all the knowledge.

If we had all the information we would have been able to do it faster. When we were applying the certification to the servers it was a different approach because it's a Java-based solution. In the first instance, we had a challenge doing the implementation. After the initial problems were resolved I did not have any problems implementing Automation Anywhere. It took approximately two hours to get it all done.

The deployments only need approximately five to ten people.

We don't have a lot of processes. If we want to expand we can change the license to allow it. Currently our license, we can only have 10,000 bots, on all processes. If we have approximately 10,000 bot processes on the control we'll be able to manage the processes in the control room. Five and ten people should be able to manage 10,000 bots.

There is an annual license to use the solution.

I would recommend this solution to any organization or individual.

I rate Automation Anywhere an eight out of ten.

The most valuable feature is the SAP application and the DLLs that Automation Anywhere provides. These DLLs help automate the SAP application. In A360, the latest version of Automation Anywhere, they provide many connectors for the different frameworks, like Office 365 or any other APIs, so those connectors are useful.

They still need to improve the SAP application's ability to use the features it has. For example, we have been using a MetaBot to automate SAP applications. They have given the SAP the ability to command Automation Anywhere itself, but we have encountered some limitations. Microsoft Power Automate has so many connectors, like its connector with Microsoft Office and SharePoint. On the other end, I have found Power Automate to be overpowered compared to Automation Anywhere because they already have so many connectors with Office 365, Teams, and other APIs. There are even more if you consider the cloud flow of Power Automate, so it's easy to get triggered.

Automation Anywhere is not so easy to trigger. For example,  I can create an automation in Power Automate where the user provides input into a form, such as Microsoft Form, and that info gets pulled into SharePoint. In Automation Anywhere, we do not have some trigger like that. We have to keep one bot running 24/7 to get this data into SharePoint. Power Automate does not have anything like scheduling. Whenever you fill out the form, it gets triggered on its own, and the information is saved into SharePoint. So this is an advantage of Power Automate that Automation Anywhere does not have.

Automation Anywhere should add the same feature that Power Automate has, so whenever I create a flow, there is a trigger given by Automation Anywhere. Instead of scheduling that bot on CR, there should be something running in the background constantly, so I do not have to schedule the bot or trigger the bot manually. The trigger should be integrated into Automation Anywhere. Also, if I am creating one variable in one module, I have to make the same variable in another subtask, then I have to create a mapping between those two. If Automation Anywhere were to come out with a feature like Power Automate's environment variables, then that variable could be created globally and used throughout the process. That would be better. 

Another feature I would like to have in Automation Anywhere is "Go To Line." When we are writing the code, it sometimes extends 500 to 600 lines. If I want to go to some line numbers — say, the bot has failed on line number 120 — I have to go manually to line 120. If Automation Anywhere provided something like a "Go To Line" feature, that would be useful for us. For example, if you face an error at line number 500 and your code is 1,000 lines, you have to scroll so far down to get to line number 500. 

Furthermore, in Automation Anywhere, you have to write a DLL separately when you want to have something from a .NET perspective. In UiPath and some other tools, there are direct call functions available. It would be nice if Automation Anywhere came up with something like that, where you can directly have the method called.

I've been using Automation Anywhere for around four years.

Automation Anywhere is quite stable. It has been around for many years now and has undergone several updates.  

To some extent, I can say Automation Anywhere is scalable.

The technical support by Automation Anywhere is quite good. Whenever we have an issue, we create a ticket on the Automation Anywhere support site, and the support from their side is quite extensive.

Setting up Automation Anywhere is a bit complex. When I entered into the RPA industry, Automation Anywhere had just been launched. Automation Anywhere was first released in 2014 or thereabouts, and I started working on it in 2017. I was just a novice when I began my journey with RPA, and it was a whole new concept in my organization as well. When we were setting up the control room server and the client, it was a bit daunting. We had to do so much in the background database and then the client. It is pretty complicated to set up the Automation Anywhere control room and the high availability clusters. 

I'm not too sure about the pricing part, because our organizers handle that. I'm just a developer. We get the software already installed on our machine. 

I would rate Automation Anywhere seven out of 10. It is a simple tool to learn, and with A360, they have gone way beyond. They also have an intelligent bot. However, I would suggest going with Microsoft Power Automate ranter than Automation Anywhere because Power Automate's cloud flow is easier to use. In addition, you can use Power Automate with very minimal coding. With Automation Anywhere, you need extensive knowledge of SQL and .NET. You have to learn so many things before implementing Automation Anywhere. 

I have worked on Automation Anywhere for four years and also UiPath. Between these two, I have found Automation Anywhere easier to work on. Also, it's stable because I have delivered around 20 plus automations on Automation Anywhere to date. Based on my experience, I have found Automation Anywhere to be more stable and accessible. I prefer Automation Anywhere. 

In my previous organization, I had worked on UiPath, but I haven't worked on UiPath much for the last two-plus years. So I only have six to eight months of experience on UiPath. I find the Orchestrator feature quite complex and difficult to understand. When I was working on UiPath, they had just introduced their advanced features in Orchestrator, so I found UiPath much more valuable from the .NET perspective. But if we're talking about how easy it is to program, Automation Anywhere is more straightforward. For the past one or two months, I have started getting my hands on Power Automate. In terms of cloud flows, I find Power Automate more useful. Every tool has its pros and cons. After working on Automation Anywhere for around four years, I do find it easy and scalable. But now, now that I've been introduced to Power Automate, I find that I like it because of built-in connectors and templates.

We are currently working on a vendor bill reconciliation process. It is in production now. We are also working on an incident management process for customer service. Within the customer services, there are four or five different processes that we are working on. All of them are incident management but for different categories at different levels. The next use case that we will be working on is bank reconciliation, and then we are planning to expand into HR for onboarding and recruitment. These are unattended robots. 

We are able to integrate it with other products through APIs, which we may not have thought about. For example, there are some in-house solutions that we have for which we have built APIs, and we're able to integrate those APIs with Automation Anywhere. We didn't expect that we'll be working on that but it happened.

The ease of use for the end user and the very low complexity in trying to build a bot are the big factors for us. We are able to work on a project, identify a use case, come up with a design spec, and execute and build a bot within a span of six to eight weeks. In nine to ten weeks, we are able to go live, which reduced complexity. Once we go live, the user interface and the user experience are extremely good.

Their bot runners could be made to handle multiple payloads at the same time because if I want to run multiple parallel operations, the number of bot runners that I have to buy just keeps increasing. It is adding to the cost. However, there is a possibility that we don't need that many bot runners, and we can run multiple operations in a bot runner. This would be a great addition to have.

I have been using this solution for six months.

You get what you paid for. What it says on the tin is what you'll get inside. As a customer, you will not be disappointed. If you're thinking that you want to build rockets using Automation Anywhere, then you will be disappointed. As long as you know your business needs, the automation that you want to focus on, and you understand the product's functionalities in a good way, you will not be disappointed.

Scalability depends on how many parallel processes you want to run. A bot runner basically runs a bot. How many bots can it run? How many of these need to run in serial? How many of these need to run in parallel? This information will determine how much you have to scale. Now, if you're willing to pay a lot of money and have multiple bot runners, that means for each and every bot runner, you can have multiple processes running at the same time. So, if you are willing to pay, yes, you can scale. It depends on your budget. The product works whether you're on 1 bot or 20 bots. The product just goes off and does its thing. That's not a problem.

If it is 1 bot that you're running once a day at 10:00 in the morning, then you need one bot runner. If you have 20 processes that you're automating and these 20 things have to run throughout the day at different points in time at 10:00, 12:00, or 2:00, you can still run them with one bot runner. In those use cases, scalability is not a problem. Scalability becomes an issue when you have multiple processes. If a reconciliation process needs to run along with the general ledger balancing, month-end closing, and everything else, and all of them need to run at the same time, then you're looking at about 10 bot runners running 10 different bots at the same time. If you're willing to pay, you can get what you want, but it becomes a very expensive affair.

We have 15 to 20 people who are touching the application for various purposes. We have business analysts, developers, testers, and the external implementation team. We also have business users.

I have used both UiPath and BluePrism in my previous organizations. Automation Anywhere gives me the flexibility for both on-prem and SaaS, and the difference is not huge for me in terms of performance, security, and all that stuff. It gives me the flexibility, but honestly, on paper, all these three products pretty much do the same. There is a plus or minus 5% difference here or there, but you'll not go wrong with any of these products.

The initial setup was very straightforward. There are specific things that they ask in terms of the environments that we need to build in our typical Windows server, that is, what kind of memory and what kind of processing capability we require. I can't talk from the SaaS perspective because we have an on-prem deployment, but giving on-prem equipment based on the defined specs is pretty much child's play. There is nothing complex about it. It is very easy for developers who understand the platform. You can quickly roll out something and get it live, but you need to understand a lot of logic and the complexity behind the applications such as ServiceNow, Workday, Salesforce, etc. 

We started off with an implementation partner, and our experience with them was good. They had about three people in their team, and we had our business people who were giving the requirements. We also had our technology people who were basically acting as the bridge between our business people and their developers.

We are expecting a significant ROI by the end of the year. 

From a business angle, understand what is it that you need. Where do you see inefficiencies? If you're going to fix inefficiencies that are going to be fixed as part of a larger company-wide transformation program, then use the transformation program and fix those inefficiencies as part of the existing solution. If you think that that larger transformation program is not going to touch some places or if that larger transformation program will touch some of these inefficient areas but not in the near future, and you want some immediate wins, then going in for an RPA tool is a good decision.

At the end of the day, the business needs to be aligned with why you're making the decision, and where and what is your priority? What is your sense of urgency with respect to the places where you're implementing it. For example, in my office, we are working on customer service. There is a massive transformation program going on right now, but that transformation program is touching sales, marketing, finance, and all those areas. It is not touching customer service at all, but customer service has its own inefficiencies. So, we introduced automation in customer service because it's not being touched by the transformation program, and we don't want to keep waiting to gain the ROI of whatever we can get or the reduced cost we'll get from customer service. For example, if I'm going to implement a massive cloud ERP like Oracle or SAP, then I will fix the process as part of that cloud ERP implementation and not wait for a bot to be developed.

From a technical perspective or an integration perspective, use an API to directly communicate between the apps, if you can. You don't need a bot or an RPA to do what an API can do.

I would rate Automation Anywhere an eight out of ten.

The use cases I have worked on made use of automated flow across multiple applications along with processing Excels and emails. We were also able to leverage a single tab for processing the entire flow of the record across three different applications. We also used the Analyze package to view the Business dashboard in the dev environment. The only drawback was that the export of the BI dashboard to the other environments is not yet available. The environments used were dev, staging, and production. The bots were exported out and imported into each environment.

Automating a tedious manual process has helped to reduce manual work and the time taken to process the records. It has also eliminated a great deal of errors because of manual processing. Since the manual process was being automated, we were able to set down sharp rules of validations which cleared out unnecessary manual interventions. Automation has also enabled uniform delivery to the customers with the emails being sent way ahead of time. This has greatly improved product delivery from our end.

The addition of excel advanced to directly append worksheets, add formulas, etc was very beneficial and made the code development faster. 

The usage of steps helped in the segregation of code blocks making it more readable and understandable. The usage of keystrokes in A2019 was much better than in v11. Also, the direct inline usage of the python scripts enabled s to handle various manual processes. 

Using the email and the file triggers were very helpful as we were able to directly execute the bots on the trigger.

We had a few setbacks because of bots getting queued and unable to force delete a task bot which kept persisting in the control room. These features should be included in future releases which will be highly beneficial. Also when the upgrade happened from .14 to .15, it did not allow for the existing task bots to be checked in. The upgrades should work seamlessly to enable high efficiency of the AA product.

We need the Business dashboard to be exported to other environments. Also for the availability of G-Suite package in the enterprise edition.

I have been using AA for six months.

A2019 needs a few more upgrades to make it more stable and robust but the AA support to handle the shortcomings has been great which has enabled us to make full use of the product.

A2019 is highly scalable and there is a lot of scope for upgrades.

Technical support was prompt and we were able to resolve most of our issues quickly

Earlier, I had used v11.3 of Automation Anywhere.

The initial setup was complex because of the confusion with the Pure cloud version. 

In-House

Our ROI is high.

There was a little confusion in terms of the setup costs for the pure cloud version because it was a bit misleading when we understood that all the Control rooms and the bot creators and runners would be on the cloud. The provisioning for the bot agents was not understood immediately.

A2019 is a very good product, there are still some upgrades to be completed, like the functionality of the GIT repository, G-suite package in the enterprise edition. One more advice would be to ensure seamless upgrades so that our current development is not hampered.

I work in the Management Consulting domain and hence am working with huge amounts of data, using advanced Excel formulae and creating reports and dashboards for clients is a routine. I primarily used the RPA AA2019 to automate and streamline few weekly reports which track KPIs (Key Performance Indicators) for few products. Also, I automated the process of Quality checks which we perform after creating the reports. Another use case that I have automated is sending a Zoom meeting invite through outlook. The user only needs to enter a few details like attendees, date, and the time of the meeting.

My organization i.e ZS has been a partner of AA for the past couple of years and this year the organization decided to reach the next level by introducing a pilot program wherein many associates are onboarded to the AA2019 tool and can implement robust and efficient solutions using the same thereby increasing productivity across the organization. This has been a success and we are planning to scale the program to a much wider audience within the organization. The saving of efforts within my project has been to the tune of 20% as of now and I am sure that it will improve as we explore the tool more and automate many more processes.

The Capture command has been a lifesaver for me in each of my use cases and the advanced Excel functionalities like running macro, reading and manipulating data, etc. It allows the bot creator to leverage the inbuilt functionalities that AA2019 has to offer to a great extent. Also, the functionality of designing child and parent bots help me to design the process in a modular way. Additionally, the error handling capabilities of the tool has really improved the troubleshooting experience when we encounter an error.

The AI Sense functionality is what I believe can be improved since when I tried to use it for automating a use case involving a Citrix Virtual Machine, it was unable to capture objects consistently. This feature can be made more intelligent and less bulky in terms of the downloadable package size of the code in the next release and also the VB/Python scripts which we can use in conjunction with the AA2019 functionalities is what I believe would help in automating many processes end to end.

I have been using the Automation Anywhere 2019 tool version for the past six months.

I would rate it an 8/10 since I believe if the AI Sense capability and handling MS power point functions is further enhanced with the next release, then it would make a much larger impact.

It is very much scalable in my opinion and should be used by big organizations lokoing to save costs and increase productivity.

The setup was a bit complex. There were many IT approvals that I needed to take.

I am currently able to save 2-3 hours of manual effort per week.

Project 1: Built an unattended bot to automate a complex Audit process for a healthcare client. There are 90+ bots deployed and it is processing 1000+ cases of different types every month.

Project 2: Built assisted bot for a healthcare client. It was used by customer service representatives. Unfortunately, this process was not used for a long time due to latency issues and a functionality gap.

Project 3: Working on migrating the Audit process automated using Automation Anywhere v10.5 to the new version, A2019.

AA has helped to automate a complex Audit process. The process was tedious to the auditors, as they need to log in to a number of applications to collect audit data for validation. It involves web, desktop, and mainframe applications (total of 20+ applications of 40+ roles).

The whole process was automated such that the bot will log in, collect screenshots, build the PDF, and then report the results to the auditors. This saved auditors from doing the mundane manual task of logging into multiple applications independently. Also, the auditors had to manage credentials for all of the applications before, whereas now, the bot takes care of storing the details in a secure vault.

The most valuable features for us are:

1. Object cloning with an option to enter wildcard selection was very useful when working in a web application that generated dynamic HTML content.
2. The Terminal client options have helped in automating terminal applications effectively.
3. The Windows capturing features that allow for automating desktop applications works seamlessly compared to web application automation.
4. Excel automation is one of the clean and very useful features that helps in reporting, as well as other Excel-related operations. Having the option of using Excel as a database helps with performing logic.

Areas that can be improved are:

1. For assisted automation, the AA bot needs the facility to be triggered through an application interface after collecting input from the user. There is no inbuilt option available in AA to collect all the inputs in an interface. In our case, we built a desktop application to collect all of the user input and, on submit, the .NET code will run the ATMX file.
   
   Can AA provide a simple user interface through which a user can collect input and submit it to trigger the bot?
   
   
2. It needs an option to change the Windows resolution.
   
   
3. It needs to have an option to select an object after a three to five-second delay. It is useful in the case of menu selection and this option exists in other tools.

We have used several versions of Automation Anywhere since 2019, as follows:

• 2019 May - 2020 January: Used Automation Anywhere v11.3
• 2020 March - 2020 October: Used Automation Anywhere v10.5
• 2020 October - Current: Migrating from AA 10.5 to A2019

We have used WorkFusion RPA, which had options for machine learning features first.

We use Automation Anywhere to track the travel and locking of our devices.

We implemented Automation Anywhere because we needed a way to track our devices and ensure they were not going beyond their boundaries.

Before Automation Anywhere we were manually tracking our devices and now it is done automatically.

Automation Anywhere helps to save a full day. Automation Anywhere helps save costs by allowing remote work and not requiring a person to be at the machine. 

The efficiency we get with Automation Anywhere is valuable.

The Automation Anywhere calibrating needs to be more user-friendly to avoid human error.

Non-technical people can not use Automation Anywhere.

I have been using Automation Anywhere for one year.

The stability of Automation Anywhere depends on the environment it is used in. For example, in hot environments, there can be deviations.

The technical support is good.

Positive

The initial setup was a little complex until we became familiar with the process.

The deployment took one week and required two people.

Automation Anywhere is reasonably priced because it can sustain us for a long period.

I would rate Automation Anywhere eight out of ten. The technology is improving every day.

With the right tools, it is easy to upgrade Automation Anywhere.

Maintenance is required for Automation Anywhere to ensure proper functionality daily. Two people for 20 minutes each day is enough to oversee the maintenance.

I recommend completing some courses and shadowing experienced Automation Anywhere users to gain hands-on experience with the automation process.

I use Automation Anywhere to automate processes for other businesses.

Automation Anywhere is user-friendly for individuals with a technical background and can also be utilized by those without specific knowledge.

The learning curve for Automation Anywhere is easy. The steps are nicely designed and of high quality, making it easy for users to learn.

Automation Anywhere has helped our customers' organizations speed up their processes and reduce the workload for their staff.

It offers automation at scale, enabling our customers to accomplish their objectives.

Integrating RPA bots, APIs, business applications, and documents is easily achievable with Automation Anywhere.

Automation Anywhere has helped to increase automation consumption.

The dashboard has room for improvement.

I have been using Automation Anywhere for one and a half years.

It is stable.

Automation Anywhere is scalable.

The technical support has been helpful, and we have not experienced any delays.

Positive

We used Power Automate before switching to Automation Anywhere as per the client's request.

The initial setup is straightforward and takes one or two days to deploy.

I believe our clients do see a return on investment because they continue to use the solution for their automation needs.

I think the pricing is reasonable, but clients often perceive it as expensive. This perception might change once we see the benefits, understand the full process, and realize what is required to achieve our goals.

I give Automation Anywhere an eight out of ten. Power Automate has better cloud flows.

For those who prefer API integration over robotic process automation, I would use an API if it's more logical to do so. It all depends on the situation. If I need to fill some Excel documents, I will use bots; and if I need to display that data on a web page, I will use APIs if available.