In Flowable 6.5.0 a new engine has been added: the Flowable Event Registry. This enables the receiving and sending of events from any source, with out-of-the-box support for JMS, Kafka and RabbitMQ. In addition, receiving …
The 6.5.0 release is a huge release with lots of new features, including a fully new Event Registry engine. Where to get it: Download link: https://flowable.com/open-source/downloads/Maven (or other): update your dependencies to version 6.5.0The source code …
Author: Jan Ohlhoff Let’s talk about DMN. No, I’m not talking about the Dallas Morning News, I’m talking about Decision Model & Notation, which is published by the OMG, the Object Management Group. They also …
2019 has been another of those years where we’ve taken huge steps forward in various aspects of Flowable, both in open source and commercially. It’s been a hard year from the sheer volume of work …
Joram Barrez and Paul Holmes-Higgin What we’re not going to do is suggest that software evolves like biology through random mutations, although we have seen some shockingly random code in our time [pause for someone …
This year we’ll be holding our community event near Heidelberg in Germany, kindly hosted by SAP at their HQ in Walldorf. And, same as last year, there’s no fee to attend but we do need …
Author: Simon Amport Overview In this blog post we’ll look at how to migrate a BPMN process instance with Flowable. Problem Let’s assume you have a running application in production and everything works fine. After …
The 6.4.2 release is mainly a bug fix release. The next release path will be towards Flowable 6.5.0 where we will be adding new features like history cleanup and improved JMS messaging support. Where to …
In Flowable 6.4.2, support for CockroachDB was added. We’ve sat together with the engineers from Cockroach Labs (the company behind CockroachDB) to make sure we’ve got the details right and to exchange feedback both ways. …
Flowable core developers Filip Hrisafov and Joram Barrez continue the Flowable + serverless journey by looking at other technologies that make a serverless “process as a function” possible. In part 1, they discussed what serverless …