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
Power Apps
Score 7.7 out of 10
N/A
PowerApps is a low code / rapid application development product from Microsoft that allows users to quickly build apps.
$20
per month per user
Pricing
Bonita Platform
Power Apps
Editions & Modules
No answers on this topic
Power Apps Premium
$20
per month per user
Offerings
Pricing Offerings
Bonita Platform
Power Apps
Free Trial
No
Yes
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
Power Apps
Considered Both Products
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 Appian has all major features and my Manager gives this 2 tools to choose one from that. I found Power Apps is easy to learn and develop, but I feel Appian is realy complex. I strugles to learn something in Appian but that didn;t works well. Power Apps gives me …
1. PowerApps functionality comes with E1 over E3 License without adding extra costs 2. For Nintex you pay (at the beginning) for each workflow, so my intention would be, to do no workflows to prevent additional costs, but I want a platform with a fair price that allows me to …
Much cheaper, much more customizable, and easier to use. There is not much of a learning curve and the licensing cost is much cheaper. PowerApps does one thing very well, whereas other platforms are mediocre. There is much more customization possible for your in-house workflows …
PowerApps includes several features and caters to several business needs. Bubble is not Microsoft, people using PowerApps find it convenient since they are already committed to Office 365.
PowerApps and Power Automate go together in the Power platform. They are made to work together to create a vast collection of connectors and out of the box pieces that come together to make a whole application. If you are unable to complete a task from within PowerApps, Power …
I have extensive experience with another low code platform, K2 and it's SmartForms. SmartForms have their own challenges but allow the developer to extend the operation of a form as needed. In addition, their vNext version promises to greatly enhance the developer and …
PowerApps is the first we have used in Office 365 and Azure Integration. It really helped us to integrate application in Azure and building short apps with low cost.
PowerApps has much power when talking about Office 365 and Azure integrations. Has low cost and it is easy to create/deploy applications. Bonita is open-source but it is necessary to have many technical skills to create applications and also to handle the infrastructure when …
I'm not sure if you can say D365 CRM is an alternative to PowerApps, because basically all the customization of using D365 CRM, or what used to be called XRM, is now called a model-driven PowerApp. Likewise, SharePoint has become intimately connected to canvas PowerApps. Both …
PowerApps is what the company has presented to us as our option. While Nintex is nice and relatively capable, it is always a +1 to the Microsoft platform and requires its own validation and integration. Nintex can also be feature limited in its online version depending on the …
It's by far the most superior simply because of its integration with what most companies already have in place Sharepoint, SQL, Azure. It's drag and drop functionality is top notch and the dream of creating mobile apps without having to duplicate the work is amazing as well. …
Along with PowerApps we evaluated Smartsheet for use and we determined that PowerApps provides a great deal more functionality and flexibility. Especially when you consider it is nested in SparePoint and all the additional functionality that SharePoint provides. PowerApps …
Although Zoho allowed for some unique customization abilities including html styling and simple scripting language. In the end it came down to the Office 365 and choice of many other connections that lead me to choose PowerApps.
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.
PowerApps is well suited for "quick-wins" and fast prototypes of business solutions. It also is beneficial for situations where business partners and developers work together - it allows the business folks to provide a "quick-and-dirty" prototype which is then fleshed-out by developers that are trained experts on the platform. The interactive and easy to understand representation of the solution allows business partners to "see" the solution and add, remove, or correct aspects of it themselves. It provides a common view and understanding of the actual solution across business units and tech teams. PowerApps, being a low-code\no-code platform is not well suited for business processes that require many complex computations or large amounts of custom code - such as solutions that are better architected as Web Site or "full-blown" desktop solutions. There are solutions that are just not easy or quick to accomplish in a low-code\no-code platform. Enterprise Architects should know the difference, however business partners often try to create a solution and only when stuck because it becomes too complex do they engage a tech team for assistance - at which point there are sunk-costs involved and hinderences to re-platforming the solution
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.
Power Apps has formats that are pre-built that don't require any coding which makes it easier to achieve your vision. This does become a challenge if your App needs don't fit into that format.
We deal with a ton of data so the fact that you can connect to any data source in addition to their pre-stablished data connections makes the process a breeze.
The online learning resources and tutorials are helpful as well for those who are tech savvy.
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.
PowerApps has a great coding option, but there are some pieces of the tool that the requirement to understand code is a barrier to fun if the user doesn't code.
MUCH time can be spent looking for solutions on this young platform and the body of forum/help/lessons learned is not as robust as it will be in a few years.
Like many early-stage Microsoft products, PowerApps is a relatively blank slate that will be improved by the feedback of their users and ongoing feature development. Right now it seems that the product lacks a critical mass of use-case driven templates (there are some, but I haven't yet found one that didn't require more work to customize it to my need that it would take to build my own tool).
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.
PowerApps is a great solution and I have spent the last year familiarizing myself with the platform and building custom applications to complete a whole range of tasks such as asset management, custom invoice generation, and item restriction tracking. We as a company have barely begun to scratch the surface of what can be achieved with PowerApps.
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 community forums are extremely responsive to questions asked, there is a good body of online documentation and many community posts to draw from. Although the platform has changed, which means some of the posts are out of date and the solutions provided aren't relevant. Of relevance, I read over 400 articles plus documentation to get this first app built in SharePoint, move it to SQL and make it work exactly the way it should.
1. PowerApps functionality comes with E1 over E3 License without adding extra costs 2. For Nintex you pay (at the beginning) for each workflow, so my intention would be, to do no workflows to prevent additional costs, but I want a platform with a fair price that allows me to create workflows without thinking about the price for each workflow and we use only some workflow and relative easy workflows and forms as a medium-sized company. 3. PowerApps provides a lot of functionality without needing to invest in premium features directly.
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.