Flowable
Business process management and workflow engine for Java
Flowable ships once a year and spends it on the Java platform, not on the process engine.
◆Recent moves
- 5mo ago
Spring Boot 4 and Jackson 3 required; JUnit 4 support removed
⚡ SPARKThe 2026 major, and a forced migration: Spring Boot 3 support ends, Jackson 3 becomes the default JSON library, and JUnit 3 and 4 testing support is removed. Consistent with the pattern where each Flowable major is a platform jump carrying a modest set of engine features.
View source ↗ - 11mo ago
Async variables, skip expressions and broader query filters
A query- and variable-focused release: asynchronous variable setting for BPMN and CMMN, skip expressions on receive and send-event tasks, local variables during case migration, and several new query filters. Refinements aimed squarely at large existing deployments rather than new adopters.
View source ↗ - 1y ago
Liquibase dropped from App, CMMN, DMN and event registry engines
Liquibase is removed from the App, CMMN, DMN and event registry engines in favour of manual SQL files, aligning them with the engines that had already made that move, plus SQL Server nvarchar indexing improvements. Schema-management consolidation, the kind of work that only matters at operational scale.
View source ↗ - 2y ago
Bug-fix release adding async leave and LocalDate timers
A bug-fix release that also adds async leave, string-collection mail recipients and LocalDate timer expressions. Maintenance on the 6.x line running alongside the 7.x platform work.
View source ↗ - 2y ago
Spring Boot 3.1.6 support and dynamic event subscriptions
A minor release adding Spring Boot 3.1.6 support, dynamically created event subscriptions for starting cases or processes, and inbound channel filter classes. Incremental extension of the event registry between majors.
View source ↗ - 2y ago
Java 17 rebase; UI apps, content and form engines removed
⚡ SPARKThe release that defined Flowable's current shape: a Spring Boot 3, Spring 6 and Java 17 rebase that also narrowed the product to the BPMN, CMMN, DMN and event registry engines plus REST APIs. The scope reduction here is why later releases read as engine-only.
View source ↗