Fortra's Automate Reviews

We primarily use this solution in order to automate manual processes in our operations. 

This tool has machine learning and voice recognition and computer vision, which are both quite useful aspects. These aren't available in other tools. It's a good addition to this tool and it gives the solution an edge on the market.  

The initial setup is easy. The deployment doesn't take too long.

Technical support is helpful. We use them a lot and they are quite responsive. 

The stability of the studio client could be improved upon. Currently, sometimes it slows down and occasionally it will force the program to close completely - which is unexpected. 

The interface could be more user-friendly and easier to navigate.

It would be helpful if the solution was available in the cloud as well as opposed to just being available on-premises. On-premises infrastructure offers limited scalability.

We started using the solution about two years ago now, and therefore that is the amount of experience I have with it. 

We aren't completely satisfied with the stability The system can slow down and the program occasionally crashes and closes. 

As the solution is on-premises, the scalability is limited. 

Just last month, we bought a new license, and therefore we do have plans to continue to use the product.

We have about 30 people currently using the product.

We use technical support a lot and we find them to be quite helpful and responsive. We are very satisfied with their level of service. 

We found the initial setup to be easy. It's not overly complex or difficult. It's straightforward for the most part.

The deployment is pretty fast. It takes about two hours to deploy the solution.

We are just a customer and an end-users.

I would recommend the solution. It's one of those solutions that are helpful in terms of reaching our goals and we've mostly been quite satisfied with its capabilities. 

I'd rate the solution at an eight out of ten.

Our use case for this solution is in the HR department. We are a company that has external consultants that perform services for other companies, and each employee has to give us reports describing their hours each month. Based on these reports, we charge the customer accordingly.

We have PDF files that are scanned and sent to us by phone. These are from our employees on the customer's site, and our human resources personnel review them afterward. The reports are compared with our in-house system, the files are reviewed, and the hours are approved. Once this is complete, an invoice is sent to the customer.

Prior to using AutoMate, our process of collecting reports from employees was manual.

The most valuable feature is the ease of use. The interface is simple, user-friendly, and very intuitive. We have a software development group and we expected to have to do some programming, but we didn't have to. Everything was already built-in, within the system.

This solution is very efficient. It took us only four hours to develop our bot that automates the process, and two people were involved in the development.

It would be nice to have an EBI connector for AutoMate.

The OCR for Hebrew text needs to be improved. The recognition of Hebrew characters is not the strongest part of AutoMate.

I have been using HelpSystems AutoMate for about six months.

We have only implemented the process in the HR department, which has approximately 400 employees. Our intention is to implement it for other uses, as well.

I contacted technical support when we had an issue with a PDF file. They responded very quickly, within six or seven hours. After speaking with them, they provided us with a solution to the problem within two hours.

We also use UiPath, although this is for other departments in the company. For the HR department, everything was done manually.

I think that the main purpose of this tool is the automation of internal processes. This is unlike their competitors, who deal mainly with business processes. If this were a customer service application, for example, then I would probably use a different product.

The initial setup was easy. One person is required for deployment and maintenance.

Our in-house team handled the deployment.

We save more than 200 person-hours per month.

Everything that I used was already built into the system, so we did not have to pay any costs beyond the standard licensing fees.

There are third-party applications that integrate with AutoMate, although we did not have a need to use any of them.

Overall, this is a pretty nice product and I really recommend it because it is very easy to use. We also save a lot of money, just with one bot.

I would rate this solution an eight out of ten.

We are a service provider and we use this solution to automate processes for our clients. Our customers are in a variety of businesses including banking, insurance, energy, and healthcare. There are lots of use cases, especially in the insurance and banking industries, but we are expanding into other industries as well.

An example use case for our clients is the automation of invoice payments.

This product is quite easy to install, learn, and use, with our new employees being able to start using it in projects for clients after only two weeks of internal training.

Compared to other products, the pricing model for this solution is much more convenient, flexible, and adaptable to the Portuguese reality.

Key automation features: email, FTP/SFTP, OCR, ODBC, terminal emulation. 

Main benefits: Full Client-Server Architecture, Multi-Machine Execution, Centralized Management Interface, Graphical Workflows, Intuitive Task Development & Debugging.

While this solution is continually improving, as it is now, the user interface could use improvement when I compare it to a product like UiPath. Specifically, the Automate Enterprise interface needs improvement. 

When you are promoting packages within the environment, it is easy to extract an import, but it would be better to have it all in the same console. As it is now, you have to extract the package separately. The environments should be able to communicate; you push the button, click on deploy, and it goes straight to the production environment.

Increasing the integration with other databases would be an improvement.

Sometimes my team reports situations where there are some unexpected errors from the tool. For example, if a Java error is reported then it doesn't mean anything at all to the end-user. This is an area that may also have room for improvement, although, at perhaps two or three times in a project, this does not happen often.

In my opinion, so far, the scalability seems to be good. However, I would not say that the scenarios I have seen are very difficult.

We have seven or eight clients using this solution, and only one or two have more than fifteen or twenty processes that have been automated. Having this number of processes with three to four robots, running twenty-four hours per day, is not a difficult test.

The roles of the people using this product vary depending on the client. In the Portuguese market, it is common to have one department that manages the robots for the entire organization. Normally, this is not the IT department. I know of only a few cases where robots are spread across different departments. Usually, a dedicated team or four to five people will manage, evaluate reports, corrects errors, and implement new requests.

