All Versions
Latest Version
Avg Release Cycle
118 days
Latest Release
629 days ago

Changelog History
Page 1

  • v6.6.0 Changes

    October 12, 2020


    • 🚀 External worker tasks have been added to the BPMN and CMMN engine. This is a new paradigm that is available to execute service logic outside of the BPMN and CMMN engine. Until this release this could be done by pushing work to another service, like with using a HTTP task or send an event with the event registry task. The external worker task can be used to pull work from the BPMN and CMMN engine. This means that a service written in any language can pull for open external worker tasks over a dedicated external worker REST API, then execute the work, and finally complete the worker task to move the state of the process or case to the next state.
    • ➕ Added support for future Java delegates to enable running service tasks and HTTP tasks actually in parallel. Until this release a parallel gateway with multiple outgoing sequence flows to a service task didn't run the synchronous service tasks really in parallel, they were still executed sequential. When these service tasks are made asynchronous and not exclusive, then they were executed in parallel by the async executor, but also in different transactions. With the new future service task support, it's now possible to run synchronous service tasks within the same transaction in parallel. The service tasks are executed in parallel on a thread pool and the future will wait until all service tasks are completed. More info is available in this blog post.
    • ➕ Added a category property to jobs to be able to distinguish between different groups of jobs. This can also be used to enable the execution of only specific job categories in the BPMN or CMMN engine. In this way different micro services with an embedded Flowable engine using the same database can be configured to only execute jobs from a defined list of categories, as an example.
    • 🚚 History jobs are now moved to the deadletter job table when the retries are exhausted. This ensures that the history job is always kept in the database.
    • ✂ Removed the get current engine configuration from the CommandContextUtil classes of the Flowable engines because in an application where multiple engines are used it could not be guaranteed that the correct engine configuration was returned.
    • ⚡️ JSON variable changes are now tracked when updated in expressions, scripts, delegate classes or Spring beans. This means that when updating a property like in a delegate class, the customer JSON variable will now automatically be updated.
    • 👍 Extended the entity link support to also record grand parent entity links, which means the parent process of a task in a sub process for example.
    • 🚀 When deploying via the BPMN, CMMN or DMN repository service the created deployment will have the parent deployment id set from its own deployment id.
    • 🏗 The FlowableExpressionEnhancer has been removed. We have adapted the Expression parsing, so now functions are enhanced during the expression tree building. This is a lower level api and uses the new FlowableAstFunctionCreator.


    • 🚦 In and out parameters can be defined for signal events, similar to the existing in and out parameter support for call activities. By defining in parameters for a signal boundary event for example, variables can be set on the process instance scope from the signal payload data.
    • ➕ Added support for triggerable service tasks with expressions.
    • ➕ Added support for event registry backed receive task and intermediate catch event.
    • ➕ Added support for JSON variables in web service tasks.
    • For ordering activity instances that are part of the same Flowable transaction, a transaction order value has been added, which is a basic numeric value starting with 1 and incremented with 1 for every new activity instance.


    • ➕ Added support for case instance migration with defining for which plan item definitions the state needs to be changed. This also includes moving new plan item definitions to available state if needed.
    • 👍 The Case task now supports in and out parameter mapping.


    • 👌 Support for Decision services and DRD (Decision Requirement Diagram) has been added to the DMN engine. This enables the usage of a hierarchy of decision tables to calculate the output of a decision service in multiple decision tables.


    • 💻 The UI Apps have been consolidated in one single Flowable UI App instead of 4 different applications. This makes the authentication and authorization logic less complex, makes the demo experience and installation experience easier and doesn't require you to switch between multiple browser tabs all the time. This means that now only 2 WAR files are provided in the Flowable Download, the Flowable UI app, that includes the Modeler, IDM, Admin and Task application together with the Flowable REST API and the second WAR file is the REST application that only includes the Flowable REST API. For more information you can read this blog post.
    • 👌 Support for OAuth2 authentication is added to the Flowable UI App, with Keycloak as an example implementation, see also this blog post.
    • ⚡️ Updated Docker images and Kubernetes Helm charts for the new Flowable UI app and with more configuration options. On the docker images the Spring boot applications are now started with a flowable user and not with the root user as before.


    • 🚀 In this release an upgrade to Spring Boot 2.3.4 and Spring 5.2.9 was done.
  • v6.5.0 Changes

    January 22, 2020


    • ➕ Added a new Event Registry engine which provides functionality to use Flowable in event driven architectures and has out-of-the-box support for JMS, Apache Kafka and RabbitMQ. Events can be received by BPMN start events, boundary events and triggerable send event tasks. In CMMN receiving events is supported by event listeners and for starting new case instances. Both engines also provide a send event task to send out an event to the event adapter implementation.
    • 🚀 To improve the support for running Flowable on multiple servers / nodes a new option was added to use a lock for creating the database schema and for executing the auto deployments at bootup. This ensures that when starting multiple servers / nodes at the same time, creating the database schema and doing the auto deployment of CMMN XML and BPMN XML files etc only happens on one server / node at the same time.
    • 👷 A new Batch service was added to support executing multiple jobs in one batch, where each job is a batch part. The first usage of the Batch service is the support for batch process instance migration, but the Batch service is designed to support many use cases.
    • 🌲 A first version of the Logging Session support has been added, which provides a full insight in the execution of case and process instances with all its child entities like tasks, variables, event subscriptions etc. This can be useful for debugging purpose, problem detection in production environments or for audit purposes.
    • 👍 The variable service has been enriched to support java.time.Instant, java.time.LocalDate and java.time.LocalDateTime as additional variable types. When using these Object types as a variable they will not be stored as serializable anymore, but with a timestamp value and when used transformed into the correct Object type.
    • 🛠 Various small bugfixes and improvements all around.


    • ➕ Added support for Event Registry start events to trigger starting a process instance with an incoming event.
    • 👍 An Event Registry boundary event has been added to support triggering a running process instance with an incoming event, with correlation and tenant detection support.
    • ➕ Added an Event Registry send event task to support sending events from a process instance and optionally listening for a response event using the triggerable task support.
    • 👍 The process instance migration support has been enhanced with supporting batch migration. Migrating a process definition with all its running instances to a new process definition is now possible with one batch, where each instance migration will be a batch part of a parent batch.
    • 👌 Support has been added for Kubernetes and HELM charts in specific. For more details see the Github documentation about this
    • 🔧 With historic information growing bigger over time, a way to cleaning this historic information was necessary. For this purpose a history cleaning job was added that can be configured to clean historic information older than a configured time period.
    • 👷 To support the history clean job, delete methods have been added to the history query interfaces to also allow to delete historic data with other criteria than just time period based parameters.
    • 👍 The mail task has been enhanced with support for sending content items as attachments.


    • ➕ Added support on a Case definition root level to listen for incoming events to start a new case instance.
    • 👍 An Event Registry event listener has been added to support triggering a running case instance with an incoming event, with correlation and tenant detection support.
    • ➕ Added an Event Registry send event task to support sending events from a case instance.
    • ➕ Added support to inject a Stage or a specific Task in a Stage instance of a running case instance. In this way a CMMN model can be enriched with new Stage or Task logic for a specific case instance.
    • 👍 Java Collection support has been added to repetition rules for plan items. This is similar to the Java Collection support for BPMN multi-instance constructs. A Java Collection variable or an expression can be used to define a repetition rule.
    • 👍 Enriched the support for evaluating if a Stage can be completed. On a plan item a parent completion rule can be defined with a type that matches the desired evaluation logic.
    • 📚 The support for expressions in a case instance has been extended. It's now possible to get a count value for all active plan item instances of a specific definition for example with the following expression: ${planItemInstances.definitionId('a').active().count()}. The CMMN documentation has been updated with all options possible.
    • 👍 A mail task has been added to the CMMN engine (similar as the one in the BPMN engine) with support for sending content items as attachments.


    • 🚀 A new engine was added with the regular deployment and deployment resources support to follow the pattern of the other engines.
    • 👌 Support for Event definitions which define the event payload, the channel definition to use, and the optional correlation parameters of an incoming or outgoing event. The BPMN start event, boundary event or send task or the CMMN Case element or event listener are linked to an Event definition based on a logical key, like it's also the case for, for example, BPMN call activities and CMMN case tasks.
    • 👌 Support for Channel definitions which define the source or target destination, with a specific adapter type (JMS, Kafka or RabbitMQ by default). Also an event key detection and an optional tenant id detection configuration can be provided. An Event definition links to a Channel definition based on the Channel logical key.
    • 👍 When using the Event Registry Spring module, there are 3 out-of-the-box adapters supported, JMS, Kafka and RabbitMQ.


    • ➕ Added support for DMN 1.2, which is the revision of the DMN 1.1 specification. The Collect hit policy logic was changed to not only consider unique outcome values but every outcome value for which the rule was hit. This was changed in the DMN 1.2 specification version.


    • 🚀 In this release an upgrade to Spring Boot 2.2.2 and Spring 5.2.2 was done. This is the last release where we have official support for Spring Boot 1.5.x and Spring 4.x. Starting from the next release this will not be officially supported anymore.
  • v6.4.2 Changes

    July 11, 2019



    • 👌 Support has been added for CockroachDB ( as an alternative DB option. A blog post with more details and getting started can be found here The full list of changes can be found here #1716
    • 👷 Extracted the event subscription logic from the BPMN engine into a service (similar to the variable and job service for example), so that event subscriptions can also be used from the CMMN engine and possibly other engines in the future.
    • ⚡️ The manual sql scripts that can be found in the distro download are updated to include convenient scripts that will update and create the engines in one sql script.
    • 🛠 Various small bugfixes and improvements all around.


    • ➕ Added support for BPMN escalation events.


    • ➕ Added support to listen to signal events in a CMMN case model. This enables more options to interact from a BPMN process instance with a CMMN case instance.
    • ➕ Added 'available condition' to CMMN event listeners (e.g. user or timer event listener) to guard precisely when an event listener becomes available. See the documentation for examples.
  • v6.4.1 Changes

    January 14, 2019



    • 🔧 A new table has been added to keep track of all changes that happen with a user / human task. A HistoricTaskLogEntry is created when the assignee of a task changes, or the owner, or for example the due date. By default the user / human task logging is disabled, with the enableHistoricTaskLogging property in the process or cmmn engine configuration, the user / human task logging can be enabled.
    • 🔧 A new runtime and historic entity link table has been added to store the relationship between parent entities and all children. This means for example that when a parent process instance has a sub process, and the sub process has a user task, that for the user task two entity links are created, one between the parent process instance and the user task, and another with the sub process instance and the user task. The same is true when a case instance starts a process instance via the CMMN Process Task for example. This makes it possible to get all child tasks for a parent process instance for example. By default, storing entity links is not enabled in the Flowable engines, but using the enableEntityLinks property in the process engine configuration and/or CMMN engine configuration this can be enabled.
    • 👌 Support for DMN 1.2 (, still in beta). This is foremost a XSD and parse support.
    • 🛠 Various small bugfixes and improvements all around.


    • A runtime activity instance table has been added to allow you to query for the activity instances that have been executed for a running process instance without needing to go to the history tables. This includes active and completed activity instances. When a process instance is completed or terminated, the runtime activity instance will be deleted and only available in the historic activity instance table.
    • The sequence flows that are taken are now also stored as part of the runtime and historic activity instance data. This provides a more complete audit history of the process instance execution.
    • 👍 The process instance migration feature has been extended with logic to allow migrating process instances with call activities and support moving the current active state from a parent process instance to a sub process instance and vice versa.
    • The admin app now contains a migrate process instance button in the process instance view, that allows for simple migration cases to define the activity mappings and execute the migration.
    • 0️⃣ Multi tenancy improvements to support lookups for process, case, form, and decision table definitions within the tenant, but also allow for a fallback lookup in a default tenant of choice. This makes it possible to share common definitions in a default tenant, and only use tenant specific definitions when necessary.
    • 🛰 REST services have been added to make it easier to fetch a form definition associated with a user task or a start event. Also, completing a form for a user task or starting a process instance with a form is now a lot easier via REST. Getting a BPMN user task form can be done via GET process-api/runtime/tasks/{taskId}/form for example, and completing a user task can be done via POST process-api/runtime/tasks/{taskId} as it was possible already before. But now the payload can contain a form definition id and outcome value to complete the user task with a form.
    • 🌐 Using transient variables in the BPMN web service task instead of using process variables for values that should not be persisted in the variables table.


    • Plan item instances are now stored in the runtime tables until the case instance is finished. This allows to query the state of a case instance without having to use the historical api's or data.
    • 🚚 The engine will automatically detect when event listeners (user, generic or timer) are not useful anymore and remove the event listener instances.
    • ➕ Addition of a new 'trigger mode' called "on event" for event resolving in sentries that allows to scope the event evaluation to that evaluation cycle only (versus with memory as is the default). This enables advanced models where events (and consequentially the related sentries) only should be evaluated at the moment they happen.
    • ➕ Addition of the task and plan item lifecycle listener, similar to task and execution listeners in BPMN.
    • 👀 To support modeling arbitrary user or automated actions in CMMN, it is now possible to use a 'generic event listeners'. This event listener behaves like a user event listener, but can be triggered programmatically through an API (see the CmmnRuntimeService).
    • It is now possible to make a user or generic event listeners repeatable, which allows a more natural way of modeling cases where a certain event happens multiple times.
    • Greatly improved cross border resolving of sentry dependencies (across multiple and potentially nested stages).
    • 👍 A first version of case instance change state has been added to the Flowable CMMN Engine. In the CmmnRuntimeService you can now use the createChangePlanItemStateBuilder to define and execute the case instance change state logic. This first version supports changing state focused on human tasks. In the next version more support will be added for more complex cases.
    • 🛰 REST services have been added to make it easier to fetch a form definition associated with a human task or a plan model. Also, completing a form for a human task or starting a case instance with a form is now a lot easier via REST. Getting a CMMN human task form can be done via GET cmmn-api/cmmn-runtime/tasks/{taskId}/form for example, and completing a human task can be done via POST cmmn-api/runtime/tasks/{taskId} as it was possible already before. But now the payload can contain a form definition id and outcome value to complete the user task with a form.
  • v6.4.0 Changes

    October 02, 2018

    FlowFest 2018 Developer Conference
    Join us for the first Flowable Open Source Developer Conference in Barcelona. You can register here: If you want to present a session about Flowable please get in contact with us, for example via the Flowable Forums


    • 👍 A first version of process instance migration has been added to the Flowable BPMN Engine. In the RuntimeService you can now use the createProcessInstanceMigrationBuilder to define and execute the process instance migration. This first version supports migrating process instances with wait states, embedded (event) sub processes and boundary events. In the next version more support will be added for more complex cases like parallel and inclusive gateways, multi-instance activities and call activities.
    • ✅ Expression support have been added for the BPMN and CMMN engines to make it easier to work with variables and in specific variables that may not have been initialized yet. When you reference a variable in an expression like ${customerNumber > 40} and there is no customerNumber variable yet, an exception would be thrown. With the variable expression support this can be handled without an exception with ${variables:getOrDefault(customerNumber, 0) > 0}. A similar expression is possible for strings with ${variables:get(customerName) == "test"}. The user guide describes the full set of available variable expressions.
    • 🚀 A first version with support for MongoDB persistence has been added. The MongoDB module is available from a separate Git repository at The MongoDB module is made available in a separate repository, so that it can be released in a different pace than the full Flowable Engine releases. The support of MongoDB already includes most BPMN constructs, but in the coming releases it will be extended to be on par with the relational database support.
    • ⬆️ Upgrade to Spring 5.x for all the integration modules using Spring.
    • ➕ Added plan item lifecycle listener to the CMMN engine, to allow for listening to plan item instance state changes.
    • 👍 In the Task app support for activating manual plan items and triggering user event listeners has been added.
    • ➕ Added support for JUnit 5.
    • 👌 Support for using java.time.Duration variables and expressions for Timer durations.
    • 🌐 Chinese translation has been added for the UI apps.
    • 🛠 Various small bugfixes and improvements all around.

    ⬆️ Upgrade notes

    Idm Engine SpringEncoder

    🔒 The deprecated constructor from SpringEncoder that accepted has been removed

    Custom IdGenerator using a Bean in Spring Boot

    0️⃣ It is now possible to define the custom IdGenerator for the Flowable Process engine, by creating a bean of type IdGenerator. If no bean is provided the StrongUuidGenerator will be used. If there is a bean qualified with @Processthen this one would be used, otherwise a unique global one would be used. If there are more global beans then the default StrongUuidGenerator will be used.

    FlowableFunctionDelegate changes

    🚚 The method functionClass has been removed from the org.flowable.common.engine.api.delegate.FlowableFunctionDelegateinterface. This doesn't change anything with regards to adding custom functions to expressions: returning the right Method in functionMethod() is enough.

    The tomcat-flowable zip download is only intended for quick demos as it uses the H2 database.

  • v6.3.1 Changes

    May 22, 2018


    • 🚀 Introduction of an app engine, so apps are now a first class citizen and the process engine is not misused any more to handle app deployments. When starting the Flowable Task application all app deployments are automatically migrated to the new app engine.
    • ➕ Added async history support to the CMMN engine.
    • ➕ Added more history information to the CMMN engine with historic plan items.
    • 👌 Improved the Spring Boot support and upgraded to Spring Boot 2.0.2.
    • ✨ Enhanced debugger in the Flowable Task application to evaluate expressions and scripts.
    • 👷 Made the job service more generic with the scope type property to improve the possibility to run different job handlers for different job types.
    • 🛠 Various small bugfixes all around.

    Community contributors

    • Pascal Schumacher (PascalSchumacher)
    • Amina Zoheir (AminaZoheir)
    • Toni (ttonl)
    • David Malkovsky (dbmalkovsky)
    • Michael Lippens (mlippens)

    ⬆️ Upgrade notes

    📦 Package renaming

    📦 To make the Flowable modules compatible with OSGi and Java 9 modules some package renaming was needed to prevent clashes. The renaming has been done according to this pattern org.flowable.engine.common -> org.flowable.common.engine

    StrongUuidGenerator usage with Spring Boot

    🔧 The Spring Boot process auto configuration now uses the StrongUuidGenerator. In case you were overwriting the default one you can remove that. In case you want to keep using the DbIdGenerator, then just add the following bean to your configuration:

        public EngineConfigurationConfigurer<SpringProcessEngineConfiguration> processEngineDbIdGeneratorConfigurer() {
            return engineConfiguration -> engineConfiguration.setIdGenerator(new DbIdGenerator());

    0️⃣ The default values of the DbIdGenerator would be filled in during the creation of the Process Engine.


    🔧 The default IdmEngineConfigurator and SpringIdmEngineConfigurator have been moved from org.flowable.spring.configurator to org.flowable.idm.engine.configurator and org.flowable.idm.spring.configurator respectively. In case you have used them please replace your imports.

    📦 Async history classes package change

    📦 The async history classes have been moved from the process engine module to the job service, to make them available for other components. Generally, the packages now have job.service added to make this clear.

    • 📦 Classes with regards to async history collection and execution (AbstractAsyncHistoryJobHandler, AsyncHistoryJobHandler, AsyncHistoryListener, AsyncHistorySessionFactory, AsyncHistorySession, DefaultAsyncHistoryJobProducer, HistoryJsonTransformer) in the org.flowable.engine.impl.history.async have been moved to the org.flowable.job.service.impl.history.async package.
    • 📦 Classes related to executing async jobs using a message queue (most notably AsyncHistoryJobMessageHandler and AsyncHistoryJobMessageReceiver) have been moved from the org.flowable.engine.impl.asyncexecutor.message to the org.flowable.job.service.impl.asyncexecutor.message package.
    • 📦 Similarly, for executing async history jobs using a message queue: the classes in the package org.flowable.engine.impl.history.async.message are now found in the org.flowable.job.service.impl.history.async.message package.

    ⚡️ Updating the imports is sufficient when upgrading.

  • v6.3.0 Changes

    April 04, 2018

    🚀 Release Notes - Flowable - 6.3.0

    🚀 Flowable 6.3.0 has turned out to be a big release with many new features (and even more fixes). Many thanks to all the community contributers that participated in the release
    and a special shout-out to Pascal Schumacher, Zach Visagie, Robert Hafner, Christophe Deneux and Seif El Deen Khaled


    Note: Flowable now requires JDK 8 as a minimum version!


    ⚡️ The Spring Boot starters have all been updated to version 2.0. There are now starters available for each engine (BPMN, CMMN and DMN).
    📚 Check the completely revised documentation for more details!

    • 👌 Support and fixes for running various modules on JDK 9 (the engines themselves already ran on JDK 9)
    • ⚡️ Updated all 3rd-party libraries to latest versions
    • 🔧 The REST app can now be configured to use privileges, instead of all users being able to make REST calls.


    • 🐎 Performance enhancements with great results. Read all about it here:
    • 👍 Dynamic task and subprocess injection into running process instances is now fully supported and out of experimental state
    • 👍 Allow the configuration of history on individual process definitions, overriding the engine default setting
    • 🔧 Introduce the 'triggerable' service task: a service task that provides configurable service calls that are executed externally and call the engine when done. The implementation is guaranteed to be correct with regards to the transactional behavior of the engine.
    • 👌 Support for a transaction-lifecycle based event listener
    • 👌 Support for 'sameDeployment' when looking up the called process definition for a call activity
    • 👍 HTTP task: support for storing response variables transiently
    • 👍 Multi instance: support for Iterable when resolving a collection (e.g. ArrayNode)


    • 👍 REST API support for all CMMN services and operations
    • 👌 Support for asynchronous service tasks
    • 👌 Support for manual activation rules and enabling/manually starting plan items through the runtime service
    • 👌 Support for required rule
    • 👌 Support for autocomplete
    • 👌 Support for completion neutral
    • A Script task type has been added
    • 👌 Support for User event listeners
    • 👌 Support for viewing and managing CMMN date in the Admin app


    • 👌 Support for collection expressions, such as IN and NOT IN
    • 👌 Improved decision table editor user experience to make it easier to add JUEL expressions in specific rules
    • 👌 Support for viewing and managing decision executions in the Admin app


    • 📚 All apps have been rewritten to use Spring Boot 2.0. All apps now use one property file for configuration. Please check the documentation, as many new configuration options are available (with backwards compatibility for old properties).
    • 👌 Support for expressions in the options fields, including dropdown, radio and hyperlink fields
    • 👌 Support for a password fields in the form editor and runtime
    • 👍 Multi-tenancy support in the Modeler by defining the active tenant in the Modeler property file

    ⬆️ Upgrade notes

    🚚 To remove duplicate code, some more logic has been added to the common modules, such as flowable-engine-common and flowable-common-rest. For example, the scripting engine has been moved to the flowable-engine-common module so it can be used by both the BPMN and the CMMN engine.
    📦 If you are using Flowable internal classes then it is possible that some package changes to the common modules are required. Most of this should be automatically handled by your IDE.

    🔧 All Flowable apps (IDM, Modeler, Task, Admin and REST) now read their configuration from the file, which is included in each WAR file in the META-INF/flowable-app folder.
    Consequently, a single, shared can be placed on the classpath for all apps.
    All property files (e.g. for the REST app) are still read and work in a backwards-compatible way.

    0️⃣ The default way user credentials are authenticated and verified when calling the Flowable REST API has changed. A user now needs to have the access-rest-api privilege (before, any valid credentials could be used). An admin user can be given this privilege by setting the and properties in the file. On start-up, the admin user will be created if it doesn't exist, or it will be given the access-rest-api privilege. This admin user can then give other users this privilige using the Flowable IDM app or through a REST call (doing an HTTP post to privileges/{privilegeId}/users with the userId in the body).

    🔧 By default, all Flowable apps (IDM, Modeler, Task, Admin and REST) are configured to use an in-memory H2 database that is persisted in the user home folder, which is shared between all apps by default. Previously, each app had its own in-memory H2 database.

    🔒 Due to upgrading to the latest Spring Security dependencies for handling the authentication for all the Flowable apps, users can get a "cookie theft exception" when accessing the apps with a cookie from a previous version that is still present in the browser.
    The reason for this is that Spring Security has changed the way cookie tokens are hashed. A hard refresh or relogin fixes this by generating a new cookie. If you don't want to force your users to do this, you can delete all rows from the ACT_ID_TOKEN database table. This will invalidate all old cookies and all users will have to login again.

  • v6.2.1 Changes

    December 11, 2017


    • 👍 Lots of additions to the CMMN 1.1 Engine, including timer support, repetition support, DMN and HTTP task support and variable query support.
    • 📚 Rest documentation is now also generated based on the Swagger definitions to ensure it's always in sync with the REST controller code.
    • 👌 Improved support of ChangeActivityStateBuilder to move an execution in a process instance to another activity that's part of the process definition.
    • ✨ Enhanced the CMMN Modeler palette with timer event listeners, DMN and HTTP tasks and additional properties like timer expressions and repetition expressions.
    • 👌 Improved support of CMMN in the Flowable Task app.
    • 🛠 Various small bugfixes all around.

    Community contributors

    • Pascal Schumacher (PascalSchumacher)
    • Stijn de Pestel (stijndepestel)
    • Robert Hafner (roberthafner)
    • Xin Wang (dram)
    • David Malkovsky (dbmalkovsky)
    • Michael Lippens (mlippens)
    • Marco van Zwetselaar (zwets)
    • Yanming Zhou (quaff)
    • Christophe Deneux (cdeneux)

    ⬆️ Upgrade notes

    🚀 To harmonize the deployers between the BPMN and CMMN engine the ProcessEngineConfigurator interface has been renamed to EngineConfigurator and moved to the flowable-engine-common module.
    In addition a new flowable-spring-common module has been added to shared common Spring classes between the BPMN and CMMN spring modules.

  • v6.2.0 Changes

    October 13, 2017


    • 🚀 Introduction of a new CMMN 1.1 Engine. This provides an implementation of the CMMN 1.1 OMG standard ( A lot of effort has been put in this new Engine, and it uses a new set of database tables optimized for CMMN execution. We've added a new CMMN user guide to help you getting started. Note that since this is a first release, the CMMN Engine is marked as an experimental feature and missing features like timers and HTTP and Decision tasks will be added in next releases.
    • ➕ Added a CMMN editor to the Flowable Modeler app.
    • ➕ Added support for CMMN cases in the Flowable Task app.
    • 🚀 The BPMN and CMMN engine share a number of common services like Tasks, Variables, Identity links and Jobs. Therefore these services are extracted from the core BPMN engine module and new modules have been created for each one of these services. The BPMN and CMMN engines make use of these services to provide for example Task and Variable support. With this approach Flowable is very flexible in the deployment model. You can run only the BPMN Engine, only the CMMN Engine or run them both together without any issues.
    • 🛠 Various small bugfixes all around.

    Community contributors

    David Malkovsky (dbmalkovsky)
    Filip Hrisafov (filiphr)
    Robert Hafner (roberthafner)
    Marco van Zwetselaar (zwets)
    Lori Small (lsmall)
    Michael Lippens (mlippens)

    ⬆️ Upgrade notes

    🚀 Because of the extraction of the Task, Variable, Identity Link and Job services, we had to change the package names of the classes used in these modules. This means that for example TaskQuery and Job Query have been moved to a new package. This was done to adhere to OSGi standards and to be ready for the new Java 9 version. This however does mean that you run into some compilation issues while migrating to version 6.2.0. We always try to prevent this as much as we can, but due to the new modules this wasn't possible in this release. The common naming pattern of these new service is org.flowable.{servicename}.api for the API module and org.flowable.{servicename}.service for the service implementation module. So org.flowable.task.api and org.flowable.task.service for example.

  • v6.1.2 Changes

    July 25, 2017

    🐛 Bug fix release:

    🚀 Thanks to whee we found out that there's an issue with the release 6.1.1 when running it without an Internet connection This was fixed with the following commit 7338015. Although an Internet connection is often available, we decided to do a bug fix release to prevent people from running into this issue.