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 4.0 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
Okta Workflows
Score 7.7 out of 10
N/A
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
Pricing
Aurea Process
Bonita Platform
Okta Workflows
Editions & Modules
License
$200,000
per year
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Aurea Process
Bonita Platform
Okta Workflows
Free Trial
No
No
No
Free/Freemium Version
No
Yes
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Optional
Additional Details
—
—
—
More Pricing Information
Community Pulse
Aurea Process
Bonita Platform
Okta Workflows
Considered Multiple Products
Aurea Process
No answer on this topic
Bonita Platform
Verified User
Anonymous
Chose Bonita Platform
We liked Bonita's architecture, the open-source framework, and the licensing and support model. Maybe fewer features than other BPM platforms but easier to implement and maintain.
Bonita Platform is very easy to use and more convenient when it comes to data handling. In the poTher Bpm Tools, the processing of the data is very difficult and connections are very confusing. In Bonita Platform, one can even use the customized search for the retrieval of the …
One of the best support for BPMN Ability to extend platforms with reusable components to offer common functionality/connectivity Based on Java, used throughout our company
Bonita has a community version, open-source, so it´s easy to test the benefits of process automation for any enterprise. Bonita Platform is also very near to Java architecture, so the learning curve for developers is not difficult, and they only need to understand how processes …
Bonita may be the easiest to start with without a steep learning curve, anyway on the other side it probably is not as powerful in the case you need to handle a very complicated and high volume or mission critical process. If look by the platform cost or license fee, Bonita has …
The Bonita platform is by far the most complete and flexible solution as a BPM suite with the added advantage that the Community edition is usable for production deployment. From a cost perspective, Bonitasoft licenses the subscription edition per server with no limitations as …
Bonita Platform is very easy to use as compared with Oracle BPM. The UI part of Bonita is very efficient and easy to use. Oracle has a more complicated UI. Bonita BPM Studio is very fast and processes can be created easily. This is not true in case of other BPM tools. Bonita …
Far better design and more intuitive than other solutions. BDM is a great tool for non IT users and help[s] them understand how structured data will improve the work. Community Edition allows us to already manipulate the software and appreciate the power of the tool. I enjoyed …
Bizagi and Bonitasoft have many similarities, an excellent process engine and integrated Data Model, unlike Kofax TotalAgility. But Bizagi beats it in the form designer.
The Tibco solution makes it possible to manage the organization of the company in a finer and more industrialized way. But Bonita is more user-friendly and can be more easily understood by users. The Bonita solution allows a dialogue with the user around an intuitive interface. …
There is no user license in Bonita. Given the opensource, we have freedom here to extend requirements that might be beyond OOTB concept. If you have to kill [an ant] you don't need a missile. I think, for simple use cases Bonita has a simplified approach to address.
I found Bonita BPM a more friendly environment, especially when it comes to front-end development. It is also better suited for a gradual introduction to an organization - PoC with Community edition, later upgrade to one of the subscription editions as needed. Tibco's product …
Bonita BPM does have some nice visual tools. The annual maintenance is not so high and we particularly liked the visual tool to create business rules. Bonitasoft’s color-coded tools make life a bit simpler and more memorable for beginners or non-coder people. We really like …
The extensibility or ability to add functions or modify existing capabilities is much easier and better supported in Bonita. The ability to integrate the Bonita system into customer solutions is much easier and allows for tightener coupling to the existing customer portals. The …
I think Okta is so much more complete and FUB is more only sales oriented instead of Customer Service, with Okta you can call, chat, get in contact internally with other departments, and do different things to solve customer issue.
I evaluated Zapier and Microsoft Flow before coming across Azuqua. Zapier was too simplistic and didn't allow for transfer of enough variables. The price point also didn't work for the value it could provide. Microsoft Flow couldn't make the connection with Smartsheet, and I …
Stampley - on the surface they look similar, but I came across this alternative after integrating with Azuqua so I haven't fully evaluated it against Azuqua.
I have used Mulesoft, Workato, my own code and in past years heavyweight data (e.g. ETL) platforms along with a number of bus technologies. In this case, I was looking for the cloud-based approach that matches our strategy of being totally cloud-focused along with simpler …
Azuqua was the first application we assessed for our purposes, and served our needs so well that we felt no need to search further. It gave us the solutions we needed in a way that was easy to set up and maintain, and the support we received was above and beyond expectations, …
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.
Azuqua offered the most customization of the other platforms we tried. While it was comparably intuitive to use, in terms of entry level, Azuqua maintained this intuitiveness at higher levels of sophistication/integration whereas the other platforms either lacked the same logic …
Smartsheet notifications is the main competitor for what we use Azuqua for. When we got Azuqua, there was no competitor and Smartsheet actually recommended it as the solution. Now, we split up the work between the 2 tools and use Smartsheet for the easier notifications and …
Easy to build out complex if/then scenarios and fire of multiple other workflows within one workflow. Like the UI of seeing how data is being utilizes, ported, and manipulated across the workflows. Also like the workflow history for optimization as well as troubleshooting. Raw …
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.
The integration I used Azuqua for was based on Salesforce, Wrike and Office 365. I found the integration of Salesforce reasonably straightforward, Wrike was limited in the "cards" capability but functional (there are bugs but there are also workarounds but they required assistance from the Azuqua support team) and Office 365 was quite immature (primarily around Excel bugs but also email was limited).
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.
The best part about Azuqua is that you do not need to write code. You do however need to have an understanding of logic and how the software works. This happens to fit me perfectly as someone with basic programming experience.
Their Support is second to none. Not only are they extremely quick and responsive, but their answers are never canned responses and always provide valuable content.
They seem to take feedback seriously and will continue to evolve and make a better product.
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.
I think it requires an easy way to migrate flows created from one user to then move the ownership to another user. It happened to us that one of our engineers left the company and he had the Azuqua account and flows. It required quite some time, cases and telephone calls to do the migration to my account.
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.
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.
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.
I evaluated Zapier and Microsoft Flow before coming across Azuqua. Zapier was too simplistic and didn't allow for transfer of enough variables. The price point also didn't work for the value it could provide. Microsoft Flow couldn't make the connection with Smartsheet, and I was unable to get Microsoft support or Smartsheet support to assist me with the issue.
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.
Increased time savings. We could not function as a matter of daily business if we did not have a tool to automate project folders (and complementary workflow management profiles) for the thousands of projects that flow through daily.
Opens up a greater understanding of all the silos and divisions within the company infrastructure and tests secure means to link those groups safely and share information.
Opens up the chance to communicate with other API information sources if our company is doing a partnership with another organization. Granted everything is square with IT security.