Aurea Process (formerly CX Process) from Aurea Software in Austin is a business process management offering, based on Savvion BPM.
$200,000
per year
Bonita Platform
Score 8.1 out of 10
N/A
Bonita is an open-source business process and workflow management platform created by the French National Institute for Research in Computer Science. It is available as a free community edition or as a commercial subscription product.
N/A
Pricing
Aurea Process
Bonita Platform
Editions & Modules
License
$200,000
per year
No answers on this topic
Offerings
Pricing Offerings
Aurea Process
Bonita Platform
Free Trial
No
No
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
Aurea Process
Bonita Platform
Features
Aurea Process
Bonita Platform
Reporting & Analytics
Comparison of Reporting & Analytics features of Product A and Product B
Aurea Process
5.3
Ratings
43% below category average
Bonita Platform
6.4
Ratings
24% below category average
Dashboards
6.00 Ratings
6.00 Ratings
Standard reports
6.00 Ratings
5.50 Ratings
Custom reports
4.00 Ratings
7.70 Ratings
Process Engine
Comparison of Process Engine features of Product A and Product B
Aurea Process
5.8
Ratings
36% below category average
Bonita Platform
7.7
Ratings
8% below category average
Process designer
6.00 Ratings
9.00 Ratings
Process simulation
7.00 Ratings
6.90 Ratings
Business rules engine
5.00 Ratings
8.20 Ratings
SOA support
5.00 Ratings
6.40 Ratings
Process player
7.00 Ratings
6.70 Ratings
Model execution
5.00 Ratings
6.90 Ratings
Support for modeling languages
00 Ratings
9.00 Ratings
Form builder
00 Ratings
8.10 Ratings
Collaboration
Comparison of Collaboration features of Product A and Product B
Aurea Process
4.0
Ratings
71% below category average
Bonita Platform
5.9
Ratings
35% below category average
Social collaboration tools
4.00 Ratings
5.90 Ratings
Content Management Capabilties
Comparison of Content Management Capabilties features of Product A and Product B
The tool has potential. Its capabilities and visual aspects could be considered rather basic but this might improve, particularly if the business intelligence/analytics aspect is leveraged. Once running well, it could allow (perhaps smaller) companies to successfully improve their customers' experiences through digitalizing customer journey - and we all know that customer loyalty goes a long way. However, whether or not the tool is comprehensive enough to deliver this for larger companies with more complex, multi- and omni-channel interactions is yet to be seen...
Well suited for low code/no code applications centered around approval flows. It has built-in task management for users to see their pending actions, comments, statuses, etc. It has a very nice design for process flows. Less appropriate may be for generic type applications with complex screens and logic within those screens that need a lot of data to process.
Efficient and fast prototyping: a process can be modeled and tried out quickly and with low investment.
Full stack prototyping for development and implementation allows the process to be developed and implemented as an application from the prototype. It's not just drawings and wire frames that are tossed over the wall to developers.
Data modeling is integral from the beginning of the prototype which is appropriate for the stakeholders in the beginning.
There is only one business data model. Even if deploying new processes does not require stopping the platform, the BDM update requires it.
During the platform evolution often new bugs were introduced so it was risky to deploy the platform in the low minor version. For example, there were memory leaks from 7.2.0 to 7.2.3.
The administrator portal could be improved. It is hard to look at subprocess data, for example and it is sometimes better to investigate with SQL queries. I don't like new (7.3) task list either.
Bonita Platform has allowed us to develop GUI relatively fast using its UI Designer while being able to seamlessly integrate our business logic in Java in a BPMN2 process diagram. It gives a nice productivity boost but still requires programming know-how to be able to deliver the final solution to your business problems.
Engine itself is efficient enough for most cases I dealt with. It can also be extended by clustering. I have done performance tests with JMeter and only managed to induce the crash of... JMeter. If there are efficiency issues they usually concern bad design/implementation of created apps or bottlenecks in integrated systems. Although I have met two cases with efficiency loss.
1. Java 7 related PermGen saturation caused by big number of installed apps (there is no jar dependency reusal between apps option).
2. Big number of waiting event handlers in processes stresses the database.
Respect of BPMN standard over the long term. Good enhancements by Bonitasoft for new use cases, for example the introduction of a real form editor even if it has been technically difficult to manage. Once done though, we have far greater possibility of human interaction.
As our customers vary in size and maturity, the ROI ranges accordingly.
For younger, smaller businesses this is a useful tool. Digitalization of he customer journey has certainly helped save time and efforts in many cases.
For more mature market players the tool is not always comprehensive enough. Dashboard and report personalization take time and efforts, and sometimes it feels that a dedicated BI tool would be a more suitable solution.
We've had serious problems with 'automated' processes in earlier versions of Bonita (via Talend), especially with connectors. In Bonita 7 we replaced these with REST calls, hoping for better performance.
Overall, using Bonita has not had a positive impact on our development efficiency. Moving from Talend (using Bonita 5) to Bonita 7 has improved this somewhat. Still, it remains a pain to integrate Bonita in the development and delivery process.
Migrating from Bonita 7.0 to 7.1 has proven to be a difficult undertaking, mainly on the database level. This has cost us a lot of time and better support would be welcomed.