Skip to content

Flowable roadmap

Jump to bottom
Paul Holmes-Higgin edited this page May 29, 2017 · 29 revisions

Flowable Engine Roadmap

How should I use this roadmap?

This is a description of features and tasks that the project has decided to prioritize. You can use this as a reference point to understand where the project is going, and also decide how you may be able to help, or understand any potential conflict with longer terms plans.

Just because a feature isn't listed here doesn't mean that a Pull Request will be refused or ignored. We always jump with joy when someone contributes code for new cool features we hadn't thought about or prioritized.

How can I help?

You can help by giving us your input on the items: use cases, edge case, and of course, code. Before doing a Pull Request for a feature, it's always best to discuss it on the Forums. This makes sure we're ready for it and can provide any guidance. Find out more on how you can contribute.

How can I change the roadmap?

Talk to us on the Forums. Help us understand why your ideas on priorities or features are right. Talk to other community members through the forums - the more people that add their voices to what is good or cool to do, the better. We want Flowable to be as widely used as possible.

6.1.0 (Mid June)

  • Asynchronous history: currently, historical data is written in the same transaction as the runtime data. Benchmark profiling has shown that, in many use cases, a significant amount of time is spent processing and persisting the historical data whilst the user has to wait for the transaction to finish. By making this asynchronous, a performance improvement is expected and there are better options to use a NoSQL database or Elasticsearch to store historic data.

  • New decision table editor based on Handsontable (https://handsontable.com/). This will improve the usability of the decision table editor and will make it easier to create more complex DMN rules.

  • REST activity behaviour. A community contribution to add a REST client as a task type to the Flowable Engine. This enables users to easily do REST calls from a process instance and store the result in process variables.

  • DMN Engine audit persistence. Make it configurable to store rule execution audit data so it will be possible to get historic information of decision tables that have been executed and see why a specific output was produced.

6.2.0 (t.b.d.)

  • CMMN 1.1 Engine. The OMG CMMN standard (http://www.omg.org/spec/CMMN/1.1) will be supported by a new Flowable Engine. Flowable users will have a choice to use BPMN or CMMN process definitions depending on their specific use cases. A CMMN 1.1 Modeler will be part of this CMMN addition. The task and admin application also need to be changed to add support for the new CMMN Engine.

  • Add support for DMN DRD (Decision Requirements Diagram). To extend the capabilities of the Flowable DMN Engine, support for DRDs will be added.

  • Move active state of a process instance to another state. Allow moving an active token in a process instance to another activity (backward or forward).

6.3.0 (t.b.d.)

  • Dynamic sub process and task support. Add the ability to inject sub processes or tasks into a running process instance. This will change the process definition for one specific process instance and it will not be used for other process instances.

  • Process instance migrations. Based on the feature to move the active state of a process instance to another state Flowable will add support for advanced process instance migrations.

Clone this wiki locally