---
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: dropDownButton
layout: subsection
wd_wcptag: dropDownButton
---

<a id="section_N10021_N1001E_N10001"></a>
Creates a button that displays a drop-down list of options. Use `dropDownButton` on view and edit pages.

Use `dropDownButton` on its own or as an inline button on the `panelList` tag.

Specify the drop-down list of options in the `values` attribute. Note that you can only specify internal app links using the `taskReference` for the page `taskId`. For external site navigation, use the `externalLink` tag instead of the `dropDownButton` tag.

## <a id="section_xc1_3sq_h2b"></a>Example

This sample `dropDownButton` displays a button with a dropdown list of navigation options. In this example, `workerDetails` and `assignPartner` are sample pages in the app.

```
{
 "type" : "dropDownButton",
 "action" : "PRIMARY",
 "id": "dropDownButtonList",
 "label" : "dropDownButton Example",
 "values" : [
   {
     "label" : "<% savedWorkerName.value %>",
     "taskReference" : {
       "type" : "taskReference",
       "taskId" : "workerDetails",
       "parameterBindings": {
         "workerId": "<% savedWorkerId.value %>"
       }
     }
   },
   {
     "label" : "Assign a Partner",
     "taskReference" : {
       "type" : "taskReference",
       "taskId" : "assignPartner"
     }
   }
 ]
}
```

## <a id="section-mobile-support"></a>Mobile Support

Android, iOS

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

-   <b>action</b>

    Data type: string

    The display style of the button. Valid values:

    -   `PRIMARY` - Displays a button with high emphasis. This display style is typically for designating the primary action that moves the user forward in a process.
    -   `AUXILIARY` - (Default) Displays a button with medium emphasis. This display style is typically for:

        -   Secondary actions on a screen.
        -   Canceling a process.
        -   Taking an action that moves the user away from a process.

    -   `LINK` - Displays a link. This display style is for a page navigation option. Not supported in the Workday mobile app.

-   <b>enabled</b>

    Data type: dynamicBinding-Boolean

    If true, users can enter values on the widget. If false, users can only view the widget.

-   <b>helpText</b>

    Data type: binding-String

    Text that displays when a user hovers their cursor over the widget.

    <b>Note:</b> The Chrome browser truncates the tooltip to 1400 characters.

-   <b>id</b>

    Data type: binding-String

    Unique identifier used to reference this widget from other tags.

    Notes:

    -   The `id` must start with a letter.
    -   The `id` must be unique per page.
    -   To enable other widgets to reference this widget `id`, place this widget before the other widgets on the PMD. The PMD validation returns an "Undefined variable" error if it doesn't find a previously defined `id` in the PMD.
    -   Workday recommends that you include the `id` in your tag definitions for debugging purposes.

-   <b>label</b>

    Data type: dynamicBinding-String

    Text that displays beside or above most widgets. Often used in simple widgets that include inputs.

    The maximum number of characters is 255.

-   <b>render</b>

    Data type: binding-Boolean

    If true, this tag renders as a widget on the page. If false, the loaded page doesn't add this tag or its children. The default is true.

    Unlike the `visible` attribute, when `render` is false, other tags on the page can't reference this tag or widget on edit pages. On view pages, a tag can't reference other tags regardless of the `render` attribute value.

-   <b>required</b>

    Data type: dynamicBinding-Boolean

    If true, the user must enter a value on the widget before submitting the page.

-   <b>sortOrder</b>

    Data type: binding-String

    When you set `sorted` to true on the `section` or `fieldSet` parent of this widget, the `sortOrder` attribute determines the order of this widget within its parent. The sort order is relative to the siblings of the widget.

    Typical values are "a", "b", "c", and so on. Example: The widget with `"sortOrder": "a"` displays before the widget with `"sortOrder": "b"`.

    <b>Note:</b> The `sortOrder` doesn't apply to sorting data on the widget. `sortOrder` only applies to the placement order of the widgets within the parent widget.

-   <b>values</b>

    Data type: list of commandButtonValueDefinition objects

    An array that lists the options on the list displayed by the `dropDownButton`. For each value, use these attributes:

    -   `label` - A string binding displayed as an option on the dropdown list. Example: `<% myButton.label %>`
    -   `taskReference` - Contains a reference to a task that the user navigates to after selecting the option. Use this for intra-site navigation. Example:

        ```
        {
          "label": "Edit Job Profile",
          "taskReference": {
            "taskId": "editJobProfile"
          }
        }
        ```

    -   `commandHttpMethod` - The method used with the HTTP request, such as the endpoint request submitted by the specified taskReference. Valid values:

        -   `GET` - Renders a view page (default).
        -   `POST` - Omits the page destination of the button from the browser history. This method is useful for non-repeatable tasks.


-   <b>visible</b>

    Data type: dynamicBinding-Boolean

    If true, the widget generated by this tag is visible. If false, this tag and its children tags aren't visible. This tag provides the ability to display or hide the widget dynamically based on user interactions on the page. The default is true. Unlike the `render` attribute, the generated widget persists on the page even when `visible` is false.

    <b>Notes:</b>

    -   When the widget or field you’re hiding changes on the page, you must include it inside a `fieldSet`.
    -   When the `visible` attribute is false for this widget on an edit page, the outbound endpoint doesn't include the `valueOutBinding` or `valuesOut` data of the widget in the payload. To include the `valueOutBinding` or `valuesOut` data in the payload, use the `onSend` event handler.



### Related Information

[Tutorial: Navigate Pages with Buttons and Button Groups](https://wd5.myworkday.com/workday/learning/course/62d106356d1b10051260edf509b90000?type=9882927d138b100019b928e75843018d)

