---
title: "The Validate and Deploy Proof Ladder for Workday Extend"
description: "Prove a Workday Extend change in order: preview, validate, save, deploy to Development, test in the tenant, then promote one level at a time."
url: https://kiweely.com/guides/workday-extend-validate-deploy-proof-ladder
---

# The Validate and Deploy Proof Ladder for Workday Extend

Preview and validate before a tenant sees anything. Save to App Hub writes a build. Deploy reaches a development tenant only. Promote one level at a time. Model components still wait for the weekly update. Orchestrations validate in Orchestration Builder.

-   **Checked** against Workday on November 16
-   Applies to **Workday Extend**
-   7 min read
-   Published November 16
-   By Kiweely

A Workday Extend change is not proven because Developer Agent said it was built, and it is not proven because App Preview looked right. Workday gives you a ladder. Each rung checks a different thing. Skipping one is how a page that previewed on your laptop fails for HR Administrator on the development tenant, or how a development success gets described as a production deploy.

App Builder keeps session edits automatically, for your account only. That session copy is not a version. Save to App Hub is what writes the latest version. Discard Changes throws away the session and returns you to the version currently in App Hub, and Workday says that discard is irreversible.

## The ladder

| Rung | What you do | What it proves | What it does not prove |
| --- | --- | --- | --- |
| 1\. Preview | App Preview, ideally in a new tab, with the tenant connected | The page renders, widgets fire, and a connected tenant can supply values such as a worker search | Security policy, a durable business-object row, or any tenant except Development |
| 2\. Validate | Validate in App Builder, or `wdcli app validate` | Schema, semantic, and syntax checks for App Builder components | Orchestrations. The CLI says to validate those in Orchestration Builder. Some schema checks do not run as you type |
| 3\. Apply | Apply Changes, and only the components you reviewed | The agent diff is now in your session | A saved version. You can still discard the session |
| 4\. Save | Save to App Hub | A build, plus a build log | A tenant. Nothing is installed yet |
| 5\. Deploy | Save and Deploy, and choose a development tenant | The app runs on that development tenant | Implementation, Sandbox, or Production |
| 6\. Tenant proof | The task a real persona runs, plus App Manager | A person in a security group can use it, and a row exists | The next promotion level |
| 7\. Promote | One level: Development to Implementation, Implementation to Sandbox, Sandbox to Production | That level can install this version | Model components, until the weekly service update deploys them |
| 8\. Install and cache | Install once per tenant, then reload | The tenant is serving this version | A later source change. You promote again; you do not reinstall for an update |

Use the rung that matches the claim you are about to make. “It works” after rung 1 is a preview. “It works” after rung 6 is a development-tenant test. “It is in Production” is rung 8 on a Production tenant, after any model components have cleared Friday.

## How to run rungs 1 through 6

**Preview.** Connect the tenant first if the page reads workers or writes a business object. The nomination tutorial opens App Preview in a new tab, checks the four fields, opens the date calendar, searches “Brown” in the worker list, and confirms Cancel and OK on an edit page. Mock data under Testing can show a page without the tenant. If you used mock data, say so. A mock response is not a worker record.

**Validate.** Select Validate. The pane can be dragged open. Fix schema, semantic, and syntax errors before you save. If the error is in a component you did not mean to change, Reject Changes or fix that file. Do not deploy over a red validate. The agent-building activity says an error is possible even when you expected none, because the agent is non-deterministic.

**Apply, then save.** Apply Changes shows the components that will be added. Confirm is the commit into the session. Save to App Hub validates again and writes the build log. Read the log when the save complains. The CLI equivalents are `wdcli app validate` and `wdcli app upload`. `wdcli app builds logs` shows the log for a build id. Validate does not cover orchestrations.

**Deploy.** Save and Deploy asks for a development tenant. You may have to sign in. Deploy Successful is the development deploy. It is not a promotion. From there the nomination tutorial opens Manage in Tenant, which is App Manager.

**Tenant proof, three checks.**

1.  Security. In App Manager, Configure, create the domain security policy if the app added a domain, grant a security group, and activate pending security policy changes. Until you do that, a successful deploy can still be invisible to the people you named.
2.  Data. Submit the page as the persona you connected, then open Extend Business Object Instance Count. A higher count is the proof a row was stored. A preview that returned to the home page is not.
3.  A second persona, when the tenant has one. The tutorials use Logan McNeil and mention other sample accounts. A page that works for the user you connected does not show you a user outside the security group.

