question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[SOLVED] Element Template UI is not shown in property panel in modeler v4.7+

See original GitHub issue

Describe the Bug

See title:

Camunda Modeler v4.6.0 Camunda Modeler v4.6.0

Camunda Modeler v4.7.0 Camunda Modeler v4.7.0

Camunda Modeler v4.8.0 Camunda Modeler v.4.8.0

BPMN diagram

<?xml version="1.0" encoding="UTF-8"?>
<bpmn:definitions xmlns:bpmn="http://www.omg.org/spec/BPMN/20100524/MODEL" xmlns:bpmndi="http://www.omg.org/spec/BPMN/20100524/DI" xmlns:dc="http://www.omg.org/spec/DD/20100524/DC" xmlns:camunda="http://camunda.org/schema/1.0/bpmn" xmlns:di="http://www.omg.org/spec/DD/20100524/DI" xmlns:bioc="http://bpmn.io/schema/bpmn/biocolor/1.0" id="Definitions_1yywux5" targetNamespace="http://bpmn.io/schema/bpmn" exporter="Camunda Modeler" exporterVersion="4.8.0">
  <bpmn:process id="HelloWorldProcess" name="Hello World" isExecutable="true">
    <bpmn:startEvent id="StartStartEvent" name="Start">
      <bpmn:extensionElements />
      <bpmn:outgoing>Flow_1egfwl9</bpmn:outgoing>
    </bpmn:startEvent>
    <bpmn:endEvent id="EndEndEvent" name="End">
      <bpmn:extensionElements />
      <bpmn:incoming>Flow_1apm4zb</bpmn:incoming>
    </bpmn:endEvent>
    <bpmn:task id="GreetTask" name="Greet">
      <bpmn:extensionElements>
        <camunda:inputOutput>
          <camunda:outputParameter name="greeting">Hello ${name}!</camunda:outputParameter>
        </camunda:inputOutput>
      </bpmn:extensionElements>
      <bpmn:incoming>Flow_0841p37</bpmn:incoming>
      <bpmn:outgoing>Flow_0ghtegg</bpmn:outgoing>
    </bpmn:task>
    <bpmn:sequenceFlow id="Flow_1egfwl9" sourceRef="StartStartEvent" targetRef="LoadInputTask" />
    <bpmn:sequenceFlow id="Flow_0ghtegg" sourceRef="GreetTask" targetRef="ReturnGreetingTask" />
    <bpmn:sequenceFlow id="Flow_0841p37" sourceRef="LoadInputTask" targetRef="GreetTask" />
    <bpmn:serviceTask id="LoadInputTask" name="Load&#10;Input" camunda:modelerTemplate="com.example.camunda.delegates.ProcessLoadInput" camunda:modelerTemplateVersion="1" camunda:delegateExpression="${processInput}">
      <bpmn:extensionElements>
        <camunda:inputOutput>
          <camunda:inputParameter name="inputKeys">
            <camunda:map>
              <camunda:entry key="name" />
            </camunda:map>
          </camunda:inputParameter>
        </camunda:inputOutput>
      </bpmn:extensionElements>
      <bpmn:incoming>Flow_1egfwl9</bpmn:incoming>
      <bpmn:outgoing>Flow_0841p37</bpmn:outgoing>
    </bpmn:serviceTask>
    <bpmn:sequenceFlow id="Flow_1apm4zb" sourceRef="ReturnGreetingTask" targetRef="EndEndEvent" />
    <bpmn:serviceTask id="ReturnGreetingTask" name="Return&#10;Greeting" camunda:modelerTemplate="com.example.camunda.delegates.ProcessSaveResult" camunda:modelerTemplateVersion="1" camunda:delegateExpression="${processResult}">
      <bpmn:extensionElements>
        <camunda:inputOutput>
          <camunda:inputParameter name="resultVariables">
            <camunda:map>
              <camunda:entry key="greeting" />
            </camunda:map>
          </camunda:inputParameter>
        </camunda:inputOutput>
      </bpmn:extensionElements>
      <bpmn:incoming>Flow_0ghtegg</bpmn:incoming>
      <bpmn:outgoing>Flow_1apm4zb</bpmn:outgoing>
    </bpmn:serviceTask>
  </bpmn:process>
  <bpmndi:BPMNDiagram id="BPMNDiagram_1">
    <bpmndi:BPMNPlane id="BPMNPlane_1" bpmnElement="HelloWorldProcess">
      <bpmndi:BPMNEdge id="Flow_1apm4zb_di" bpmnElement="Flow_1apm4zb">
        <di:waypoint x="875" y="97" />
        <di:waypoint x="932" y="97" />
      </bpmndi:BPMNEdge>
      <bpmndi:BPMNEdge id="Flow_0841p37_di" bpmnElement="Flow_0841p37">
        <di:waypoint x="435" y="97" />
        <di:waypoint x="485" y="97" />
      </bpmndi:BPMNEdge>
      <bpmndi:BPMNEdge id="Flow_0ghtegg_di" bpmnElement="Flow_0ghtegg">
        <di:waypoint x="655" y="97" />
        <di:waypoint x="705" y="97" />
      </bpmndi:BPMNEdge>
      <bpmndi:BPMNEdge id="Flow_1egfwl9_di" bpmnElement="Flow_1egfwl9">
        <di:waypoint x="215" y="97" />
        <di:waypoint x="265" y="97" />
      </bpmndi:BPMNEdge>
      <bpmndi:BPMNShape id="_BPMNShape_StartEvent_2" bpmnElement="StartStartEvent" bioc:stroke="rgb(229, 57, 53)" bioc:fill="rgb(255, 205, 210)">
        <dc:Bounds x="179" y="79" width="36" height="36" />
        <bpmndi:BPMNLabel>
          <dc:Bounds x="185" y="122" width="25" height="14" />
        </bpmndi:BPMNLabel>
      </bpmndi:BPMNShape>
      <bpmndi:BPMNShape id="Event_0sh71z8_di" bpmnElement="EndEndEvent" bioc:stroke="rgb(67, 160, 71)" bioc:fill="rgb(200, 230, 201)">
        <dc:Bounds x="932" y="79" width="36" height="36" />
        <bpmndi:BPMNLabel>
          <dc:Bounds x="940" y="122" width="20" height="14" />
        </bpmndi:BPMNLabel>
      </bpmndi:BPMNShape>
      <bpmndi:BPMNShape id="Activity_0fzlqj1_di" bpmnElement="GreetTask">
        <dc:Bounds x="485" y="67" width="170" height="60" />
      </bpmndi:BPMNShape>
      <bpmndi:BPMNShape id="Activity_0io6g2a_di" bpmnElement="LoadInputTask" bioc:stroke="rgb(30, 136, 229)" bioc:fill="rgb(187, 222, 251)">
        <dc:Bounds x="265" y="67" width="170" height="60" />
      </bpmndi:BPMNShape>
      <bpmndi:BPMNShape id="Activity_1v2zghv_di" bpmnElement="ReturnGreetingTask" bioc:stroke="rgb(30, 136, 229)" bioc:fill="rgb(187, 222, 251)">
        <dc:Bounds x="705" y="67" width="170" height="60" />
      </bpmndi:BPMNShape>
    </bpmndi:BPMNPlane>
  </bpmndi:BPMNDiagram>
