The App Catalog is Workday’s library of reference Extend apps and templates, not a gallery of finished production apps for your tenant. The jump start that matches the docs is: filter for the shape you want, read that app’s overview, create a copy with its own name and reference ID, connect your development tenant, and only then ask Developer Agent to amend the copy. The agent can modify an existing app. It does not configure security, and a copy that contains model components still waits on the weekly service update once you promote it past Development.
Starting from scratch is the other legal option, and so is uploading a zip. Copying is the one that gives you a working structure on the first save. It also gives you someone else’s field names, routes, and security domains. Read those before you prompt “make this our promotions app.”
Copy the app Workday’s way
From the getting-started tutorial:
- Open the hamburger menu and select Reference, then App Catalog.
- Filter Model if you want apps that include a business object. Under Type, select Extend App if you want Extend apps that also have model components.
- Open View App. The overview page is where Workday puts deployment and configuration instructions for that app. Read it before you copy.
- Select Create Copy. Change the name. Select Copy and Go to Overview.
You can do the same thing from Create an Extend App and choose Copy from App Catalog. Amend the copy’s name and reference ID, and optionally the description. Upload a Zip File and Start from Scratch are the other two choices on that page. Integration apps have the same three choices on their own create step.
The reference ID is not a label you can recycle. It is the id you enter, plus a unique id for your account, joined with an underscore. Workday’s example shape is myWcpApp_zsttxv. The id you enter must be unique in the account, start with a letter, and use only letters, digits, ., and -. App Hub appends the account part when you upload. You cannot reuse a reference ID even after you delete the app. Name the copy for the job it will do. “Copy of Charitable Donations” becomes a permanent id the moment you create it.
A copy is a different app from the catalog original. Changes you make do not flow back, and later catalog updates do not flow forward. Workday has not published an automatic refresh from catalog app to your copy.
What a useful catalog app already contains
Workday’s business-object example points at the Charitable Donations sample in the App Catalog. That sample uses business object and business process APIs on the createCharity and viewCharityEvent pages. It is a concrete place to see a task route that is not the page id (/charities/create for createCharity in the app-metadata examples) and a page that talks to a custom object.
Use the catalog for that kind of pattern:
| You need to learn | Filter or sample | What you still write |
|---|---|---|
| You need to learnA business object and a page that lists it | Filter or sampleModel, type Extend App | What you still writeYour fields, your security policy, your labels |
| You need to learnA business process around an object | Filter or sampleCharitable Donations, and the model-components business-process tutorial Workday links from the example | What you still writeThe routing and the pages for each step |
| You need to learnAn integration app rather than an Extend UI | Filter or sampleThe integration create flow, Copy from App Catalog | What you still writeThe tenant configuration the overview describes |
| You need to learnA blank shell an agent will fill | Filter or sampleStart from Scratch, or a prompt that builds a shell | What you still writeEverything, including the security domain |
The Developer Agent prompt guide includes “Build a complete shell for a Project Tracker app including a Business Object for Tasks and a dashboard page.” That prompt is how you start when no catalog app is close. It creates model components. App Builder warns, when you add a model component, that promotions to Implementation, Sandbox, and Production queue until the Friday maintenance window. The components it lists are attachment, business object, business process, report, security domain, and task.
Then let the agent amend the copy
Connect the development tenant before you ask for pages that read or write the copied objects. Open the app in App Builder and prompt against the names that are actually in the copy. The prompt guide’s pattern is specific: “Update my EmployeeList PMD to include a search bar at the top that filters by last name,” not “make the list nicer.”
A workable first amendment names all four of these:
- The app, if you are not already inside it in App Builder. The prompt guide says the best place to ask about your app is in App Builder, and it says to be specific.
- The component id as it exists in the copy, not the name you wish it had.
- The behavior change, including which field is required or which route should change.
- What must not change. In particular, say not to add a new business object if the copy already has one. A second object is another model component, and you cannot remove a model component that has deployed in a previous version.
Review added components in green and updated ones in yellow. Apply only the files you intended. Validate. Save to App Hub. Deploy to the development tenant. Then follow that app’s overview for configuration. Developer Agent does not configure security. If the copy shipped a security domain, you still create the domain security policy in the tenant, grant a security group, and activate pending changes. The nomination tutorial does this for a from-scratch app. A catalog copy does not skip it.
Search on the Developer Site returns catalog apps alongside docs and APIs. That is useful for discovery. It is not a deploy button. “View App” then “Create Copy” is the deployable step.
Failure modes
- The copy will not create. The reference ID was used before, including by an app you deleted. Pick a new id. Do not try to overwrite the catalog app’s id.
- You prompted against “the donation app” and the agent created a parallel object. The copy’s object was named something else. You now have two model components. Keep the one the pages call. Do not promote the extra one if you can avoid it.
- Preview works and the tenant says you have no access. The domain is in the app and the policy is not active in the tenant. Overview instructions for the catalog app are the checklist. The agent will not complete them.
- You expected the catalog original to update your copy. Workday does not describe that link. Your copy is your source from the moment you create it. Put it on disk and in version control before the next agent session.
- You filtered only by type and copied a presentation-only app, then asked for stored records. Stored records need a business object. Filter Model first, or expect the agent to add one and to queue the weekly update.
Frequently asked questions
Is a catalog app safe to promote to production as-is?
Workday says each overview carries deployment and configuration instructions. That is the opposite of a one-click production install. Copy it, configure it, validate it, deploy it to a development tenant, and promote level by level when the tests pass. Production promotion still shows you a checklist you have to accept.
Can Developer Agent start from the catalog without a copy?
The published create options are copy, zip upload, and start from scratch. The agent modifies an app you have. Create the copy first, then prompt inside it.
Do model components in the copy deploy immediately?
On a development tenant, you deploy the app to test. On Implementation, Sandbox, and Production, new or updated model components deploy with the weekly service update, and you have to promote before the weekly deadline or you wait an extra week. Copying an app that already has a business object means you inherit that rule on the first promotion.
What if I only wanted the page layout?
Prefer a presentation-only example, or copy the app and do not promote it. Once a model component has deployed in a promoted version, Workday says you cannot remove it. Layout ideas are cheaper to retype than a permanent object you did not mean to ship.