---
title: "How AI Agents Inspect Workday Before Building a Screen"
description: "How Kiweely Leaf inspects your live Request Time Off business process, eligible absence plans, hours vs days units, and routing before drawing a single field."
url: https://kiweely.com/blog/from-plain-english-prompt-to-live-workday-screen-how-leaf-works
---

# From One Sentence to a Live Workday Screen: How AI Agents Inspect Your Tenant Before Designing

Generic AI code generators guess Workday endpoints and invent broken forms. Kiweely Leaf inspects your live tenant metadata first—reading your actual Request Time Off business process, absence plan units, eligibility rules, and approval routing—before rendering or wiring a single control.

-   By Kiweely
-   November 15
-   6 min read

Type *“Build a clean mobile time-off screen for our warehouse and corporate staff”* into a generic AI app builder and it will draw a pretty calendar with a hardcoded dropdown (`Vacation`, `Sick`, `Personal`) and an `"Hours"` text box that fails on your very first real Workday employee. **[Kiweely Leaf](https://kiweely.com/leaf)** (coming next) works in the exact opposite order: before drawing a single form control, Leaf’s AI agents **inspect your live Workday tenant**—reading your real `Request Time Off` business process definition, eligible absence plans, unit types (`Hours` vs. `Days`), schedule calendars, and approval chain—so the screen matches how your tenant actually runs.

Two Workday customers never share the same `Request Time Off` configuration. Even inside a single company, a salaried London manager, a California hourly associate, and a part-time employee holding two concurrent positions hit completely different validation rules inside Workday’s Absence engine.

## What Actually Hides Behind “Request Time Off” in a Real Workday Tenant

When an HRIS administrator configures Absence Management (`Create Time Off Plan`, `Edit Time Off`, and the `Request Time Off` business process definition), at least seven tenant-specific rules determine what a valid UI screen must show and submit:

| Tenant Configuration Dimension | Real-World Variation Inside One Tenant | What Breaks If a UI Guesses Instead of Inspecting |
| --- | --- | --- |
|  **1\. Eligible Time Off Types & Plans** | US Hourly sees *PTO (Hours)* + *Sick*; UK Salaried sees *Annual Leave (Days)*; California sees *Floating Holiday* | Hardcoded dropdowns show plans the worker cannot take or miss statutory regional plans. |
|  **2\. Unit of Time & Entry Mode** | `Hours` (e.g., `8.0` or partial `2.5`), `Days` (`1.0` or `0.5`), or required `Start Time` / `End Time` clock fields | Submitting `dailyQuantity: 8` against a `Days` plan either requests 8 full days or throws a validation fault. |
|  **3\. Work Schedule, Holidays & DTI** |  **Days To Include (DTI)** + worker **Holiday Calendar** (`Thanksgiving`, regional bank holidays, 4x10 shift schedules) | Workers accidentally deduct 8 hours of PTO on a paid company holiday or unscheduled Sunday. |
|  **4\. Multi-Job Position Prompt** |  **Require Position on Time Off Request** enabled on worker-based plans when a worker holds multiple active positions | Submission fails with a missing `position` reference error for dual-role workers. |
|  **5\. Projected Balance & Lower Limits** | Dynamic balance as of target date (`Start of Period` vs. `End of Period`), `Time Off Lower Limit` (`0` vs. `-16`), `Unpaid Time Allowed?` | Static “current balance” badges lie about December availability or fail to warn before hitting a `0` floor. |
|  **6\. Required Reasons, Comments & Attachments** |  *Bereavement* requires a `Reason` code; *Jury Duty* or 3+ consecutive *Sick* days requires a document attachment | Generic forms omit conditional attachment uploaders or reason pickers, causing HTTP `400`/`500` validation rejections. |
|  **7\. Business Process Routing & Custom Labels** | `Approval by Manager`, skip rules, custom translations ([translated plan descriptors](https://kiweely.com/guides/workday-custom-labels-translations-reading-tenant-terminology)) | Confirmation screens cannot tell the worker [who actually approves next](https://kiweely.com/guides/workday-find-approver-chain-supervisory-org-business-process). |

## Walking Through How Kiweely Leaf Goes From One Sentence to a Live Screen

Suppose an HRIS admin connects their Sandbox tenant once with a user-delegated Workday API client (`Register API Client`) and types one sentence into **Kiweely Leaf**:

> *“Create a 3-step Request Time Off screen in English and Spanish that shows projected balances on the chosen dates, skips company holidays automatically, and tells the worker who will approve it.”*

Trace the four stages Leaf’s AI agents run behind the scenes before presenting the live preview:

### Stage 1: Inspecting Tenant Metadata, Schemas, and Security Domains

Instead of guessing routes ([why generic prompt builders stall on Workday](https://kiweely.com/blog/retool-superblocks-lovable-on-workday-oauth-trap)), Leaf’s agents query your tenant’s live metadata:

-   **Absence & Time Off Configuration:** Reads configured `Time Off` types, plan `Unit of Time` definitions (`Hours` vs. `Days`), lower limits, reason requirements, and whether multi-job position selection is active.
-   **Business Process Definition (`Request Time Off`):** Inspects initiation actions (`Submitted` WID `d9e4223e446c11de98360015c5e6daf6`), conditional routing steps (`Approval by Manager`, `HR Partner` review thresholds), and custom validation rules.
-   **Translations & Terminology:** Checks enabled languages on `Edit Tenant Setup - Global` and verifies Spanish translations on `Translate Business Object` so Spanish-speaking associates receive localized plan descriptors natively from Workday.
-   **API Client Functional Area Check:** Verifies that the registered API client includes `Time Off and Leave` and `Core Navigation` / `System` scopes—flagging any missing domain permission in plain English before you ever test with an employee.

### Stage 2: Composing the Multi-Call Live API Sequence

Leaf’s agents never wire a naive single-POST form. For a time-off screen, Leaf automatically wires Workday’s exact `absenceManagement/v5` and `businessProcess/v1` sequence:

http

```
# 1. On screen open: load worker's eligible absence types & current balances
GET /ccx/api/absenceManagement/v5/{tenant}/workers/me/eligibleAbsenceTypes HTTP/1.1

# 2. As soon as the worker taps target dates: project balance AS OF the last requested date
#    and validate scheduled workdays + holidays via validTimeOffDates
GET /ccx/api/absenceManagement/v5/{tenant}/balances?worker={me}&effective=2026-11-27 HTTP/1.1
GET /ccx/api/absenceManagement/v5/{tenant}/workers/{me}/validTimeOffDates?timeOff={typeID}&date=2026-11-25&date=2026-11-26&date=2026-11-27 HTTP/1.1

# 3. On submit: POST only valid scheduled dates with exact unit quantities, then read inProgressSteps
POST /ccx/api/absenceManagement/v5/{tenant}/workers/{me}/requestTimeOff HTTP/1.1
GET /ccx/api/businessProcess/v1/{tenant}/events/{eventID}/inProgressSteps HTTP/1.1
```

Look at what step 2 accomplishes automatically: when an associate selects Wednesday Nov 25 through Friday Nov 27 during US Thanksgiving week, `validTimeOffDates` sees Thursday Nov 26 (and Friday Nov 27 if configured on their **Holiday Calendar**) as non-requestable holidays. The UI immediately badges Nov 26 as *“Paid Company Holiday — 0 hrs deducted”* and stages `8.0 hours` only on valid working days—while showing their exact [projected balance as of Nov 27](https://kiweely.com/guides/workday-accrued-time-off-balance-as-of-future-date).

### Stage 3: Generating Branded, Role-Adaptive UI Without `.pmd` Limits

Because **Kiweely Leaf** runs outside Workday’s `.pmd` layout engine (**no Workday Extend license required**), the generated interface adapts cleanly to your brand typography, colors, and target form factor:

-   **Dynamic Unit Controls:** If the signed-in worker’s selected plan uses `Days`, the quantity control offers `Full Day (1.0)` / `Half Day (0.5)`. If their plan uses `Hours`, it defaults to their scheduled daily hours (`8.0` or `10.0` on a 4x10 shift) with clean partial-hour steppers.
-   **Conditional Prompts Only When Needed:** If the worker holds only one position, no confusing `Position` dropdown ever appears; if a dual-job worker signs in on a plan requiring position selection, the selector renders automatically.
-   **Human-Readable Validation Feedback:** If a tenant **Custom Validation** rule fires (for example, *“Floating Holiday must be taken in full-day increments”*), Leaf translates Workday’s structured error response into an inline field message next to the date row instead of dumping raw API fault codes.

### Stage 4: Persona Verification in Sandbox and Instant Multi-Channel Publish

Before publishing to your workforce, the HRIS admin tests the live screen against real Sandbox worker personas—verifying how it renders for a Spanish-speaking `Warehouse 4` hourly associate versus an exempt manager.

Once approved, one click publishes the screen simultaneously across:

-   **Any desktop or mobile browser** at your company’s custom subdomain (`timeoff.yourcompany.example`),
-   **Embedded workplace chat tabs** inside **Microsoft Teams, Slack, DingTalk, Feishu, or Lark**, and
-   **Your company’s branded space inside the Kiweely Leaf phone app** on iOS and Android (one public store install, Workday SSO + Face ID/fingerprint, privacy-safe push notifications, zero App Store review waits).

Throughout both testing and production, **zero employee HR data is stored at rest** on Kiweely servers—every call executes live in memory under the signed-in employee’s own Workday OAuth token. \*(And if you also build in-tenant Workday Extend apps or Studio integrations, **[Kiweely Vine](https://kiweely.com/vine)** is live today on Mac and Windows, while **[Kiweely Bridge](https://kiweely.com/bridge)**—coming next alongside Leaf—brings the same governed Workday actions directly into Claude, ChatGPT, and Gemini.)\*

## Frequently asked questions

### Why can't a generic prompt-to-UI tool build a working Workday Request Time Off screen?

Every Workday tenant configures different Time Off Types, unit tracking (hours vs. days vs. start/end timestamps), multi-job position prompts, holiday calendars, lower balance limits, and comment or attachment requirements. Without inspecting tenant metadata first, generated UI code fails on real workers.

### Does Kiweely Leaf store employee absence history or HR records while inspecting the tenant?

No. During design time, Leaf's AI agents inspect structural configuration metadata (business process definitions, plan units, WQL schemas, security domains). At runtime, every employee request executes as a stateless pass-through in memory with zero HR data stored at rest.

### How does a single screen handle both salaried US employees tracking Days and hourly warehouse staff tracking Hours?

Because Leaf binds form controls dynamically to Workday's per-worker eligibility and validTimeOffDates responses under each signed-in employee's OAuth token, an exempt worker on a Days plan sees whole/half-day controls while an hourly worker on an Hours plan sees hour quantities automatically.

### Do HRIS administrators need to write PMD, AMD, or WQL queries to build a screen in Kiweely Leaf?

No. HRIS administrators connect their tenant once with a standard Workday API client and describe the screen in plain English. Leaf's agents wire REST, WQL, RaaS, and SOAP calls automatically without requiring a Workday Extend license.

## Read next

[All posts](https://kiweely.com/blog)

-   [November 15 ### How to Give Employees Live Workday AI Answers Without Flex Credits or Workday Extend](https://kiweely.com/blog/connecting-ai-to-workday-without-flex-credits-or-extend)
-   [November 15 ### Bringing Developer-Built Web Apps and HRIS-Built Screens Together in One Employee App](https://kiweely.com/blog/combining-agent-built-and-developer-built-workday-web-apps)
-   [November 15 ### Using an AI Admin Agent to Configure Workday API Clients and Test Role Boundaries](https://kiweely.com/blog/ai-admin-agent-for-workday-connector-setup-and-role-testing)

### More guides on Custom agents and Workday AI

[All 91 guides](https://kiweely.com/guides#custom-agents)

-   [Stop or audit a Workday AI agent: an admin runbook](https://kiweely.com/guides/stop-audit-workday-ai-agent-admin-runbook)
-   [Workday Developer Agent Prompt Templates That Hold](https://kiweely.com/guides/workday-developer-agent-prompt-templates)
-   [A Learning Path on a Workday Build Personal Tenant](https://kiweely.com/guides/workday-build-personal-tenant-learning-path)
-   [Build Your First Workday Extend App with Developer Agent](https://kiweely.com/guides/first-workday-extend-app-developer-agent)
-   [What counts as Workday test evidence when an agent helped](https://kiweely.com/guides/workday-uat-evidence-pack-ai-agents)
-   [Security workshops that follow Workday’s own access model](https://kiweely.com/guides/security-design-workshops-deployment-agent)
-   [Pick a Workday integration tool before you prompt an agent](https://kiweely.com/guides/ai-workday-integration-design-workshop)
-   [Is there an AI agent that can do Workday configuration, business processes and security changes in a tenant for me?](https://kiweely.com/guides/ai-agent-for-workday-configuration-business-process-security)

## 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.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## 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.
