Author: Tijs Rademakers
Today we released a new version of Flowable with the 6.1.0 release.
The 6.1.0 release has the following highlights:
Introduction of async history. By enabling the asyncHistoryEnabled property on the process engine configuration (default is false), the history tables are not filled in the same transaction as the runtime tables. Instead an async history job is created and the history information will be written to the history tables in a separate, asynchronous transaction. This also opens up the option to not use the relational history tables at all, and move the historic information to a NoSQL database directly. Pluggability points are available to implement the persistence logic to a NoSQL database.
New REST task feature thanks to Harsha. With the new REST task it becomes trivial to do REST calls from a Flowable process instance. There’s also support in the Flowable Modeler for REST tasks.
Introduction of a new DMN decision table editor. To improve the usability of the DMN decision table editor we are now using the Handsontable framework.
The Odysseus JUEL code is now included directly in the flowable-engine-common module to prevent classloading issues due to conflicting JUEL libraries or even different versions of JUEL libraries.
Added option to use a password encoder for the Flowable IDM engine (instead of the default plain text password persistence), thanks to Faizal!
Support for static Groovy scripts compilation with the new flowable-groovy-script-static-engine module by using the groovy-static scriptFormat value, thanks to Filip (fgroch)!
Several additions to the Form builder and renderer (min/max length, improved expression field and more).
Various small bugfixes all around.
A big thank you to the whole Flowable team for making this release possible. You can use the forum to ask specific questions about the 6.1.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.