Use versions for element-templates

[simonhir]

Is your feature request related to a problem? Please describe.

In the last releases there were always changes on element-templates which needed to be done manually by process developers. That often caused problems and additional work.
To improve this ux element-template versions.-,version%20%3A%20Integer,-%3A%20Optional%20version%20of) should be used.

Describe the solution you'd like

• Use versions on all element-templates used in bpm-modeler
  • Deprecated can be excluded
  • Good folder/file structure to represent versions
• Create workflow for adding, deprecating and removing versions

Describe alternatives you've considered

No versions just like in last releases: bad ux, problems and additional work for process developers

Acceptance Criteria

• Workflow for creating, deprecating and removing versions is documented and communicated to process developers
• All bpm-modeler element-templates have versions (except deprecated?)
• The element-templates are placed in a easy to manage and understand folder/file structure

Additional context

[darenegade]

Hab es mal probiert. Problem ist, dass die Einführung dazu führt, dass alle nicht versionierten Templates nicht mehr verknüpft sind. Die Umstellung ist also ein Breaking Change für alle Templates

Optional version of the template. If you add a version to a template it will be considered unique based on its ID and version.

https://docs.camunda.io/docs/components/modeler/desktop-modeler/element-templates/defining-templates/

[simonhir]

Ich hatte da vor meinem Urlaub auch mal rumprobiert und war eigentlich der Meinung da ging es ohne Probleme, weil in der UI da nur z.B. (V2) in der Anzeige angehangen wird und man dann einfach mehr Einträge in der Auswahl sieht.
Muss man dann vll. im Rahmen des Tickets nochmal mehr ausprobieren am Anfang.