An override RuleSet contains rules that by design override rules in other, non-override RuleSets.
For example, you can include enterprise-wide information (such as a company logo image, in a binary file rule) in an override RuleSet. A retail chain that operates many stores in multiple states can create an override rule to force the sales price of an item to a uniform value company wide.
Override RuleSets cannot contain:
As you log in, Process Commander develops a RuleSet list from the information in your access group and rules that it references. Override RuleSet Versions appear at the top of the RuleSet list and during rule resolution supersede any rules with identical names found in RuleSet Versions lower in your RuleSet list.
For example, after installing an application that contains many locked RuleSets, a business can choose to override a small subset of the locked rules by creating an override RuleSet for the entire organization. Other override RuleSets might apply to regions or divisions of the organization.
A rule in an override RuleSet
can't override a rule with Availability set to
Final
. (This is checked when you save the rule,
not at runtime.)
To mark a RuleSet as an override RuleSet, set the
Type on the Category tab of the RuleSet form to
Override
. Add, update, and test rules in any
Version of the RuleSet using normal development tools.
This change is permanent.
Once a RuleSet is marked as Override
, the category
Type cannot later be changed.
To include an override RuleSet in your own RuleSet list, identify the RuleSet in the Override RuleSets array on the Advanced tab of an application rule referenced by your access group.
Rules in an override RuleSet
can't be checked out. You can add, update, or delete such
rules, or change the availability to Blocked
or
Withdrawn
.
context-free expressions, override, RuleSet list, rule resolution | |
About
RuleSets
About Application rules How the system assembles and uses your RuleSet list |