- Issue created by @rclemings
- 🇩🇪Germany jurgenhaas Gottmadingen
Moving this to the bpmn_io project since this is where this is coming from. The executable checkbox is BPMN specific and that's why it's there. We haven't even invented that, we just thought that the existing BPMN property "executable" would perfectly match the enabled/disabled state for Drupal entities. Not sure how to resolve this without getting BPMN to change their standard spec.
- 🇩🇪Germany rkoller Nürnberg, Germany
One option might be to add some sort of a "status bar" (not as a drupal status message) to the top of the canvas across the full width with a centered "this model is disabled" label. That way it would not interfere with the bpmn io ui necessarily and on the other hand it would be directly apparent to the person editing that this is not an enabled model and something is different here.
The second option might be instead of introducing a status bar using the aforementioned regular drupal status/info message. the downside, it takes up way more screen estate due to its height and might be too much of a distraction since disabled bpmn io models are still editable.
The last option to consider as an addition to one of the previous options or even as an alternative is adding the info that a model is disabled to the h1 in the model header. for screenreader users that might be an mandatory bit of information anyway, but it might be worth to be considered for sighted users as well?