The intelligent automation feature could be improved. It's interesting because it's simple, but the automation quality isn't always good. It's easy to use, but sometimes you need to make a slight improvement to the automation, and that's not so easy. 

We have many customized cases, so sometimes, it's not enough. We need to change and customize some processes. We have a little methodology where we sit with the key user and save all the programs because they often have a lot of exceptions. Understanding the risk and whether the processes are good candidates for automation is crucial. 

In the case of health systems, particularly the OCR functionality is not available. You need to buy a separate license for OCR. 

Sometimes and the server loses contact with the agents installed in the equipment. That's something that I personally worry about due to the fact that, when the agent loses contact with the server, you stop receiving the locks of the receiver of the program.

The solution has a very weak knowledge base.

Much like Automation Anywhere, the product could offer virtual development via the web. AA has a web browser interface that allows users to deploy from the web using AWS. It's less reliant on on-premises technology.

The solution should have stronger password management. This should be centralized.

The documentation for errors needs improvement as many of the error messages we receive are very vague. For example, an error message might simply say, "The workflow has run into an unknown status," which does not provide any insight into how or why the failure occurred. As a developer, it can be difficult to debug these errors due to the lack of information. 

The logging and failure notifications could be improved because we can set up logging for each step, but we have to manually add it to each task. Similarly, we can set up an action so that when the task fails, a screenshot is taken and an email notification is sent, but we have to go into the task and build a condition for that. It would be better if the logging and error failure notification could be done at a global level, rather than having to go inside the code and adjust each task.

The stability could be improved slightly. This is not a major issue, but we do occasionally lose connectivity. For example, the main central server for Automate is the developer console we are working on. If the developer console loses connection to the main console, this can happen occasionally without us realizing it until later. We may think our task is being saved, but it is not actually being saved on the server and we can lose some data. These occurrences are not frequent, but they do happen. Additionally, there are occasional crashes, although these are not too frequent. 

I would like to have more third-party integrations, as Automate already has a lot, such as Microsoft Dynamics and SharePoint. However, it would be nice to have native actions built into Automate for further third-party integrations.

The community portal is not very active, so it is not a large community. Therefore, if we encounter an issue, we cannot simply search for a solution on Stack Overflow or a similar platform.

It would be an improvement if Automate had better stability tools, whether by recommending a certain amount of memory because it can be a memory hog at times, depending upon the type of application or license you run. Fortra does have an enterprise-level automated manager to manage different automated machines running on different servers. We primarily used a desktop version before they discontinued the desktop license. So, going on to the Automate manager, the enterprise manager is a good tool for using it to check the different servers that are running the actual tool. Maybe there are more alerts built into the enterprise tool to check on things like system memory, uptime, or any freezing in the OS versus the application in terms of turning the application from a piece of software into a service or a system running in the background.

Error messages should be better. For error status, there should be better documentation because a lot of times, error messages that you get are quite vague. For example, you get a message saying that the workflow has run into an unknown status, which is vague. It just tells you that it failed, but you don't know how or why it failed. It makes debugging difficult. From a developer's perspective, it gets a little difficult to debug at times due to these error messages. It's not with all the errors, but for quite a few errors, the documentation is vague.

Event logging and failure notifications could be improved because you can set up logging for each individual step, but you have to go and manually add it to each step or task. The same issue is there with the failure notification. You can set up an action so that when a task fails, you can take a screenshot and send an email notification, but you have to go into the task and build a condition for that. It would be better if event logging and error failure notifications can be done at a global level without having to go inside the code and add it for every single task.

Its stability could be improved a little bit, and it could also have a few more third-party integrations. Currently, you can integrate with almost any third-party service. You can integrate either through the API or through the GUI, but it would be nice if there were native actions built into Automate. It already has a lot of integrations. For example, we have Microsoft Dynamics, SharePoint, etc. We do have a fair bit of third-party integrations, but it would be nice to have a few more software integrations.

There is a community portal, but it's not particularly active. It's not a very big community. If you run into an error, you can't just look it up on Stack Overflow or something like that. However, the tech support from the vendor side has been excellent, so it isn't a big issue.

There is room for improvement regarding cloud functionality; there are a few missing features, and the logging could be better, especially air logging. We can go into logging events and create our own task, but it would be nice if this were more detailed.

We really need a free development environment for customers. Building and testing automation on production isn't ideal.

Sometimes when we communicate with the ERP system and there is an issue, we are not always aware of the specifics of Automate and the source of the problem. Automate simply states "failure" and nothing else. This is an area that could be improved by having wizards available to assist.

So far, for two years, I have not found anything amiss.

That said, nothing is 100%. Each RPA product is not mature enough. There are always have to find innovative ways of automating. There are always challenges for automation. It is a continuously growing process. The majority of the clients want more automation in AutoMate and they want that in the roadmap. 

Some companies have asked for voice integration. This is likely part of the roadmap. 

Fortra's Automate is not as reliable as I would like it to be. For example, it sometimes has trouble finding elements on a page. I noticed that on occasion when I come in the morning and check the automation, it did not run properly.  I am not sure if it is because of the way I programmed it, but this happens more often than I would like.

The workflow for variables could be better. The input and output of task-level variables could be made a little clearer in terms of passing those around from one task to another upon success, etc. Things like that could be a little easier potentially.

The OCR needs improvement. 

The solution needs image recognition to integrate front-end and back-end workflows. They need to offer better organization of image capturing for image recognition.

The documentation is not that great. There have been times where I've had to reach out to HelpSystems to just try to accomplish what we're looking for. I've used other solutions that have much better documentation available.

I believe we need to test various OCR tools that assist in evaluating six different customer resyncs. We analyze their spending patterns and documentation, but current OCR support has limitations, requiring highly standardized documents, which isn't always the case. With a more advanced OCR system, we could improve processes related to credit risk management and legal matters.

We're exploring how to integrate Fortra's Automate with our CRM platform, taking cues from instances where Salesforce seamlessly merged with Automate. However, we use a different CRM, Insight for New Enterprise, and we're seeking ways to connect the automation process within our CRM. We aim for the automation to continue smoothly, even in instances where traditional automation methods might face hurdles.

The technical support could be better. We suffer from language barriers, as we are in Argentina.

The OCR (optical character recognition) capacity could be improved a bit.

There are many things that need to be improved.

The security needs to be improved. They do not encrypt passwords, so this is an issue with HIPAA compliance.

They don't have an auto-recording capability, which means that you have to program everything.

The impression that we had and the feedback that we received is that the interface is confusing and there are too many things that you have to do. It can be a very intimidating UI for a lot of people. They have drag-and-drop features, but they are not all that great. The interface needs to be streamlined and if they want broader adoption in a company then they need to do a better job at taking the technology out of it.

Unlike many of the larger competitors, they do not have a Community Edition where you can deploy it and test it out. You might be able to run it for a month or a couple of weeks, but that is not enough. I think that this is something they could improve on.

Adaptive Growth finds that AutoMate satisfies the workflow and repetitive business processes of most any company we would address. The product's improvement will come mostly from its users which has been the case. 

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.

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

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.

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.

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.