Legacy Issue Number: 14696
Source: International Business Machines ( Suzette Samoojh)
As per the current spec, a Lane references FlowElements. But FlowElements include SequenceFlow, which introduces issues given that SequenceFlow can span Lanes (e.g. the source is in one Lane while the target is in another).
Recommendation: The spec text should indicate that SequenceFlow are not included in the list of FlowElements referenced by a Lane. Tools are then responsible for presenting and laying out the SequenceFlow appropriately, based on its source and targets.
Reported: BPMN 2.0b1 — Thu, 19 Nov 2009 05:00 GMT
Disposition: Resolved — BPMN 2.0
Lanes will reference FlowNodes, which exclude SequenceFlows (only activities, events and gateways are FlowNodes).
We will change the semantic metamodel to reflect this change.
a) in Figure 10.122 - The Lane class diagram , replace FlowElement with FlowNode
b) below Figure 10.122, replace Flow Element with FlowNodes in these sentences:
- "Each LaneSet and its Lanes can partition the Flow Elements in a different way."
- "a tool can use to determine the list of Flow Elements to be partitioned into this Lane"
c) in Table 10.128 - Lane attributes and model associations
Replace flowElementRefs with flowNodeRefs, and FlowElement with FlowNode
d) in Table 10.132 - Lane XML Schema
Replace flowElementRef with flowNodeRef in this snippet
<xsd:element name="partitionElement" type="tBaseElement" minOccurs="0" maxOccurs="1"/>
<xsd:element name="flowElementRef" type="xsd:IDREF" minOccurs="0" maxOccurs="
Updated: Fri, 6 Mar 2015 20:57 GMT