Skip to content
KiweelyKiweelyKiweely

Discovery questions Workday’s Deployment Agent can answer

A fit-gap workshop is a project meeting, not a Workday product. Deployment Agent can explain, inspect calculated fields and security in a non-Production tenant, and suggest Configuration Catalog packages. It cannot sign a fit decision. Read-only as documented; changes are in partner early access.

  • Checked against Workday on
  • Applies to Workday Extend
  • 7 min read
  • Published
  • By Kiweely
On this page

Workday has not published a fit-gap workshop, a discovery module, or a scoring method for “fit.” Discovery is your meeting. What Workday has published is a way to walk into that meeting already knowing what the non-Production tenant contains.

Deployment Agent with Ask runs in Implementation, Preview, Sandbox, and Customer Central. It grounds answers by searching, opening tasks, and running reports, and it retrieves Administrator Guide and Community content. The concept topic calls the configuration inspection read-only. It will not mark a requirement as in scope, and as documented it does not create the configuration the workshop just approved. Workday says that with Configuration Cloud, in opt-in early access for Workday partners since 18 November 2026, Deployment Agent can carry out changes once approved.

What to open before the workshop

Implementation tenants are Workday’s space for testing, prototyping, and training. Customers may have several, for integrations, legacy data, and unit and end-to-end testing. Sandbox is typically a copy of Production. Sandbox Preview is that copy plus functionality coming in a release, delivered to preview about five weeks ahead of the feature release. The Global Modern Services tenant is sample data for a fictitious customer, for research and learning, not a record of your design.

Use Ask in the tenant the workshop is talking about. In Implementation, Sandbox, and Preview it reads the active tenant. From Customer Central, name the connected tenant. Workday’s check that you are in the right place is: “What tenants are available to me?”

There is no badge that Ask is on. Before the session, ask for five calculation fields and confirm them in View Calculated Field. If the names are fiction, you are on documentation Q&A. Deployment Agent (Q&A) cannot see instances or security policies.

A workshop sequence that stays inside the product

Agree the requirement in one sentence in the room. Then use one prompt per requirement, in a new chat. Workday summarizes long threads and deletes history after 14 days. The decision log is the record, not the chat.

Question the room is actually asking Workday capability to use Prompt shape Workday published
Question the room is actually askingDo we share a definition? Workday capability to useKnowledge discovery Prompt shape Workday publishedRole, concept, “bullet points.” The published example is Top of Stack for a Workday administrator.
Question the room is actually askingDoes this tenant already do it? Workday capability to useTenant inspection Prompt shape Workday published“In my tenant, how does this calculated field work: [Calculated Field]” or custom reports by user or security group.
Question the room is actually askingWhat would we configure? Workday capability to useConfiguration intelligence Prompt shape Workday publishedFunctional area, “in my tenant,” numbered steps. The published example is a Financials calculated field for Scheduled Weekly Days.
Question the room is actually askingIs there a delivered package? Workday capability to useConfiguration Catalog, via Ask’s catalog support, then the catalog itself Prompt shape Workday publishedAsk for smart package suggestions. Then open View Configuration Catalog Content in Customer Central and filter by SKU or country.
Question the room is actually askingWhat will it hit? Workday capability to useWorkday Touchpoints Kit, in the tenant, not in the agent Prompt shape Workday publishedThe HCM course describes the kit as the picture of data flows and configuration relationships across areas you have deployed and areas you have not.

Worked prompts

Shared definition, first ten minutes.

As a Workday administrator, give me a layman’s terms explanation of the ‘Top of Stack’ concept. Provide the answer in bullet points.

Stop there. Put the bullets on the wall. Do not continue into design in the same thread.

What is already configured.

In my tenant, show me all custom reports created by [security group]. For each report, name the data source.

Workday’s published inspection prompt names the report list. The “for each, name the data source” clause is your addition. If Ask is on, check two reports in the tenant before you trust the list. If a report name does not open, discard the list.

A gap that is really a missing field.

