Since ECA provides no real "else" clause, many times conditions need to be duplicated and then negated. This makes process flows even more complicated when having multiple conditions in a chain.
We may start adding the support of a real "else" clause in the ECA engine itself. Although we don't have a concrete approach for the mostly used bpmn modeler yet, still it may be good to already have the engine being capable of else clauses.
The ECA configuration could store an else within the successor list of an action:
Activity_0:
plugin: eca_void_and_condition
label: AND
configuration: { }
successors:
-
id: Activity_1
else: Activity_2
condition: Condition_0
Active
3.0
Code
Agreed, this will make a lot of tings much easier. When it comes to the syntax on how to express this in an ECA config entity, I suggest we do that in relation to the ✨ Improve gateway support Active issue to cover them all.