The Flowable Async Executor (also known as the Job Executor) is a crucial component of Flowable. At its core, it is a reusable, standalone component running within the various engines of Flowable that provides a …
Introduction The GraalVM project has been something we’ve kept a close eye on since its very beginning. It was two years ago that we did two Youtube videos on running Flowable “serverless” and building a …
Introduction Flowable has supported running Sequential and Parallel Multi instance executions since its very beginnings, as it is a fundamental concept in BPMN. It has different use cases, such as allowing multiple users to give …
The 6.6.0 release is a huge release with lots of new features, including external worker tasks and true parallel execution. Where to get it: Download link: https://flowable.com/open-source/downloads/Maven (or other): update your dependencies to version 6.6.0The source …
Flowable has had example UI Apps for a while now. We decided to do some small improvements to make it easier for you to try them out and test the Flowable capabilities. From release 6.6, …
“Ok, so there’s a download of Flowable available, meaning I don’t need to checkout and build from source, but you know what, I’ve still only got a few minutes to see if it’s worth investing …
Those that know the history of Flowable know that it is a fork of the Activiti open source project made by the team that originally created Activiti. This article isn’t going to go into the …
We’ve been following through an example CMMN model as a means to introduce some of the ways to use CMMN to describe case management automation. In the previous post, we finally completed a case instance. …
Introduction Executing tasks in parallel has been supported by Flowable since its very beginnings, most of the time using the BPMN parallel gateway. In CMMN, parallel executed tasks are the default way tasks behave (if …
We’ve been following through an example CMMN model as a means to introduce some of the ways to use CMMN to describe case management automation. In the previous post, we got to the point where …
