Community
Participate
Working Groups
OMG Schema (https://www.omg.org/spec/BPMN/20100501/Semantic.xsd) defines specific order of elements, for example for process <xsd:sequence> <xsd:element ref="auditing" minOccurs="0" maxOccurs="1"/> <xsd:element ref="monitoring" minOccurs="0" maxOccurs="1"/> <xsd:element ref="property" minOccurs="0" maxOccurs="unbounded"/> <xsd:element ref="laneSet" minOccurs="0" maxOccurs="unbounded"/> <xsd:element ref="flowElement" minOccurs="0" maxOccurs="unbounded"/> <xsd:element ref="artifact" minOccurs="0" maxOccurs="unbounded"/> <xsd:element ref="resourceRole" minOccurs="0" maxOccurs="unbounded"/> <xsd:element ref="correlationSubscription" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="supports" type="xsd:QName" minOccurs="0" maxOccurs="unbounded"/> </xsd:sequence> But the files generated by BPMN2-Modeler are not following the order - for example generating 'property' elements after 'flowElement' elements. I'm trying to use bpmn files in a tool (Activiti) that apparently uses xsd based parser and I'm forced to manually fix process definitions to get them understood - and the order is broken after each save. To verify add xsi:schemaLocation="http://www.omg.org/spec/BPMN/20100524/MODEL https://www.omg.org/spec/BPMN/20100501/BPMN20.xsd" to the process definition and validate it as xml in eclipse.