</bpmn:definitions>

Template file

{
  "$schema": "https://unpkg.com/@camunda/element-templates-json-schema/resources/schema.json",
  "name": "Process: Load Input",
  "id": "com.example.camunda.delegates.ProcessLoadInput",
  "description": "Loads specified process input parameters into corresponding process variables.",
  "version": 1,
  "appliesTo": [
    "bpmn:ServiceTask"
  ],
  "properties": [
    {
      "label": "Delegate expression",
      "type": "Hidden",
      "value": "${processInput}",
      "editable": false,
      "binding": {
        "type": "property",
        "name": "camunda:delegateExpression"
      }
    },
    {
      "label": "inputKeys: Map (REQUIRED) | Syntax options in description below.",
      "description": "Syntax: In keys, use dot notation (.) to access sub-keys if they exist, e.g. address.zipCode. Use arrow notation (->) to specify that a key X should be saved as process variable Y, e.g. address.zipCode->zip. Values, if specified, represent default values for created process variables in case corresponding keys were not found.",
      "binding": {
        "type": "camunda:inputParameter",
        "name": "inputKeys"
      },
      "constraints": {
        "notEmpty": true
      }
    }
  ]
}

Note: The issue remains even when specifying a concrete json schema, e.g. https://unpkg.com/@camunda/element-templates-json-schema@0.2.0/resources/schema.json

Installed plugins:

  • Autosave
  • Color-Picker
  • Process-IO-Specification
  • Rename Technical IDs
  • Resize Tasks
  • Token Simulation
  • Tooltip

Steps to Reproduce

Copy the above template into the appropriate template folder to load it when the modeler starts, and assign it to a service task.

Expected Behavior

The Template UI should show in Camunda Modeler 4.7+ as in previous versions.

UPDATE: SOLVED I could isolate the issue to be linked to the Process-IO-Specification plugin. I had an outdated version, Updating it solved the issue and the template UI was shown again in v4.8.0.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:6 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
jtvilmcommented, May 12, 2021

UPDATE: SOLVED I could isolate the issue to be linked to the Process-IO-Specification plugin. I had an outdated version, Updating it solved the issue and the template UI was shown again in v4.8.0.

0reactions
MaxTrucommented, May 12, 2021

Thanks @jtvilm for digging deeper and sharing the solution here!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Make it possible to structure element templates in sections
The properties panel structures contents logically into groups and these groups can be collapsed and expanded by users based on what is ...
Read more >
Visual Modeler UI properties - IBM
UI : CONTROL, string, This property is used to set the name of the generic UI control type used to render an option...
Read more >
Template selector not working - Modeler - Forum - bpmn.io
We've got element templates working for events, sequence flows and tasks in version 0.4 of the properties panel.
Read more >
Retrieving and displaying data with model binding and web ...
In Solution Explorer, right-click your project, select Add and then New Item. In the Add New Item dialog box, select the Web Form...
Read more >
10 Most Common Bootstrap Mistakes That Developers Make
Common Bootstrap Mistake #4: Using everything that Bootstrap offers. As mentioned before, Bootstrap is comprehensive. It offers a lot of UI components, HTML...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found