Chain action for AND condition vs Gateway

This is a great question. Gateways will, in fact, later change their behaviour, in particular if there are multiple successors to a gateway. For single successors, there won't be any change.

We will take care of this breaking change when we implement the real gateway feature such that there will be a setting to keep legacy behaviour for existing sites, or for existing ECA models.

So we avoid using Gateway and only use "Chain action for AND condition" for And Condition conditions.

It is reassuring that every ECA update will be done in a way that will not break previous Models, so you don't have to check every function of every Model again and again after every ECA update to see if something has broken.

Thank you for the attentive development!

It is reassuring that every ECA update will be done in a way that will not break previous Models

We try hard, and we have good test coverage as well. However, for our own enterprise projects, we do implement Cypress E2E tests for all our ECA models to ensure that they always create the same result. I'd encourage everyone to do the same if their application is in any way business relevant.