Automation Anywhere Reviews

I have done a lot of use cases. Recently, I have done SAP automation. I worked with MS Excel, a web application, a Windows application, and a mainframe application. We automated three to four applications at once. We automated them in a row where one application's output would be input for another application.

I have done development and production support. I have helped organizations with integration.

The Visual Studio development for the basic version, which they launched long back, that's amazingly good. It has a good design, which is better than Blue Prism and somewhat better than UiPath.

They have good people.

Citrix automation is unstable. It is failing on a frequent basis. With the bot, they claim a lot of things, but it is not the real picture. It is not as powerful as they claim. It is not up to the mark.

Once I'm friendly with a tool, then I'll start checking the stability and power of it. It is not there with Automation Anywhere.

The management people don't know the technicalities. The actual tool is not as powerful as they claim. They are pitching the IQ Bot, but it's not as powerful or as fruitful in real world scenarios as it should be.

The user analytics are not analytics.

Their Community Edition is awful. Every second day, it will fail. It will become corrupt.

Stability depends on your use case and what type application you are automating.

Stability is good, RPA is a emerging field, so you can't expect a lot of stability. You develop things and the maintenance is there. 

Stability depends on the applications being developed. E.g., if it's a Windows application, they are already stable. Doing automation is not a big thing, but doing automation with little maintenance, that is a big thing.

Scalabilty is good.

The technical support is good. 

Their marketing team is good.

The initial setup is good.

I am the person with does the integration. I am developer. I can develop an application in three weeks (done and dusted). After moving it to production, there are a lot of challenges. Then, I am spending three hours of my bandwidth being occupied every day with maintenance.

RPA implementation will be always fruitful. Return on investment will be always higher than the input costs.

Automation Anywhere is a bit more expensive. This is one of the things that we face when we talk to small start ups in Bangalore. They want to do an RPA implementation, but don't have the money. UiPath is the answer.

We have done a lot of complex automation using different RPA tools: Automation Anywhere, UiPath, and Blue Prism.

UiPath is a bit better. UiPath is a bit strong in fewer areas, such as Citrix automation. Citrix automation is like a thin client automation. For applications not present on your local machine and in the cloud, UiPath is more powerful. With RPA, you can automate things. Howe, are those automations stable? That is another question. In order to stabilize automation of thin client, UiPath is more powerful. There are few other features which are better than Blue Prism and Automation Anywhere.

UiPath has amazing scalability, while Automation Anywhere and Blue Prism are good.

UI Path is leading the market. There is no doubt about it. They have their own challenges. They aren't flawless. 

UiPath Visual Studio is not good. It is messy. Automation Anywhere Visual Studio integration is smooth and user-friendly. 

Automation Anywhere is good in some parts with their Smart Recorder that they they are launching in A2019, that is there but yes they are leading. They are putting in real hard work and emerging. They are in second place as of now in the RPA world.

I use automation for finance. For example, SAP, Oracle, and other applications. In the past nine months, I have automated approximately thirty-five hundred hours. Next year we expect to reach at least eighty-five hundred hours.

All of my leaders are pushing us to use automation because they're thinking that other companies are ahead of us. I am looking forward to working on the IQ Bot to see how it might make my life easier.

Recently, the auditors were looking for a tool to assist them with checking incidents. For the American region, there were between twenty-seven and thirty thousand incidents, which as a human we cannot search manually. For each one, they have to check what the incident is, and verify whether they have the proper data. Because the audit was only going to run for one or two months, they wanted the results in ten days. I spent about one and a half days building a bot and started running it. The bot was moved to production, and within seven days, I was able to get all of the details in Excel format to them. They can filter it, see whatever fields are empty, and they can do the audit. They got one hundred percent sampling, which they were happy about. Our plan now is to sell the Bot to the project owners so that instead of having the auditor catch problems, they can run it every month and see what improvements they need and where it is lagging. The bot will educate the team.

The MetaBot is a very good feature that allows me to do things that were not available in earlier versions. I can now run multiple commands, instead of just one.

It is easy to develop using this solution, and it doesn't take much technical skill. It is very easy to integrate any of the macros or DB scripts. It is easy to find people who can work with this solution, unlike Blue Prism, where it is hard to get candidates.

