# TransitionPolicyConstraintType (Complex Type)

### Namespace: http://midpoint.evolveum.com/xml/ns/public/common/common-3

Supertype: AbstractPolicyConstraintType
Specifies how the inner constraints are to be evaluated with regard to operation start and end state. May not include any transitional constraints itself!

Item Summary
Name | Type | Multiplicity | Description
--- | --- | --- | ---
name | property string | [0,1] | Identifier of the constraint.
description | property string | [0,1] |
documentation | property string | [0,1] | Technical documentation for a particular object or construct.
presentation | container PolicyConstraintPresentationType | [0,1] | How should be triggering of this constraint presented, e.
stateBefore | property boolean | [0,1] | Expected inner constraint state before the operation.
stateAfter | property boolean | [0,1] | Expected inner constraint state after the operation.
constraints | container PolicyConstraintsType | [1,1] | Non-transitional policy constraints to be evaluated.

- ### Items

  - #### name

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    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.

  - #### description

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

  - #### documentation

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Technical documentation for a particular object or construct.

    The purpose of this element is to document system configuration and behavior. The documentation will not be presented to end users. In fact, it will probably not be presented at all in midPoint user interface. This documentation element is supposed to be a part of the technical documentation of midPoint deployment. The tools than generate deployment configuration will look for these elements and combine them to compiled documentation document.

    AsciiDoc formatting is assumed for this element. Any leading or trailing whitespace is skipped. Indentation equivalent to he indentation of the first non-blank line of text is also skipped.

  - #### presentation

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    How should be triggering of this constraint presented, e.g. in enforcement messages, in approvals, in certification, in notifications, etc.

  - #### stateBefore

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Expected inner constraint state before the operation. True means the constraint must evaluate to true. False means the constraint must evaluate to false. Unspecified means the constraint is not checked before the operation.

  - #### stateAfter

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Expected inner constraint state after the operation. True means the constraint must evaluate to true. False means the constraint must evaluate to false. Unspecified means the constraint is not checked after the operation.

  - #### constraints

    Flags: RAM,runtime

    Multiplicity: [1,1]

    Display order:

    Non-transitional policy constraints to be evaluated.