Cleo Integration Cloud is a framework providing data integration between disparate systems and people within and across organizations.
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
SAP Integration Suite
Score 8.5 out of 10
N/A
SAP Integration Suite is a modern, secure integration platform as a service (iPaaS) that connects applications, data, processes, and AI agents across SAP and non‑SAP environments.
$11,199
per year
Pricing
Cleo Integration Cloud
OpenText MBPM
SAP Integration Suite
Editions & Modules
No answers on this topic
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Cleo Integration Cloud
OpenText MBPM
SAP Integration Suite
Free Trial
No
No
Yes
Free/Freemium Version
No
No
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
Optional
No setup fee
No setup fee
Additional Details
—
—
Access to free tier services does not expire while there is an active Pay-As-You-Go or CPEA account with SAP. Once a free tier service limit has been reached users have the option to update from a free to a paid service plan in the same account.
CLEO Integration Cloud is well suited in any environment where you need to move and translate business data from one format to another or multiple other formats. It is very well suited to replace existing EDI systems that are cumbersome, are a lot of work to add new mappings (add customers for example), or where the support is lousy and you are constantly creating support tickets to try to resolve issues. It just works very well and is constantly improving including keeping up to changes made by various services such as Shopify.
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.
Good at: 1. Integrations with in SAP applications, especially with event based triggers 2. Can be integrated very well with other BTP services to attain Batch processing and store credentials 3. Supports many authentication models Improvements: 1. No version history available compared to as it is available in S4HANA 2. Need a lot of improvement in git hub connections
A great platform perfectly integrated with the rest of the company's software.
Detailed design with simple and easy access from anywhere to our information.
Multi-location and multi-device access.
We save on hardware, software and maintenance, by minimizing the user's need for powerful equipment and the programs in charge of managing and configuring them, reducing the investment in their acquisition.
Cleo integration is in charge of technical maintenance and updates.
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.
Provide more pre-built integrations to use within SuccessFactors or other modules instead of everything having to be custom built
Support is unable to provide advice on custom builds so you often have to engage a 3rd party partner
Works best when you have the functional and technical teams working together. Otherwise, the system is too technical for a functional user to create integration and a technical user not always understand the functional perspective
It is in place, our system integrators are familiar with it, and it fits into the ecosystem. A better user interface, flow build and debugging experience would see it grow, many technical staff do not enjoy using it for this reason, however it is quite capable and powerful behind this one shortcoming.
The user interface is messy and not intuitive. It has a steep learning curve, and flows developed around are easy to make a mess with layout and can be difficult to follow. The debugging is also quite difficult, it takes some time to figure out how to follow the flow and examine data. Error handling is also difficult and not intuitive, it is better to let some errors leak and monitor through ALM.
The support for SAP Integration Suite is satisfactory. We leverage SAP support through our manage services partner. So far, we have not had many major issues. One concern, to make our rating a ten, would be turnaround time on high priority incidents. SAP Integration Suite drives our key business functions forward. Without a reasonable service level agreement on turnaround, we sometimes find us running into issues running pay, etc.
Before choosing a solution, we did a detailed analysis of cost, performance, scaling and support. Cleo checked all the right boxes and we have been very satisfied with our choice.
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.
Before deploying SAP Integration Suite, we assessed Oracle Financial Services Analytics and IBM Risk Analytics. While Oracle had proved its mettle in the exceptional database support and IBM in presenting risk model tools, SAP Integration Suite overwhelmed others by being effortlessly integrated with our existing banking framework.
We have easily improved our EDI tenfold (or more) as far as ease of adding new customers for example
We have saved a ton of money by reducing chargebacks for missing ASNs for example
We have improved customer scorecards where they measure our EDI performance such as one large brand name customer we sell wholesale to who originally scored us around 28% and after implementing CLEO we quickly went to a 96%+ score.
