I cannot keep defining the same shape data for each new pool I create for each diagram. If pools end up next to lanes within my diagrams the integrity and meaning of my diagrams is destroyed. Both my pool shape, which I use to represent business processes, and my lane shape, which I use to represent organizational functions or roles, each capture different data. ![]() I've created my own BPMN 2.x stencil containing slightly modified Visio BPMN master shapes that capture customized shape data. Pools and lanes are the same things to Visio, which is causing me some major difficulties. If I drop a pool on top of a pool, Visio treats them as lanes and wraps them in a pool, even if I specify in the shape data that they're pools. If I drop a lane onto a pool, Visio treats them both as lanes and wraps them in a pool. If I place a pool on top of a lane, Visio wraps them both in a container that's a pool it treats both the lane and the pool as lanes. Visio 2019 or 2020 (whatever the current version is) draws no distinction between pools and lanes they're both visio containers. ![]() According to the BPMN 2.x standard, pools and lanes are two different things I want Visio to treat them as such.
0 Comments
Leave a Reply. |