---
category: [Administration & Integrations, Platform and Product Extensions, Platform and Product Extensions/Integration, Administration & Integrations/Custom Integrations & Apps, Platform and Product Extensions/Workday Extend]
keyword: [Extend, Presentation Components, widgets, tags, UI components]
nav: wcp_docs
parent_url: /wcp_docs/
title: presentation
layout: subsection
wd_wcptag: presentation
---

<a id="section_N10021_N1001E_N10001"></a>
The main subschema of the Page Metadata that contains all visual components of a page. The `presentation` property contains the header, body, and footer of a page.

<a id="section_xz1_wjc_ccb"></a>
The `presentation` tag is always required in a PMD. Use `presentation` on view and edit pages.

## <a id="section_lg4_v1g_khb"></a>Mobile Support

Android, iOS

## <a id="section_qpw_1kc_ccb"></a>Attributes

-   <b>applicationExceptions</b>

    Data type: array

    List of `applicationException` tags that the page can render. You can conditionally set the `render` attribute in the `applicationException` to display the exception window when an error is encountered on page load.

-   <b>headerSize</b>

    Data type: string

    Defines the size of the page header. Valid values:

    -   STANDARD - (Default) Displays the standard Workday page banner containing the page title.
    -   HIDDEN - Hides the page banner and page title.

-   <b>body</b>

    Data type: body

    Wraps a collection of page widgets within a container or layout widget. Valid `body`tags include:

    -   [section](/wcp_docs/wjy1524108289078.html)
    -   [fieldSet](/wcp_docs/qim1518457781328.html)
    -   [hub](/wcp_docs/qum1635896773979.html)
    -   [listDetailHub](/wcp_docs/fki1636492536198.html)
    -   [editWizard](/wcp_docs/GUID-e22407f5-5782-4e59-a714-85499158a0bb-enHYPHENus.html)

-   <b>cancelOverride</b>

    Data type: taskReference

    Defines the task that the <b>Cancel</b> button should navigate to, which overrides the default behavior. By default, the <b>Cancel</b> button on an edit page navigates to the previous page.

    Example:

    ```
    "cancelOverride": {
    "taskId": "aPageTaskId"
    }
    ```

-   <b>dirtyPage</b>

    Data type: binding-Boolean

    If true, the edit page always displays a confirmation window when the user clicks <b>Cancel</b>. The default is false. By default, the confirmation window displays only if the user has modified the page before clicking <b>Cancel</b>.

-   <b>extender</b>

    Data type: bpExtender

    A page extension for container widgets. Currently only used with `bpExtender`. See `bpExtender` for details.

-   <b>footer</b>

    Data type: footer tag

    The [footer](/wcp_docs/wnf1518114200880.html) tag and a collection of widgets that appear at the bottom of the page.

-   <b>micro</b>

    Data type: boolean

    If true, we render the page as a popup window. Set this attribute if you plan to use popup windows in an edit flow.

    <b>Note:</b> You can only start a micro edit flow from a view page. An edit page that starts a micro edit flow can cause undefined behavior. Example: An edit page can't have a button that links to a micro edit page.

    When the app user clicks <b>OK</b>, the popup window closes when one of these conditions is true:

    -   The flow leads to a page whose `presentation` subschema contains `"microConclusion" : true`.
    -   The `presentation` subschema of the popup window contains `"microFirstPageOnly" : true` and the flow leads to another page. If `microFirstPageOnly` is false, the next page in the flow continues to render in a popup window.

-   <b>microConclusion</b>

    Data type: boolean

    If true, the page displays a green message window indicating that the edit flow is complete. You can use `microConclusion` in an edit flow with popup windows that set the `micro` attribute. When the app user clicks <b>OK</b> on the preceding popup window, we close it and display a message such as this: <i>Your changes have been saved</i>. If the only purpose of the PMD is to end the edit flow with a confirmation message, the PMD that uses `microConclusion` can be an empty page. Example:

    ```
    {
      "id": "microConclusionPage",
      "endPoints": [],
      "presentation": {
          "microConclusion": "true",
          "body": {
              "type": "section",
              "horizontal": "true",
              "children": []
          }
      }
    }
    ```

-   <b>microFirstPageOnly</b>

    Data type: boolean

    If true, we display only the first page in an edit flow as a popup window. Use `microFirstPageOnly` with the `micro` attribute. When the app user clicks <b>OK</b> on the popup window, the second page in the flow renders as a regular page. If `microFirstPageOnly` is false or not set, the subsequent pages in the edit flow render as popup windows.

    <b>Note:</b> You can only start a micro edit flow from a view page. An edit page that starts a micro edit flow can cause undefined behavior. Example: An edit page can't have a button that links to a micro edit page.

-   <b>pageType</b>

    Data type: string

    Defines the type of page to render. Valid values:

    -   `view` - The app user can't edit the widgets on the page. All widgets are read-only.
    -   `edit` - The app user can interact with the widgets and enter data on the page. An edit page displays the <b>OK</b> and <b>Cancel</b> buttons. The page becomes an edit page if `presentation` contains `"pageType": "edit"` or if the PMD has `outboundEndpoints`.
    -   `confirm` - Similar to a view page, and also displays a <b>Done</b> button at the bottom. Use `"pageType": "confirm"` on a conclusion page that ends a flow.

-   <b>preferredLabelPosition</b>

    Sets the label position of all widgets on the page. Valid values:

    -   `atop` - The labels display on top of the widgets. `atop` is the default position.
    -   `aside` - The labels display on the left of the widgets.
    -   `amiss` - The labels don't display.

-   <b>standardEditButtonsHidden</b>

    If true, the edit page hides the standard edit (<b>OK</b> and <b>Cancel</b>) buttons. Use `standardEditButtonsHidden` to:

    -   Conditionally hide the standard edit buttons.
    -   Use custom edit buttons instead of the standard edit buttons. To display custom edit buttons, set `"standardEditButtonsHidden" : true` with the `editButtonBar` tag.

-   <b>tabs</b>

    Data type: list of tag objects

    An array of tags that display as tabbed sections on the page. Each tab displays the `label` attribute of the contained tag as the tab heading.

    You can use these tags within `tabs`:

    -   `grid`
    -   `fieldSet`
    -   `section`

-   <b>title</b>

    Data type: title

    Defines the title at the top of the page and the browser tab.

    Example:

    ```
    "title": {
    "type": "title",
    "label": "Create Charity"
    }
    ```

    <b>Note:</b> The `titles` property in the SMD overrides the `title` attribute of the `presentation` tag on a PMD.



### Related Information

[Concept: Page Types](/wcp_docs/zrd1553321160092.html)

[Concept: Page Flows](/wcp_docs/zji1528861641063.html)

[Concept: Page Navigation](/wcp_docs/qoc1553369215127.html)

