Less than you might expect. Workday’s Extend documentation says you can’t remove model components that deployed in a previous version of the app, and after promotion only certain properties of existing fields and objects can change. So if your Extend app uses model components, its first deploy is a design decision you can’t fully take back.
What a later version can do
When you update an app with model components, Workday lets you:
- add new model components
- add new fields to existing model components
- add new security domains to business objects, and to individual fields on them
- update page routes in business processes
Removing a model component that an earlier version deployed isn’t on that list.
What you can still change on a business object
Workday’s reference of allowed updates after promotion lists, for business objects:
- the object’s name and label, and the name and label of its default collection
- a field’s name and label
- the security domain of the object or of a field: change or remove
- a field’s
enableIndexandenableSearchattributes: change or remove - a field’s
isPurgeableattribute, thedecimalsof aDECIMALfield and theprecisionof aDATEfield - on a
SINGLE_INSTANCEfield,secureByTarget, andenableReportingFromTargetfromfalsetotrueonly useForDisplayon aTEXTfield- a derived field: remove it, or change its label, type or expression
A stored field’s type isn’t on the list, and of a business object’s fields, only derived fields can be removed. A value that can be calculated from other fields stays changeable if you make it a derived field. A value you store is there for good.
The same reference does list some removals elsewhere in the app: a task or a report, a column from a report, a model profile group, and actions in a business process’s Approval step (though not all of them, and not only the SEND_BACK action).
Model components deploy once a week
On Implementation, Sandbox and Production tenants, new or changed model components deploy as part of Workday’s Weekly Service Update, so you have to promote the app before that week’s deadline:
- Thursday at 11:59:59 PM Pacific for most data centers
- Thursday at 08:59:59 AM Pacific for the Asia Pacific public cloud data centers WD102 (Singapore), WD105 (Australia), WD109 (Japan) and WD117 (India)
Promote before the deadline and the model components deploy in that Friday night’s Weekly Service Update. Promote after it and they deploy on the Friday night a week later.
An update that doesn’t change the model is available to the tenant straight away, unless model components are already queued for an upcoming Weekly Service Update. Then the update becomes available after that service update completes.
Timing a first go-live
For an app with model components to be on your Production tenant when your Workday implementation goes live for the first time, promote it to Production one week before Workday creates your Production tenant from your Gold tenant. Otherwise it won’t be available to install on Production until you promote it to Production.
Before version one ships
- List the business objects and fields the app really needs, and the type of each stored field.
- Decide which values are stored and which can be derived from others.
- Security domains can be added later, so you don’t have to settle every access rule up front. The objects and stored fields they protect are what to get right.
- Put the promotion deadline in the cutover plan, with the go-live week counted back from when Production is created from Gold.
How kiweely handled it in the Peer Recognition app
When kiweely built a Peer Recognition app from a business brief, it worked out the data model before building anything: the recognition records, the point balances, and separate access rules for employees, managers and HR. On screen it flagged that “Once shipped, Workday limits which model components can be removed.”
The app, and the film of kiweely building it: https://kiweely.com/extend/apps/peer-recognition