I’m just pointing out some things since I’ve seen this updated recently:
I have an issue with these yellow and blue blocks both named “Qty”.
I do understand the difference but I wonder if it’s clear enough so that everyone does understand the difference (I don’t believe so).
I don’t disagree but I also have no power over that. I’m not sure what it should be labeled though.
When adding them to the script it’s pretty obvious what they do though.
But once they are added to a script it does become a little jumbled.
Thank you for the great article and DP! I think it shows the importance of reusability.
It’s always nice to learn something new, and I’m going to try 1st approach for email/event alerts.
One comments: I read in the documentation the DSL actually supports calling other rules with UID, is it not true in the newer version?
Where have you read this? There is a callScript Action but I actually didn’t find that in the docs anymore. And that only works to call a Rules DSL script, not another rule.
I’m trying to find the doc but can’t seem to find it anymore. I recall it says rules can be created without condition and in which case it can be called by other rules.
Conditions are only a concept of managed rules (i.e. those created in the UI). You can have one rule call another time in the UI; there’s a separate action for that. You can even choose whether or not to apply the conditions.
But you cannot call another rule from Rules DSL code. That’s not supported.
