# AssignmentEvaluationTraceType (Complex Type)

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

Supertype: TraceType
Trace for assignment evaluation operation.

Item Summary
Name | Type | Multiplicity | Description
--- | --- | --- | ---
text | property string | [0,-1] | Unstructured text information to be used when existing structure is not sufficient.
assignmentOld | container AssignmentType | [1,1] | Generic assignments of one object to another object.
assignmentDelta | property ItemDeltaType | [1,1] |
assignmentNew | container AssignmentType | [1,1] | Generic assignments of one object to another object.
primaryAssignmentMode | property PlusMinusZeroType | [1,1] |
evaluateOld | property boolean | [1,1] |
textSource | property string | [0,1] |
sourceDescription | property string | [1,1] |
textResult | property string | [0,1] |

- ### Items

  - #### text

    Flags: RAM,runtime

    Multiplicity: [0,-1]

    Unstructured text information to be used when existing structure is not sufficient.

  - #### assignmentOld

    Flags: RAM,runtime

    Multiplicity: [1,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

  - #### assignmentDelta

    Flags: RAM,runtime

    Multiplicity: [1,1]

  - #### assignmentNew

    Flags: RAM,runtime

    Multiplicity: [1,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

  - #### primaryAssignmentMode

    Flags: RAM,runtime,AVals:3

    Multiplicity: [1,1]

  - #### evaluateOld

    Flags: RAM,runtime

    Multiplicity: [1,1]

  - #### textSource

    Flags: RAM,runtime

    Multiplicity: [0,1]

  - #### sourceDescription

    Flags: RAM,runtime

    Multiplicity: [1,1]

  - #### textResult

    Flags: RAM,runtime

    Multiplicity: [0,1]