OpenText Robotic Process Automation vs UiPath comparison

"It lets us automate almost anything, even with the legacy tools. It is very easy for us now to automate with legacy tools, which used to be difficult earlier. We work with a lot of other automation tools from Micro Focus, such as Operation Orchestration, but these tools can only connect to the API. So, there was a gap when we wanted to automate older and legacy tools that didn't have any API to connect to. We can now also automate without any changes in the customer environment. We don't need to change anything in the way that the customer environment works."

"The initial setup is straightforward. There is a lot of guidance in the configuration and actual setup. It feels like installing Windows. It's simple compared to other solutions which tend to be a bit more complex."

"This solution has increased productivity in our organization."

"The most valuable feature is automating tasks that are highly repetitive, such as Accounts Payable. It is also easy to use."

"Overall, the most valuable aspects are the automation, UI navigation, and orchestration."

"UiPath's most valuable feature is its ability to view and extract any data throughout the entire development process in the automation framework."

"UiPath support is pretty good. It's adequate when needed. Fortunately, they have UiPath Academy and other information out there, so you don't need to use it often."

"I like how it integrates with the Orchestrator and everything works together. There are so many different use cases that we can easily connect through APIs, databases, and user interfaces to automate all kinds of applications."

"The user interface is simple and allows people to learn from it faster than other applications."

"It currently supports only on-premises deployments. They can include support for cloud deployments. It should provide us the ability to choose a robot for executing a workflow. We want to control which robot executes a certain workflow. Right now, it automatically chooses the robot that is going to execute our workflow. It should also provide the ability to get filters on the outputs of the steps. We have each workflow as a step, and each step has some output. We would like to have the functionality to execute some script or some logic on these outputs to format the tests directly on the variables."

"The on-prem orchestrator was an issue for us."

"Most of our PDFs are scanned PDFs and the OCR does not always capture all the information correctly. That's why the document understanding feature will be good for us."

"It took quite a bit of time to understand some of the document types. Some of the documents were already pre-built, but some of the documents were new, and it took us quite a bit of time to get it to train on those documents. If there was any variation, we had to re-train it. It took longer than expected."

"There is a need for more videos and examples on upcoming enhancements and changes."

"They can probably focus more on attended stuff or creating a UI around that. We are not using the attended bot a lot, however, I have seen some use cases in other organizations, as I'm working in consulting. I've seen in some other areas where an organization wants to use attended automation, however, the feature is not very well designed which makes it difficult to use."

"UiPath's OCR features could be improved. It's to do complex OCR captures with UiPath. I would also like improvements in the dashboard for executing processes."

"I find it difficult to set up the Orchestrator and it should be more user-friendly for non-technical people."

"The UiPath Academy courses could be improved, there are many courses, and some are more useful than others. I would also like to see improvements in course categorization to make it easier for newcomers to learn the solution."

"The pricing model is very straightforward. You can have a one-year or three-year subscription. You pay for each robot that you want to use simultaneously. If you want, you can install 50 robots and get 50 licenses. If you want to use only one robot at a time, you just need one license. For each license, you pay around 10% or 15% to support. You pay for the license, and you pay a small percentage of the cost of the license for support. This is their licensing model, which is very easy to understand."

"I find its pricing to be okay, but it also depends on the size of the company. Small users and individual users might not be able to exhaust all the features of the platform, but SMEs and large organizations are able to use the platform in a broad manner. They are able to enjoy many more benefits. UiPath needs to come up with a pricing and licensing model that favors small users and individual users."

"The cost depends on how many licenses are needed and how bots are used. Right now there is no solution that is less expensive."

"UiPath's pricing and licensing have been reasonable and manageable for us. Despite challenges in constantly monitoring SharePoint folders, UiPath has worked well within our resources. We have a fully dedicated, unattended license for our invoice processing, which needs to be a top priority and is always running throughout the day. We have another one for all of our other scheduled automations, and we've been pleased with that so far."

"UiPath is more cost-effective than any other tool."

"UiPath's licensing could be cheaper and more dynamic. The licensing can sometimes feel high, especially for smaller companies, but generally, the pricing is reasonable when considering the time saved and corresponding costs."

"We analyzed and compared the costs of RPA from different vendors and we found that UiPath was the most cost-effective in the long term. An unattended robot costs approximately $8,500 annually."

"UiPath's cost is a bit high compared to other RPA tools."

"The pricing is good. They offer a Community edition that we currently use, which is free. Their paid pricing is pretty affordable for businesses as well."