Allow extension properties on all elements in Zeebe Modeler

[berndruecker]

In Camunda Modeler we can define properties on all elements, e.g. you could configure a message start event to contain meta information about queue names or Kafka topic names. The result BPMN XML looks like this:

   <bpmn:startEvent id="StartEvent_1" name="A">
     <bpmn:extensionElements>
       <camunda:properties>
         <camunda:property name="sdsadd" value="dsadsada" />
       </camunda:properties>
     </bpmn:extensionElements>

This should also be possible in the Zeebe modeler. The properties approach of Camunda would work fine, so I don’t see a need to change the attribute layout, but obviously it should be in the Zeebe namespace :-)

This is requested by a Zeebe prospect, ask @berndruecker for details on the company/project

[nikku]

Is this supported by Zeebe already? If not, please link an issue that tracks building support in zeebe for it.

[berndruecker]

No need for a feature in Zeebe - the extension properties are read from the BPMN model directly by custom code (as it was done in Camunda BPM for this use case). So for example you want to read a queue name or Kafka topic from the properties to know, that you have to provision a Kafka Connector to listen to this topic.

[nikku]

We do need Zeebe to not blow up on zeebe:properties, that is the part we require from the broker. If it does not blow up right now, it is not strictly validating input (which can change anytime I guess).

@menski Please consider this feature request and give us the O.K. if / when we should support this in the Zeebe Modeler. It makes loads of sense from the users perspective.

[pinussilvestrus]

@menski any opinions on whether we should add this?