Process Diagram does not display in Cockpit for processes with BPMNDI information

Hi All,

I am still using Camunda 7.2, I finally got around to generating the BPMNDI process diagram information using the model API. The BPMNDI ( below - simple start - edge - stop ) looks to be correct, and the standalone Camunda Modeler can read and display the diagram metadata without issue ( no warnings in the logs ). I expected the diagram to display in cockpit when it was deployed ( via the REST API ). Instead the standard “Unable to render process diagram.” message is displayed.

Is anyone aware of any issues with cockpit not displaying diagrams ? ( I cant see anything in the Camunda logs reporting an issue )

Thanks in advance…

<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://www.omg.org/spec/BPMN/20100524/MODEL" xmlns:bpmndi="http://www.omg.org/spec/BPMN/20100524/DI" xmlns:camunda="http://activiti.org/bpmn" xmlns:dc="http://www.omg.org/spec/DD/20100524/DC" xmlns:di="http://www.omg.org/spec/DD/20100524/DI" id="process-definition" targetNamespace="http://camunda.org/examples">
  <process id="7F0000017ADA9CEC86D52AFF33FA4167" isExecutable="true" name="Layout">
    <laneSet id="laneSet_ea248226-805f-4e66-ad7b-7e2d4b495130">
      <lane id="lane_1ec6dfff-ca86-45bb-aaf2-02ecfe0b5b39" name="admin">
        <flowNodeRef>GUID-7F0000015609EBFCE638A36083A544A0</flowNodeRef>
        <flowNodeRef>GUID-7F0000015609EBFCEBAB09A6FD4D46C9</flowNodeRef>
      </lane>
    </laneSet>
    <endEvent id="GUID-7F0000015609EBFCE638A36083A544A0" name="Silent end">
      <extensionElements>
        <camunda:executionListener event="end" expression="${execution.setVariable(&quot;finalState&quot;,&quot;Completed&quot;)}"/>
      </extensionElements>
      <incoming>GUID-7F0000015609EBFC4C9510D32FB14871</incoming>
    </endEvent>
    <startEvent camunda:asyncAfter="true" camunda:asyncBefore="true" id="GUID-7F0000015609EBFCEBAB09A6FD4D46C9" name="Manual start">
      <extensionElements>
        <camunda:executionListener event="end" expression="${execution.setVariable(&quot;startDateTime&quot;,&quot;2016-11-28T09:36:37&quot;)}${execution.setVariable(&quot;guid&quot;, execution.getId() )}"/>
      </extensionElements>
      <outgoing>GUID-7F0000015609EBFC4C9510D32FB14871</outgoing>
      <messageEventDefinition id="GUID-7F0000011575059B051E3B5728BB4B38" messageRef="GUID-7F0000011575059B1F565039FF2A4698"/>
    </startEvent>
    <sequenceFlow id="GUID-7F0000015609EBFC4C9510D32FB14871" sourceRef="GUID-7F0000015609EBFCEBAB09A6FD4D46C9" targetRef="GUID-7F0000015609EBFCE638A36083A544A0"/>
  </process>
  <collaboration id="collaboration_377d8e05-3ae6-4f75-b221-8709f7ec71cf">
    <participant id="participant_73ec0e4e-809c-457f-9c4a-e625450c80c6" name="admin" processRef="7F0000017ADA9CEC86D52AFF33FA4167"/>
  </collaboration>
  <message id="GUID-7F0000011575059B1F565039FF2A4698" name="GUID-7F0000015609EBFCEBAB09A6FD4D46C9-7F000001275E2486045D8C60706A4885"/>
  <BPMNDiagram xmlns="http://www.omg.org/spec/BPMN/20100524/DI">
    <BPMNPlane bpmnElement="7F0000017ADA9CEC86D52AFF33FA4167">
      <bpmndi:BPMNShape bpmnElement="GUID-7F0000015609EBFCE638A36083A544A0">
        <dc:Bounds height="50.0" width="50.0" x="190.0" y="60.0"/>
      </bpmndi:BPMNShape>
      <bpmndi:BPMNShape bpmnElement="GUID-7F0000015609EBFCEBAB09A6FD4D46C9">
        <dc:Bounds height="50.0" width="50.0" x="50.0" y="60.0"/>
      </bpmndi:BPMNShape>
      <bpmndi:BPMNEdge bpmnElement="GUID-7F0000015609EBFC4C9510D32FB14871">
        <di:waypoint x="100.0" y="85.0"/>
        <di:waypoint x="190.0" y="85.0"/>
      </bpmndi:BPMNEdge>
    </BPMNPlane>
  </BPMNDiagram>
</definitions>

I tried to deploy this and failed because the ID is not a valid QName

But once I changed the ID it deployed and displayed correctly in cockpit:

Hi Niall,

Thank you for checking. I changed the ID before posting as I prefix a value i couldn’t share. ( and forget the UID would then be invalid ).

Which version of Cockpit are you using ( I am using 7.2.0 ) ?
Did you restart Camunda or anything special ?

Thanks again.

Gareth

I didn’t need to restart Camunda or make any changes - but i was using using Camunda 7.5.x. That may be a factor.