Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Boundary Message Event Reference Duplicated in Lanes

See original GitHub issue

Describe the Bug

The ID of a message boundary event is duplicated in the XML laneSet element when you move the event from one lane into another lane.

Steps to Reproduce

Model a process with two lanes, name them a and b.
Place tasks into each lane (with sequence flows)
Add a intermediate message event with message name c.
Move the message event as an boundary event to one task.
Move the boundary event to the task in the other lane.
Inspect the XML. The message event is referenced in both lanes.

It looks like this:

    <bpmn:laneSet id="LaneSet_0hjii36">
      <bpmn:lane id="Lane_1eda2db" name="a">
        <bpmn:flowNodeRef>StartEvent_1</bpmn:flowNodeRef>
        <bpmn:flowNodeRef>Task_1fi2xts</bpmn:flowNodeRef>
        <bpmn:flowNodeRef>IntermediateThrowEvent_0gw9m8r</bpmn:flowNodeRef>
      </bpmn:lane>
      <bpmn:lane id="Lane_1890u86" name="b">
        <bpmn:flowNodeRef>IntermediateThrowEvent_0gw9m8r</bpmn:flowNodeRef>
        <bpmn:flowNodeRef>Task_0hz09v4</bpmn:flowNodeRef>
      </bpmn:lane>
    </bpmn:laneSet>

Expected Behavior

The message event should be included in the single correct lane only.

Environment

OS: [Windows 10]
Camunda Modeler Version: 3.3.2

duplicated message reference in lanes.bpmn.txt

Issue Analytics

State:
Created 4 years ago
Comments:7 (7 by maintainers)

Top GitHub Comments

1reaction

pinussilvestruscommented, Sep 23, 2019

The second flowNodeRef is created after step 4, it’s referenced twice in the same lane.

<bpmn:laneSet id="LaneSet_0hjii36">
    <bpmn:lane id="Lane_1eda2db" name="a">
        <bpmn:flowNodeRef>StartEvent_1</bpmn:flowNodeRef>
        <bpmn:flowNodeRef>Task_1fi2xts</bpmn:flowNodeRef>
        <bpmn:flowNodeRef>IntermediateThrowEvent_0gw9m8r</bpmn:flowNodeRef>
        <bpmn:flowNodeRef>IntermediateThrowEvent_0gw9m8r</bpmn:flowNodeRef>
    </bpmn:lane>
    <bpmn:lane id="Lane_1890u86" name="b">
        <bpmn:flowNodeRef>IntermediateThrowEvent_0gw9m8r</bpmn:flowNodeRef>
        <bpmn:flowNodeRef>Task_0hz09v4</bpmn:flowNodeRef>
    </bpmn:lane>
</bpmn:laneSet>

So this appears with the newest “Transform intermediate to boundary event and backwards” feature.

0reactions

oguzeroglucommented, Oct 16, 2019

Closed via Camunda modeler 3.4.0 release.

Top Results From Across the Web

BPMN 2.0 Symbols - A complete guide with examples.

A comprehensive resource for BPMN 2.0 symbols. Learn about BPMN events, tasks, subprocesses, messages and more.

Using intermediate and boundary message events to receive ...

If such a naming clash happens, you can break the unintended polymorphism by renaming the duplicate event names and then click X (delete)...

BPMN - Alfresco Docs

Message start events begin a process instance when a named message is ... Boundary events are assigned to other BPMN elements such as...

How to Mark duplicates with MarkDuplicates or ...

For RNA-Seq data mapped against the genome, use MarkDuplicates. Specifically, MarkDuplicatesWithMateCigar will refuse to process data with large reference skips ...

PositionBasedDownsampleSam (Picard) - GATK

Downsampling invalidates the duplicate flag because duplicate reads ... the reads may be distributed non-evenly within the lanes/tiles, ...