A base rule is the fallback rule selected by rule resolution when no other circumstance version's criteria is met. Base rules have no circumstance qualification.
A base rule must exist for every circumstance rule.
- Circumstance rules are valid only when certain qualifications are met. You cannot delete a base rule when a circumstance rule with the same key exists; the circumstance version provides a fallback.
- For rules with an Apply to key part, the base rule can have an Apply to class that is a parent or ancestor class of the Apply to class of the circumstance rule.
- You cannot check out a rule that is a base rule when a related circumstance rule is checked out.
- You cannot check out the base rule of a date circumstance rule at a time between the start and end date and time.
- If a date circumstance stream rule contains JSP tags (rather than directives), the base rule must also contain JSP tags rather than directives. Conversely, if the date-circumstanced rule contains directives, the base rule must contain directives.
- In releases before PRPC Version 5.2, circumstance rules with a ruleset version number lower than the ruleset version of a base rule were ignored (never selected) during rule resolution. Starting with PRPC Version 5.2, this is not the default rule resolution behavior. You can copy a base rule to a higher version without the need to also copy each of the (possibly many) circumstanced rules associated with the base rule into that higher version. While not recommended, you can revert to previous behavior by selecting the Base Rule check box on the form produced by the Availability label on the rule toolbar. The Base Rule check box only impacts rule resolution. Other tools, such as skimming a ruleset, do not honor the check box.