Product roadmap

Upcoming releases

Orbeon Forms 2026.1

For Orbeon Forms 2026.1, we are planning to work on the following items:

• Form Builder user interface:

  • Improved actions editor: We would like to improve the current editor to progressively support more of the action syntax. Actions are powerful, but not always easy to use, and we want to make them more accessible to users of all levels.

  • Workflow editor: This has been a long-standing item, and we would like to make it possible to edit simple workflows in the Form Builder UI.

  • More user-friendly formulas: See #2282.

• Form Runner user interface:

  • Styles/theme editor: With 2025.1, we have refactored the CSS to use variables. The next step will be to expose the UI configuration at a higher level in the Form Runner UI.

  • Properties editor: Similarly, we now have a powerful API to define configuration properties. We'd like to add a UI to edit those properties so that administrators, form authors, and end users alike can change settings without having to edit server-side configuration files.

• Additional form controls:

  • Improved phone number control: See also #6734.

• Other

  • Additional demo forms: we plan to continue creating more demo forms to show the capabilities of Orbeon Forms.

  • Additional integrations: A candidate is to add support for Google Sheets as a data destination, which would be a great addition to the existing support for databases and HTTP services.

See also the tentative 2026.1 items for details.

As usual, we also are considering:

• low-hanging fruits

• dogfood items

• maintenance items

• spare time items

• top issues

• top RFEs

Please remember that the following schedule is a plan, not a promise:

• 2026-12: tentative release date

Past releases

See the Orbeon Forms release history.

Release strategy

• How often do we release? Since 2020 we have switched to one major release per year with point releases as needed.

• What do releases contain? Releases address both new features and bug-fixes. Point-releases (2020.1.1, 2020.1.2, etc.) essentially contain bug-fixes and sometimes very small features. They are done only when necessary, and only for the PE version of the product. Bigger features are left to the major releases (2019.1, 2019.2, 2020.1, 2021.1, etc.), and we strive to do those on a regular schedule.

Planning strategy

• How far ahead do we plan? Once we've published a major release, we do the planning for the following one. You can see the future releases listed on the open projects page, and from there, see what has been planned for the next release. We don't plan feature or bugs to be included in releases beyond the very next release, so we can react faster to our customers needs, deciding for every release what will best serve our customers.

• How do we decide what improvements to include in a release? A fair amount of the new features we develop are designed in collaboration with our customers, and sponsored by customers through a Dev Support plan. Other features are added to better serve existing and future users of the product. And last, but not least, for every release we strive to do work in each one of the development tracks outlined below.

Development tracks

These are general development tracks which we consider from release to release:

• Mobile – Better support responsive design, and the ability to run our form engine on the client to enable offline support and native apps.

• Performance – While Orbeon Forms has been proven to be able to sustain a fair amount of load, we 're always striving to improve the product in that regard, including reducing memory usage, reducing load time, and improving performance on MySQL.

• Architecture and maintenance – Like any project, Orbeon Forms has some technical debt. It is not possible to remove all of it at once, but, like garbage collection, we want improve the code base incrementally. In addition, we want to look to the future to use the best possible languages and frameworks. This includes: modularizing of the code, taking care of issues flagged as "maintenance", drop old frameworks and adopt new ones (get rid of YUI, use Scala.js), and do more automated testing (we have almost 800 tests, but need more).

• Integration and workflow – We want to make it easier to embed forms, make it easier to use HTTP/DB services for validation, allow forms to be imported/exported with dependencies, better document standard use cases / workflows, make integration with external systems/workflows simpler, include built-in Basic workflow, and more.

• Form Builder modernization – We want to push the envelope and keep improving the usability of Form Builder.

What's in a release

For each release we would like to:

• have bug-fixes

• have at least one new feature (which can be small)

• book one day of work on documentation tasks

• pick one maintenance task (build system, refactoring, …)

The idea is, as some of those tasks are large, to do it incrementally when possible, so that some progress is made.