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

<a id="section_N10021_N1001E_N10001"></a>
Creates a bar that displays multiple types of edit buttons at the bottom of an edit page.

To customize the edit buttons, specify [editButton](/wcp_docs/dof1530079947097.html) tags in the `editButtons` attribute of the `editButtonBar`. You can use `editButtonBar` to:

-   Modify the label and button type of the <b>OK</b> button.

    To change the label of the <b>OK</b> button, specify the `label` attribute of the `editButton` tag.

-   Display additional buttons as finalizing actions on the edit page.

    The `editButtonBar` tag can include only buttons that submit data like the default <b>OK</b> button. To define the page navigation for the custom buttons in the `editButtonBar`, configure the flow definitions in the AMD just like you would for the <b>OK</b> button.

    <b>Note:</b> You can't use the `editButtonBar` to customize the <b>Cancel</b> button. To hide the <b>Cancel</b> button, set `"standardEditButtonsHidden" : true` on the `presentation` tag.



Use `editButtonBar` only on edit pages.

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

This sample `editButtonBar` modifies the <b>OK</b> button label to <b>Submit</b>. It also adds another button.

```
{ 
  "type":"editButtonBar", 
  "editButtons": [ 
    { "type": "editButton", 
      "label": "Submit", 
      "id": "1", 
      "buttonType": "PRIMARY", 
      "ignoreRequiredFields": "true" 
    }, 
    { "type": "editButton", 
      "label": "Add related data", 
      "id": "2", 
      "buttonType": "AUXILIARY" 
    } 
  ] 
}
```

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

Android, iOS

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

-   <b>editButtons</b>

    Data type: list of editButton objects

    An array containing `editButton`s that display on the toolbar on an edit page.

-   <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>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.