The following example explains more about interpreting a combination of AND and OR relations.
For example, you have this filter:
CountryCode ="DK" AND LocationCode ="1" OR Status = "Open"
Given a business entity where the fields in question have these values:
LocationCode = "2"
Status = "Open"
the filter evaluates as True - meaning that this business entity would be selected by the filter. But was that the intention? The intention might really have been to express this:
CountryCode ="DK" AND (LocationCode ="1" OR Status = "Open")
or, in more accessible terms: select the business entity if the country code is "DK" and, either the location code is "1" or the Status is "Open."
Because there is no way to put the parentheses in, it is not possible to express the second version in Business Notification.
The solution is to create two schemes:
A scheme with a filter like this: CountryCode = “DK” AND LocationCode = “1”.
And a scheme with a filter like this: CountryCode = “DK” AND Status = “Open”.
In the example above, by creating two schemes, the business entity would not be selected by any of these filters (and this was the intention.) Of course, users will have to subscribe to both schemes in order to get the notifications as intended.