Deployment of Process Diagram on camunda server "ENGINE-09005 Could not parse BPMN process


#1

I have implemented Launch workFlow functionality where i have Deploy button which will Call rest api to deploy Process Diagram on Camunda server

I can able to generate xml for CustomeElement but whenEver i am trying to deploying on camunda server using ‘camunda/api/engine/engine/default/deployment/create’ API,

it failed with message

{“type”:“ProcessEngineException”,“message”:“ENGINE-09005 Could not parse BPMN process. Errors: \n* cvc-complex-type.2.4.a: Invalid content was found starting with element ‘al:trigger’. One of ‘{“http://www.omg.org/spec/BPMN/20100524/MODEL”:flowElement, “http://www.omg.org/spec/BPMN/20100524/MODEL”:artifact, “http://www.omg.org/spec/BPMN/20100524/MODEL”:resourceRole, “http://www.omg.org/spec/BPMN/20100524/MODEL”:correlationSubscription, “http://www.omg.org/spec/BPMN/20100524/MODEL”:supports}’ is expected. | EmbeddedFormExample.bpmn | line 2 | column 42”}


#2

i also happy if i get any idea how we can restrict some Custome Element to not update xml ,

because if i remove custom Elemnt tag from xml its able to deploy sucessfully


#3

Hi @vikashsingh009, If I understood you correctly, you would want to remove the custom element tags before deploying in order to get it to working on the Camunda server? Have you managed to get it working properly when you removed them manually?


#4

Yes if I removed manully it will able to deploy successfully


#5

You said you have implemented a launch functionality that deploys your workflow process automatically. Isn’t then possible for you to remove the custom elements from xml before deploying?


#6

Thats possible ,but my question is since i have lots of Custom Element which is attaching to Orignal element like userTask …in that case if i remove those my diagram will be fully modified


#7

First of all the namespace al is not defined in your XML which leads to an error. Secondly you can’t just put an element you came up with somewhere in the process. This will result in invalid BPMN. Extension elements are the right place to put those things. A task could then look like this:

<bpmn:task id="Task_1">
  <bpmn:extensionElements>
      <myAwesomeNamespace:trigger id="foo" />
  </bpmn:extensionElements>
  <bpmn:incoming>SequenceFlow_1</bpmn:incoming>
  <bpmn:outgoing>SequenceFlow_2</bpmn:outgoing>
</bpmn:task>