Microsoft Power Automate vs OpenText Robotic Process Automation comparison

"We have saved thousands of hours by automating tasks that would have been labor-intensive and error-prone if done manually."

"It servers our purposes in bringing together all types of applications, being able to automate them with the right intelligent output from the data that we plugin."

"The sequencer programming mode's ease of use is its most valuable aspect. The ease of calling out the functions in a sequence, basically from the functional side, is great."

"The solution is easy to understand and to develop connectors."

"Microsoft Power Automate is very easy to use."

"AI Builder is a good add-on."

"From my personal experience of using Microsoft Power Automate, I think that the automatic document processing feature is helpful for many organizations in streamlining administrative processes. It is a very good feature. It has helped many enterprises to process documents without spending much time on them."

"The program requires no code making it very easy to implement various functions."

"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."

"Sometimes there are issues with security policies within the company. Some parts get blacked. There are some drawbacks when we use it connected to the cloud. We need to convince clients to open some parts. This is often an issue that originates from the company itself, not Power Automate."

"The product should improve its RPA capabilities."

"During their merger, some key functions were eliminated which no longer allows it to run independently from the cloud as a standalone for other companies. For example, options to schedule and trigger have been removed. It would be nice to have these capabilities back. The flow and the connectivity between databases and so on is a bit complex as well."

"They can build more templates and more connectivity with other platforms. They can provide a more user-friendly way to connect with other platforms. They have their own in-built plugins for certain third-party vendors, but there are still a lot of third-party vendors that are not there."

"One of the challenges is dealing with OCR text recognition."

"It would be good to have some kind of on-premises solution for BPMN users, but I don't think Microsoft will ever go back to the on-premises solution. They all train their clients to use their online services. It is easy, but it doesn't follow the industry-wide standards. I can only use the processes that Microsoft gives us. I can't map a business process by using other standards or notations, such as Business Process Management (BPM). I have to use whatever Microsoft gives us. I would like to have support for some standards because if we decide to use another BPM tomorrow, we will have to remap everything in notation to transfer from this solution. This is the only block or obstacle that I see in using this solution. It is closed in its infrastructure."

"The tasks that can be automated are limited to Microsoft applications only."

"They can improve the description of errors and provide more details. Sometimes, when I receive an error, I can't understand what is wrong. It would be useful to have a desktop version to modify or edit workflows. Its scalability can also be better."

"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 solution is free with Microsoft 365."

"There should be increased transparency about which features attend the pricing."

"This is a cost-effective RPA solution."

"I believe one of the advantages of this device is its low cost."

"It has a cost-effective pricing model compared to competitors."

"This solution is bundled with our Office 365, so there is no additional licensing fee."

"You can have two types of licenses, one is user-based, and the other is app-based in the Power Platform."

"Comparatively, WinAutomation is cheaper than the other automation tools. When we purchased the license, it was around $50 or $60 per user most probably per month."

"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."