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 (Azuqua)
Score 8.2 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…
Very good : to design and execute business processes with just a few data. You can use BDM and it’s easy. It’s really easy to get data from external applications using custom connectors. less appropriate : if you use complex BDM tree objects, using them in form can significantly decrease performance. Be careful to follow guidelines that are given in Bonita Documentation.
Azuqua is well suited to connect data based systems or to add an extra level of automation to Smartsheet without requiring the control center. It is also well suited for people who don't have in depth understandings of programming. The UI is mostly visual with click and drag systems instead of requiring manually entered variables.
Bonita seems particularly suited for processes requiring a great deal of human interaction. Its user model allows you to control access to business processes in a fine-grained way. This allows for business processes to move smoothly between users and services as the process advances.
The definition and usage of custom forms from the latest version of Bonita seems particularly powerful. It allows for a thorough customization of the look-and-feel and does not require complex developments.
The web interface and administration section have greatly improved in the latest versions. Installation and configuration of processes has become more flexible and more structured. The administration section gives a good view on failed processes, allowing to analyse problems in an efficient way.
The concept of reduced code to simplify use by less technical teams lowers the barriers to integration and allows teams to collaborate with ideas and concepts much easier
The ability to review simply any error cases simplifies the old approaches of debugging and reviewing large and complex logs
While not strictly part of the platform the support team's efforts to assist, to help clarify issues and then (where necessary) to resolve bugs was a large benefit and a key driver to extend the platform's footprint.
There is a learning curve beyond the boot camps that needs to be addressed with more structured curriculum.
The full stack technologies are industry standard, but these [are] challenging to learn and could use a learning path and orientation. There's probably opportunity for third-parties here to help with learning and adoption.
The lack of connection/card documentation. Every card does have a section with details, but they are sometimes lacking.
The help center and community also need some structuring work. Every single connection/app should have a section with detailed documentation regarding its triggers and actions.
The FLO history section needs to be more refined. It sometimes does not load and choosing the date doesn't actually show execution results from that particular day.
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.
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 to hardware, users, processes, etc.
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.
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.
Even though our revenue has grown 3x since we started using Azuqua we have only marginally increased many of the teams due in large part to the efficiency gains that we have been able to realize with Azuqua.
Before Azuqua we spent a large amount of time talking about technical complexities in solving for customer success and value. Now we only talking about solving for customer success and values because the technical complexities disappeared with the introduction of Azuqua.