With the new multi layered and cascading Business Rules we are finding that what was working fine no longer works in the same way.

 

We thought that after some support from the SD+ team that we understood what was now happening but it doesn't appear to be so.

 

We use Business Rules (at the moment) only for filtering incoming emails and we had about 15 Business Rules that worked like a conveyor belt, i.e. each time an email found a match/fit within a rule it was handled accordingly and nothing further happened.

 

We had one rule that processed an incoming error alert email with specific content indicating that a particular site's server was offline. It set a level of severity, allocated it to a site etc etc.

 

This rule is/was about number 7 of the 15.

 

When we went over to cascading rules anything that would match rules 1-7 worked fine, but everything else seemed also to trigger rule 7.

 

So we have taken rule 7 out of the top level/default site list and put it into a list just for that site. We have tried turning various rules off but still seem to be getting the same problem.

 

So our question is, what is the process for checking Business Rules. Do they first hit the general/default list, complete that and then go through each of the site lists?  My understanding was that it went through the default list and if no match found it was processed by the last rule in the list? If that is the case, how do you handle a message at site list level or are they used once a job has been raised and allocated to a site, i.e. has no effect prior to this?

 

Also, the term cascading, in the general list if say rule 5 has cascading turned off, does that mean that the incoming email will not be checked against rule 6?

 

What we really want is what we had before, the default list processes the incoming email until it hits a match and off it goes to created a job with the set fields. If it doesn't find any match at all then do the default request.

 

Thanks for any pointers - Terry