I would like to have the MetaBot screen name title dynamic instead of static. This would allow us to use wild card entries and make our lives much easier. As it is now, we cannot automate using MetaBot because the screen name changes. The only way it can be done is to use multiple MetaBots.

We are having a problem when trying to automate the opening of very large Excel files. One example is our 70MB Excel file, which normally takes approximately twenty minutes to open. Automation Anywhere crashes before it opens, so we moved it to Instaknow-ACE, which is another RPA tool. It imports the Excel file, creates its own database, and then you perform whatever operation you want. After this, it generates the output result without crashing. If this were fixed in Automation Anywhere then it would be a large benefit because we are in a phase of moving away from smaller automation. We are doing a lot with bigger data, and most of it is still in Excel files instead of a database. It isn't the fault of Automation Anywhere because it is Excel that is crashing, but we need to have a feature where Automation Anywhere can import Excel files directly.

The stability of this solution needs to be improved.

The OCR capability needs to be improved to be made more accurate.

Compared to earlier versions it's a lot more stable, but it still needs a lot of improvement in terms of the OCR. We are getting more OCR projects where we have to scan and get data from contracts and give it to the auditors, or other people. The data includes things like region and the product that was ordered. It is very difficult for me to scan because I can't tell customers that it isn't accurate. Sometimes, it will read the letter "I" as the number one, which is one of the issues we are facing. The upper management thinks that everything is ok, but as a developer, I know that there is a problem. If you were to come to me and ask for an OCR to be done, I could only guarantee you about eighty percent accuracy. If I tell the customer that there might be twenty percent errors, they may not be happy.

Scalability is very good. Compared to others, Automation Anywhere is on top.

We have more than eight hundred developers in our company, and most do not have a technical background.

I do not deal with technical support directly. We have a COE who deal with technical support, and my team speaks with them. If there is a problem that they cannot fix then they go to Automation Anywhere.

Our COE took care of the implementation of this solution.

What it takes a human ten hours to do, automation should complete it in one hour. In the past ten months, I have saved the work of two people. People are happy with the results.

We are still in the procurement process for IQ Bot, but I am looking forward to seeing how it is going to help me.

My advice for anybody who is considering RPA is to use Automation Anywhere because it is easier. You can learn it, but if you go for other solutions then it will be more difficult. Not all of the people in our company are from a technical background. Many are BCOM graduates and analysts, but they are being trained in using this solution.

This is a good solution, but it still needs improvement and there is a long way to go. Artificial Intelligence still needs to be added.

If they allow the direct import of data from Excel, improve the OCR, and allow variables to be used in the MetaBot start screen, then this solution would be perfect.

I would rate this solution an eight out of ten.

Primary use case is automating data entry functions for accounting and general entry. That has been our primary use case. Since we've started, we have create about five bots (of which three work).

We're too new. We haven't really begun to invest in the option of having automation. I'm hoping at least in the accounting area, people are inquiring about the tool now that they are seeing results.

Of the bots which work, they have automated three of the most time consuming tasks and completely freed up one person to do real work.

Anything that can be done to simplify the solution. I would love to see it where anybody who can run Excel will be able to create bots. Right now, I am watching everyone around me struggle with the tool. I do think the tool is getting there.

From an IT perspective, we had too many issues and headaches.

From an IT perspective, the migration is still very complicated, getting everything set up and running. Security was an issue for us, as well. Developers had to come through our firewalls to develop bots, internally. However, they were coming through a Citrix platform, so there were breakpoints in things they were trying to automate, file servers they were trying to get to, and FTPs that they couldn't get through. 

I understand the next version will have support for Citrix, which might solve some of our problems.

So far, the stability has not been great. We had a lot of migration issues before we got up and running. We will wait and see if this continues with the next version that is being installed. However, once something is up and running, the issues do not persist.

We are only running three bots, so we haven't had to worry about scalability yet. We built the tool to handle about 30 bots. So far, we haven't had any problems with scalability.

It took about six months to scale from the pilot to the number of bots that we are currently using, but the majority of those months were wasted on our upgrade issue.

We went through an Automation Anywhere partner, who handled all the technical support. So, we didn't go the Automation Anywhere technical support directly, except on occasion. We got through all our issues, eventually.

We were not previously automated in any way.

The initial setup was complex.

The IT team wasn't involved directly at the start, so the business sort of started it on their own. Then, the product over came to IT, and we were blindsided by the requests. That was when it became complicated.

