# GuiObjectDetailsPageType (Complex Type)

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

Supertype: AbstractObjectTypeConfigurationType
Specifies form that are used for displaying and editing of specific object type

Item Summary
Name | Type | Multiplicity | Description
--- | --- | --- | ---
type | property QName | [1,1] |
roleRelation | container RoleRelationObjectSpecificationType | [0,1] | Definition of object with respect to subject relation to a role.
summaryPanel | container SummaryPanelSpecificationType | [0,1] | Specifies the look and feel of the summary panel.
saveMethod | property DetailsPageSaveMethodType | [0,1] | Specifies the method how page save/preview buttons are shown and processed.
forms | container ObjectFormType | [0,1] | Specification of forms (tabs) to be used on object details page.
container | container VirtualContainersSpecificationType | [0,-1] | Used to specify "virtual" containers for displaying details page in GUI.

- ### Items

  - #### type

    Flags: RAM,runtime

    Multiplicity: [1,1]

  - #### roleRelation

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Definition of object with respect to subject relation to a role. Used to specify role approvers, owners and so on.

    EXPERIMENTAL. Use at your own risk.

  - #### summaryPanel

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Specifies the look and feel of the summary panel.

  - #### saveMethod

    Flags: RAM,runtime,AVals:2

    Multiplicity: [0,1]

    Specifies the method how page save/preview buttons are shown and processed.

  - #### forms

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Specification of forms (tabs) to be used on object details page.

    NOTE: As of midPoint 4.0 this works for archetypes only. It is not supposed to work anywhere else than in archetypePolicy.

  - #### container

    Flags: RAM,runtime

    Multiplicity: [0,-1]

    Used to specify "virtual" containers for displaying details page in GUI. As an example, the user might need to reorganize attributes to some logic block such as personal info, basic info, additional info. Each of this section should have only attributes which belong to it, e.g. given name, family name, date of the birth are attributes corresponding to the personal info. Basic info section will contains attributes describing organizationalUnit, emailAddress or job position and additional info will contain attributes about user's nickname and so on.