The question came up, here is a write up. Feel free to ask any clarifying questions.
Operaton Web Apps Status 2026-04
An overview on what works, is missing and needs testing from real users.
Abstract
Many features are added, but details are missing.
The most important thing would be to test the new web apps with a realistic back-end load. Currently we have a node server, which generates instances of mock process definitions on. With those we can simulate high load.
Additionally, we should start collection user feedback on the UI/UX. This includes the feedback of long time Camunda 7 users and user testing where we look at how the apps are used (e.g. with screen sharing).
The work focus on the web apps are currently the “meta features” like authentication and testing different deployment options. The planned next steps are testing and user feedback before adding more pages. (As long as no other needs arise first from the community or clients)
Pages
Tasks
Most of the features work and are tested.
We implemented a renderer for form-js JSON forms to give users a way to use the form editor. The JSON form is also easier to implement in other front-ends either with the form-js rendering library or a simple custom renderer.
Processes
The processes page offers basically all the features to navigate between process definitions and instances and showing the data.
What is missing are some interactive parts on the BPMN diagram.
Token Manipulation
A basic version of token manipulation exists for single process instances. The next step would be to integrate a batching option (e.g. if a user looks on a process definition diagram).
Decisions, Deployments
Those pages are relatively simple, as they only show data and have little interaction. They mostly need testing and user feedback on layout and usability.
Batches
This page does not exist yet.
Migrations
The migration process is translated from the legacy web apps, works and needs feedback on the interaction flow.
Admin, Account
Are mostly CRUD interactions on configuration settings. Here we should add unit tests, as it is relatively simple. Maybe some details are missing, but overall it works as well.
Meta Features
Search
Works quite well. Potential for unit tests and needs understanding of user search behavior before trying to improve something.
Authentication
There are working implementations for Basic Auth and OAuth 2.0, yet they aren’t well tested and only used locally against simple containerized setups with KeyCloak.
One big question is, how to properly work with a REST API that requires authentication as well. Again, we have some approaches tested, but need validation that this is how a org would use this.
Deployment Methods
Embedding the new web apps
Originally, the legacy web apps came embedded with each Camunda 7 deployment. They used a Spring Boot application which did two things: First, provide authentication with some session handling. Second, it extended the REST API with some specialized endpoints. For our new web apps, we can fortunately use the existing REST API, as it offers all the endpoints we need. The hard, and yet to be solved part, is to embed the web apps in a similar way. Currently, this proved to be more complicated than hoped for and needs some assistance from people with a stronger Java background.
Standalone deployment
The working and easy to integrate way for using the web apps now, is a standalone deployment. We provide a Dockerfile, which containerizes the Vite build and also has an nginx reverse proxy included (e.g. for having the REST endpoints only accessible through the web apps). This Dockerfile comes with multiple Docker Compose files for different setups or as reference for custom setups.
We offer configuration of the web apps with environment variables, which may be set through Docker.