---
title: "Workday Extend Model Components and the Weekly Update"
description: "Model components in a Workday Extend app deploy past Development only with the weekly service update. Miss the Thursday deadline and you wait another Friday."
url: https://kiweely.com/guides/workday-extend-model-components-weekly-update
---

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

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

A Workday Extend model component is part of the tenant’s data model, not part of the page. App Builder names the set when you add one: attachment, business object, business process, report, security domain, and task. The moment you add any of them, App Builder tells you that promotions to Implementation, Sandbox, and Production queue until the Friday maintenance window. Pages, app metadata, and scripts are not on that list. You can change those and see the change without waiting for Friday, except when a model-component update is already queued. In that case Workday holds the app update until the weekly service update finishes.

You can deploy to a development tenant and test there without that Friday wait. You cannot install the app on an Implementation, Sandbox, or Production tenant until the model components have deployed to that tenant as part of the weekly service update.

## What you are allowed to change later

After a model component has deployed in a previous version, Workday says you cannot remove it. An update may only:

-   Add new model components.
-   Add new fields to existing model components.
-   Add new security domains to business objects.
-   Add new security domains to individual fields on business objects.
-   Update page routes in business processes.

You do not reinstall the app after that update. You promote the new version. The new and updated model components still ride the weekly service update. Plan names, field types, and security domains as if a mistake is permanent once Friday has passed on a promoted version. A generated “just in case” business object is not cheap if you promote it.

## The deadline is Thursday, and the clock is Pacific

Promote before the deadline and the model components deploy on Friday night of that week. Promote after the deadline and Workday schedules them for Friday night one week later. The deadline depends on your Extend region and the data center that hosts the tenant.

| Extend region | Tenant data center | Promote before |
| --- | --- | --- |
| EU | All Workday or public-cloud data centers | Thursday, 03:59:59 AM Pacific |
| US | WD102 Singapore, WD105 Australia, WD109 Japan, WD117 India | Thursday, 08:59:59 AM Pacific |
| US | Every other Workday or public-cloud data center | Thursday, 11:59:59 PM Pacific |
| Other Extend regions | All Workday or public-cloud data centers | Thursday, 03:59:59 AM Pacific |

“Thursday night” is the wrong phrase for an EU tenant or a US tenant in those four Asia-Pacific data centers. Their deadlines are Thursday morning Pacific. A promotion you start after lunch in London on Thursday is already late for the EU row.

Workday also says that if a customer is going live for the first time, promote the app to Production one week before Workday creates the Production tenant from the Gold tenant. Otherwise the app is not available to install on Production until you promote it to Production.

## How a normal update moves

Workday’s update concept uses a version table. Version 1 is live in Production. You change the source and deploy to a development tenant. Only Development moves to version 2. Implementation, Sandbox, and Production stay on version 1 until you promote.

| Environment | Right after you deploy the change | After you promote that level |
| --- | --- | --- |
| Development | 2 | 2 |
| Implementation | 1 | 2, with model components on the weekly update |
| Sandbox | 1 | 2, same weekly rule |
| Production | 1 | 2, same weekly rule |

If you have not yet promoted this version off Development, further source changes update that same Development version. Workday does not create another version number for every save. Once you promote, the next source change is how version 3 starts, and only Development has it until you promote again.

Non-model updates become available on the tenant immediately, with one exception: if model components are already queued for an upcoming weekly service update, Workday waits to make the app update available until that weekly update completes. A page-only fix shipped while a business-object change is in the Friday queue does not jump the queue.

## A practical week

1.  Do the model work on the development tenant early in the week. Add the business object, the fields, and the security domains you are sure about. Validate, deploy, and test there. Development is where a wrong field is still only a development version.
2.  Identify the row in the table for your region and data center. Put the Thursday deadline on the calendar in Pacific time.
3.  Promote one level. Development promotes to Implementation. Implementation promotes to Sandbox. Sandbox promotes to Production. You do not skip.
4.  If the promotion includes new or updated model components, do it before the deadline. Then wait for Friday night. You cannot install on that tenant type until the model components have deployed.
5.  After the weekly update, confirm the version. Implementation tenants can take up to 1 minute to refresh the cached app. Sandbox and Production can take up to 15 minutes. Those cache times are about the promoted app. They do not replace the Friday model-component deploy.
6.  Activate security policy changes in the tenant after the domains exist there. The domain file in the app is not the activated policy.

## Failure modes

