Nico Rehwaldt

> The combinaton of not sending all data to zeebe but leveraging the result expression plus output mappings is perfectly fine (as it reduces the amount of data and PII...

I see the root cause in the fact that the update is _immediate_. What I'd propose is that we do the actual update on blur only, following along the direct...

The alternative is that we keep the intermediate commit feature, but build the component properly on top of `diagram-js-ui`. A "proper" implementation must account for selection update as the elements...

@VonDerBeck Thanks for opening this report. What you'd like to see supported is starting a BPMN process from a form, in Camunda 8 self-managed? Where would you expect that form...

> Or is there an aspect I do not know? I'm not aware of that and my question had no hidden agenda :slightly_smiling_face:. Thank you for sharing your expectations :star2:!

This works on Linux :heavy_check_mark: I rebased it on to of `develop`.

~~The Java client seems to [transparently choose between REST or GRPC](https://camunda.slack.com/archives/C06UKS51QV9/p1733151968913549?thread_ts=1733148050.961199&cid=C06UKS51QV9) based on what is supported. You can assume _it just works_. I'd like to understand if the JS client...

To date the JS SDK does not seem to transparently handle this, we need to [choose explicitly between GRPC and REST clients](https://github.com/camunda/camunda-8-js-sdk?tab=readme-ov-file#usage). Going forward this means additional work for _anyone_...

Java client does not fully transparently handle the difference, too, so work has to be done by users ([ref](https://camunda.slack.com/archives/C06UKS51QV9/p1733306912779599?thread_ts=1733148050.961199&cid=C06UKS51QV9)).

@Balazs-PM @barmac This is an item we should consider for 8.8. The unified REST API will be the new thing, enabled per default, and GRPC becomes the "secondary option". Probably...