Skip to content
KiweelyKiweelyKiweely

How a client can test Workday when an agent is in the room

User testing happens in an implementation tenant, or in Sandbox when you mean to test a copy of Production. The client’s evidence is the business process event and the screen they saw. An agent transcript is a lead with a 14-day life, not a signature.

  • By Kiweely
  • 6 min read
On this page

The client is not testing the agent. The client is testing whether a person in a real security group can complete a real Workday task. Workday’s implementation tenants are the place it names for unit and end-to-end user testing. Sandbox is the place to test against a copy of Production. Deployment Agent can sit beside that test in those tenants. It cannot sign the result, and it cannot run the test as the client.

What the client should do with their own hands

Give the client a worker who is actually in the security group the design names, in the tenant you said you configured. Ask them to start the business process and finish their step. The result is the event: which definition ran, whether the step appeared, and who acted.

Workday selects the definition by inheritance. It looks for one on that organization, then on superiors, then the default. A definition with errors, or an inactive one, is skipped. If the client “tests the default” while their organization has its own definition, they tested the wrong one. Say the organization name in the script.

Conditions are part of the test, not a footnote. Entry conditions decide whether a step runs. Some are delivered and cannot be edited; yours are evaluated too, and the step runs only when all of them pass. Business Process > Test Rule on the event is the check, and it requires the Business Process Administration domain. An agent’s sentence “the condition looks right” is not that check.

If the client cannot see a field, that is often a domain policy, not a missing step. Workday’s own Ask example is a payroll role that cannot see a compensation field. The fix is the policy, then Activate Pending Security Policy Changes, then the client opens the field again. Until they open it, the test is open.

What the agent may do during the session

Tool Useful in the room Out of bounds
ToolDeployment Agent with Ask Useful in the roomExplain, in that non-Production tenant, which step and which domain are involved. Cite a guide topic. Out of boundsEnter the test for the client. Sign off. Serve as the record. Chat is deleted after 14 days and is not shared across tenants.
ToolDeployment Agent (Q&A) Useful in the roomDefine a term the room is misusing, such as Top of Stack, in plain language. Out of boundsProve what this tenant contains. It cannot see instances or policies.
ToolKiweely Vine Useful in the roomRun the screen after approval, or test with Start Proxy in a browser the room can watch, as a person whose access you mean to prove. File a test script from the tenant. Out of boundsClaim the client tested it if the client was not watching and the proxy was not their role. Production stays behind approval.

Vine is a desktop product. It is not Deployment Agent, and Workday’s catalog does not list it. Vine Free is free on a Workday personal developer tenant. Any other tenant needs a Personal license, $99 a month, or a firm seat at $149 a month.

There is no badge that tells the room Ask is inspecting the tenant. If the facilitator wants a tenant answer, the prompt has to say “in my tenant,” and someone has to open the object named in the reply before the client hears it as fact.

A session shape that survives a skeptical reviewer

  1. Say the tenant out loud. Implementation for a prototype. Sandbox only if this week’s refresh is the Production copy you intend to test. A Sandbox refresh wipes prototype work that lived only there.
  2. Say the person. Name the security group and the worker. Confirm they can sign in. Service-center or implementer access is not the client’s access.
  3. One scenario, one event. Hire, change job, or whichever delivered type you configured. You cannot invent a business process type.
  4. The client performs their step. Everyone else watches the event, not a chat window.
  5. On a miss, one prompt, then the task. Paste the step name and ask Ask which entry condition and which definition. Then run Test Rule or open the policy. Do not debug five scenarios in one thread. Workday summarizes long threads.
  6. Write the result from the event before the meeting ends. The chat will not be there in two weeks. A post-migration summary, if this test included a migration, will be there for two years. Use that for configuration tests, not for “the manager could approve.”

Failure modes the client will notice before you do

  • The facilitator demos as a security administrator. The client’s manager still cannot see the task. The domain policy was never granted to the manager’s group.
  • The script says “approve the title change” and the organization uses a different definition than the default you edited. Inheritance did its job. The script named the wrong organization.
  • Someone reads an Ask answer to the client as “Workday configured this.” The calculated-field and security examples both end with a person editing the tenant.
  • The team tests in Production chat. There is no conversational Deployment Agent in Production.
  • A proxy test runs as the implementer while the slide says “tested as employee.” The room watched the wrong groups.
  • The only notes are in the agent. Fourteen days later the client asks what they signed. You have the memory and not the event ID.

What to put in the client’s hands afterward

A short note, in their language:

  • Tenant and date.
  • Their name and security group.
  • The process they ran and the event they can ask you to open.
  • What they could do, and the one defect still open, tied to a condition test or a policy that is not yet activated.
  • No transcript. Offer to open the event on a call instead.

If a desktop agent wrote a test script, attach the script only after a person has checked it against that event. Kiweely’s copy says the script is written from the tenant. It does not say the script replaces the client.

Frequently asked questions

Can the client use Deployment Agent themselves?

Only if their security group is on the Deployment Agent Users domain and on the Ask skill, and only in a non-Production tenant or Customer Central. Most clients in a test are there to complete a business process step, not to operate the agent. Do not add every tester to the agent so they can “see the AI.”

Should the client test in the GMS tenant?

The Global Modern Services tenant is fictitious sample data for learning. It is not their configuration. Test their Implementation or Sandbox tenant.

What if the agent and the client disagree?

The client’s event wins. Use the agent to find the condition or the policy, then show the client the corrected step. Workday tells you the agent can be wrong.

Is a watched proxy session fair to count?

It is fair to count as a test of that proxied person’s access if the room watched the browser and you record the person and the event. It is not the client’s signature. The client’s signature is the client doing the step, or the client accepting a result they were shown in the event.

Sources checked

Public Workday topics listed above, fetched 2026-11-16. Vine’s proxy and test-script behavior is from kiweely.com, not from a Workday page. Workday does not publish a client-UAT product on the pages checked.

Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.

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