Microsoft Power Automate vs OpenText Robotic Process Automation comparison

"The best feature of the tool is that it is generic, so it allows one to do as he wishes."

"The engineers on-site can generate an automated report that takes approximately 10 minutes, while before it took them two days."

"WinAutomation is very handy to use, and it has the power to interact with multiple systems, such as SAP, Oracle, or .NET systems."

"Microsoft Power Automate's no-code workflows help my team in daily operations to a great extent."

"Power Automate is not complex and is very easy-to-use in deploying most development projects."

"Instead of manually triggering payments through the website, everything was done through robotic process automation (RPA), saving us a lot of time."

"Microsoft Power Automate has positively impacted my organization as it has saved a lot of time and effort."

"Triggering and scheduling were pretty good. There was no real commitment with WinAutomation because the licensing was very fair and you could trigger bots very easily."

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

"Microsoft Power Automate could improve by offering recurring execution on the desktop."

"It would be great if it was able to integrate more with various other platforms. It would make development easier."

"Some automation features on some programs did not work smoothly."

"More OCR and AI capabilities are needed to improve the solution. Other solutions have better features, such as Blue Prism and UiPath."

"When compared to other workflow automation tools out there, it's just not as mature."

"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 licensing model is difficult to understand and is something that should be improved."

"The tool should improve its price."

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

"This solution is reasonably priced and offers a free trial period."

"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 licensing price should be more cost-effective."

"The price of the solution is reasonable."

"This solution can save money when used for simple tasks specifically using only Microsoft products."

"This is a cost-effective product and now that it has been acquired by Microsoft, we don't expect the cost to increase with the next release."

"Its license is a part of our enterprise agreement. It is a three-year contract, but we pay yearly. So, it is a yearly license. There are no additional costs."

"The platform is averagely priced. I rate the pricing a five out of ten."

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