Control attribute rule execution order

[Bud]

From @JohannesLindner : 

If multiple rules trigger on the same table, you have no control over the execution order, which can give unwanted results if a rule depends on a field that is calculated by another rule. 

Lessons Learned — Attribute Rules 

Could attribute rules be enhanced so that we can control the execution order? That would allow us to split huge attribute rules into smaller more manageable rules.

[MikeMillerGIS]

You can define the order of calculation attribute rules:

[Bud]

@MikeMillerGIS 

Thanks Mike. Just to clarify, does that functionality fully/currently exist in Pro? Or is it coming in a future version?

[MikeMillerGIS]

That screen shot was from 2.9.  I believe it has always been there for calculation rules.  It is not present for constraint.

[Bud]

@MikeMillerGISand @JohannesLindner:

Would there be any benefit in controlling attribute rule order of execution globally for that FC/table?

For example, the order ID would be a unique number between all calculation, constraint, and validation rules. The order ID would be honored, regardless of what kind of attribute rule is.

For example:

1. Calculation rule
2. Constraint rule
3. Calculation rule
4. Calculation rule
5. Validation rule
6. Constraint rule

I don't have a lot of experience with attribute rules. So I don't know if that's sensible or not.