Add a Workday Extend model component only when the data, process, or security it represents must live in the tenant model. Once that component has deployed in a previous version of the app, Workday says you cannot remove it. New and updated model components also wait for the Weekly Service Update after you promote past Development. A speculative business object, report, or security domain is therefore a lasting commitment, not a temporary scaffold.
What counts as a model component
Workday’s getting-started material treats these as the foundational model set: business objects, business processes, attachments, tasks, and security domains. Reports belong with that model folder as well. Pages, app metadata, and scripts are presentation or related non-model pieces. They are not covered by the same “cannot remove” rule, though a queued model change can still hold an app update until Friday.
The irreversible rule, in Workday’s words
When you update an app with model components, Workday allows you to:
- 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.
Workday’s note is explicit: you can’t remove model components that deployed in a previous version of the app.
On a WCP Development tenant the picture is different. If you delete a model component from the app and redeploy there, Workday removes the component and all tenanted data tied to it. After you promote, Workday’s update concept says you cannot delete attachments, business objects, business processes, or regular fields, and you cannot remove or change security domain assignments from attachment objects and business processes. Workday recommends finishing as much development as possible on Development before the first promotion.
When not to add one
| Situation | Prefer instead |
|---|---|
| SituationYou are still discovering the data shape | Prefer insteadKeep iterating on Development. Do not promote a version that contains objects you might drop. |
| SituationThe need is a screen layout, label, or scripted calculation | Prefer insteadUse presentation components. Do not invent a business object for temporary UI state. |
| SituationYou only need a one-off extract | Prefer insteadPrefer a report or query pattern you can revise without promoting a new object you later regret. |
| SituationSecurity is not decided | Prefer insteadDo not add domains “to be safe.” Domains that deploy cannot be removed later under the update rules above. |
| SituationYou are near a Thursday promotion deadline | Prefer insteadDelay new model work rather than promote a half-designed object into this Friday’s queue. |
| SituationThe app already approaches Workday’s per-app limits | Prefer insteadTwenty business objects, ten security domains, five business processes, five attachments, twenty tasks, and ten reports are hard caps. Spare capacity is part of the design. |
Why the weekly update makes hesitation rational
You can install an app with model components on Implementation, Sandbox, or Production only after those components deploy with the Weekly Service Update. Promote after your region’s Thursday Pacific deadline and you wait an extra week. That means every speculative model addition costs calendar time as well as permanence. Pages and scripts normally become available immediately, unless a model change is already queued for the upcoming Friday window.
A decision sequence that stays reversible longer
- Prove the page and orchestration behavior on Development with the smallest model you truly need.
- Name fields and
idvalues as if they will never change. Workday says you cannot change a model component’sid, swapidvalues between two fields of the same type, or change the type of a regular field after the fact. - Unit-test on Development until you would be willing to keep every object in the promoted version forever.
- Promote only when the model is settled. Treat the first promotion as the point of no return for removal.
- For later versions, prefer additive updates: new fields, new domains, new components you are sure about.
Failure modes
- “We’ll delete it after UAT.” Not after it has deployed in a previous version. Hide it on the page if you must; the model entry remains.
- Assistant-generated “complete” model packs. An extra report, task, and attachment each become permanent once promoted.
- Changing a regular field’s type after promotion. Not allowed. Design the type before the first promoted version that includes the field.
- Mixing an urgent page fix with a speculative object. The queued model change can hold the page fix until Friday.
Frequently asked questions
Can I delete a business object on Development?
Yes. Redeploying without it on a WCP Development tenant removes the component and its tenanted data there. After promotion, removal is not an allowed update.
What can I change after a model component has deployed?
Add components, add fields, add security domains to objects or fields, and update page routes on business processes. You cannot remove deployed model components.
Do pages count as model components?
No. Presentation changes are not on the model-component list. They can still wait if a model change is already queued for Friday.