I am an implementer working on Financials. In my tenant, provide step-by-step instructions on how to create a calculated field that counts Scheduled Weekly Days. Provide the answer in a numbered list of steps.

That is Workday’s new-configuration example plus “in my tenant,” which the sample-prompt topic says to include because nothing on screen shows that Ask is enabled. Take the steps to Create Calculated Field after the workshop. The agent does not create the field.

Delivered content instead of a custom build.

Configuration Catalog, in Customer Central, migrates Workday-provided content to implementation and sandbox tenants with Object Transporter, at no cost. Packages are sample locale-based reports, dashboards, integrations, and related items. Workday’s example is the HCM Condition Rules package: common condition rules and calculated fields you can use in business processes or change. Each package description includes the applicable SKU, the content, and prerequisites. Ask can suggest packages. The catalog task is where you see them. Test the content before anyone migrates it toward Production. Workday says that confirmation is yours.

What the agent must not decide

Workshop temptation Why it is outside the product
Workshop temptation“Mark this requirement Fit.” Why it is outside the productNo such status exists on the pages above.
Workshop temptation“Configure the default business process now.” Why it is outside the productInspection is described as read-only. The examples end with you editing.
Workshop temptation“Use the GMS tenant as our design.” Why it is outside the productGMS is fictitious sample data.
Workshop temptation“The chat is the requirements record.” Why it is outside the productDeleted after 14 days, and summarized when the thread gets long.
Workshop temptation“Skip security until build.” Why it is outside the productThe security example shows a field the role cannot see because a domain policy is missing View. That shows up in discovery if you ask.

How to record a fit decision without inventing a Workday object

For each requirement, write four lines in the project record the same day:

  1. The sentence the business asked for.
  2. The tenant you inspected, and whether Ask returned objects you could open.
  3. The Workday object family involved: a delivered business process type, a calculated field, a report, a domain policy, or a Configuration Catalog package. The HCM course is explicit that customers do not change delivered domains or the items secured on them. They define business process definitions and grant security groups on policies.
  4. The open point a person must confirm. Workday says the agent can be incomplete. A citation to the Administrator Guide is a lead, not a signature.

Workday’s optimization example belongs in this meeting when the requirement is “keep compensation grades and job requisitions consistent during high-volume hiring.” Ask for the practices, then open the grades and requisitions in the tenant and see whether those practices describe your data.

Failure modes

  • Running discovery in Production. There is no conversational Deployment Agent there.
  • Running it in Customer Central without naming the tenant. You may inspect the wrong connected tenant, or none.
  • Accepting a package suggestion without View Configuration Catalog Content. The suggestion is not the package.
  • Using Sandbox after a refresh as if last week’s prototype were still there. Sandbox is a copy of Production. Prototype work lives in an Implementation tenant, or in an extract you reloaded.
  • Letting one long chat cover security, a calculated field, and a report. Start a new chat per topic so summarization does not drop the field names.

Frequently asked questions

Can Deployment Agent run the fit-gap workshop?

It can answer the questions above in a non-Production tenant. It cannot host the workshop, score requirements, or store the decisions.

Should we inspect Production configuration by refreshing Sandbox?

Sandbox is typically a copy of Production, so a fresh Sandbox is the usual place to inspect what Production contains. Confirm the refresh has finished before you treat it as Production’s copy. Implementation tenants are the place for prototype configuration that Production does not have yet.

Does the Touchpoints Kit replace the agent?

No. The HCM course describes the kit as a visual of data flows and configuration relationships. Ask answers questions about configuration and documentation. Use the kit when a design in one area will hit another.

What if Ask and the task disagree?

Believe the task. Workday tells you to validate every suggestion against official documentation, and to rate the answer after you have checked it.

Sources checked

Public Workday topics listed above, fetched 2026-11-16. No Workday page fetched for this article defines a fit-gap workshop.

Sources checked

Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.

We’ll email you once to confirm. Unsubscribe in one click from any issue.