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

A widget that enables you to guide the user through a series of independent tasks. `editWizard` includes these components:

-   `title` and `subtitle`.
-   `editTasks` - A collapsible navigation pane containing a list of tasks. The list of tasks renders as a dropdown menu for smaller displays.
-   Optional summary view page where you can review all the fields from each task. For widgets that aren't supported on view pages, Workday converts the widget to a close counterpart for the view page. Example: `checkBoxList` renders as a list of text values on a view page.
-   Optional conclusion view page. The `editWizard` redirects to the conclusion page after the user submits the `editWizard`. You can use the conclusion page to show users a confirmation message that the update process has been submitted. Without the conclusion page, the `editWizard` navigates to the last viewed page by default.
-   Buttons that enable you to navigate to the next task or a previous task and submit data.
-   Optional <b>Save for Later</b> button and autosave. To enable both the <b>Save for Later</b> button and automatic saving of data on the current page of the `editWizard`, set the `enableSaving` attribute to true. You must also use `section` as the top-level container for each `editWizard` step page.


Use the `editWizard` widget only on a view page.

You can't use flows within an `editWizard`.

## <a id="section_3"></a>Prerequisites

-   Although the `editWizard` widget displays on a view page, each task within the `editWizard` must be an edit page. Each edit page renders as an embedded edit page within the `editWizard` widget.
-   `editWizard` must be the only tag within the `presentation` `body`.


Consider these guidelines and recommendations:

-   `editWizard` doesn't submit any outbound data until the user clicks the <b>OK</b> button.

    When you enter data and navigate to another page in the `editWizard`, your changes are cached on the server but no data is submitted. Navigating away from the `editWizard` without clicking <b>OK</b> discards the data.

-   Numerous widgets and outbound endpoints in editWizard can slow performance.

    Because `editWizard` submits all outbound endpoints after the user clicks the <b>OK</b> button, there may be a performance impact from having too many widgets and outbound endpoints on each edit page.

-   You can't pass data from one page to another in `editWizard`.

    An edit page can't use the data you intend to create on a previous page or anything from an endpoint. The `editWizard` submits all outbound endpoints on all the edit pages when the user reaches the last page and clicks the <b>OK</b> button. The `editWizard` is simply a mechanism that groups edit pages and encourages a user to go through them all at once.

-   `editWizard` doesn't support warnings. If you call the `setWarning` function on a page, `editWizard` displays an error when it submits the pages and encounters a warning.
-   Widget guidelines with `editWizard`:

    -   The edit pages within `editWizard` can use all widgets except `editButtonBar`.
    -   Include no more than 2-3 grids across all pages in the `editWizard` to avoid large amounts of data being cached.
    -   Don't use an `editWizard` page as a navigation task in a `hub`. However, you can use an `editWizard` page as an additional link in a `hub`.



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

```
{
"type" : "editWizard",
"title" : "Job Application",
"subtitle" : "Product Manager",
"summarySettings" :
  {
    "enabled" : true,
    "label" : "Review Application"
  },
"editTasks" : [
  {
    "label" : "Personal Information",
    "task" :
      {
        "taskId" : "personalInformation"
      }
  },
  {
    "label" : "Internal Hire Details",
    "render" : "<% queryParams.isInternalApplicant ?: false %>",
    "task" :
      {
        "taskId" : "internalHireDetails"
      }
  },
  {
    "label" : "Resume and Cover Letter",
    "task" :
      {
        "taskId" : "resume"
      }
  },
  {
    "label" : "Education and Employment History",
    "task" :
      {
        "taskId" : "educationAndEmployment"
      }
  },
  {
    "label" : "References",
    "task" :
      {
        "taskId" : "references"
      }
  }
]
}
```

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

Android, iOS

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

