---
title: "Workday Extend PMD Routing, multiStepLayout & flowVariables"
description: "Render conditional pods on PMD page load, replace tabBar with multiStepLayout for button navigation, and avoid large grid payloads in flowVariables."
url: https://kiweely.com/guides/workday-extend-pmd-conditional-page-routing-tabbar-flowvariables-limits
---

# Conditional Page Routing on Load, multiStepLayout vs. tabBar Navigation, and flowVariables Payload Limits in Workday Extend PMD

Workday Extend PMD does not expose a redirect API in onLoad, cannot switch tabBar tabs from a button, and serializes flowVariables on the server across page transitions. Learn how to use conditional pods, multiStepLayout or editWizard, and Business Object persistence.

-   **Checked** against Workday on November 6
-   Applies to **Workday Extend**
-   3 min read
-   Published November 6
-   By Kiweely

## Why PMD `onLoad` Cannot Auto-Redirect to Another Page (and How to Use Conditional Pods)

Workday Extend Presentation Metadata (PMD) does not expose an imperative navigation or redirect method that fires during the `onLoad` page lifecycle. Page-to-page navigation in Workday Extend only occurs when a user clicks a `button` (linked to a `taskId`), clicks an `externalLink`, or submits an edit page that triggers a `flowDefinitions` transition in the Application Metadata (`.amd`) file.

When you need a user opening a task to see one of two completely different page experiences based on an inbound WQL or REST check at load time—for example, showing an Enrollment Form if the worker has not enrolled yet, or an Enrollment Summary page if a record already exists—encapsulate each experience inside its own **Pod** (`.pod`) and conditionally render the matching pod on a single host PMD page:

json

```
{
  "id": "enrollmentRouterPage",
  "endPoints": [
    {
      "name": "workerEnrollmentCheck",
      "baseUrlType": "wql",
      "authType": "sso",
      "url": "<% '/data?query=' + string:urlEncode('SELECT workdayID, status FROM customApp_enrollments WHERE worker = \\'' + currentLoggedInUser.id + '\\' LIMIT 1') %>"
    }
  ],
  "presentation": {
    "pageType": "edit",
    "title": {
      "type": "title",
      "label": "Program Enrollment"
    },
    "body": {
      "type": "section",
      "id": "routerBodySection",
      "children": [
        {
          "type": "pod",
          "podId": "newEnrollmentFormPod",
          "render": "<% empty(workerEnrollmentCheck.data) %>"
        },
        {
          "type": "pod",
          "podId": "existingEnrollmentSummaryPod",
          "render": "<% !empty(workerEnrollmentCheck.data) %>"
        }
      ]
    }
  }
}
```

Because `render` is evaluated on the server during page load after inbound `endPoints` complete, only the matching pod is instantiated and sent to the browser. If the two experiences require different `pageType` behaviors (for example, an `edit` page versus a read-only `view` page with no **OK** button), use a lightweight landing view page with conditional `button` widgets whose `taskReference` routes the user to the appropriate target `taskId`.

## Switching Sections with Buttons: Use `multiStepLayout` or `editWizard` Instead of `tabBar`

When designing a long data-entry form, developers often group sections into a six-tab `tabBar` layout and then attempt to add a **Proceed to Next Tab** button at the bottom of each tab.

In Workday Extend PMD:

-   `button` widgets navigate between separate PMD tasks (`taskId`) or external URLs.
-   `pageActionButton` widgets run PMD scripts on the current page, but `tabBar` does not expose a scripting method (such as `setActiveTab()`) to switch the selected tab programmatically.

If your users require guided **Next** and **Previous** button navigation across sections of a single PMD page, replace `tabBar` with **`multiStepLayout`** (up to 10 steps, supported on both `view` and `edit` pages as the top-level tag inside `body`) or **`editWizard`**:

json