So far, I am really happy with the technical support. The delay is between one and two days.

In all of our requests so far, we have had a response in one day's time. Sometimes the response is not final, but then they put us in contact with somebody who has the right knowledge, so it is good.

At my previous company, I worked with UiPath and Blue Prism. My experience with UiPath is between two and three years, and I worked with Blue Prism for a long time as well.

My reason for switching was one of personal opinion. In my previous company, we always used one of the big four. In my current company, I wanted to approach things a bit differently. I believe that there are many players in the market that also have good tools, and are more competitive. All of these tools are growing together, and we ultimately settled on this solution.

The initial setup is quite easy for us, although this is in part because we have been working with the partner for a long time. We have lots of direct connections for support, so if we have a problem that is a show-stopper, or something urgent, then we have a direct channel that bypasses the usual help desk.

We handle the integration of the solution from beginning to end.

The pricing model is the biggest advantage of this solution, and it is opening a lot of doors.

This solution is quite easy to install and to manage for most processes between environments. Everything related to usability and automation is really quite close to the leading candidates, and using this product has been a good experience.

My advice to others who are implementing this solution is to start small. This is something that we always tell our clients. Rather than look at the larger responsibilities, start small to test and to gain confidence from several areas within the organization. Once you have three, four, five, or even ten processes automated, start looking at everything that is related to governance. At the same time, do not be afraid to start, even if you don't have everything planned from the beginning.

I would rate this solution an nine out of ten.

It's difficult to say which feature is the most valuable as there are so many, each a must-have for any automation system. A great feature that you seldom see in these kind of systems is the ability to use a database as trigger to launch a task. This is something I asked for a few years ago and that was added.

We use AutoMate to interface different systems with each other, as an EDI tool, as an FTP tool, to automate AD reporting.

I would like to see some better web automation, a wizard like the one in the product WinAutomation would be very nice. Showing the global variables of a workflow in a task when you select it, which variable some result should be stored in. Now, you can't see the global variables but have to type them, which works but isn't ideal.

About eight years I think.

In some older versions there were some instabilities, but the latest version (v.11) seems very stable.

No, you can scale very easily by adding agent licenses and deploying these agents on different computers. You can see these agents as small runtimes of the actual BPA server. This way you can deploy the workflows across the agents and spread the load between the different computers. You can also add development licenses to allow more concurrent developers connecting to the AutoMate console.

We didn't actually deploy the solution. It was basically testing the product. It was just some simple testing we were doing. We've tried downloading reports from the new RP system, using RPA, and doing some manual uploading from some PDF files into our ERP. It was just used for some super simple operations to try it out and get a feel for it.

I actually quite liked the no-coding functionality. You don't have to be too technical or be a coding expert to utilize the solution. 

The platform was fairly user-friendly in terms of designing the bot. I was able to make it do what I needed it to do.

It's difficult for me to answer as I'm not really an expert on HelpSystems and I don't know it well enough to really give great feedback just yet. I'm not really that comfortable critiquing the platform. I'm sure there are some of those issues there. 

It's possible that they could use a stronger community for seeking guidance and help. For example, I know with Automation Anywhere or UiPath, there are strong community areas where I can ask questions and search for information. I don't know if that exists for HelpSystems. I find, for example, it's helpful, if I'm using UiPath, to go onto some of the community pages and I have found answers to my questions fairly easily. I don't know if that's something that exists with HelpSystems. 

The user interface could use a bit of an improvement.

I've only been working with the solution for a short period. I've only used it a little bit for about a month or two, however, I don't have great experience in RPA's.

The solution was quite stable. We didn't have to deal with bugs or glitches. It didn't crash or freeze. We found it to be reliable for the most part.

We were only using the free version and not the paid option. However, that said, I did find it to be fairly flexible. It could scale if you needed it to.

We haven't really used the solution for too long at this point. There aren't too many people using it in our organization.

I haven't really had much experience with technical support, as I haven't used the product that much or for that long. I wouldn't be able to critique their level of service.

I tried to download and use Micro Focus. However, it was too complicated for my skill level and I gave up before I really got too far into the process.

The installation of HelpSystems was not difficult at all. I'm not technically strong, however, I could do it myself without too many problems. It's pretty straightforward, even for non-technical users.

I don't remember how long the deployment took, to be honest. It was one of the easier installations I've dealt with on the platform. When I've looked at other platforms, I've found that some of their rivals were very difficult to install for a person with my lack of experience. For example, Micro Focus was one I tried to download and install and I gave up due to the fact that it was just too complicated. I can compare this experience to Micro Focus where I just found I wasted a lot of time and got very poor feedback. I found HelpSystems refreshingly easy to install. 

I handled the implementation myself.

I was not using a paid version. I was using a free version. We didn't have to pay for any licensing.

We're evaluating RPA at the moment, and therefore we haven't made any payments yet, or we haven't made any purchases to commence operations. We are looking at that, however, we haven't started anything officially. I have a good idea of the pricing of the HelpSystems and UiPath solutions. We're comfortable with what it would cost if we decide to continue with either option.

I've been looking at UiPath for a couple of months, however, I don't have a great amount of knowledge in the topic and I'm not an expert in the area.

I'm not sure which version of the solution we're using.

So far, from my limited experience, I would recommend the solution to other organizations.

However, based on my limited understanding of the product, as I haven't used it for too long just yet, I would rate it at a seven out of ten.