I use regex in automated rule assignment
More than once, I forgot to activate then "regex" button. Quite annoying and not newcomers friendly.
thus, here is
MY MISH :
When a rule can be wrote in REGEX, on saving, the program will TEST the rule, WITHOUT and WITH regex activated.
...if REGEX was NOT activated (in the param windows), but A/ the rule WITHOUT regex activated (in exit test) give no result, and B/ the same rule WITH regex activated (in test) give some matchs, a popup window saying "you didn't activate REGEX, but it seems to be a regex rule..." shall appear, with two buttons "keep regex OFF", and "Oops, activate REGEX". And of course a checkbox "Do not ask to activate REGEX again".
Same if REGEX was activated and A/ the rule WITHOUT regex activated (in exit test) give matches, and B/ the same rule WITH regex activated (in test) give no matches, a popup window saying "you activated REGEX, but it seems to be a regular rule..." shall appear, with two buttons "keep regex ON", and "Oops, deactivate REGEX". And of course a checkbox "Do not ask again to deactivate REGEX".
The test shall be executed on all accounts, as the rule could be executed... On any account. The probability to have a false positive in, IMHO veeeery low.
WHY :
- it's QA on the fly
- it's beginners and newcomers friendly
- it's idiot proof
- It avoid debugging frustration and rant on forums ("it's a non working app, I can't make it working", when, in fact, the issue is located between the chair and the keyboard.).
...by the way, we could do exactly the same test/verification on case sensitivity...
I use regex in automated rule assignment
More than once, I forgot to activate then "regex" button. Quite annoying and not newcomers friendly.
thus, here is
MY MISH :
When a rule can be wrote in REGEX, on saving, the program will TEST the rule, WITHOUT and WITH regex activated.
...if REGEX was NOT activated (in the param windows), but A/ the rule WITHOUT regex activated (in exit test) give no result, and B/ the same rule WITH regex activated (in test) give some matchs, a popup window saying "you didn't activate REGEX, but it seems to be a regex rule..." shall appear, with two buttons "keep regex OFF", and "Oops, activate REGEX". And of course a checkbox "Do not ask to activate REGEX again".
Same if REGEX was activated and A/ the rule WITHOUT regex activated (in exit test) give matches, and B/ the same rule WITH regex activated (in test) give no matches, a popup window saying "you activated REGEX, but it seems to be a regular rule..." shall appear, with two buttons "keep regex ON", and "Oops, deactivate REGEX". And of course a checkbox "Do not ask again to deactivate REGEX".
The test shall be executed on all accounts, as the rule could be executed... On any account. The probability to have a false positive in, IMHO veeeery low.
WHY :
- it's QA on the fly
- it's beginners and newcomers friendly
- it's idiot proof
- It avoid debugging frustration and rant on forums ("it's a non working app, I can't make it working", when, in fact, the issue is located between the chair and the keyboard.).
...by the way, we could do exactly the same test/verification on case sensitivity...