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.
In the past few months, this has culminated into a clear understanding of the strengths and weaknesses of the Generative AI (GenAI) technology; and where it makes sense to integrate with it and – perhaps more important – where it doesn’t make sense.
As AI gains prominence as a pivotal technology and enterprises increasingly seek to leverage its capabilities, we are actively exploring diverse avenues for integrating AI into process automation.
The key to managing complexity is to combine different and multiple tools leads to better, faster, and more maintainable solutions. For example, combining BPMN with CMMN.