We used consultants to build our bots. We are still in the learning process.

We used KPMG for the deployment. They obviously knew the product very well and were also surprised about the migration issues, but they got us through the deployment.

We are measuring our ROI in terms of power saved.

Start simple. There is no reason to jump in with complicated bots. Find simple, small processes that need automating.

The software is there, and it does what it needs to do. The tool can grow and become huge, if it is not already. I hope that we got on early enough that we can keep building on our success.

We have gotten around to looking at the Bot Store yet.

The primary use case for this solution ranges from the web scraping to working on more complicated applications, which are built in-house. For example, in the case where we would have to get into an application that is not automation-friendly, we would use the OCRs to recognize the fields, insert information into the application then extract some of the information. We also do a little on the database front.

We are a solution provider for a back-end team who works on a different manual task.

We tried the same type of flow automation using a Python and VB application, but we don't have the leverage of OCR which is available from Automation Anywhere. 

Most of the automation that we currently handle is that which has already failed when using the previous versions with the VBAs and Python.

We are using this product on-premise, so we still haven't upgrade to the cloud.

In our organization, we track the number of hours we saved, not work for the customers, but work for ourselves. 

Those numbers were tracked in a tracker called Smartsheet. We saved approximately 10,000 hours of work for ourselves. The numbers are staggering, considering we have only been using Automation Anywhere for a short period of time.

I have not worked with all of the commands offered in this solution, but some of the helpful features are OCR and web scraping. 

The OCR application is excellent and has helped resolve many issues that I had been facing. Also, to some extent, the web scraping is more effective, and the delays are really good.

I am also a programmer with VBA, but I found that I am more comfortable with Automation Anywhere, because it is faster and you get more results within a short period of time. we use the Excel VBA.

Most of the times you find the solution that you are looking for in the Bot Store. You might have to customize here and there. It is a good place to get into because somebody might have the same type of scenario. However, I have not used it extensively.

This solution should be more user-friendly so that our clients can take a bot that we have developed for them, and then run it by themselves. As it is now, we write the VBA code and give it to the user, our client, and then they run the code. However, they do not like this. Having this is the next release would be helpful.

Automation Anywhere is intuitive. Initially, you may struggle a little, but once you get used to it, then it's intuitive and you don't really have to know all the commands beforehand. There is scope for improvement here.

The feature often asked about by the users, the product owners, is that they want to learn more about the bots themselves.

We have not used anything attended. As far as we are aware that feature not available, but it is to be released soon.

Version A2019 is something that could be beneficial to new users. At the same time, I cannot rule out completely that you need to have a very good programming skills. It will be easier if you have some knowledge on the programming front because you might be using a command which is already built-in. Therefore, you should know how the loops works and how the conditions work in order to implement them. If you want to do a bit of deep-diving into automation but you will need a little technical knowledge at this point of time.

We haven't had any issues with stability. The ecosystem provided is great, because we have bot stores that can be downloaded, so we don't have to start from scratch.

Before creating a bot, I can go directly to the bot store to see if the bot is already available. That way, I don't have to waste any time.

Most of the time we built the bots for ourselves. When we purchased the licenses from Automation Anywhere we had them provide us with training. It was approximately a week for the training.

Also, there was another training session for photo documentation purposes.

Automation Anywhere is an excellent example of a solution that scales up. 

When we develop a task we modularise it and upload it into the repository. If another team member is working on another project and they require a section of my bot then it then gets downloaded and modified. Somebody else plugs in the variables, etc. In this way, the scalability is great.

At the moment, there is no setup in place.

We don't have a Citrix environment. It's mostly web-based. We also have in-house built applications that we use for our day in and out operations.

The technical support team has been with me from the beginning of my journey with Automation Anywhere. I was not a good developer initially, so I give them all of the credit.

They have a very good support team. I would advise my colleagues to use the IT help desk as much as they can.

As developers, we have evolved. Initially, at the start of using automation Anywhere we had many struggles. We contacted support for some help and suggestions, and with the help they provided, we are now more comfortable with Automation Anywhere.

There were instances where they couldn't help me, but it was because of the task not being suitable for automation. I understand that there are hindrances in the evolution of a solution, but they helped wherever they could. I would say that in 80% of the cases, they were able to help me.