-   <b>editTasks</b>

    Data type: List of pages.

    (Required) The list of tasks in the `editWizard`. Each task must be an edit page that's independent of all other tasks in the `editWizard`.

    The maximum number of active tasks is 10. You can include more than 10 tasks as long as only 10 render at runtime.

    Each task includes these attributes:

    -   <b>label</b>

        Data type: stringScript

        (Required) The link title on the left navigation pane.

    -   <b>render</b>

        Data type: booleanScript

        If true, this item renders as a link on the left navigation pane. If false, the navigation pane doesn't add this link. The default is true.

    -   <b>task</b>

        Data type: staticTaskReference map

        (Required) The `StaticTaskReference` map contains these attributes:

        -   <b>taskId</b>

            Data type: string

            (Required) The `taskId` that corresponds to a page to display on the right pane. Ensure that you've defined the `taskId` in the AMD.

        -   <b>parameters</b>

            Data type: Map<String, StringScript>

            A map containing task parameters sent to the specified `taskId` page. Note that the parameter value supports PMD Scripting. The page can reference these parameters using the `queryParams` variable.



-   <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>title</b>

    Data type: stringScript

    The `editWizard` title, which displays at the top of the left navigation pane.

-   <b>subtitle</b>

    Data type: stringScript

    The `editWizard` subtitle, which displays at the top of the left navigation pane under the title.

-   <b>summarySettings</b>

    Data type: Nested object

    `summarySettings` contains these attributes:

    -   <b>label</b>

        Data type: stringScript

        Specify the summary page label in the sidebar. By default, the summary page label is <b>Review and Submit</b>.

    -   <b>enabled</b>

        Data type: booleanScript

        Specify whether the `editWizard` displays a summary page. The default is true.


-   <b>conclusion</b>

    Data type: Nested object

    Specifies the conclusion page that the `editWizard` redirects to after the user clicks <b>OK</b> on the `editWizard`. If you don't specify `conclusion` or if you set the `render` attribute to false, the `editWizard` navigates to the last viewed page.

    <b>Note:</b> App Preview doesn't redirect to the conclusion page. The `editWizard` redirects to the conclusion page only on the tenant.

    `conclusion` contains these attributes:

    -   <b>task</b>

        Data type: Nested object

        (Required) `task` contains these attributes:

        -   <b>taskId</b>

            Data type: string

            (Required) The `taskId` that corresponds to a view page. Ensure that you've defined the `taskId` in the AMD.

        -   <b>parameters</b>

            Data type: Map<String, StringScript>

            A map containing task parameters sent to the specified `taskId` page. Note that the parameter value supports PMD Scripting. The page can reference these parameters using the `queryParams` variable.


    -   <b>render</b>

        Data type: booleanScript

        If true, the `editWizard` redirects to the specified conclusion page. If false, the conclusion page is disabled. The default is true.


-   <b>enableSaving</b>

    Data type: boolean

    If true, the `editWizard` enables both the <b>Save for Later</b> button and automatic saving of data on the current page while the user is interacting with the `editWizard`. The default is false.

    Notes:

    -   The `enableSaving` attribute enables or disables both <b>Save for Later</b> and autosave features. You can't enable or disable these features individually.
    -   When enabled Workday automatically manages the storage of temporary draft data for 30 days. Developers don’t need to configure external storage or custom data-saving logic. The number of days is not configurable.
    -   Draft data is scoped strictly to the active user session, not to specific inbox tasks or worker contexts. Because only one active draft can exist per session, the Save for Later feature doesn't support processing tasks for multiple employees simultaneously.
    -   Saved draft data takes priority and overrides any dynamically autofilled or default values.
    -   Ensure that every tag within the `editWizard` has a unique `id`. Any tag within the `enableSaving` without an `id` results in a validation warning.
    -   The Save for Later feature uses these `id` values when storing temporary data:

        -   The `id` of the page containing the `editWizard` tag.
        -   The `id` of the page for each step in the `editWizard`.
        -   The tag `id` of each widget on each step in the `editWizard`.

        Don’t change any of the `id` values after you’ve deployed the app. If you change these id’s, users will lose their temporary data.