Hello all,
Take this Common Incoming filters construct:
Filter 1: If A do 1 (Set to continue processing with other filters)
Sub-filter 1: If B do 2
Sub-filter 2: If C do 3
Filter 2: If D do 4
...
And now consider theses cases:
1.- A message that meets conditions A, B and D.
Only actions 1 and 2 are executed. Filter 2 is _not_ triggered even
though Filter 1 is set to continue.
2.- A message that meets conditions B and D.
Only action 2 is executed. When it should only execute 4 because, if
filter 1 did not have a match, sub-filter 1 should have never been
executed.
I could illustrate a few more cases, but I think these two are enough to
be able to say that sub-filters (common sub-filters) behave as if they
were normal filters and, in some cases, preventing the execution of any
account filters.
One very important note: The same construct works just fine if done at
Account level.
And a second note. I don't know if this bug is new to v3.0.2.4 Rush
because I had never tested Common filter before.
I have added BT report: https://www.ritlabs.com/bt/view.php?id=4021
--
Best regards,
Miguel A. Urech (El Escorial - Spain)
Using The Bat! v3.0.2.4 Rush on Windows 2000 5.0 Service Pack 4
Current beta is 3.0.2.4 Rush | 'Using TBBETA' information:
http://www.silverstones.com/thebat/TBUDLInfo.html
IMPORTANT: To register as a Beta tester, use this link first -
http://www.ritlabs.com/en/partners/testers/
