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
Process Street
Score 8.2 out of 10
N/A
Process Street in San Francisco offers their application which allows teams to create simple recurring checklists, collaborate around them and track as they’re completed.
$0
per month per user
Pricing
OpenText MBPM
Process Street
Editions & Modules
No answers on this topic
Free
$0
per month per user
Pro
$25
per month per user
Enterprise
Custom
per month per user
Offerings
Pricing Offerings
OpenText MBPM
Process Street
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
OpenText MBPM
Process Street
Features
OpenText MBPM
Process Street
Reporting & Analytics
Comparison of Reporting & Analytics features of Product A and Product B
OpenText MBPM
7.0
Ratings
16% below category average
Process Street
10.0
Ratings
20% above category average
Dashboards
7.90 Ratings
10.00 Ratings
Standard reports
9.00 Ratings
10.00 Ratings
Custom reports
4.00 Ratings
10.00 Ratings
Process Engine
Comparison of Process Engine features of Product A and Product B
OpenText MBPM
7.3
Ratings
14% below category average
Process Street
9.7
Ratings
15% above category average
Process designer
8.10 Ratings
9.20 Ratings
Process simulation
7.10 Ratings
00 Ratings
Business rules engine
9.00 Ratings
00 Ratings
SOA support
6.00 Ratings
00 Ratings
Process player
7.00 Ratings
00 Ratings
Support for modeling languages
8.00 Ratings
00 Ratings
Form builder
6.90 Ratings
10.00 Ratings
Model execution
6.10 Ratings
10.00 Ratings
Collaboration
Comparison of Collaboration features of Product A and Product B
OpenText MBPM
7.6
Ratings
10% below category average
Process Street
9.0
Ratings
7% above category average
Social collaboration tools
7.60 Ratings
9.00 Ratings
Content Management Capabilties
Comparison of Content Management Capabilties features of Product A and Product B
OpenText MBPM is well suited for rapid application development where process workflows are well designed in a detailed environment. A servicing organization could benefit from being able to manage and design complex case management processes and applications. It is not suited for the automotive industry where complex custom engineering processes exist within product engineering (vehicle) and manufacturing plants.
if you have standard processes that are often executed, it's worth to use. If you are a small company it is generally not worth to implement because you will need somebody who permanently works with it and maintains the processes.
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.
If you had the ability to drag tasks around in a nonlinear way, it could be a cool creative feature. An example is to have a subtask next to another that says N/A if the task wasn't executed because it wasn't applicable.
Inbox tab can be overwhelming but that may just be the style in which I built my checklists.
Since my last login into the platform, the latest update made the app much easier to use and learn. It's incredibly clean, and everything is exactly where it should be location-wise. You can tell they listen to their user base for features.
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.
I've tried other checklist tools like Google Keep, but it was too simple. I've tried Flowster, which is very similar to Process Street, but I like Process Street better. The interface is a lot more balanced and pleasant to look at. I found Flowster to be a less appealing interface even though the features were similar. I also briefly tried systemHUB but it is very expensive for what it offers compared to Process Street.
Because of Process Street I am no longer losing money when having to redo things
It helps me eliminate those nasty "egg on the face" situations with clients because now nothing slips through the cracks. The team is able to be on top of it!