Microsoft Power Automate is an advanced automation platform offering a range of features, including AI-powered automation, robotic process automation (RPA), business process automation (BPA), digital process automation (DPA), and process/task mining. The platform aims to empower organizations to securely automate their operations at scale by leveraging low-code and AI technologies.
$15
per month per user
OpenText MBPM
Score 7.2 out of 10
N/A
OpenText acquired BPM solution Metastorm in 2011, and has rebranded the product as OpenText MBPM. It is an alternative BPM solution to OpenText's primary BPM offering called OpenText Cordys Business Process Management.
Microsoft Power Automate is the best tool to extend Microsoft services you already use. Hands down. Prototyping workflows is very easy in Microsoft Power Automate. It's also the best choice for sending custom cards through Teams and email. It's the easiest way to get data from Microsoft Graph.
Metastorm is well-suited for scenarios in which internal stress testing an application is needed in a hurry before showcasing it to potential customers. It supports different views of the process from Swimlane perspective, so different methodologies can be handled. It is an Enterprise level tool and handles both small and large projects quite well, although smaller companies may be stressed out by the amount of time it takes to properly maintain the application.
The Metastorm process engine is based on an older version of .NET. Updating to a newer version would resolve several known issues with .NET email functionality.
Metastorm builds web pages at run time. While the UI presented to the end user is fine, the Document Object Model is convoluted and subject to change with new releases. Providing a more simplified DOM or at very least a custom function to replace document.getElementById() would make client-side scripting a much more powerful tool.
One function that I've seen Metastorm competitors do well, is email wizards. Having a WYSIWYG email editor would be really nice.
Power Automate has an intuitive interface that is easy for novices to use. It doesn't require programming knowledge, however having that experience will help troubleshoot potential issues if they do arise. There are advanced features that allow the use of "code-like" steps that will help power users get more advanced automations set up quickly.
I really have had a need to contact Win Automation support, but when I do google how to do a task, Win Automation has an extensive message board with a broad number of topics and questions answered where I could see how other people were able to solve similar problems to the ones I have.
after reviewing the main features of Power Automate, the Microsoft trainer focused on some of our real life use cases implementation, from simple to more advanced.
although it was productive, it is more difficult to stay focused and in a 7 hours a day online training (including screen share issues and the fact that the trainer just can't precisely show the exact location of your mistake)
I had to migrate from Robocorp to Power Automate. The automation was using API and sharepoint. So it was better to use Power Automate instead of Robocorp so we did the migration. in some areas the migration was easy but creating flows and making it smaller codes was difficult. Debugging the code was tough so we took lots of time.
Power Automate is a no-code/low-code solution tailored for workflow automation, data integration, and AI integration, making it an excellent choice for Microsoft-centric organizations. OutSystems, on the other hand, is a comprehensive application development platform, offering rapid app development with both low-code and traditional development options. This platform is well-suited for organizations seeking custom application development. Nintex specializes in workflow and process automation with a strong focus on SharePoint and Office 365 integration. It also includes advanced features like document generation and robotic process automation (RPA).The choice among these platforms should align with your organization's specific needs, considering factors like integration requirements and the desired level of technical expertise. In the bottomline, it's up to cost and licensing.
We found that OpenText MBPM held its own quite well against IBM BPM. We ended up choosing OpenText MBPM due to the analytics, complex routing, and the ease of SOA service integration. Furthermore, the ability to quickly develop simple User interfaces make this tool a daily component of our most-used toolbox components.
