Adding swimlanes for optical logic encapsulation

Created on 19 December 2024, 3 days ago

When working in ECA together with bpmn_io it sometimes becomes not easy to create an easy to read, easy and "intuitive" to understand workflow, especially when workflows become more complex.

When taking a look at bpmn in general there are ways to optical encapsulate different logic clusters with the usage of swimlanes (s. first screenshot, ).

In my opinion this could be a huge advantage to use, because it makes eca with bpmn much better read- and understandable and the most important part more intuitive to read.

I'll just leave this here and looking forward to a great discussion about it :)

Feature request
Status

Active

Version

2.1

Component

User interface

Created by

🇩🇪Germany Istari

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @Istari
  • 🇩🇪Germany Istari

    Just noticed that this is the wrong place here and we need to move it to bpmn_io.

  • 🇩🇪Germany jurgenhaas Gottmadingen
  • 🇩🇪Germany jurgenhaas Gottmadingen

    @mysdiir you can easily give this a try by deleting the following 2 lines from the bpmn_io.css file:

    72: .djs-palette-entries .bpmn-icon-participant,
    79: .djs-context-pad .bpmn-icon-participant,
    

    Visually, that should already be all that's required. But we need to test of saving and executing models, where plugins are contained in such "participants" will still work as expected.

  • 🇩🇪Germany jurgenhaas Gottmadingen

    Ah, just tested a bit and it's not that simple because the XML structure changes completely. Each "participant" is treated like a model of its own, i.e. pretty much as if multiple ECA models were contained in a single one. That requires us to re-architect the \Drupal\eca_modeller_bpmn\ModellerBpmnBase class.

Production build 0.71.5 2024