# ItemProcessingResultPolicyConstraintType (Complex Type)

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

Supertype: AbstractPolicyConstraintType
Constraint based on the result of the processing for one object that is processed by the activity.

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.
status | property OperationResultStatusType | [0,-1] | Operation result status to match.
errorCategory | property ErrorCategoryType | [0,-1] | Error category (network, security, policy, .

- ### 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.

  - #### status

    Flags: RAM,runtime,AVals:8

    Multiplicity: [0,-1]

    Display order:

    Operation result status to match. It can be either PARTIAL_ERROR or FATAL_ERROR. If not present, we decide solely on error category. If error categories are not specified, any error matches.

  - #### errorCategory

    Flags: RAM,runtime,AVals:9

    Multiplicity: [0,-1]

    Display order:

    Error category (network, security, policy, ...) to match. NOTE: that some errors are not propagated to the level where they can be recognized by this selector. If not present, we decide solely on the status.