Flowable roadmap

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.

Features and refactorings

• Finalize and release 6.0.0 final
• Update documentation for 6.0.0
• Update migration guide for 6.0.0

6.1.0 ideas

• 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.
• Undo functionality: allow to 'go back' in a process instance to a previous state via an API call.
• Improve and expand event subprocess support.
• Implement transaction lifecycle support for event listeners (https://github.com/flowable/flowable-engine/issues/11)
• CountingTask: similar to the CountingExecution (https://g