Orchestrations are a side door. App Builder can list them and open Orchestration Builder. `wdcli app validate` will not validate them. A page that calls a synchronous orchestration also has a 25-second cap when the page triggers it. Preview of the page does not prove that the orchestration finishes inside that cap.

## Rungs 7 and 8

From the Console section of the Developer Site menu, open Apps, open the app, open Promotions, and promote the latest version to the next level only.

| Current level | Action |
| --- | --- |
| Development | Promote to Implementation |
| Implementation | Promote to Sandbox |
| Sandbox | Promote to Production |

Promoting to Production shows a checklist. You select that the app meets the criteria, then promote again. If the app uses connectors, configure a Production account for each connector before that promotion.

Install once on each tenant. You do not reinstall when you promote a later version. You do reinstall if you refresh an Implementation tenant from a tenant that did not have the app, or if Production was not installed before a Sandbox refresh. Implementation can take up to 1 minute to refresh its cached app. Sandbox and Production can take up to 15 minutes.

If the version adds or changes a model component, the tenant cannot install it until the weekly service update deploys that component. Promoting after your region’s Thursday deadline slips that deploy by a week. A green deploy on Development does not move Friday.

`wdcli app promote` follows the same deadlines and the same levels as the Developer Site. The CLI is not a way around the weekly update.

## Failure modes

-   **Discard Changes after a good preview.** The session is gone. App Hub still has the previous version. Commit with Save to App Hub before you start a riskier prompt.
-   **Save and Deploy pointed at the wrong tenant alias.** You proved a different development tenant. Check the alias in the deploy dialog, not the browser tab title.
-   **Validate passed and the orchestration is broken.** You validated App Builder components only. Open Orchestration Builder and validate there.
-   **Instance count did not move.** The outbound endpoint did not write the object you think it wrote, or the security policy blocked the write and the page still navigated away. Read the count before you call the test done.
-   **You told someone it is in Sandbox because you deployed.** Deploy is Development. Sandbox is a promotion, plus install, plus the cache delay, plus Friday if model components changed.

## Watch Kiweely Vine build and test an Extend app

