Updating the element templates with camunda:Connector leads to duplicated <camunda:connector> element in XML
See original GitHub issueDescribe the bug
Given one template on my local machine
When I make a change to it i.e. increase the version number The upgrade is correctly suggested in the UI. ✔️
When upgrade to the newer version Then the one camunda:connector element in the XML is not replaced, but it is duplicated. ❌
Steps to reproduce
- Create a new template in your element-template folder in your Camunda Desktop Modeler installation with the following content:
This is the same template example provided here that uses the Camunda 7 Connectors. See docs here and here
{
"$schema": "https://unpkg.com/@camunda/element-templates-json-schema/resources/schema.json",
"name": "ConnectorGetTask-LOCAL",
"id": "9a158cf8-c500-40d8-90a5-c4a62727684110",
"appliesTo": [
"bpmn:Task"
],
"version": 1,
"properties": [],
"scopes": [
{
"type": "camunda:Connector",
"properties": [
{
"label": "ConnectorId",
"type": "String",
"value": "My Connector HTTP - GET",
"binding": {
"type": "property",
"name": "connectorId"
}
},
{
"label": "Method",
"type": "String",
"value": "GET",
"binding": {
"type": "camunda:inputParameter",
"name": "method"
}
},
{
"label": "URL",
"type": "String",
"value": "https://bpmn.io",
"binding": {
"type": "camunda:inputParameter",
"name": "url"
}
},
{
"label": "Response",
"type": "String",
"value": "wsResponse",
"binding": {
"type": "camunda:outputParameter",
"source": "${S(response)}",
"scriptFormat": "freemarker"
}
}
]
}
]
}
-
Create a new C7 BPMN diagram and add a task to it
-
Apply the template to the task and save
-
Increase the version number in the template from
1
to2
-
Go to your diagram from (3.) and Upgrade the template
-
Open the XML view and see two entries of camunda:connector in the XML
See screen recording:
And the only difference between the two templates is the version:
Expected behavior
The upgrade of the template should replace my cammunda:Connector, not duplicate it.
Environment
- OS: all
- Camunda Modeler Versions : tested in v4.12.0 and v5.3.0
- Execution Platform: Camunda Platform 7
- Installed plug-ins: Cawemo Cloud Connect Plugin
Additional context
The issue has been reported by a customer via SUPPORT-14645
Issue Analytics
- State:
- Created a year ago
- Comments:5 (4 by maintainers)
Top GitHub Comments
Low effort to patch release this. We have an existing process + branching strategy in place.
Hi Team, customer has migrated their plugins to V5.x now. Is it possible to get a timeline for a fix on V5?