Be able to collapse and expand Pools / Participants without loosing contents
See original GitHub issueUsers often request a pool / participant to be collapsable, similar to sub-processes.
Use Case
Under certain circumstances a user would like to reduce the complexity of the shown collaboration diagram by collapsing individual pools. Each pool should keep its content so that it can be expanded again later on. Message flows in and out of the pool should remain visible, too, docking to the pool borders rather than to hidden elements.
Full spec: https://github.com/bpmn-io/bpmn-js/issues/736.
Referenced via SUPPORT-5274
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Be able to collapse and expand a Pool / Participant ... - GitHub
One alternative could be to permit collapsing pools with content to avoid this situation.
Read more >Expand, collapse, or show details in a PivotTable or PivotChart
Right-click the item, click Expand/Collapse, and then do one of the following: To see the details for the current item, click Expand. To...
Read more >Drawing BPMN Pools and Lanes - Visual Paradigm
When a pool is stretched, the pool and the contained lane(s) will expand or collapse by following the size of diagram and you...
Read more >BPMN 2.0 Symbols - A complete guide with examples.
In two cases, the message flows do not end in an activity or event, but at the participants' respective pool boundaries. The first...
Read more >1.5.2 Configuring a Block Device on a Ceph Client
This example creates a 4096 MB volume named vol01 in the datastore pool. Note. If you do not specify a storage pool, rbd...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
One issue with our current implementation of collapsing pools is that people do not realize that this also deletes all its content. They might realize this only when they expand the pool again and find it being empty.
A quick fix for this could be to disallow collapsing of pools if they are not empty. This way, we could prevent the negative surprise of large diagram content being deleted.
I think we should keep this issue for its original purpose, namely collapsing and expanding Pools without losing contents, which we are not going to build any time soon. Let’s move it to backlog then.
Rationale: saving the contents is still a valid feature request, but not related to the approach we will go for as a next step. We could consider to close this one and keep the feature request as a general bpmn.io concern (https://github.com/bpmn-io/bpmn-js/issues/736).
I created another issue to track the work regarding the last discussions: https://github.com/camunda/camunda-modeler/issues/2022