Class OrderConstraintsType

java.lang.Object
com.evolveum.midpoint.prism.impl.binding.AbstractMutableContainerable
com.evolveum.midpoint.xml.ns._public.common.common_3.OrderConstraintsType
All Implemented Interfaces:
Containerable, Freezable, ContainerablePrismBinding, DebugDumpable, Serializable, Cloneable

public class OrderConstraintsType extends AbstractMutableContainerable
Constraint that defines the range of "orders" and relations when this assignment/inducement should be applied. Set of orderConstraint definitions are evaluated together. Each orderConstraint item specifies number (or number range) of assignment path elements with a given relation. Therefore assignment path containing one manager relation and two default relations should be specified by two orderConstraint items. First one specifying relation manager and order 1, the other specifying default relation and order 2 - even though the total "order" of the assignment path is three. This is rather counter-intuitive, but it is current implementation.
See Also: