The Property Configuration Settings content panel contains the rules for your property. Rules consist of match criteria and behaviors. If a request meets the conditions in a rule's match criteria, the behaviors in that rule are applied.
Property Manager applies a specific logic with the application of rules and the behaviors they contain. There are default settings that apply to every request. There are parent-level rules that can have nested child-level rules. And, there is a priority order in which all of your rule matches are applied. Before you begin, review Configuration best practices in the Property Manager documentation to get a better understanding of how rules are applied.
Your Ion property includes a host of rules that live as children to the Default Rule.
Some of these sub-rules have behaviors with options preset for best practice optimization. You can change them, but we recommend you leave them set as is.
Some sub-rules are optional. We've included them so you don't have to manually add them yourself from the behavior catalog. You can set them as desired, or leave them disabled.
Throughout these docs, these sub-rules are labeled as Required, Recommended—you can remove them, but they're best left in your property, or Optional—you don't have to include if it doesn't fit your needs. Specific requirements and usage are discussed in more detail in the description of each of these rules, later in this section.
As children of the Default Rule, these rules and their sub-rules apply to all requests—their Criteria is default set to Match All and some have additional "If" arguments that must be met. For best results, leave them at this setting. If you need to use one of these behaviors to match on specific requests, add a new rule, outside of the Default Rule, and set the appropriate match criteria for it.
Updated 3 months ago