Promoting a Workday Extend app is not deploying it again. Deploy sends a build to a development tenant. Promote moves an existing version to the next level: Development to Implementation, Implementation to Sandbox, Sandbox to Production. You do not skip a level. The tenants you have not promoted to keep the old version until you do.
Workday’s prerequisite is blunt. You have deployed the app to a development tenant and finished development and unit testing there. Implementation is where you run data validation and integration tests. Sandbox is where you test with production data. Production is where a company administrator can install and configure the app, after you accept the production checklist.
Promote the latest version, one level
- On the Developer Site, open the Console section of the menu and select Apps. The list is the apps in App Hub for your account. “Extend Apps in Production” filters to apps that have already been promoted to Production.
- Find the app by name or reference ID. You can view your own apps or all apps.
- Open the app, open the Promotions tab, and promote the latest version to the next level only.
| You are on | The only next action |
|---|---|
| You are onDevelopment | The only next actionPromote to Implementation |
| You are onImplementation | The only next actionPromote to Sandbox |
| You are onSandbox | The only next actionPromote to Production |
- For Production, read the checklist. If the app meets it, select that the app meets the criteria, then promote again. If the app uses connectors, configure a Production account for each connector before this step.
- Install the app on the tenant. You install once per tenant. Later versions do not get another install.
wdcli app promote with a level such as implementation follows these same rules, including the model-component deadlines. The CLI is not a second, faster ladder.
What “available” means on the clock
After a promotion, Workday gives two different clocks.
Cache. Implementation tenants might take up to 1 minute to update the cached app. Sandbox and Production might take up to 15 minutes. If you open the tenant in the first minute and do not see the new pages, wait out the cache before you call the promotion a failure.
Model components. Attachments, business objects, business processes, reports, security domains, and tasks deploy to Implementation, Sandbox, and Production as part of the weekly service update. You can install an app that has model components on those tenants only after that deploy. Promote before the Thursday deadline in Pacific time, and the components go out Friday night. Promote after it, and they go out Friday night the following week.
| Extend region | Data center | Thursday deadline, Pacific |
|---|---|---|
| Extend regionEU | Data centerAll | Thursday deadline, Pacific03:59:59 AM |
| Extend regionUS | Data centerWD102, WD105, WD109, WD117 | Thursday deadline, Pacific08:59:59 AM |
| Extend regionUS | Data centerAny other | Thursday deadline, Pacific11:59:59 PM |
| Extend regionOther regions | Data centerAll | Thursday deadline, Pacific03:59:59 AM |
Non-model changes are available immediately, unless a model-component change is already queued for the upcoming weekly update. In that case the whole app update waits until the weekly update finishes. A page fix does not pass a queued business object.
If this is the first time the customer goes live, promote to Production one week before Workday creates the Production tenant from the Gold tenant. Otherwise the app is not installable on that new Production tenant until you promote it.
Updating an app that is already in Production
Download is not required for a tiny App Builder edit, but Workday’s update path starts from the source you upload back to App Hub. Deploy the new build to a development tenant. Only Development moves to the new version. The table Workday prints is:
| Environment | After you deploy the new source |
|---|---|
| EnvironmentDevelopment | After you deploy the new sourceNew version |
| EnvironmentImplementation | After you deploy the new sourcePrevious version |
| EnvironmentSandbox | After you deploy the new sourcePrevious version |
| EnvironmentProduction | After you deploy the new sourcePrevious version |
Promote to Implementation and test there. You do not reinstall. Sandbox still has the old version until you promote to Sandbox. Production still has the old version until you promote to Production. On each of those promotions, model-component changes wait for the weekly update again.
If you are still editing a version that has never left Development, further saves update that same development version. Workday does not mint a new version number for every save.
Allowed model updates, and only these, once a component has deployed in a previous version: add model components, add fields, add security domains on objects, add security domains on fields, and update page routes in business processes. You cannot remove a model component that has already deployed. Check the diff before you promote, not after Friday.
Sandbox, refresh, and a second install
Workday calls out one Sandbox-specific failure. On the external client credential store you must create refresh tokens in both the Sandbox tenant and the Sandbox Preview tenant. If you create business objects in Sandbox Preview and you do not have refresh tokens there, you get HTTP 500 when you access those objects. Tokens that exist only on Sandbox let you access the objects only on Sandbox.
You also reinstall, despite the once-per-tenant rule, in two refresh cases:
- You refresh an Implementation tenant from a tenant where the app was not installed.
- You did not install the app on Production before Workday refreshes Sandbox.
Those are reinstalls of an app that fell off the tenant. They are not how you ship version 2.
A beginner sequence
- Validate, save, and deploy to the development tenant. Test as a user who has the domain security policy, not only as the developer who built the page.
- Activate security policy changes on that development tenant and confirm a real row, for example with Extend Business Object Instance Count.
- Promote to Implementation before your Thursday deadline if the version has model components. Wait for Friday night if it does. Allow up to a minute for the cache. Test integrations there.
- Promote to Sandbox. Create the Sandbox and Sandbox Preview refresh tokens before you depend on business objects in Sandbox Preview. Allow up to 15 minutes for the cache. Test with production data, which is the point of Sandbox.
- Promote to Production only after the checklist is true. Configure connector production accounts first. Allow up to 15 minutes. The company administrator installs and configures it if this is the first time on that tenant.
Failure modes
- You promoted Development straight to Sandbox in your head. The action from Development is Promote to Implementation. Sandbox is the action from Implementation.
- Friday came and Implementation still has no object. The promotion was after the deadline, or it was the wrong region’s Thursday. The US-all-day deadline does not apply to WD102, WD105, WD109, or WD117, and it does not apply to EU.
- Production promotion is disabled until you check the box. Workday requires you to confirm the checklist and promote again. Connectors without a Production account are a reason to stop, not a warning to click through.
- HTTP 500 on a business object in Sandbox Preview. The refresh-token note is the published cause. Create the Sandbox Preview refresh token. Do not redeploy the development tenant to fix a Sandbox Preview grant.
- A new security domain is in the app and the Sandbox policy is empty. The domain file arrives with the model deploy. The policy is something you configure on that tenant. Development’s activated policy does not copy itself.
Frequently asked questions
Is Save and Deploy a promotion?
No. Save and Deploy targets a development tenant. Promotion starts from the Promotions tab, or from wdcli app promote, and only to the next level.
Do I install on every version?
Install once on each tenant. Promote later versions onto that install. Reinstall only after the Implementation or Sandbox refresh cases Workday names.
How long before Implementation shows the app?
Up to about a minute for the cached app, longer if you are waiting for a model component’s weekly service update. Sandbox and Production can take up to 15 minutes for the cache, and the same Friday rule for model components.
Can I remove a field I promoted by mistake?
Not if that field deployed in a previous version. The allowed updates do not include removal. Catch it on the development tenant, before the promotion.