Element Templates Feature Can Update Versions

[philippfromme]

• applying an element template takes previous element template into account and if there is one the new element template will be applied according to our defined rules:

1. If property is set in new template it will override unless property was set by old template and changed afterwards
2. If property is not defined in new template it will unset
3. Sub-properties of complex properties (e.g. camunda:In, camunda:Out, camunda:ExecutionListener) will be handled according to these rules if they can be identified

Examples:

Element	👴 Old Template	👨 New Template	▶️ Result
"foo"	value = "foo"	value = "bar"	▶️ "bar"
"baz"	value = "foo"	value = "bar"	▶️ "baz"
undefined	property not specified	value = "bar"	▶️ "bar"
"foo"	property not specified	value = "bar"	▶️ "bar"
"foo"	value = "foo"	property not specified	▶️ undefined
"foo"	value = "foo"	value = undefined	▶️ undefined

Child of camunda/camunda-modeler#1969

[philippfromme]

List of complex properties:

camunda:Property

Can be identified by name. Can have an id property according to the model but it's not set in the properties panel.

Example: <camunda:property name="foo" value="bar" />

camunda:InputParameter

Can be identified by name.

Example: <camunda:inputParameter name="foo">${bar}</camunda:inputParameter>

camunda:OutputParameter

Can be identified by value which is serialized as body.

Example: <camunda:outputParameter name="foo">${bar}</camunda:outputParameter>

camunda:In

Can be identified by target.

Example: <camunda:in source="foo" target="bar" /> or <camunda:in sourceExpression="${foo}" target="bar" />

camunda:Out

Can be identified by source.

Example: <camunda:out source="foo" target="bar" /> or <camunda:out sourceExpression="${foo}" target="bar" />

camunda:ExecutionListener

Execution listeners are always hidden and therefore can be overridden. Only execution listeners with scripts can be created through templates.

Examples:

<camunda:executionListener class="Foo.java" event="start" />

<camunda:executionListener class="Foo.java" event="start">
  <camunda:field name="foo">
    <camunda:string>bar</camunda:string>
  </camunda:field>
</camunda:executionListener>

<camunda:executionListener expression="${foo}" event="start" />

<camunda:executionListener delegateExpression="${foo}" event="start" />

<camunda:executionListener event="start">
  <camunda:script scriptFormat="FooScript">console.log('foo');</camunda:script>
</camunda:executionListener>

camunda:Field

Can be identified by string or expression.

Examples:

<camunda:field name="foo">
  <camunda:string>bar</camunda:string>
</camunda:field>

<camunda:field name="foo">
  <camunda:expression>${bar}</camunda:expression>
</camunda:field>

Scope Elements

camunda:Connector

Can be identified by id.

Example:

<camunda:connector>
  <camunda:inputOutput>
    <camunda:inputParameter name="foo">foo</camunda:inputParameter>
    <camunda:outputParameter name="bar">bar</camunda:outputParameter>
  </camunda:inputOutput>
  <camunda:connectorId>foo</camunda:connectorId>
</camunda:connector>