What is coming next?
6.4.1 release (beginning December)
CMMN Engine improvements
Plan item lifecycle listeners, event listeners, condition
evaluation flexibility, parse handlers etc
Support for call activity sub process and parent process
activity migration, variable definition
Process instance migration improvements
Make it unnecessary to go to historic data when getting
activity info for a running process instance
Activity instance runtime data
6.5.0 release (t.b.d)
DMN DRD
Support for complex decisions
Have multiple layers and dependencies to calculate the
outcome(s) for a decision
DMN DRD (2)
DRD editor in Flowable Modeler
New model type and DMN decision tasks in BPMN and
CMMN can be linked to DRD
DRD runtime execution in DMN engine
Calculate DRD elements in correct order and return the
decision outcome at the end
Process instance migration v1
Support for doing simple to complex migrations
Add more use cases for process instance migration, also
based on community feedback
Support migrating each process instance of a process definition
version to a new version in batch (using job executor)
Batch migration support
Support migration running process instances to the newly
deployed process definition in batch
Migration on process deployment
Out-of-the-box support for message queues
Remove the need for Camel and Mule for JMS messages
Camel and Mule are powerful frameworks when implementing
integration use cases, but JMS messages should be handled directly
with a Flowable Module as well
Make it easy to correlate incoming message to running process and
case instances and add correlation info to outgoing messages
Support correlation
Support Spring message handling when running Flowable
in a Spring context
Provide Spring support
Stable version of MongoDB BPMN Engine
Enhance current implementation with more coverage
Current foundation is already more than a proof of concept, but
enhance it with more test coverage
Is MongoDB support a nice deliverable for the community? We
welcome any feedback.
Welcome community feedback and help
Kubernetes support
Add Kubernetes support to Flowable deliverables
Similar to the Docker images that are already provided, there will also
be support for Kubernetes in specific
As part of an internal Flowable Hackaton, already a prototype with
Kubernetes support was implemented
Prototype already available from Flowable hackaton
Heatmap support in Flowable Task App
Provide visual information on duration and frequency
Upcoming book?
In conversation with Manning
Covering CMMN, BPMN and DMN
Using Flowable as the platform to show examples
Flowable is community focused
Feedback is very much appreciated
We welcome feedback via the forums to discuss possible new
features, potential bugs etc.
Input for the roadmap can be provided at any time and we value
feature requests via the community
The roadmap is community focused
Adding unit tests, writing sections of documentation, small features, or
bigger features that we can work on together, everything is
appreciated and valued by the rest of the community
Contributions can be done at various levels
Any feedback / questions / remarks ?
Flowable What´s coming next?

Flowable What´s coming next?

  • 1.
  • 2.
    6.4.1 release (beginningDecember) CMMN Engine improvements Plan item lifecycle listeners, event listeners, condition evaluation flexibility, parse handlers etc Support for call activity sub process and parent process activity migration, variable definition Process instance migration improvements Make it unnecessary to go to historic data when getting activity info for a running process instance Activity instance runtime data
  • 3.
  • 4.
    DMN DRD Support forcomplex decisions Have multiple layers and dependencies to calculate the outcome(s) for a decision
  • 5.
    DMN DRD (2) DRDeditor in Flowable Modeler New model type and DMN decision tasks in BPMN and CMMN can be linked to DRD DRD runtime execution in DMN engine Calculate DRD elements in correct order and return the decision outcome at the end
  • 6.
    Process instance migrationv1 Support for doing simple to complex migrations Add more use cases for process instance migration, also based on community feedback Support migrating each process instance of a process definition version to a new version in batch (using job executor) Batch migration support Support migration running process instances to the newly deployed process definition in batch Migration on process deployment
  • 7.
    Out-of-the-box support formessage queues Remove the need for Camel and Mule for JMS messages Camel and Mule are powerful frameworks when implementing integration use cases, but JMS messages should be handled directly with a Flowable Module as well Make it easy to correlate incoming message to running process and case instances and add correlation info to outgoing messages Support correlation Support Spring message handling when running Flowable in a Spring context Provide Spring support
  • 8.
    Stable version ofMongoDB BPMN Engine Enhance current implementation with more coverage Current foundation is already more than a proof of concept, but enhance it with more test coverage Is MongoDB support a nice deliverable for the community? We welcome any feedback. Welcome community feedback and help
  • 9.
    Kubernetes support Add Kubernetessupport to Flowable deliverables Similar to the Docker images that are already provided, there will also be support for Kubernetes in specific As part of an internal Flowable Hackaton, already a prototype with Kubernetes support was implemented Prototype already available from Flowable hackaton
  • 10.
    Heatmap support inFlowable Task App Provide visual information on duration and frequency
  • 11.
    Upcoming book? In conversationwith Manning Covering CMMN, BPMN and DMN Using Flowable as the platform to show examples
  • 12.
    Flowable is communityfocused Feedback is very much appreciated We welcome feedback via the forums to discuss possible new features, potential bugs etc. Input for the roadmap can be provided at any time and we value feature requests via the community The roadmap is community focused Adding unit tests, writing sections of documentation, small features, or bigger features that we can work on together, everything is appreciated and valued by the rest of the community Contributions can be done at various levels
  • 13.
    Any feedback /questions / remarks ?