# EvaluatedExclusionTriggerType (Complex Type)

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

Supertype: EvaluatedPolicyRuleTriggerType

Item Summary
Name | Type | Multiplicity | Description
--- | --- | --- | ---
ref | property int | [0,1] |
triggerId | property int | [0,1] |
ruleName | property string | [0,1] |
constraintName | property string | [0,1] |
constraintKind | property PolicyConstraintKindType | [0,1] |
message | property LocalizableMessageType | [0,1] |
shortMessage | property LocalizableMessageType | [0,1] |
presentationOrder | property int | [0,1] |
final | property boolean | [0,1] |
hidden | property boolean | [0,1] |
conflictingObjectRef | reference ObjectReferenceType | [0,1] |
conflictingObjectDisplayName | property PolyStringType | [0,1] |
conflictingObjectPath | property AssignmentPathType | [0,1] |
conflictingAssignment | container AssignmentType | [0,1] | Generic assignments of one object to another object.

- ### Items

  - #### ref

    Flags: RAM,runtime

    Multiplicity: [0,1]

  - #### triggerId

    Flags: RAM,runtime

    Multiplicity: [0,1]

  - #### ruleName

    Flags: RAM,runtime

    Multiplicity: [0,1]

  - #### constraintName

    Flags: RAM,runtime

    Multiplicity: [0,1]

  - #### constraintKind

    Flags: RAM,runtime,AVals:17

    Multiplicity: [0,1]

  - #### message

    Flags: RAM,runtime

    Multiplicity: [0,1]

  - #### shortMessage

    Flags: RAM,runtime

    Multiplicity: [0,1]

  - #### presentationOrder

    Flags: RAM,runtime

    Multiplicity: [0,1]

  - #### final

    Flags: RAM,runtime

    Multiplicity: [0,1]

  - #### hidden

    Flags: RAM,runtime

    Multiplicity: [0,1]

  - #### conflictingObjectRef

    Flags: RAM

    Multiplicity: [0,1]

  - #### conflictingObjectDisplayName

    Flags: RAM,runtime

    Multiplicity: [0,1]

  - #### conflictingObjectPath

    Flags: RAM,runtime

    Multiplicity: [0,1]

  - #### conflictingAssignment

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Generic assignments of one object to another object. This will usually be assignment of a role to a user, assignment of an organizational unit, team or whatever. It may also be used to assign role to another role, creating a role hierarchy. Assignment is an abstract concept. It can be anything that gives the "receptor" object additional access rights, privileges, capabilities or similar ability or right. But it may also constraint the object with policy, e.g. to implement separation of duties. Roles, organizations and privileges in IDM system are examples of assignments. The assignment may target either existing IDM object (such as a role) or abstract resource account that may or may not exist. In case of resource objects it is constrained to accounts, as accounts are the only resource objects that can be assigned to a user. Other resource objects (entitlements) can be assigned to accounts, but not to users. TODO: constraints