Operaton 2.1.4 and 2.2.0-M3 released

Announcements
1

We’ve published a new maintenance release, Operaton 2.1.4, alongside an early milestone preview of the upcoming 2.2 line, Operaton 2.2.0-M3.

Operaton 2.1.4 — recommended update

2.1.4 bumps the Spring Boot baseline from 4.0.7 to 4.0.8 and Spring Framework from 7.0.8 to 7.0.9, picking up the latest fixes on their maintenance lines. There are no database schema changes and no REST API changes, so upgrading
from 2.1.x is a drop-in replacement. We recommend all 2.1.x users update.

Operaton 2.2.0-M3 — milestone preview

This milestone brings two preview features we’d like feedback on before they land in a final release:

New web applications (webapps-neo). A new, Preact-based implementation of the web apps, integrated alongside the existing legacy webapps. Includes a first administrator setup screen, plus follow-up fixes for packaging and a handful of security defects found reviewing it against a real build.

SKIP LOCKED job acquisition. The job executor can use FOR UPDATE SKIP LOCKED so parallel nodes skip rows already locked by another node instead of blocking — reduces contention in clustered setups. Opt-in via ProcessEngineConfiguration#setJobExecutorAcquireWithSkipLocked(true) (or operaton.bpm.job-executor-acquire-with-skip-locked: true in Spring Boot). Config/API may still change before the final release — try it and let us know how it goes.

Also in this milestone: SpringBoot 4.1.1, WildFly 41, Quarkus 3.33.3.1.

The Operaton Team

1 Like
2

Hello @kthoms ,

Sorry to write here (definitely not the correct location).

I am currently blocked from replying on the Liquibase migration from camunda - #17 by Rares27 thread since there are a max of 3 messages that can be sent out, can you please help me send the information I promised to a proper thread? (I have it already prepared). Any direction is more than welcome.

Thank you!

3

I think the forum is still the right place for this. An issue on the code repo is IMO not the right place. Just open a new thread. Users can then find your findings.

If you like to add the information directly to the documentation, open a PR for the documentation repository. The database schema doc might be an appropriate place.

Sorry that you faced the 3-messages-restriction. I will ask the forum admin if he could raise the limit.

4

Hello, thank you for all the information.

Sorry, I don’t really have time right now to do a PR / change the docs. I have created a topic for future references, hope that helps.

Thank you! Liquibase migration from Camunda, already on version 7.24.0

(these posts can be removed)