```
{
  "id": "onboardingProfilePage",
  "endPoints": [],
  "presentation": {
    "pageType": "edit",
    "title": {
      "type": "title",
      "label": "Onboarding Profile"
    },
    "body": {
      "type": "multiStepLayout",
      "id": "onboardingWizard",
      "steps": [
        {
          "type": "layoutSection",
          "id": "step1WorkerDetails",
          "children": [
            {
              "type": "fieldSet",
              "id": "workerFieldSet",
              "title": "Step 1: Worker Details",
              "children": [
                {
                  "type": "text",
                  "id": "workerName",
                  "label": "Full Name",
                  "required": true
                }
              ]
            }
          ]
        },
        {
          "type": "layoutSection",
          "id": "step2Equipment",
          "children": [
            {
              "type": "fieldSet",
              "id": "equipmentFieldSet",
              "title": "Step 2: Equipment and Access",
              "children": [
                {
                  "type": "instanceList",
                  "id": "equipmentType",
                  "label": "Equipment Type",
                  "instanceList": [
                    { "id": "LAPTOP", "descriptor": "Laptop" },
                    { "id": "DESKTOP", "descriptor": "Desktop" }
                  ]
                }
              ]
            }
          ]
        }
      ]
    }
  }
}
```

`multiStepLayout` automatically renders numbered progress steps at the top of the page and provides built-in step navigation controls without requiring custom `taskId` transitions. Note that `multiStepLayout` must be the root widget of `body` and cannot be nested inside a `pod`.

## Understanding `flowVariables` Server-Side State and Data Volume Limits

When passing data from one PMD page to the next inside an `.amd` page flow (`flowDefinitions`), developers use an `outboundVariable` endpoint with `"variableScope": "flow"` and read the values on the destination page via `flowVariables`.

A common misconception is that `flowVariables` are stored purely in browser memory on the client. In reality, **PMD scripting and `flowVariables` are server-side state managed by the Workday Extend presentation runtime**. That is why `flowVariables` must be populated through an `outboundVariable` endpoint inside `outboundData` when the first page submits:

json

```
"outboundData": {
  "outboundEndPoints": [
    {
      "type": "outboundVariable",
      "name": "transitionOutboundVars",
      "variableScope": "flow",
      "values": [
        {
          "outboundPath": "batchRequestId",
          "value": "<% createBatchRequest.id %>"
        },
        {
          "outboundPath": "isValid",
          "value": "<% !empty(createBatchRequest.id) %>"
        }
      ]
    }
  ]
}
```

Because `flowVariables` are serialized into the server-side page context and transmitted between the browser and the Workday presentation server on page transitions, passing hundreds of grid rows or large nested JSON objects inside `flowVariables` increases network round-trip payload size, slows down next-page rendering, and risks hitting presentation state serialization limits.

### Best Practice for Passing Multi-Row Grid Data Across Pages

Instead of serializing an entire 500-row grid array into `flowVariables`:

1.  Persist the grid rows to a Model Business Object on the first page (or save the filter criteria/parent record).
2.  Pass only the lightweight parent Business Object `id` or query filter parameters inside `flowVariables` (as shown with `batchRequestId` above).
3.  Query the rows on the destination page using an inbound WQL or Business Object REST endpoint filtered by `flowVariables.batchRequestId`.

## How to Verify in the Tenant

1.  Deploy the host PMD page with conditional pods and open it with both an enrolled and an unenrolled user account to confirm that the `render` expression displays the appropriate pod on load without requiring a second click.
2.  Open the `multiStepLayout` page and verify that users can step forward and backward across `layoutSection` steps before submitting the page.
3.  Inspect network timing and **View Application Logs** when transitioning across pages in a `flowDefinitions` flow, confirming that only lightweight identifiers are passed in `flowVariables` while the destination page fetches the grid rows via its inbound endpoint.

## Sources checked

