Azuqua was a tool that helped users integrate their SaaS applications and build custom automations. It was acquired by Okta in late 2019, and is now part of Okta Workflows. Okta Workflows leverages Azuqua’s workflow orchestration engine and application integrations to automate complex identity-centric processes such as user onboarding and offboarding. The product is available as part of the Okta Lifecycle Management…
N/A
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.
N/A
Pricing
Okta Workflows
OpenText MBPM
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Okta Workflows
OpenText MBPM
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Okta Workflows
OpenText MBPM
Features
Okta Workflows
OpenText MBPM
Reporting & Analytics
Comparison of Reporting & Analytics features of Product A and Product B
Okta Workflows
-
Ratings
OpenText MBPM
7.0
3 Ratings
11% below category average
Dashboards
00 Ratings
7.93 Ratings
Standard reports
00 Ratings
9.02 Ratings
Custom reports
00 Ratings
4.03 Ratings
Process Engine
Comparison of Process Engine features of Product A and Product B
Okta Workflows
-
Ratings
OpenText MBPM
7.3
3 Ratings
13% below category average
Process designer
00 Ratings
8.13 Ratings
Process simulation
00 Ratings
7.13 Ratings
Business rules engine
00 Ratings
9.02 Ratings
SOA support
00 Ratings
6.02 Ratings
Process player
00 Ratings
7.02 Ratings
Support for modeling languages
00 Ratings
8.02 Ratings
Form builder
00 Ratings
6.93 Ratings
Model execution
00 Ratings
6.13 Ratings
Collaboration
Comparison of Collaboration features of Product A and Product B
Okta Workflows
-
Ratings
OpenText MBPM
7.6
3 Ratings
9% below category average
Social collaboration tools
00 Ratings
7.63 Ratings
Content Management Capabilties
Comparison of Content Management Capabilties features of Product A and Product B
Azuqua is well suited to connect data based systems or to add an extra level of automation to Smartsheet without requiring the control center. It is also well suited for people who don't have in depth understandings of programming. The UI is mostly visual with click and drag systems instead of requiring manually entered variables.
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 concept of reduced code to simplify use by less technical teams lowers the barriers to integration and allows teams to collaborate with ideas and concepts much easier
The ability to review simply any error cases simplifies the old approaches of debugging and reviewing large and complex logs
While not strictly part of the platform the support team's efforts to assist, to help clarify issues and then (where necessary) to resolve bugs was a large benefit and a key driver to extend the platform's footprint.
The lack of connection/card documentation. Every card does have a section with details, but they are sometimes lacking.
The help center and community also need some structuring work. Every single connection/app should have a section with detailed documentation regarding its triggers and actions.
The FLO history section needs to be more refined. It sometimes does not load and choosing the date doesn't actually show execution results from that particular day.
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.
The system is working as it should, keeping our programs safe from outside hackers. Helping us keep our passwords safe, convenient and already ready to get us logged into the program securely and quickly. Verification that only authorized users are able to access our company's programs. Okta Workflows (Azuqua) is a very good system that has helped our company greatly.
I had to use the Automate tool for funneling image assets in bulk (tens of thousands) from FTPs into various destinations on an eCommerce platform. The user interface was quite harsh in comparison to Azuqua. Far more text/code line driven.
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.