Engineering
Flowable 5.23.0 release
Today we released a new Flowable 5.x engine version (5.23.0). The easiest way to start using it is through Maven:
The version 5 code is on the flowable5 branch on Github https://github.com/flowable/flowable-engine/tree/flowable5.The version 6 code is on master https://github.com/flowable/flowable-engine.
The 5.23.0 release has the following highlights:
Great community contribution for collapsed sub processes by David Pardo. You now can model processes in a hierarchical way without needing to use call activities, which result in different process definitions in the Flowable Engine. When using collapsed sub processes, the modeling part is hierarchical and using different model diagrams for the main process and the sub process models. But when deploying on the Flowable Engine, there’s still one process definition using embedded sub processes. So this feature it targeted at the modeling level.
Bug fix for service tasks with class attributes using skip expressions.
Added support for using the Flowable namespace in addition to the Activiti namespace in BPMN XML.
Several bug fixes and smaller enhancements
A big thank you to the whole Flowable team for making this release possible, and a special thank you to David Pardo for the Modeler contribution. You can use the forum to ask specific questions about the 5.23.0 release, any feedback is welcome.
Optimizing end-to-end business automation can be a tall task for legacy systems that lack integration abilities such as APIs. But robotic process automation can provide a successful interim transition to replacing these when time to market is crucial.
Enterprises need to process a large volume if documents daily — quickly and accurately. Flowable uses Intelligent Document Processing (IDP) to improve content processing and support enterprises in managing documents end-to-end.
CMMN was mainly designed with case management in mind to handle dynamic, human-driven processes, where the execution is not always a straight line, but might involve human decision to drive the process forward. But it can do way more than that.