![Kiweely Vine testing a Remote Work Arrangement Extend app as the employee: the request page flags a missing start date before it can be submitted](https://kiweely.com/guides/workday-extend-validate-deploy-proof-ladder/media/vine-extend-app-remote-work-ea72afc873ba.webp)

From the film: testing as the employee, the request flags missing details before it is submitted.

A consultant describes a remote work request app in plain business words. Kiweely Vine builds it, publishes it to a Workday Development tenant and tests it as the employee, the manager and HR: employees ask to work remote or hybrid, managers approve or send back with a comment, and HR sees one list of who works where. About two hours of real work, shown in 13 minutes. Every acceptance check passed in Development.

[Watch the film (13 min)](https://kiweely.com/vine/films/remote-work-arrangement) · [Start for free](https://kiweely.com/sign-in?intent=signup)

## Frequently asked questions

### Does Validate deploy the app?

No. Validate checks the code. Save to App Hub writes a build. Save and Deploy sends that build to a development tenant you choose.

### Can I validate orchestrations with the app?

Not with `wdcli app validate`. Workday says that command covers App Builder components and that you validate orchestrations separately in Orchestration Builder.

### Do I reinstall after every promotion?

No. Install once per tenant. Promote the next version onto it. Reinstall only in the refresh cases Workday names: an Implementation refresh from a tenant without the app, or a Sandbox refresh when Production was never installed.

### What is the fastest rung that proves a business-object write?

Deploy to the development tenant, submit the page as a user who has Modify on the domain, and read Extend Business Object Instance Count in App Manager. Preview and Validate do not store a row.

## Sources checked

-   [Create Extend Apps Using App Builder](https://developer.workday.com/documentation/xer1651695264256/CreateExtendAppsUsingAppBuilder)
-   [Concept: App Builder](https://developer.workday.com/documentation/zxh1651687589440/ConceptAppBuilder)
-   [Promote Extend Apps Through the Lifecycle](https://developer.workday.com/documentation/ujq1579478936974-1/PromoteExtendAppsThroughtheLifecycle)
-   [Reference: Workday Developer CLI for Extend Apps](https://developer.workday.com/documentation/GUID-16d9d3f3-ba63-4022-8a84-ad78bd5189ca-enHYPHENus/ReferenceWorkdayDeveloperCLIWDCLIforExtendAppsCommands)
-   [Build an Extend App Fast with Developer Agent](https://developer.workday.com/documentation/GUID-73f17cca-3686-4921-84bf-44b819d9671e-enHYPHENus/BuildanExtendAppFastwithDeveloperAgent)

## Related guides

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

-   [### Workday Extend Model Components and the Weekly Update Business objects, security domains, attachments, processes, reports, and tasks are model components. Development deploys immediately. Other tenants get model changes on Friday night, and only if you promoted before Thursday. Deployed model components cannot be removed.](https://kiweely.com/guides/workday-extend-model-components-weekly-update)
-   [### Promote a Workday Extend App Past Development Deploy and test on a development tenant, then promote only to the next level. Implementation can take a minute to refresh. Sandbox and Production can take 15 minutes. Model components still wait for Friday if you made the Thursday deadline. Install once per tenant.](https://kiweely.com/guides/workday-extend-promote-past-development-beginners)
-   [### The 25-Second Synchronous Orchestrate Trap Workday allows 5 minutes for a synchronous Extend orchestration, and 25 seconds when a presentation page triggers it. The page limit wins over any timeout you set. Longer work belongs in an asynchronous orchestration, which can run up to 48 hours and returns a job id instead of holding the page.](https://kiweely.com/guides/workday-orchestrate-25-second-sync-trap)
-   [### Your First Workday Extend Validation Error from AI Validate checks schema, semantics, and syntax, and some of those checks do not run as you type. A generated diff can still fail. Model error codes name the limit you hit. Reject a bad diff instead of stacking repairs, and do not deploy over a red validate.](https://kiweely.com/guides/first-workday-extend-validation-error-ai)
-   [### Build Your First Workday Extend App with Developer Agent Developer Agent proposes Extend components in App Builder. You still create or accept the business object and security domain, apply the diff, validate, deploy to a development tenant, and activate the domain security policy yourself.](https://kiweely.com/guides/first-workday-extend-app-developer-agent)

### More guides on Extend apps and pages

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

-   [Use the Workday Extend App Catalog as an AI Jump Start](https://kiweely.com/guides/workday-extend-app-catalog-ai-jump-start)
-   [AMD vs PMD in Workday Extend, for Beginners](https://kiweely.com/guides/workday-extend-amd-vs-pmd-beginners)
-   [Security Domains for Your First Workday Extend App](https://kiweely.com/guides/first-workday-extend-app-security-domains)
-   [Is there an AI tool that can build, validate and deploy Workday Extend apps?](https://kiweely.com/guides/ai-tool-build-validate-deploy-workday-extend-apps)
-   [AI Browser Testing for Workday Extend Pages: Grids, Attachments, and BP Steps](https://kiweely.com/guides/ai-browser-testing-workday-extend-grids-attachments-bp)
-   [Workday Extend App Preview Is Not Proof the App Works in the Tenant](https://kiweely.com/guides/workday-extend-app-preview-is-not-tenant-proof)
-   [How to Map Control Fields and Related Business Objects in Workday Composite Subreports](https://kiweely.com/guides/workday-composite-report-control-fields-business-object-swap)
-   [Workday Lookup Related Value (LRV) Explained: Crossing Business Objects Without Blank Rows](https://kiweely.com/guides/workday-lookup-related-value-lrv-calculated-field)

### From the blog on Extend apps and pages

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

-   [How do you test a Workday Extend app end to end?](https://kiweely.com/blog/test-workday-extend-app-end-to-end)
-   [When a Workday Custom Report Is Enough vs. When You Need Prism or an Extend App](https://kiweely.com/blog/when-workday-custom-report-is-not-enough)
-   [Five Workday Extend app blueprints you can build in a free personal tenant](https://kiweely.com/blog/five-workday-extend-apps-to-build-in-open-developer-program)

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