Removing conditions in BPMN.iO leaves a dis-functioning condition in ECA

Issue information

From user: jurgenhaas

Related to !143 (merged)

Contribution record

Fork management

Problem/Motivation

When editing a model and assigning a condition to a sequence flow which will later be removed again, leaves a trail of a "condition" in the XML data which relates in a condition in ECA that has no plugin and hence always asserts to FALSE, i.e. all subsequent actions will never be executed although it looks like there isn't a condition in the model.

Proposed resolution

Improve the save process in \Drupal\eca_modeller_bpmn\ModellerBpmnBase::readComponents

Edited by drupalbot
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information