The syntax for rule filters supports prefix-oriented Boolean operators (AND, OR, and NOT) and uses comma-separated name/value pairs to specify properties and numeric rule IDs. The wildcard operator (*) is also supported.
Here are the syntax requirements for specifying rule filters:
The following special characters cannot be a part of a property name or value: ( ) : , *
Property names are separated from property values with a colon (:). The example
<application>?N=0&Nmrf=state:approvedfilters for rules where state property has a value of approved.Name/value pairs are separated from other name/value pairs by a comma. The example
<application>?N=0&Nmrf=or(state:pending,state:approved)filters for rules where state property is either approved or pending.Rule IDs are specified by their numeric value. The example
<application>?N=0&Nmrf=5filters for a rule whose ID is 5.Multiple rule IDs, just like multiple name/value pairs, are also separated by a comma. The example
<application>?N=0&Nmrf=or(1,5,8)filters for rules where the value of the rule ID is either 1, 5, or 8.Boolean operators (AND, OR, and NOT) are available to compose complex combinations of property names, property values, and rule IDs. The example
<application>?N=0&Nmrf=and(image_path:/common/images/book.jpg,alt_text:*)filters for rules where the value of the image_path property is book.jpg and alt_text contains any value including null.Wildcard operators can substitute for any property value (not property name). The example
<application>?N=0&Nmrf=and(not(state:*),not(alt_text:*))filters for rules that contain no value for both the state property and alt_text property.
Boolean operators are reserved words, so property names or values such as "and," "or," and "not" are not valid in rule filters. However, properties can contain any superset of the Boolean operators such as "andrew", "bread and butter", or "not yellow".
Although the Boolean operators in rule filters are not case-sensitive, property names and values in the filter are case sensitive.
