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
SharePoint Designer (discontinued)
Score 6.6 out of 10
N/A
Microsoft's SharePoint Designer was a tool for developing SharePoint applications that has been discontinued.
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.
SharePoint does not provide, out of the box, a tool to create / update workflows from web. You have to use SharePoint Designer in order to create them. If you need to implement custom workflows for specific business processes, then SharePoint Designer is well suited. SharePoint Designer allows you to create workflows with task approval, email notifications, assign variables and update SharePoint Lists / Documents properties. In our company, we have created specific workflows for : - Purchase order - RH forms validation like annual employee review - Dematerialized existing forms and validation
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.
2013 Workflows - Loops: You can build loops to work while a value (not) equals something, or N number of times. You can insert Parallel Blocks to do multiple things at once, or to watch for multiple things, and when 1 thing finishes, cancels the others and moves to the next step or stage.
2013 Workflows - Stages: Previously all we had were steps, which worked sequentially. With the Concept of Stages, we can create blocks of steps and based on the data collected during those functions, we can tell the workflow to go to a different Stage in the workflow based on a set of 1, or multiple, Conditionals in a transition area after each Stage. Giving you the power to develop multiple entire processes and skipping to the correct part of the workflow, rather than going through 20 conditionals to find out you needed to do action 31.
2013 Workflows - REST API: the "Call HTTP Web Service" is a very powerful tool, but hard to understand if you have never seen it done, or have a guideline. It works very similar to the requirements in PowerShell to connect and get and post data to SharePoint using the Rest API. You can also use this to manage permissions on List Items, Lists, Sites, and Site Collections. Best part is when developed correctly, it is SUPER FAST!
Intentionally Building Infinite Loops: I have built multiple review process from Managing Certifications to Updating Published Documentation, that monitors when an Item, based on provided approved metadata, when the "Author" needs to review the document within the given amount of time. They will get e-mails with links asking if changes are needed. If not, it is routed to the Approving Executive, and the Workflow Automatically updates the Metadata to push out the review dates to the next date, based on metadata provided on how how often the document should be reviews. By using conditionals in the transition of stages, it basically starts over, and goes into a parallel block to allow the monitoring of multiple values of metadata to move to the next stage. Very Powerful when you want to automate these types of process. It truly is a "Set It and Forget It" process.
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.
In the newest version of SharePoint Designer, they have gotten rid of the Design view which makes what used to be quick and easy changes much more code-intensive. This makes it harder for non-IT users and is more risker for all SharePoint Designer users.
SharePoint Designer workflows have a lot of functionality, but there are also some crucial limitations, such as not being able to put lookup fields in email subjects or using parenthesis to separate/group logical conditions.
Although this goes along with the Design view, there really isn't a good user interface anymore for adding conditional formatting and styles in views/pages.
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.
Support is good from Microsoft. They are quite responsive when we raise a ticket but SP Designer support will be ended by Microsoft in the near future as they have got new techs like PowerApps and Flow to achieve the same functionality SP Designer does and even more than that.
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 haven't used anything else like this. I use different products for workflows and forms, but they aren't listed in the listings for this page. Instead of using it for workflows or forms (deprecated 2 years ago), I use Nintex. For everything else, I have what I need in the Modern version of SharePoint online
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.
For my needs, I have not found SharePoint Designer useful for my day to day maintenance of SharePoint. It is useful for viewing all the objects that make up the SharePoint site.
It is not as intuitive in regard to setting up Workflows. I have yet to use it to set up workflows in SharePoint. Maybe if I needed more complex workflows, it would be beneficial.
I like to use SharePoint Designer for moving around files within SharePoint sites.
