In my opinion, no objects can be added outside the pool if a pool exists in the modeling. But “DataStoreReference” can. It’s unreasonable.
In addition, when I change type of object to “DataObjectReference”, the previous object is not removed from SVG, and new object is rendered under previous object.
You can check the behavior in the GIF below:
Hi @TriPham ,
DataStoreReference outside of a pool, please read this thread. Note that:
- The actual
dataStoreReference will still be part of the process inside the XML (BPMN compliant). Example:
<bpmn:participant id="Participant_1v5jqua" processRef="Process_0vh71fz" />
<bpmn:participant id="Participant_1qf84cl" processRef="Process_1ldr0lb" />
<bpmn:process id="Process_0vh71fz" isExecutable="false">
<bpmn:dataStoreReference id="DataStoreReference_0zm2l5f" />
<bpmn:process id="Process_1ldr0lb" isExecutable="false" />
- It was deliberately decided to be able to model the graphic representation outside of pools. See thread for use case examples and rationale.
Regarding the bug when morphing to
DataObjectReference => I agree, that is an issue. I created this issue to follow-up.