Keboola Connection vs. OpenText MBPM

Keboola Connection allows data to be well stored, accessed when required, and proper analytics handled in case the company requires information from various sources. Keboola Connection is fully integrated with various collaborative tools, and all of the needs are well addressed to bring a consistent and reliable summary report. Finally, Keboola Connection is a warehouse, that is flexible, secure, and standard.

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.

Incentivized

• Complex routing of tasks based on calculated criteria
• Linking between tasks and accessing relevant information
• Organising, scheduling and prioritising
• Different views for different people

Incentivized

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

There are other products that seem to be a better fit for future initiatives.

Incentivized

Although it is intuitive to use it does require training

Incentivized

Great customer service for an API support related query

Incentivized

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.

Incentivized

• The development of the ticketing system has enabled us to greatly improve customer relationships
• The scheduling and allocation of the tasks has reduced both the number of open tickets and the turnaround time to resolution
• Management information from the system has improved decision making

Incentivized