I work at a company that has been using Flowable for about 3 years.
We’ve recently started using CMMN and we’ve found some gaps in Flowable Modeler that I’d like to address here. I know that Flowable Modeler hasn’t been getting much attention lately but I’d like to know your position about some of the issues. Mainly I need to know if you’re planning on adding this features or if you’re willing to accept contributions regarding this matter.
All issues referred here refer to version 6.6.0.
1. Supported activity types
When modeling in BPMN, there is no such activity as “Case Task”, the activity that lets you instantiate a case instance through a BPMN process. We know that open-source Flowable Engine is prepared for this activity type but Flowable Modeler is not. This means that if we want this feature we need to stop using Flowable Modeler and that reduces the productivity, specifically because our models are quite big at the moment.
There is also no way to add a signal event listener for CMMN models.
2. Lifecycle listeners
Once again, the Flowable Engine is prepared for working with case lifecycle listeners but there is no way to configure them using Flowable Modeler.
3. Definition of groups for cases
We’re currently using the concept of “potential start groups” in both processes and cases for defining who can see the process or case in your frontend application. Even though the Flowable Engine supports this concept when parsing the model, Flowable Modeler doesn’t currently support adding potential start groups in a case. It only supports this concept for processes.
4. Sentry placement bug
This is an old bug. It’s been there since version 6.4.2. When modelling in CMMN, if you pick the sentry activity (either the Entry Criterion or Exit Criterion) and drag it to a plan item, it doesn’t stay attached to that plan item the first time. After you drop the sentry the first time, you are obliged to pick it up again and drop it a second time. If you forget to drop-and-drop a second time, it’s like that sentry never existed in the first place.
5. Boolean properties
I think this bug has appeared in version 6.6.0, but I’m not sure about this one. Basically, all activity properties that represent a boolean value and are usually represented with checkboxes are not working at the moment. For some reason, Flowable Modeler is not showing the checkbox which prevents you from changing the default value of that property.