Closed jfriedenstab closed 2 months ago
@jfriedenstab to clarify status of this issue / if it will make it before the 8.6-alpha4
release
I see that this is not implemented yet, so it's not coming as part of 8.6-alpha.4. I think it's quite unfortunate that the users can already use the new property, but are left in the dark about the support of the feature.
I'm moving this to ready.
Assigning @philippfromme as the assignee of https://github.com/camunda/camunda-modeler/issues/4385. Feel free to drop it if you don't have capacity.
Thanks, @barmac! Is there any chance that this could be implemented in the next days, @philippfromme? Then we could still try to include it in the release.
@jfriedenstab I'm on it!
Great, thank you! 🙂
In that case, we may also include it in https://github.com/camunda/camunda-modeler/pull/4439
In that case, we may also include it in #4439
Yes, I'd like that.
I've updated the milestone since this is shipped with the current release.
Problem you would like to solve
The new binding type
deployment
will only be supported by Zeebe 8.6 or newer. Users should be warned if they're using the new binding type in their BPMN process, but have selected a lower execution platform version.Proposed solution
Add a new linting rule that warns the user if the binding type selected for a called process, called decision or linked form is not yet supported by the current execution platform version, for example:
A <Call Activity> with <Binding: Deployment> is only supported by Camunda 8.6 or newer
Alternatives considered
none
Additional context