Supertype: AbstractPolicyConstraintType

Constraints for collection stats (statistics). Can be used to trigger policy rules on the number of objects in collection, percentage and so on.

Policy rules with this constraint are ignored during normal processing. Evaluation of such policy rules require special handling (e.g. scanner task).

Item Summary
Name	Type	Multiplicity	Description
$itemDefinition.Name.LocalPart	property string	[0,1]	Identifier of the constraint.
$itemDefinition.Name.LocalPart	property string	[0,1]
$itemDefinition.Name.LocalPart	container PolicyConstraintPresentationType	[0,1]	How should be triggering of this constraint presented, e.
$itemDefinition.Name.LocalPart	container CollectionSpecificationType	[0,-1]	Refers to "itself" as a collection.

Items
- $itemDefinition.Name.LocalPart
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
  
  Identifier of the constraint. It is used when midPoint needs to refer to a specific constraint, e.g. in order to record exception. This element is formally specified as optional, mostly due to the compatibility reasons. But it has to be provided in order for some functionality to work correctly.
- $itemDefinition.Name.LocalPart
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
- $itemDefinition.Name.LocalPart
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
  
  How should be triggering of this constraint presented, e.g. in enforcement messages, in approvals, in certification, in notifications, etc.
- $itemDefinition.Name.LocalPart
  
  Flags: RAM,runtime
  
  Multiplicity: [0,-1]
  
  Refers to "itself" as a collection. This means that it interprets the object to which the rule applies as a collection. And this element specifies the details how the collection should be interpreted. E.g. whether we mean the list of objects that ObjectCollectionType refers to by filter. Or whether we mean assignees (owners/approvers) of that object.