Tested with camunda modeler 2.0.12

On import Yaoqiang ignores the label (name attribute) for datastore reference (expects and uses the name attribute of the dataStore itself).

According to the relevant section of the spec (p209 and following) both datastore and datastore reference may have a name. If only one has a name I would think that should be used (whichever it is) and if both have a name I suggest that the reference's name should take precedence (or display both but that will likely take up more space than is desireable).

In MID Innovator 11 R5 E (Version 11.5.1.30223) Events and Gateways are positioned in the upper left corner of the containing Lane.

Examples:

There are edges in the XML having 3 waypoints in a line (see example below). It actually helped me to detect issues in the import of Signavio, but is this intended?

<bpmndi:BPMNEdge bpmnElement="_0020ed6a-6dde-499f-9fda-36c8bde20ec6" id="E1365195429527__0020ed6a-6dde-499f-9fda-36c8bde20ec6">
<di:waypoint x="842.0" y="400.0"/>
<di:waypoint x="860.0" y="400.0"/>
<di:waypoint x="880.0" y="400.0"/>
bpmndi:BPMNLabel/
/bpmndi:BPMNEdge

[DG] Honestly, this was not intended, it is a side effect of the default waypoint (re: breakpoints in the segments) of our routing in both our tools. One could argue that we should filter them out as they do not “add value” to the layout, but it does indeed provide a nice test case and discussion point to be brought up in the agenda. Should the serialization be as minimal as possible (i.e. optimized) or as long as it is valid everything should go through?.

Tested with camunda modeler 2.0.12

Data object names are not imported.

Example B.1.0:

• Imported Diagram:
  
  Note: The data object in question is in the center of the diagram.
• Reference Diagram

Tool: eclipse BPMN2 modeler
Affected Tests: A.1.0, A.2.0, A.3.0, A.4.0, B.1.0, B.2.0
Roundtrip

height, width, x and y values for BPMNDI/DC elements are rounded during roundtrip.

I think there is an error in either the bpmn or the pfd file.

In the bpmn file, the label for the "Inclusive Gateway 1" is ABOVE the gateway:

<bpmndi:BPMNShape bpmnElement="_dec393e7-f182-4d31-b05f-e33ac3a5e35f" id="S1368567295078__dec393e7-f182-4d31-b05f-e33ac3a5e35f">
<dc:Bounds height="42.0" width="42.0" x="569.0" y="67.0"/>
<bpmndi:BPMNLabel labelStyle="LS1368567294511">
<dc:Bounds height="36.27136901041668" width="105.60000000000001" x="535.0503937007874" y="30.061165888492283"/>
</bpmndi:BPMNLabel>
</bpmndi:BPMNShape>

The label's y position is above the gateway's y location.

The pdf, however, depicts the label BELOW the gateway.

Matthias Kurz reported: "The Innovator creates both a process model as well as a diagram during update (these are two different yet linked entities in Innovator). Yet the diagram misses basic basic layout information like connectors."

Examples:

Collapsed call activities display the name of the called process. A name may be assigned but is not displayed.

Example B.1.0:

• Imported Diagram:
  
  Note: The call activity in question is the call activitiy at the cennter border of the diagram.
• Reference Diagram

Cameo Business Modeler lacks direct support for importation of the *.BPMN XML file format. The tool provides import support for XPDL and XMI formats.

Text annotations appear not to be imported from the BPMN file in MID Innovator.

Example B.1.0:

Call activities cannot be expanded in MID Innovator. Therefore, they are not imported correctly as expanded call activities but as collapsed call activities. The elements of the expanded call activity are not supported as well.
As modeling expanded call activities is not supported by the software, the export fails as well.

Similarly, collapsed subprocesses are not supported as well.

Example B.1.0:

• Imported Diagram:
  
  Note: The call activity in question is the call activitiy in the lower left border of the diagram.
• Reference Diagram

As according meeting of 24-04-2013, Please include in the BPMN MIWG Test Case Structure.xlsx file that:

Bizagi Process Modeler version 2.4 - only supports XPDL, However, this has not been tested.

Aris express version version 2.4 - only support Visio VDX file format import only. However, this has not been tested.

Best

Alberto

Text annotations are not exported in the BPMN file.

Example B.1.0:

