Question

[Rule Chain] How does nested rules queries work?

  • 18 April 2016
  • 6 replies
  • 44 views

Didn't find the precise answer to this question in the Documentation, so let's go:



Does child rules are applied only to resulting customers of the Parent Rule?

Or does the child rules query results work independently of the parent's result?



Example: 100 customers



(A) Not Nested: 



- Rule 1 (20 resulting lines out of 100)

- Rule 2 (50 resulting lines out of 100)

- Rule 3 (10 resulting lines out of 100)



(B) Nested:



- Parent Rule 1 (20 resulting lines out of 100)

--- Child Rule 2 (5 resulting lines out of 20)

--- Child Rule 3 (3 resulting lines out of 20)



If it works like (A), then probably all child CTA rules will need controls so the CTA doesn't open over and over again.



Thanks,

Bruno

6 replies

Userlevel 5
It works like what you described in (A). Use the same CTA name across the rules to avoid duplication.



Nested rules are meant to stop child rules from executing when parent rules fails.



Does this help?
Hi Sundar,



Thanks for the reply.



What happens if the parent rule partially fail?



Morever, what do you mean by "Use the same CTA name across the rules to avoid duplication"? 



Thanks
Userlevel 5
When the parent rule partially fails then child rules will not run.

If you see this article, in create CTA action you will see the option "Include in identifier". If you have the same name for CTA across those rules and check this box, then duplicates will not be created if one already exists.
Following this thread - is there a way to make the rule chain nested?



If I want the child rule to be applied only on the results of the parent rule, is that possible?



Maybe there is a field that we can use for that as condition in the child rule?



Thanks much!



Aviv.
Userlevel 5
Rule chain does not carry the result from Rule 1 to Rule 2, you have to write a flag into destination to identify the resulting records and then use that as a filter criteria in the successive rules. 

We are in building a new rule type "Bionic Rule" which will address your usecase.
I understand, thank you!

Reply