How rule sets are applied

When creating your rule sets, be aware of the following

• A rule can have multiple conditions and actions.
• An action can have multiple variable substitutions.
• A condition can have an action that affects multiple service provider types
• A variable substitution can be used independently.
• Only headers used in the conditions element of the rule can be used in variable substitution.
• Rules are not applied in the same order as they appear in a rule set. If you have conflicting rules, results will be inconsistent. Rules that are more specific (that is, have more conditions) are evaluated first. When a header is used in multiple rules that use the same number of conditions, all of those rules are evaluated and actions can be applied where conditions are true. For more information, see Example 3 in Format of a rule set.
• If a property is changed by two rules in the same ruleset, message BAQR1204W is issued.
• When more than one condition is specified in a single rule, all conditions must be met for the actions to be performed
• When match="ANY_VALUE" is used in a condition, the value attribute is still required on that condition element (as value=""). The condition will be met when the named header is present on an API request, regardless of the headers value.
• Leading and trailing white space for each comma-separated value is ignored.
• Property names are case sensitive.
• The value of the imsTranCode property is not checked. You must validate the value in your application.
• If you update a valid ruleset with an invalid ruleset, the old rules are removed.