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.
BPMN is dead, long live BPMN
Tools like ChatGPT can handle a variety of business tasks, automating nearly everything. And it’s true, GenAI really can do a wide range of tasks that humans do currently. Why not let business users work directly with AI then? And what about Agentic AI?
Measuring model complexity – Part 3: Introducing Complexity Analyzer
In this post, we continue our exploration of workflow complexity - learn how key metrics like activity count and control flow reveal natural groupings of models, making it easier to identify and improve overly complex designs.
Measuring model complexity – Part 2: Putting theory into practice
In this post, we continue our exploration of workflow complexity - learn how key metrics like activity count and control flow reveal natural groupings of models, making it easier to identify and improve overly complex designs.