-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Flowable 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.
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.
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. Take a look at our Release History to see the type of changes that have happened in the past.
-
First version of process instance migration
-
JUnit 5 and Jupiter refactoring
-
Proof of concept of running Flowable on MongoDB
-
Second version of process instance migration covering more advanced use cases
-
CMMN Engine improved coverage and other new features
-
Add support for DMN 1.2 XML files in the DMN engine
-
Added more support for handling default tenant and tenant specific process / case / decision definitions
-
Enhanced version of process instance migration
-
Out-of-the-box support for message queues (including correlation)
-
Heatmaps to show the process path that is taken most often
-
Kubernetes support
- DMN DRD