# PagedSearchCapabilityType (Complex Type)

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

Supertype: CapabilityType
How to handle paged searches. Although deals primarily with GUI issues, may be useful for other kinds of access as well. If not present, paged searches are not enabled for this resource/kind/intent/objectClass. EXPERIMENTAL.

Item Summary
Name | Type | Multiplicity | Description
--- | --- | --- | ---
enabled | property boolean | [0,1] | Element specifying whether the capability is enabled or disabled.
defaultSortField | property QName | [0,1] | If no sorting is specified by client (higher levels), use this field as the default.
defaultSortDirection | property OrderDirectionType | [0,1] | If the defaultSortField is used, this element specified the sorting order (ascending is the default).

- ### Items

  - #### enabled

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Element specifying whether the capability is enabled or disabled. Enabled capability work as usual (this is the default). Disabled capability acts as it is not there at all. This is used to disable undesirable native capabilities. Each capability definition should have this element. It is made a top-level element in this XSD definition to make that easier.

  - #### defaultSortField

    Flags: RAM,runtime

    Multiplicity: [0,1]

    If no sorting is specified by client (higher levels), use this field as the default.

  - #### defaultSortDirection

    Flags: RAM,runtime,AVals:2

    Multiplicity: [0,1]

    If the defaultSortField is used, this element specified the sorting order (ascending is the default).