Our current project requires models with multiple conditions using the same plugin. The current behaviour of this module disables editing the label for conditions (unlike event and actions). This makes it difficult to understand what a model is doing.
The code that disables the label field on conditions appears to be related to #3302933: Unable to add Submit form event to model → and #3303008: Cannot customise the labels of events, conditions or actions → . But neither provide an explanation for why disabling the label is required.
I do note that the config schema in the main ECA module does not contain a 'label' entry for conditions, as it does for events and actions.
Add a 'label' entry to ECA's config schema, then remove the special-casing that is keeping conditions from acting like event and actions.
I already have this working locally. I'll post a sister ticket to ECA ( 🐛 Add missing 'label' for conditions in config schema Active ) for the schema change, then open MRs in both projects.
Needs review
1.0
User interface
I pushed a fix to the MR branch. Note that this requires the fix in 🐛 Add missing 'label' for conditions in config schema Active in ECA to work.