-   **App Manager on Sandbox does not list the new object on Thursday afternoon.** You promoted after the deadline, or you promoted on time and Friday has not happened. Check which. Installing again will not pull Friday forward.
-   **You deleted a field in the JSON.** If that field deployed in a previous version, removal is not an allowed update. Put the field back before you promote. Hiding it on the page does not remove it from the model.
-   **You added a security domain in the same change as a page tweak, and the page tweak is urgent.** The queued model change holds the app update until the weekly service update completes. Split the next cycle: promote model changes on their own week when you can, and do not mix a Friday-queued object with a page fix you need the same day.
-   **Production is about to be created from Gold and the app is not promoted.** Workday says to promote to Production a week before that tenant is created. Missing that window means the app is not installable on the new Production tenant until you promote it.
-   **An assistant added a report, a task, and an attachment “to be complete.”** All three are model components. Each one you keep is subject to the same deadline and the same no-removal rule.

## Frequently asked questions

### Does the development tenant wait for Friday?

No. You deploy to a development tenant to build and test. The weekly service update is how new or updated model components reach Implementation, Sandbox, and Production after you promote.

### Can I remove a business object if nobody has used it?

Only if it has not deployed in a previous version. Once it has, Workday’s update rules do not include removal. Avoid promoting a version that contains an object you are unsure about.

### Why did my page change wait until Friday?

Workday makes app updates available immediately unless model components are already queued for the upcoming weekly service update. A queued business-object or security-domain change holds the rest of that update.

### Which Thursday applies to a US tenant in Singapore?

WD102 uses Thursday at 08:59:59 AM Pacific, not Thursday at 11:59:59 PM Pacific. The later deadline is only for US-region tenants in data centers other than WD102, WD105, WD109, and WD117.

## Sources checked

-   [Concept: Extend Apps with Model Components](https://developer.workday.com/documentation/svf1623189172850/ConceptExtendAppswithModelComponents)
-   [Reference: Promotion Deadlines for Extend Apps with Model Components](https://developer.workday.com/documentation/giw1660842903762/ReferencePromotionDeadlinesforExtendAppswithModelComponents)
-   [Create Extend Apps Using App Builder](https://developer.workday.com/documentation/xer1651695264256/CreateExtendAppsUsingAppBuilder)
-   [Concept: Update Workday Extend Apps](https://developer.workday.com/documentation/inq1613067239283/ConceptUpdateWorkdayExtendApps)
-   [Concept: Extend App Components](https://developer.workday.com/documentation/kwv1612374098305/ConceptExtendAppComponents)

## Related guides

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

-   [### 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)
-   [### Use the Workday Extend App Catalog as an AI Jump Start The App Catalog holds reference Extend apps. Create Copy makes a new app with its own reference ID. Developer Agent can amend that copy. You still validate, deploy to a development tenant, and configure security. A reference ID cannot be reused.](https://kiweely.com/guides/workday-extend-app-catalog-ai-jump-start)
-   [### AMD vs PMD in Workday Extend, for Beginners In Workday Extend, the AMD declares data providers, task routes, flows, and app properties. A PMD draws one page and calls those providers. Business objects, security domains, and other model files are separate and follow the weekly update once you leave Development.](https://kiweely.com/guides/workday-extend-amd-vs-pmd-beginners)
-   [### Security Domains for Your First Workday Extend App A security domain file does nothing until you deploy, create the domain security policy, grant a security group, and activate it. Page security should use unconstrained role-based groups. Developer Agent can write the file. It does not configure the tenant.](https://kiweely.com/guides/first-workday-extend-app-security-domains)

### More guides on Extend apps and pages

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

-   [The Validate and Deploy Proof Ladder for Workday Extend](https://kiweely.com/guides/workday-extend-validate-deploy-proof-ladder)
-   [Your First Workday Extend Validation Error from AI](https://kiweely.com/guides/first-workday-extend-validation-error-ai)
-   [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)
-   [Fixing Graph API DataSourceFilter Is Inaccessible Errors and Blank processingWorker Fields When Proxying](https://kiweely.com/guides/workday-graphql-datasourcefilter-inaccessible-processingworker-proxy)

### From the blog on Extend apps and pages

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

-   [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)
-   [From Business Brief to Tested Workday Extend App: Why Zero Validation Errors Is Not Proof](https://kiweely.com/blog/why-workday-extend-validation-is-not-testing)
-   [Workday Extend Graph API and AppHub Promotion: Moving Apps From Development to Sandbox](https://kiweely.com/blog/workday-extend-graph-api-and-apphub-promotion)

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