They need a better community support with online resources. Though, there are good resources in regards to other programming languages, such as Python, VBA, and .NET.

Previously, we had been using VBAs and Python, albeit our use in Python was not extensive.

We chose Automation Anywhere because we heard that you don't need to have expertise in a particular area, and anyone can develop a simple bot in a short time.

We still do not have a setup in place. We do have licenses, but we are trying to have more bot programmer licenses in place. As such, the deployment is still in progress, but from what I understand it is simple and straightforward. I expect that it will be completed within the next week or two.

Most of the team who were working on Automation Anywhere had a little programming background, such as VBA or Java. Initially, we struggled a bit to use the rich commands but Automation Anywhere provided initial training when we got our licenses. Somebody came and gave us training for three to four days. Then, it took about three to four months to transition from the PoC to using the bots.

We handled the implementation ourselves, and have not sought out help from anyone.

When we initially bought the licenses, we had the Automation Anywhere team come down to train us. This lasted for approximately a week. They also visited on another occasion for documentation, but otherwise, we work on our own.

We do a cost-benefit analysis along with a feasibility study. We do this initially when there is a project that is lined up. We look at how many hours the project will take. We also delivery time and its urgency. Even if the project may not save a huge number of hours, we still might pick it up because of the urgency. Sometimes, we also look at it from an error reduction standpoint. There could be a lot of errors coming out because it was manually processed and this may cause the company issues. With Automation Anywhere, we reduce these errors.

I was not involved in the cost or purchasing, but as far as I know, the return is great. There are a couple of projects that we have worked on where we could have saved approximately 4000 hours on just one project that we built in two to three weeks. This is the type of impact this solution has.

We have purchased licenses, but are trying to obtain more bot programmer licenses. That should be happening in the next week.

UiPath was the closest competitor that we were considering. We provided pros and cons for both UiPath and Automation Anywhere. There may have been a cost-benefit analysis done from management, but I was not involved in that area.

We just did a PoC with UiPath. We did not work extensively with it. The product was based more on a workflow model. Automation Anywhere will also have a workflow model with its A2019 version.

We were not compromising on quality for dollar value. If you are looking at it from all aspects then Automation Anywhere is the clear winner.

We can automate anything with Automation Anywhere. Initially, we were skeptical about whether this small project would be automated or not because we were not well acquainted with the Automation Anywhere capabilities. After using the product for a while, we understood its potential, such as the OCR capabilities.

My experience with Automation Anywhere to date has been great, however, there are areas that I have not explored which could be features that should be added or improved upon, such as APIs. I have yet to explore this area of the solution and there may or may not be room for improvement.

We used to use Excel VBAs. However, if you want to manipulate stuff in Excel files, you have to write the back-end code in VBA. This is more effective than writing your code in Automation Anywhere. There are no hiccups in integrating with VBA.

We have completed the 11.2 expert certification in Automation Anywhere University and are in the process of completing 11.3. The University has a lot of stuff in their repository. As a programmer, you might not use all those commands extensively in your development. It's a good place to learn, but I didn't see everything being learned in the University being implemented.

For anybody who is considering this solution, I would start by suggesting that they look at their business requirements. We looked at it from a business standpoint because in our day to day operations, we needed automation. This is how we realized we needed a solution. If you are doing web scraping or another type of mundane task every day then you need Automation Anywhere.

I would rate this solution an eight out of ten.

In our banking center, we are using Automation Anywhere for loan settlements, credit card transactions, and reconciliation forms. It has been easy to use.

I like working with most of the commands in Automation Anywhere, such as object cloning commands.  I like MetaBot for automating Citrix.

They need to improve the speed. It runs too slowly.

There are some setup limitations:

• There is no direct passing mechanism to manipulate adjacent data and send it back to the server. 
• There is not one task that lets you debug everything.

Version 11.3 already has a lot of things that we want: quickness, ease, bigger, and more functions.

It is 90 percent stable. 

10 percent is due to network issues, slow performance of the application, or failed bots. These happen infrequently though. We implemented some fallback mechanisms around the network issues.

Scalability is fantastic. We can build anything out of the application. Though in some places, there are limitations. Fixing those would be good.

We are deployed in five different regions.

We are using the technical support. They are fantastic, but sometimes we aren't getting the expected outcome that we want from the tech support team. We would like to see this improve.