-   [Concept: Page Flows](https://developer.workday.com/documentation/zji1528861641063)
-   [multiStepLayout PMD Tag Reference](https://developer.workday.com/documentation/GUID-565421f6-9997-4c31-9928-82d46da8df88-enHYPHENus)
-   [editWizard PMD Tag Reference](https://developer.workday.com/documentation/GUID-e22407f5-5782-4e59-a714-85499158a0bb-enHYPHENus)
-   [pod PMD Tag Reference](https://developer.workday.com/documentation/haf1605747581619)
-   [outboundVariable PMD Tag Reference](https://developer.workday.com/documentation/lmd1529983805787)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### Fixing radioGroup Options Disappearing When selectedValues Is Empty and Disabling Specific Options in Workday Extend PMD In Workday Extend PMD, setting enabled to false on a radioGroup when selectedValues is null or \[\] hides every option. Learn how to keep unselected radio options visible, bind 3+ option radio groups on edit pages, and filter radioGroup or multi-select instanceList choices with setValues().](https://kiweely.com/guides/workday-extend-pmd-radiogroup-options-disappear-disable-specific-items)
-   [### Displaying dynamicColumns in a Workday Extend PMD Grid and Flattening Nested Arrays into Rows Workday Extend developers often confuse variable child rows with runtime-generated grid columns. This guide covers flattening nested RaaS or REST arrays into grid rows, configuring dynamicColumns with cellTemplates, and rendering arbitrary WQL SELECT fields using map:getKeys().](https://kiweely.com/guides/workday-extend-pmd-dynamic-grid-columns-flattening-arrays)
-   [### Clearing Grid Cell Validation Errors on onChange and Blocking Page Save on pageActionButton Failure in Workday Extend PMD Learn how to clear cell-level validation errors in Workday Extend PMD grids when a user updates a cell, avoid the getSelectedRows() border-highlighting trap during onSubmit, and block page submission when a pageActionButton deferred WQL lookup fails.](https://kiweely.com/guides/workday-extend-pmd-clear-grid-cell-error-pageactionbutton-block-save)

### More guides on Extend apps and pages

[All 97 guides](https://kiweely.com/guides#extend)

-   [Resolving “Tenant mapping not found (OP-4008)”, EU vs. US Regional Base URL 401 Errors, and client\_secret\_basic in Workday Extend OAuth 2.0](https://kiweely.com/guides/workday-extend-oauth-tenant-mapping-op-4008-eu-base-url-client-secret-basic)
-   [Working Around the 10-Relationship Limit on a Workday Extend Model Business Object (MCBO) Using a Helper Object](https://kiweely.com/guides/workday-extend-mcbo-10-single-instance-relationship-limit-helper-bo)
-   [How to Blank Out Text Fields and Nullify Reference Values on Workday Extend Business Objects via Inbound EIB Using {empty}](https://kiweely.com/guides/workday-extend-eib-clear-text-nullify-fields-empty-tag)
-   [Fixing “Object instance has properties which are not allowed by the schema (parentBusinessProcesses, initiationPageRoute)” on Extend Subprocesses](https://kiweely.com/guides/workday-extend-bp-subprocess-allowedparentprocesses-eventstepid)
-   [Cascading dropdowns and instance lists in Workday Extend](https://kiweely.com/guides/workday-extend-cascading-instance-lists)
-   [How to move Workday Extend apps to a new developer tenant before the old one expires or is deleted](https://kiweely.com/guides/workday-extend-move-apps-new-developer-tenant)
-   [Why a Workday Graph API query suddenly fails with “Cannot query field”](https://kiweely.com/guides/workday-graphql-cannot-query-field)
-   [How to build a worker search prompt in a Workday Extend page](https://kiweely.com/guides/workday-extend-worker-search)

### From the blog on Extend apps and pages

[All posts](https://kiweely.com/blog)

-   [Debugging Workday Extend web services: Postman vs. kiweely](https://kiweely.com/blog/debugging-workday-extend-web-services-postman-vs-kiweely)
-   [Rapid ideation and prototyping of Workday Extend apps](https://kiweely.com/blog/rapid-prototyping-workday-extend-apps-with-kiweely)
-   [Claude Code for Workday Extend: what changes when it can reach your tenant?](https://kiweely.com/blog/claude-code-workday-extend-tenant)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
