# ComplexAttributeTypeDefinitionType (Complex Type)

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

TODO

Item Summary
Name | Type | Multiplicity | Description
--- | --- | --- | ---
name | property QName | [1,1] | The name of the association type.
displayName | property string | [0,1] | Human readable name.
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.
delineation | container ResourceObjectTypeDelineationType | [1,1] | TODO
focus | container ResourceObjectFocusSpecificationType | [0,1] | Type of the focus objects that correspond to this resource object type.
attribute | container ResourceAttributeDefinitionType | [0,-1] | Specification of handling of attributes of this complex type.

- ### Items

  - #### name

    Flags: RAM,runtime

    Multiplicity: [1,1]

    Display order:

    The name of the association type. It must be either unqualified, or in the "ri" namespace.

  - #### displayName

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Human readable name. This name may be displayed in tools and GUIs to provide more pleasant user experience, as the XML data type names or object names may look quite frightening.

    The "displayName" should contain a value that is readable for almost any user. It is never used in the "logic", it is used only for display purposes.

    The use of national characters is in "displayName" is fully supported.

    DisplayName is reused in several location, but the meaning is still the same.

  - #### description

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    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]

    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.

  - #### lifecycleState

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    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.

  - #### delineation

    Flags: RAM,runtime

    Multiplicity: [1,1]

    Display order:

    TODO

  - #### focus

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Type of the focus objects that correspond to this resource object type. TODO change the type (ResourceObjectFocusSpecificationType) to something specific for complex attributes.

  - #### attribute

    Flags: RAM,runtime

    Multiplicity: [0,-1]

    Display order:

    Specification of handling of attributes of this complex type.