Camunda-modeler: Reuse bpmnlint style coding to create element templates

Created on 18 Oct 2018  路  5Comments  路  Source: camunda/camunda-modeler

Given we now have bpmnlint and the style of access it provides, it would be great if we could get the same functionality in element templates. Rather than being limited by the Json style of element templates, we could use JS to define templates

backlog enhancement

All 5 comments

What exactly are you referring to as the style of access? Just trying to understand this a bit better so we can make a proper feature request out of this.

Style of access is the ability to access the bpmn through the js api. Having this same ability for element templates opens huge amounts of possibilities in the molder. Allowing simple and complex templates to be created with various dependencies. The Json templates are like a simplification to injecting the data into the bpmn, but with the js style API access we could just write some basic lines of js and have full access to the bpmn without limits of the element template Json "dsl"

This sounds reasonable to me. It would also spare us from having to supporting every single property that one might want to template.

+1 for sure.
As part of this, if you provide a dsl for some basic form fields as well, then i think that would tie it all together. Being able to define fields similar to how they are defined in the json: such as text fields, drop downs, Key/Values, lists.

This sounds reasonable to me. It would also spare us from having to supporting every single property that one might want to template.

As someone who would like to preassign values for multi-instance fields for his multi-instance external service task used to send mails, I would welcome this or a similar improvement.

Was this page helpful?
0 / 5 - 0 ratings