The initial setup is not that complex. We just download the software. Anyone can go and download it. It can be downloaded with two-way server. Then, the next step is to get a license for development and other things. Once development is done and it has been move to product, the client can use it.

I would recommend using this product. It is very useful. We can automate anything through it. There is much flexibility. It provides a robust mechanism, which is good.

We look at process which are feasible for automation on a case-by-case basis.

Right now, we have two business units which use it for automation, mostly for:

• Back office
• Shared services automation
• Accounts payable
• Accounts receivable
• Most finance functions.

We have two different business units which have already begun their journey. One has been doing it for two years, and another one for one year. We have another two business units which will be beginning their journeys this Summer. Certainly, the value of it has been proven already in the business units which have already started their journeys. They have seen the value in terms of automating some of their redundant, important processes. This has allowed some of their users to move onto more value-added activities.

The most valuable feature is that it is intuitive. It is designed so business users can use it with a drag and drop functionality to develop automation of business processes. Since they are the experts on business processes, there are probably the best ones to create the automation.

They designed the bot creation process where we can drag and drop and all of the commands are available to us on the left side of the screen, but in some ways, it can be overwhelming. There is a lot at a developer's fingertips to do their development process.

I would like the ability to extract the code. You can go line by line, then open up each line of code and dig into the details, but it would be nice to extract all of the lines of code and all of the details into a document so we could read through everything. Right now, there is no way to really consume all of the code at once, except line by line, which can be fairly time consuming if we don't really know what we are looking for.

As we deploy more solutions and take advantage of some of the features, like the Credential Vault, where we are introducing new administrative processes, we continue to have to go in and change passwords on a monthly basis. Tools that would make these administrative tasks more streamlined is an area where Automation Anywhere could really add value.

I love the new features that they're offering and the direction that they're going. We've tried to deploy some of them. Sometimes, we're running into some bugs in different things, so they haven't worked out all of the kinks yet. Hopefully, they can get some of these things resolved and continue introducing new features like they have been.

Our first business unit who started their journey two years ago went from one bot initially to about 55 over a two-year period. Typically, they were averaging a new bot about every two to three weeks. That was with a team of five to six people sort of dedicated to the process. We have had consistent growth with our numbers over that time.

We have been pleased with the technical support. Their response times, capabilities, and patience when working with us, taking the time to understand the issues, and helping us to resolve them. This has improved over time. We are encouraging our users to use them as a resource when they do have questions or problems.

I was involved in setting up our upgraded environment for the new version. The documentation that they provided us was very thorough. We chose to go back to our integrator (our consulting company) to help us build our new environment, just so we would have ready resources available if we ran into questions. However, in this situation, we were able, from start to finish, to build the new environment without many problems, by just following the documentation.

We did initially use an integrator (consulting company) to do our training. That was a very important part of the process, and it helped us be successful.

Automation Anywhere is a great tool. I have been in IT for 30 years, and am amazed at how far we have come with technology and tools to help us do our jobs. The ease of use and the power which the product offers you in a matter of minutes, if not just an hour, and what you can create with it.

It integrations really well with other applications, as long as you have access from the same computer which you're running the software on to your other systems. Then, it can interact with those other systems just as if you were any user who is on that same computer. From this aspect, it is more powerful than other tools which I am familiar with.

We are just starting to look into the solution's cognitive document processing by doing a proof of concept.

Early on, I did try a few of the Automation Anywhere University courses, mainly to get familiar with what was available, so I could guide others to the website for training. At this point, there hadn't been much there that I needed for myself. However, we have looked at the courses, and we are encouraging a lot of our business users to take advantage of the tools.

The important thing about any RPA tool is it has to be a collaborative effort between IT and the business. It needs to be driven by the business, or it won't be successful. An important overall goal or strategy to have as you start your journey: Have good buy-in and ownership from the business. They have to want to do this and take advantage of this new tool.

We mainly use it for development of finance operations, and it's been performing fairly well for the most part. We have 40 automations going right now and they run daily on the Bot Runner.

We've automated journal entries, bank reconciliations, different claims-accounting - a lot of finance processes. For example, we created a system where accountants can drop in journal entries and the journal entries will be read and posted to our system.

One of the processes we automated was that people who work in treasury would go into their email and download PDFs from their emails over and over. Sometimes there would be 200 or 300 emails that they would have to go through, and they would spend a whole day doing that. Now we have an automation that does it, and it only takes one or two hours, and it frees up their time too.

