# Operaton 3.0 scope

**URL:** <https://forum.operaton.org/t/operaton-3-0-scope/446>\
**Category:** Development\
**Created:** [September 18, 2026, 8:15am UTC](https://forum.operaton.org/t/operaton-3-0-scope/446 "2026-09-18T08:15:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![kthoms](https://forum.operaton.org/user_avatar/forum.operaton.org/kthoms/32/33_2.png) [@kthoms](https://forum.operaton.org/u/kthoms)\
**Post date:** [September 18, 2026, 8:15am UTC](https://forum.operaton.org/t/operaton-3-0-scope/446/1 "2026-09-18T08:15:56Z")

</div>

Next month, Operaton 2.2 will be finally released. The Operaton team is building some interesting stuff which will mark a new milestone in Operaton’s history and will make it worth to deliver a version 3.0. However, we decided that the April 2027 release will be a version 2.3, and making Operaton 3.0 for October 2027.

Some interesting features will be already available in 2.2 and 2.3, but opt-in. Anyway, I would like to collect and discuss by this thread what can be expected to be delivered.

The following topics are on the list for Operaton 3.0 in October 2027:

- The new web applications become default
- The current legacy web applications will be dropped (TBD: or kept as opt-in)
- The minimal Java version to execute Operaton is raised to Java 21 (TBD: or 25 as 25 is LTS and 21 goes end of support already in Sep 2028)
- API marked with `@Deprecated(forRemoval=true)`will be removed
- Implementation of the Outbox Pattern for history data and API to allow to store history in separate databases or other storage
- Implementation of Ad-hoc subprocesses

This list will be extended and eventually coined into work items.

What is on your list that has to be considered for 3.0?