Figure 1P-12 - Detailed PolicySet

A PolicySet has two attributes. The isMandatoryEvaluation attribute is a Boolean attribute that, if TRUE, signifies that evaluation (and possibly action execution) of this entity is mandatory and must be attempted. If the Mandatory property value of this entity is FALSE, then the evaluation of this entity is considered to be “best effort” and may be ignored.<br/>The usage attribute is a free-form string attribute that recommends how this policy object should be used.<br/>The ContainedPolicySets aggregation is used to gather together discrete PolicySet objects to form a group of PolicySet objects. Such a group must share the same DecisionStrategy. Its semantics are implemented by the ContainedPolicySetsDetail association class.<br/>The ContainedPolicySetsDetail association class represents the semantics of the ContainedPolicySets aggregation. It provides additional semantics that enable this grouping of PolicySets to be prioritized and enabled, so that they can interwork with other PolicyRules and PolicyGroups. Note that each object in this aggregation must have the exact same decision strategy. It defines two attributes. The first, enabled, is an enumerated integer. If its value is 1 (which means enabled), then this signifies that this object is enabled for evaluation. If its value is 3 (which means that it is enabled for debugging), then this rule can be used in test or debug scenarios. If its value is 2, then this object is disabled and cannot be used or evaluated.<br/>Note that this object still might end up being disabled, even if this attribute is TRUE. For example, an associated PolicyTimePeriodCondition might evaluate to FALSE, effectively disabling this object. <br/>The second attribute, priority, is a non-negative integer that is used to prioritize PolicyRules among each other, and/or PolicyGroups that are contained within a PolicyRule. Larger integer values indicate higher priority<br/>Priorities apply to PolicySets (e.g., PolicyGroups and PolicyRules) and are to be used at the same level of scoping. That is, if a PolicyGroup contains n PolicyGroups or PolicyRules, the priority of the outermost (or parent) PolicyGroup can be compared with either stand-alone PolicyRules or PolicyGroups (at that same level of nesting).<br/>The default setting of this attribute is zero.<br/>