We have saved time or money using this solution, but I don't know how much. That information is tracked by my manager.

The most valuable feature of the product is the flexibility. There are so many features that you can use to develop; it can hit a lot of use cases.

In terms of the usability, the drag-and-drop, instead of being able to type, makes it hard for somebody with a programming background to get used to it. The drag-and-drop slows down development; I can't just keep my hands on my keyboard, I have to use my mouse as well.

The bot creation process is tedious. The solution has a lot of features, but since you have to drag down a lot of the commands, it can get tedious to use it. You end up having to use the mouse a lot more. You can't do it as fast as if, say, you just typed it out on a keyboard.

Since I do a lot of bot development, I'd like a different way to develop them, other than dragging the commands down. If there were a way to type out the commands, to make it a little bit easier or a little bit faster to create the automation, that would be good.

Integrating this solution with other applications is hit or miss, depending on the application. For some applications it's very easy and then sometimes, for others, it's very difficult. There are occasions when, the first time, the application doesn't work at all, so we have to use commands that are not as consistent.

The stability of the solution is hit or miss. It depends on what you're using it for. Sometimes it's very stable and you'll never have issues, but for some processes it may have issues, and you have to be able to fix them and develop it properly.

What we're trying to figure out right now is how to scale this. That's where the hardware comes in. For the most part, scaling with the application is more a matter of building the infrastructure around it.

To scale from pilot to the point where we are now, where we're developing three or four bots every two weeks, it took us six months. A lot of that was trial and error, creating our standards, and hiring developers to whom we could pass the projects.

Sometimes technical support has been very helpful and they've solved a problem very quickly, while sometimes it takes a month or a few weeks to get a problem solved.

The setup was complex because we didn't want to just start making bots immediately. We needed to build the infrastructure around it so that, in the future, it would be a lot easier for us. Once we had a process for how to build bots, it was a lot easier for us, and we had proper standards.

We used Neuralify. They helped a lot in getting us set up and it's been a good experience working with them.

I'm not 100 percent sure how we measure the ROI of a process we automate because a lot of that is handled by my manager. From what I know, we measure it based on time returned to the employee. Instead of calculating how much time it takes for the automation, we calculate how much time the employee was spending on this task beforehand, and now that we've moved it to an automated process, how much we have saved them.

Overall, I think we have seen ROI, but I don't have specifics.

On the shortlist we had UiPath, Blue Prism, and Automation Anywhere. They ended up using Automation Anywhere because it was the most flexible and the easiest to use.

Instead of trying to build a bot immediately, first build the infrastructure for how you want to build the bots. That way, when you scale in the future, it's a lot easier than trying to figure that out after you've already made multiple bots.

I have taken courses at the Automation Anywhere University, but for the most part the courses have been very basic. I had prior training, but when taking it again in the University, a lot of it was just going over the basics of Automation Anywhere.

We are a distributor of Automation Anywhere in Malaysia, and our focus is on solving business problems related to accounting, reporting, network operation centers, and first-level troubleshooting.

We deploy the solution on both AWS and Google Public Cloud.

Since we are the distributors of the solution, the improvements provided by Automation Anywhere vary for each of our customers.

The drag-and-drop feature is valuable.

Once we deliver to the customer, and they see the code, they can truly understand it without needing programming knowledge. As customers don't want to rely on vendors constantly.

The analytical dashboard in the Control Room could use some improvement. Currently, it's quite basic, which can pose a challenge when customers require more advanced features. Of course, different customers will have varying needs and expectations, so there's no one-size-fits-all solution. However, I believe it would be helpful if our team could have more flexibility in developing a more sophisticated analytical bot to meet these diverse demands.

I have been using the solution for five years.

The solution is stable.

The solution is scalable. We use the solution in multiple locations.

The technical support is good.

Positive

I previously used UiPath and WinAutomation by Softmotive but Automation Anywhere is easier to use.

The return on investment that our customers experience with Automation Anywhere typically revolves around the saved processing time and reduced headcount.

Although the initial implementation cost of Automation Anywhere is relatively high compared to other options, its annual subscription cost is lower than UiPath's, which has the opposite pricing structure.

I give the solution an eight out of ten.

I recommend Automation Anywhere to others.