# ShadowAssociationTypeNewDefinitionType (Complex Type)

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

TODO

Item Summary
Name | Type | Multiplicity | Description
--- | --- | --- | ---
name | property QName | [0,1] | The name of the association type.
description | property string | [0,1] | Free-form textual description of the object.
documentation | property string | [0,1] | Technical documentation for a particular object or construct.
lifecycleState | property string | [0,1] | Lifecycle state of the object.
subject | container ShadowAssociationTypeNewSubjectDefinitionType | [0,1] | TODO
focus | container ShadowAssociationTypeFocusDefinitionType | [0,1] | TODO
attribute | container ResourceAttributeDefinitionType | [0,-1] | TODO
association | container ResourceObjectAssociationType | [0,-1] | TODO
activation | container ResourceActivationDefinitionType | [0,1] | Definition of activation handling for this account type.
correlation | container CorrelationDefinitionType | [0,1] | How objects of this type are correlated to focus objects?
synchronization | container SynchronizationReactionsType | [0,1] | Defines reactions to specific synchronization-related situations (like "unmatched resource object", or "disputed" (owner), and so on.

- ### Items

  - #### name

    Flags: RAM,runtime

    Multiplicity: [0,1]

    The name of the association type. The namespace must be "ri:" or none.

  - #### description

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Free-form textual description of the object. It is supposed to describe the object or a construct that it is attached to.

    This information may be presented to midPoint users, even to ordinary end users. For example role description may be presented to users when they are selecting roles to request. Therefore the description should be written in a language that the users can understand.

    Description is assumed to be a plan, non-formatted text. Amount of white space is considered insignificant. E.g. leading and trailing white space may be skipped, multiple spaces can be collapsed to one and so on.

  - #### documentation

    Flags: RAM,runtime

    Multiplicity: [0,1]

    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.

  - #### lifecycleState

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Lifecycle state of the object. This property defines whether the object represents a draft, proposed definition, whether it is active, deprecated, archived, and so on. See "Object Lifecycle" in the documentation.

  - #### subject

    Flags: RAM,runtime

    Multiplicity: [0,1]

    TODO

  - #### focus

    Flags: RAM,runtime

    Multiplicity: [0,1]

    TODO

  - #### attribute

    Flags: RAM,runtime

    Multiplicity: [0,-1]

    TODO

  - #### association

    Flags: RAM,runtime

    Multiplicity: [0,-1]

    TODO

  - #### activation

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Definition of activation handling for this account type.

  - #### correlation

    Flags: RAM,runtime

    Multiplicity: [0,1]

    How objects of this type are correlated to focus objects?

  - #### synchronization

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Defines reactions to specific synchronization-related situations (like "unmatched resource object", or "disputed" (owner), and so on. Before 4.6, this information was part of the "synchronization" section of the resource definition.