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
ServiceNow Now Platform
Score 9.1 out of 10
N/A
The ServiceNow Now Platform is a digital workflow building and extension tool for ServiceNow featuring a number of low-code / no code tools.
N/A
Pricing
Bonita Platform
ServiceNow Now Platform
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Bonita Platform
ServiceNow Now Platform
Free Trial
No
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Bonita Platform
ServiceNow Now Platform
Features
Bonita Platform
ServiceNow Now Platform
Reporting & Analytics
Comparison of Reporting & Analytics features of Product A and Product B
Bonita Platform
6.4
Ratings
24% below category average
ServiceNow Now Platform
-
Ratings
Dashboards
6.00 Ratings
00 Ratings
Standard reports
5.50 Ratings
00 Ratings
Custom reports
7.70 Ratings
00 Ratings
Process Engine
Comparison of Process Engine features of Product A and Product B
Bonita Platform
7.7
Ratings
8% below category average
ServiceNow Now Platform
-
Ratings
Process designer
9.00 Ratings
00 Ratings
Process simulation
6.90 Ratings
00 Ratings
Business rules engine
8.20 Ratings
00 Ratings
SOA support
6.40 Ratings
00 Ratings
Process player
6.70 Ratings
00 Ratings
Support for modeling languages
9.00 Ratings
00 Ratings
Form builder
8.10 Ratings
00 Ratings
Model execution
6.90 Ratings
00 Ratings
Collaboration
Comparison of Collaboration features of Product A and Product B
Bonita Platform
5.9
Ratings
35% below category average
ServiceNow Now Platform
-
Ratings
Social collaboration tools
5.90 Ratings
00 Ratings
Content Management Capabilties
Comparison of Content Management Capabilties features of Product A and Product B
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.
Using it in the application support team is worth it as it is capable of carrying a lot of information. But using it for a Service Desk operation might not be of much use as it won't be used up to its full potential and will be costly as compared to other alternatives available in the market.
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.
It helps put manage the request really well. It is easier to create a request, track the request and manage the request. It doesn't get lost into a pile of requests.
We've already pre-setted some settings into our ServiceNow. So it automatically assigns the level of urgency and mentions on the ticke if its a high or low priority request.
I really like the ServiceNow dashboards. They ate setup in a really nice way. The dashboards show the real time data aswell as old data incase if we need to see if there is a pattetn in the request or to fix any recurring issue.
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.
Providing admins/devs with easier mechanisms for providing businss stakeholders with self-service admin capabilities across the platform
Tutorials on how to be the best at reporting in servicenow
Guided tour functionaltiy is a bit rigid and could use more workflow capabilities
Making it easier to push form variables to the user so there is more context when providing an approval. The out of box approval UI/form is terrible in my opinion.
While we are very likely to renew, we are also assessing if we should renew all of what we currently subscribe to as we try to reduce costs. Some parts of the business feel there may be a better tool out there to fit their process requirements. We are currently working with them to identify what those requirements are to see if it makes sense while also pointing out a reduced cost of tooling is not always the best fit if we have an increased cost of customization and maintenance between tools.
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.
ServiceNow is a web platform that does not require any installation on a customer's computer. It is very easy to use and it is user-friendly. The customer started to open incidents very fast without investing time and money in training. Customer loves the dashboard at the startup where they can see all their open incidents or look at KB articles for any issue.
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 platform is provided as a SaaS solution and support from the vendor has been good. There are regular software releases with bug fixes, new features and enhancements, and furthermore we are given the opportunity to fully test these before rolling these new releases out into the production environment to minimise the risk of business disruption
We went through a re-implementation last year with a partner and were very pleased with the outcome. We looked at several partners and chose one that was able to provide an entire scope and cost upfront of what would be required to complete our requirements. We worked very closely with the dedicated team assigned to our project throughout the process and they fully delivered on all of our requirements that we presented in the initial scope.
ServiceNow was chosen as replacement for Microsoft Project , due to better licensing model, more flexible configuration of the project stages and components, better API with Azure DevOps. Also ServiceNow is best in the area of Incident and Service management systems and the proof of concept with Jira and incident.io were not successful and we kept relying on ServiceNow. ServiceNow is much more scalable than MS Project for constantly growing enterprise companies for both employee and external contractor type personas.
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.
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.
The biggest positive impact ServiceNow has made to our organization is reduced IT support cost. When we didn't use ServiceNow, we needed a bigger support team. Now we don't need as many support employees.
The other positive impact that I've noticed is faster solutions to any problems. ServiceNow makes very easy to resolve IT issues, in a efficient way. The tickets are organized in a way that the higher priority tickets get worked on quicker.
The dashboard has also made the job easy to find a recurring problem from its core and fixing it forever so that we don't repeatedly get the same issues again and again