Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
- Process designer (48)8.989%
- Form builder (44)7.979%
- Business rules engine (39)7.979%
- Model execution (43)7.777%
Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of Bonita Platform, and make your voice heard!
Entry-level set up fee?
- No setup fee
- Free Trial
- Free/Freemium Version
- Premium Consulting / Integration Services
Would you like us to let the vendor know that you want pricing?
Bonitasoft supports digital operations and modernization of information systems with Bonita, an open-source and extensible platform for automation and optimization of business processes.
Presented as easy to handle and integrate into heterogeneous information systems, Bonita accelerates development and deployment of process automation projects, service orchestration and application development. This is made possible by its low code capabilities, reusable components, and unified deployment on-premise and on the cloud.
CIOs can confront both short-term challenges (often from requests from business teams who wish to support their business development), and the long-term challenge of modernizing IT to deliver on business needs and customer expectations.
Open-source, extensible and integrated, Bonita is based on an architecture that clearly separates the process, data and user interface layers. All project team members can collaborate effectively to develop, deploy and maintain sustainable processes in line with the expectations of business users. Project governance, specific to each company, is respected by a clear separation between visual programming and coding capabilities. Each project team member can leverage their specific know-how and skills to add value. The technologies used do not require learning new languages or methods, but instead rely on commonly used components such as Java, enterprise services such as SSO and LDAP, continuous delivery, and the ability to develop in SDKs. These capabilities avoid the need for additional resources.
The use of BPMN, reusable components, numerous extension points, deployment on premise or in the cloud all help guarantee rapid and agile developments.
Even the most complex business processes gain visibility thanks to centralized monitoring. Traceability, execution control and reduced risk of errors allow teams to focus on optimizing and improving operational efficiency on an ongoing basis.
- Supported: Process designer
- Supported: Business rules engine
- Supported: SOA support
- Supported: Support for modeling languages
- Supported: Form builder
- Supported: Model execution
- Supported: Social collaboration tools
- Supported: Dashboards
- Supported: Standard reports
- Supported: Custom reports
- Supported: Content management
|Deployment Types||On-premise, SaaS|
|Operating Systems||Windows, Linux, Mac|
|Mobile Application||Mobile Web|
|Supported Languages||English, French, Spanish|
- Change the business logic without redeploy
- Licencing - ability to share keys and account
- Premium users website area - there are serveral bugs
- Multiple integration points (emails, storage systems, databases, etc.)
- BPMN used to model the process
- Low-code development
- Updates to the Business Data Model are not as smooth as they could be
- Support workflow
- Support process model
- Good UI
- Prebuilt integration support
- Process as code
- Detailed doco
It seems to be working well in our testing for small and straightforward workflow processing, but we haven't really built any complicated ones for a production, such as to engage mutiple stakeholders, talking to different backend or a long runner etc. so can't really say much from that perspective.
- Task distribution.
- The number of columns in basket.
- Database writing of buffered information.
A less appropriate scenario would be to implement lots of specific rules with various webpages that would deliver a huge number of ending scenarios.
- Automation of business processes.
- Managing task assignment.
- Use by non-technical trades.
- Task assignment
- Process monitoring
- Process analysis
- A document management function needs to be added
- Process analytics needs to be improved
BONITA has been used for 2 kinds of automation processes:
- Dynamic interfacing between IT applications including human interaction. The interface has been dynamically adapted according to the various events managed by the BPM process. It's used at the company level to enable communication with the Customer Services team using CRM Salesforce cases, and with R&D team using Clearquest as a bug management tool. The Bonita BPM process is the basis for dialog between Customer Services and R&D teams.
- Automating the HR process for employees changing their job within the company (change of manager, location, cost center, position in the HR org in the ERP, IT tools)
- Mixing interactions between several IT applications with human interaction through automatic email receipt and response
- Offering several formats for comminicating with IT applications: web services, email, files
- Provides an effective form editor, including fields where values entered by humans drive the next actions of the business process
- Not easy to delpoy new releases
- License key management has to be renewed too frequently, even with a commercial contract in place
- Adding more standard interfaces to common IT applications such as ERP systems
- Change the culture from a technical / engineering culture to a customer-focused culture - this is already underway with the arrival of BONITA Customer success
It is well suited to mixing IT applications and human interactions in numerous dynamic combinations.
It is less suited for mass data transfer with few case management combinations, where an ETL tool would be more efficient.
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.
- Modeling the business data.
- Building a responsive UI for the process users.
- Building integration with LOB systems in the form designer now requires implementing REST API's. This is a development overhead, and should be simplified.
- The studio should include more options for handling exceptions.
- Bonita simplifies the way to produce interfaces between applications of the market.
- Bonita reduces time to implement interface and time to maintain interfaces, using standard connectors.
- The IDE helps to draw a user friendly chart to accelerate deployment of process and increase process governance.
- Bonita forms are not highly customizable in terms of design.
- Some updates may break down your interface. A "test mode" on a virtual appliance with replicated copy of your [production] environment would be a great improvement.
- There is no ctrl-Z, no undo or redo, in the UI Designer editor.
- Easily design workflows & business processes using the GUI studio tool.
- Develop responsive web-based applications quickly and efficiently.
- End users can easily modify BPM applications without needing any code expertise.
- Be able to be implemented on LAMP Stack.
- Make it easier to upgrade between versions.
- Reduce the need for high-level Java expertise for developing applications.
- Dynamic form data capture, with validation and cross references.
- Process flow control with excellent roles and responsibilities allowing the ability to get the right information to the right person at the right time.
- Fantastic extensibility, both in the GUI and workflow connectors. Allows us to make the product meet customer requirements.
- Great bang for your buck, compared to other BPM products in the marketplace.
- I would love to see the process activities pre populate GUI fields, there are excellent REST capabilities, however a gap from the uplift from v6 to v7 is the auto mapping of data form a process activity into a the form. Having to retrieve it from the inside the form is cumbersome.
- Would love to see GIT support in the designer to allow for integration into modern SDLC and CI/CD tools.
- The ability to have a subscription licence work after an AWS node rebuild or a docker container rebuild would be a definite need. Licensing tools that support modern CI/CD and cloud scalability models.
- Run the Forms GUI as a web view inside the Eclipse runtime, better continuity of design tools and stops the incessant screen hopping.
- Satisfied Customers
- Satisfied Developers
- Ease of Implementation and fit for purpose
- Make interfaces between two system easy to modelise and to maintain in the long run.
- Avoid customised development or specific webservice interfacing to exchange data between systems following a workflow.
- Give the needed flexibility and ease of maintenance to automate internal activity processes in a versatile and agile way.
- Stability of the solution was a real issue in a first stage, latest release software is now much more reliable
- Modelisation and maintenance still need a significant initial investment in knowledge aquisition where end users or managers remains dependant from IT department
- BPM is still highly IT oriented from my point of view where needs are on end-users or enterprise core activities, continue to improve marketing target towards non-IT users may give a better adoption by mid-size companies
- Build great work flow logic
- Great API
- Good customizations
- Implementation of variables and code
- Product installation
- Interfacing our CRM with Bonitasoft APIs
- Modeling simple business processes
- The studio is very heavy
- The portal is a handicap for users. Takes too many steps to complete a task
- Why did they not implement gmail authentication?
- Very friendly user interface
- Really easy to implement workflows
- The software installation process has some redundancies
- Complicated license management if you're using the subscription version
- Frequent release of new versions of the software. Lot of work for the system admins for the upgrade, and no chance to do it without service downtime
- 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.
- From a technical point of view, Bonita is not well-suited for integration in a development environment.
- Upcoming support for 'unit' testing and continuous integration seems bloated and overly complex. Its starting point is clearly the Bonita point of view, not the development point of view.
- To integrate Bonita efficiently in a continuous integration process, it should be possible to: completely build a process .bar without having to start the studio and/or server (typically a single maven plugin); deploy .bar files in a maven (or other) repository; start an embedded Bonita server automatically when running unit tests.
- The usage of images and the (apparently mandatory) integration with Jenkins make this more complex than it should be.
- The constraint to deploy only one database model on the server is particularly painful.
- It necessitates that unrelated processes are combined into the same repository. In fact, it completely nullifies the possibility of having multiple repositories.
- While it is definitely a great idea to allow process parameters to be configured in the web interface, it would be useful to allow import (and export) of these parameters as a .properties file. Currently, a re-install of a process requires you to reconfigure these parameters manually (not nice if there are more than a few parameters).
- It is very unintuitive (and even illogical) that the XOR operator is named as such, while it does not act as an Exclusive Or when used with multiple incoming flows.
- A formal ticketing system for encountered issues with Bonita studio and server would be nice. (if it exists, I was never pointed to it)
- Mapping of values (message variables, process and sub-process variables, step variables) is often inconsistent. Certain cases allow the usage of scripts, others don't. Same for calling Java methods on an Object. Making this more consistent would avoid surprises and probably create lesser bugs. Data operations at the entry of a step would be useful too.
- User interface programming
- Business Data Model
- API extensions for complete separation between the process and the user interface
- SAML authentication
- Features that in the new version are no longer supported.
- Easy workflow creation.
- BDM makes better integration.
- Escalations between organization entities.
- Front end is not easy for non developer users.
- BDM has some disadvantages.
- Migration tools for update arent easy to deal with.