Reviews (1-25 of 29)
The best part is that this tool gave the business the cool swim-lane process views before they sign it off to be implemented into the system.
Not suited - For any enterprise level order management requirements.
In my organization I implemented the registry of non-conformance to allow users to submit company-related complaints and this was a complete success based on the extended capabilities of Bonita BPM from UI design to reporting.
- UI design
- Workflow using BPMN
- Use of Java code
- Integration using connectors
- I can only think of database connection, it could be improved for a better and shorter experience connecting the data since this is a low-code technology.
- UI design and experience in general.
- Connectors: Data Base connectors with almost every DB suite.
- BPMN language and standard: Very good instantiation of Business Process Management Notation.
- Roles and automation of business process.
- Great business rule engine.
- Perfect integration using Java code, which is easy to maintain and improve.
- Great reporting tools.
- Connection to other legacy systems, ERP, CRM.
- Easy UI development
- Fast time to market
- Bonita needs to improve its low code development
- It needs a BRMS functionality
- It needs a Document Records functionality
- It is a very low cost platform. You can start with open-source edition which is free and with the application number growth upgrade to subscription editions for more features and support. Subscription editions are still not expensive compared to bigger players platforms.
- It offers a great UI designer tool for rapid building process forms and web applications.
- It gives a lot of flexibility and extensibility. It comes with features like built-in connectors, convenient API, and a web portal. You can add your own connectors, extend the API and customize the portal for your own needs.
- 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 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.
- 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 UI Editor is using latest technologies and is very easy to develop. You have complete freedom.
- Living application as part of version 7 brings huge functionality for custom development.
- Modifying case instances in production environment can be easily done from the portal.
- The big list of connectors.
- API system allows you to easily access all the data you need.
- The BPM API system has no security and all authenticated users can access data with no restrictions. This can impact data security across different departments.
- You have no option to deploy processes directly from Bonita Studio in the production environment.
- Security for Bonita's Java API system should also be reviewed. Normal users should not have the possibility to access engine information.
- Ease of integration modularity
- Building up workflow from design
- Traceability logs, in order to allow audit processes
- Licensing model
- Would be useful having more functionalities of document management
- Increase the number of backward supported releases
- 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.
- Excellent process authoring studio and experience. Fully featured but incredibly extensible.
- Excellent ability to author and attach forms, using a system that de-couples form development from the process engine but still has a powerful form environment.
- Difficult to understand the difference between the pool and the first task. The UI barely differentiates them. Sometimes this is confusing to new users who click the "start" icon instead of the pool and lose track of where the starting contract is.
- Need a better way to deliver forms that does not use IFRAMES.
Needs more help and "out of the box" groovy scripts for common tasks, especially using the Engine API.
- The modeling tool is very easy to use, it took me less than 20 minutes to create and deploy my first application.
- The large number of connectors is a plus, we manage to connect our application to SAP & Alfresco.
- We use a lot Bonita APIs, that way you can use the BPM engine in any business application.
- The administration console can be improved, for example, it's not easy to access the logs when you have a problem.
- The new forms are responsive in design but there is no mobile application!
- I would like them to add a milestone feature. With a milestone, it's more easy to follow complex business processes.
- 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?
- Easy worflow design and update.
- Form creation can be done by non IT resources.
- Roles and users are really managed well.
- The web portal does not allow advanced search.
- Standard connector does exist for SAP but not for Oracle EBS.
- We like it that it is open source.
- Easy to use with good management tools.
- The technology using AngularJS framework
- We like to see more API tools to allow integration with third party tools.
- Better report writer and analytics tools.
- Creating workflows for evaluation of the product was easy. Makes comparing against other tools easier and quicker.
- Integration with AngularJS applications is documented and supported. This is good for existing applications you want to expand with workflow capabilities.
- UI customization was difficult.
- 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.
- 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.
The challenges we are facing today is the business value that is not well understood by the business regarding what an application like Bonita can provide them. They would like a big data from workflow but that's not the purpose of a software like Bonita, it's only a first step to do that!
- My management don't understand why we cannot access to document when cases are closed.
- Bonita form cannot be accessed anymore when case is closed.
- BDM is not really appropriate to store information that is input through Bonita forms
- Bonita is not a data warehouse and it's difficult for people to understand this and don't find today the advantage on doing workflow only
- 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.
- Mapping the steps of the process
- Connection with a SQL Server is very simple
- Connection with web services based on the SOAP protocol
- HR processes that include candidate requests (a new employee)
- Initiation of a new project
- Quotation mapping
- The documentation does not have enough samples or examples. This is the weak point of Bonita BPM.
- 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
- Bonita uses JBoss and is very easily integrated with Java if using API calls or even their REST services.
- Bonita has the use of JasperReports which makes it easier for us to build reports on our own and attach them as part of the process.
- Bonita Development Studio is very slow in performance. It's built on top of Eclipse BUT one needs too much patience to work with the development studio.
- I have used up till v6.3 so I am not aware of the latest and greatest features on v7.x. But I would like full control on what we can display and how we display things on BPM Admin and User Portal to the customer. Be able to use latest and greatest technology like Angular and less frameworks (They already have less).
- Development Studio should have the capability of communicating with an enterprise database server such as SQL or Oracle. The inbuilt Bonita Database is not that reliable for developers.
Bonita BPM Scorecard Summary
Feature Scorecard Summary
About Bonita BPM
Bonita BPM is a BPM-based application platform that is designed to help users build highly engaging, personalized business applications that can be continuously updated to adapt to business changes in real time. Bonita BPM provides an integrated suite of capabilities and is composed of the following core modules:
- an Eclipse based, modeling and development environment which allows business analysts and developers to graphically design and share processes using the industry standard BPMN 2.0 notation.
- a web based, drag and drop designer, based on HTML5 and Angular JS, to create personalized user interfaces for BPM applications, including web pages and process forms. It is highly extensible so developers can build their own interfaces using standard technologies.
- a powerful and scalable Java-based process orchestration engine build on service-oriented architecture. It is flexible enough to adapt to any information systems architecture, from simple to complex while supporting intensive workload.
- a web-based, out-of-the-box, portal for users and administrators to perform their day to day task. While this is a generic BPM application, users can also completely customize the end-user interface.
Bonita BPM Screenshots
Bonita BPM Competitors
Bonita BPM Support Options
|Free Version||Paid Version|
|Video Tutorials / Webinar|
Bonita BPM Technical Details
|Operating Systems:||Windows, Linux, Mac|
|Mobile Application:||Mobile Web|
|Supported Languages:||English, French, Spanish|