• Reference Diagram
• [Exported BPMN](https://raw.github.com/bpmn-miwg/bpmn-miwg-test-suite/master/B%20-%20Validate%20that%20tool%20covers%20conformance%20class%20set/MID%20Innovator 11.5.1.30223/B.1.0-export.bpmn)

When a group is imported its background color is grey and opacity 100 by default so the contents of the group are invisible. Set the background opacity lower as a workaround.

The 'width' and 'height' values within the label bounds of lanes seem to be inverted. "Lane 1", for instance, defines a label with 'height="12.80..." and width="35.59...", hence representing a horizontal rectangle. The label, however, is supposed to be displayed vertically.

According to the Diagram Definition (DD) specification, the size of the rectangular described by the bounds is specified along the x-y axes. The bounds should therefore always be relative to the x-y axes, independently of the label's direction. If the label is depicted vertically, its bounds should also represent a vertical rectangle.

It could be argued whether an additional 'direction' or 'angle' attribute is needed for labels. At least for the moment the direction can be derived from the shape's 'isHorizontal' attribute.

Also see:
Diagram Definition (DD) spec: Bounds, page 9
BPMN spec: BPMNLabel, page 377

Trisotech BPMN Web Modeler does not yet support call activity calling a global task.

Tool: eclipse BPMN2 modeler
Affected Tests: A.1.0, A.2.0, A.3.0, A.4.0, B.1.0, B.2.0
Roundtrip

The dc:Font attributes isBold="false" isItalic="false" isStrikeThrough="false" isUnderline="false" are deleted during roundtrip.

Tested with camunda modeler 2.0.12

Data store references are imported, yet not displayed. The node is assigned the name correctly. Yet, data store references have a separate label which is assigned a default text. The name of the node can be retrieved when looking at the node properties.

Example B.1.0:

• Imported Diagram:
  
  Note: The data store reference in question is in the left center of the diagram.
• Reference Diagram

Line 5 reads:

<semantic:process isExecutable="false" id="_ba16239e-181e-4b9f-bc5b-0bb2ee973450">

Line 96 reads

<semantic:callActivity calledElement="_6" name="Call Activity - Expanded" id="_ba16239e-181e-4b9f-bc5b-0bb2ee973450">

Hi,
I'm currently evaluating the eclipse BPMN2 modeler and in doing so I spotted a spec violation in the reference model B.2.0:
The "Event Base Gateway 3" links to a Message Intermediate Catch Event and to a Receive Task. This is not allowed by the Spec (p. 298):

"Event-Based Gateways are configured by having outgoing Sequence Flows target
an Intermediate Event or a Receive Task in any combination[...] except that: 
If Message Intermediate Events are used in the configuration, then Receive 
Tasks MUST NOT be used in that configuration and vice versa."

Kind regards,
Matthias

Tested with camunda modeler 2.0.12

Data associations cannot be assigned a name / label in the tool.
Therefore, the associations cannot be imported or exported as well.

Example B.1.0:

• Imported Diagram:
  
  Note: The call activity in question is the call activitiy in the center left border of the diagram.
• Reference Diagram

This validation is at the warning level, may be ignored, and all behaviour appears to be correct.

The BPMN spec requires that a lane shape extend the full length of its enclosing pool. This, however, is hard to achieve as BPMNDI does not specify the size of the pool label box. Since tool vendors are free to define whatever size they like, pools and lanes will hardly ever be aligned.

Bruce Silver and I have discussed this issue a while back and we then agreed that the best thing to do would be to export the inner bounds of a pool instead. That way lanes will always be perfectly aligned and there is no risk of the separating label line crossing another shape that was drawn too close to the borders.

Bruce Silver also recommends this approach in his book 'BPMN Method & Style': "...in BPMN-I the dc:Bounds/@x value of horizontal lane and pool shapes should be the same. (p. 206)

The label of the association between “Call Activity Collapsed” and “Text Annotation” is not present in the BPMN 2.0 XML. This makes the import test failing implicitly as labels are missing on association when capturing the canvas.

Correct me if I am wrong, but from my understanding the BPMN 2.0 Spec does not want to have labels put on associations. At least there is no name attribute.

<semantic:association associationDirection="None" sourceRef="_1237e756-d53c-4591-a731-dafffbf0b3f9" targetRef="_4815ea6a-ede2-489b-8b37-2cdb2835b02c" id="_5362a7ef-ce7e-4a91-9c38-66c07b1b5f49"/>

[DG] You are quite correct that “Labels” of “Associations” and “DataAsssociations” is not possible in BPMN (and cannot be imported in another, just as for the position of labels). This raises the higher question of “Should test cases be of only what is serializable” also to be put on the agenda for discussion.

Tool: eclipse BPMN2 modeler
Affected Tests: A.3.0, B.2.0
Import, Export

eclipse BPMN2 modeler does not show the name of BoundaryEvents

We have an issue with importing model B 2.0 to ADONIS. Object "Parallel Gateway 2" is defined as:
semantic:parallelGateway gatewayDirection="Unspecified" name="Parallel Gateway 2" id="_397c783e-ad6a-4cf3-8266-9b41962c83bd"

while it seems to us it should be:
semantic:parallelGateway gatewayDirection="Converging" name="Parallel Gateway 2" id="_397c783e-ad6a-4cf3-8266-9b41962c83bd"

The boundary event "Boundary Intermediate Event Interrupting Escalation" is not supported.

Tested with: IBM BPM 8.0.1

Dear team,

We agreed upon sharing the result files for each test in files that are named in a standardized way:

• B.1.0-import.{pdf,png}
• B.1.0-export.bpmn
• etc.

Yet many of the test results are not stored in the bpmn or png files:

• Which model elements are not imported / exported correctly?
• What kinds of errors occur?
• Are there constraints of the editor that make it impossible to recreate every aspect of the reference?

Therefore, I'd like to propose using a simple Markdown file for each application.
In this file, all key model elements are stored. For each model elements, the test case results are documented.

Let us exemplify this for the B.1.0 export test of MID Innovator:

• Participant (Pool) -- OK
  • Start Event Timer -- OK
  • Abstract Task 1 -- OK
  • User Task 2 -- OK
  • Service Task 3 -- OK
  • End Event None 1 -- OK
• Lane 2 -- OK
  • Group -- ISSUE: Cannot create a group in editor
  • User Task 5 -- OK
  • Exclusive Gateway Divergence 2 -- OK
  • Collapsed Sub-Process -- ISSUE: Cannot create an collapsed sub process in editor. Instead used an call activity.
  • Service Task 7 -- OK
    • Data Association 1 -- ISSUE: Cannot assign a name to a data association in editor
      • Data Object -- OK
    • Data Association 2 -- ISSUE: Cannot assign a name to a data association in editor
      • Data Store Reference -- OK
  • Exclusive Gateway Convergence 2 -- OK
  • End Event Terminate -- OK

That way, we have a much more detailed view on the outcomes of a test case.

The entire file is available here:

https://raw.github.com/mskurz/bpmn-miwg-test-suite-fork/master/B%20-%20Validate%20that%20tool%20covers%20conformance%20class%20set/MID%20Innovator-11.5.1.30223/README.md

Any comments?

Best Regards,

Matthias

BPMN MIWG recommends to the BPMN 2.1 RTF to add a justification attribute to the BPMN DI Label in order properly complete rendering within the bounds of the label.

Tested with camunda modeler 2.0.12

The Signavio Process Editor has issues when importing the “Expanded Call Acitivity” as Start Event 3, Start Event 4 Conditional, User Task 12 Muti-Inst. Seq., User Task 13 are wrapped by an subprocess element in the XML,

but Boundary Intermediate Event Interrupting Message, End Event 5 Terminate, End Event 4, Service Task 14 are contained in a separated process element reference by an call activity element.

I guess the subprocess element needs to be merged and replaced by the process element.

[DG] We caught that one. This was a bug with our serialization that was getting lost in some particular cases. We will correct it and provide a new serialization ASAP.

Definition of object "Boundary Intermediate Event Interrupting Error" contains part that we find a bit misleading (since Error event needs to be interrupting and thus cancel activity):

semantic:boundaryEvent attachedToRef="_7e6ccf38-e740-4537-a439-a8e984d066de" cancelActivity="false" parallelMultiple="false" name="Boundary Intermediate Event Interrupting Error" id="_3c56e6dc-bc87-4d98-b499-462c5b741c5a"

wouldn't >>cancelActivity="true"<< be more correct here?

The current reference models do not contain label positions. The BPMN Spec defines them as optional, but I would suggest to have them available by default for test results not to look broken immediately. In addition, we could have one test case without label positions to see if tools behave correctly in that case.

Tested with camunda modeler 2.0.12

The file to be imported to the tool can only be bpmn format? Cannot be XPDL?

Tested with camunda modeler 2.0.12

The group artifact defined at line 195 does not define any label. In the Reference PDF (B.1.0.pdf) we can see this group is named "Group".
Some information is missing in the BPMN file and seems to be stored in visio file (.vsd) only.

On line 96, called element should no be "_6" but "_ba16239e-181e-4b9f-bc5b-0bb2ee973450" (ie : process defined on line 5).
See also issue #2, seems to be related.

When created using another tool, Yaoqiang is capable of displaying the call activity expanded. Also a sub-process may be expanded and collapsed fine.

Export and Roundtrip tests produce bpmn code in a very different way. The number of discrepancies is big.

Tested with: IBM BPM 8.0.1

Tool: eclipse BPMN2 modeler
Affected Tests: A.1.0, A.2.0, A.3.0, A.4.0, B.1.0, B.2.0
Import, Export, Roundtrip

Label positions are not saved when saving a (newly) created model.
BPMNDI label position definitions are ignored when displaying models.

Warning that may be ignored.

Testing date - 4/22/2013
A.3.0 export – Missing element Event Interrupting Escalation
A.3.0 import & RT – Labels layered over elements, labels could not be moved
A.4.0 export – Could not draw model as in .pdf, i.e. sequence flow element between lanes; tool only allows for message flow element.
B.1.0 import – "BPMN 2.0 Schema Validation Error"; label annotation not handled well
did not import group elements and label annotation associated with model.
B.2.0 import – "Yaoqiang BPMN Editor does not support the Sub Process defined in a separate diagram ."

It is proposed to the BPMN 2.1 RTF to remove gatewayDirection attribute as BPMN MIWG fail to see the value of this attribute. It seems to duplicate information already derivable from the model (it may actually lead to conflict with the model).

Hi Denis,

it looks like your last commit left the reference BPMN file of test case A.4.0 with no contents.

Git also shows that you modified the Visio file, from which it was exportet, in the same commit.

Could you please provide the correct BPMN XML file?

Cheers,
Falko

On line 267, the BPMN Share matching the "expanded call activity" (on line 96) should have its attribute "isExpanded" set to "true".