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 (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 |
|---|---|---|
| Tenant Configuration Dimension1. Eligible Time Off Types & Plans | Real-World Variation Inside One TenantUS Hourly sees PTO (Hours) + Sick; UK Salaried sees Annual Leave (Days); California sees Floating Holiday | What Breaks If a UI Guesses Instead of InspectingHardcoded dropdowns show plans the worker cannot take or miss statutory regional plans. |
| Tenant Configuration Dimension2. Unit of Time & Entry Mode | Real-World Variation Inside One TenantHours (e.g., 8.0 or partial 2.5), Days (1.0 or 0.5), or required Start Time / End Time clock fields |
What Breaks If a UI Guesses Instead of InspectingSubmitting dailyQuantity: 8 against a Days plan either requests 8 full days or throws a validation fault. |
| Tenant Configuration Dimension3. Work Schedule, Holidays & DTI | Real-World Variation Inside One TenantDays To Include (DTI) + worker Holiday Calendar (Thanksgiving, regional bank holidays, 4x10 shift schedules) |
What Breaks If a UI Guesses Instead of InspectingWorkers accidentally deduct 8 hours of PTO on a paid company holiday or unscheduled Sunday. |
| Tenant Configuration Dimension4. Multi-Job Position Prompt | Real-World Variation Inside One TenantRequire Position on Time Off Request enabled on worker-based plans when a worker holds multiple active positions | What Breaks If a UI Guesses Instead of InspectingSubmission fails with a missing position reference error for dual-role workers. |
| Tenant Configuration Dimension5. Projected Balance & Lower Limits | Real-World Variation Inside One TenantDynamic balance as of target date (Start of Period vs. End of Period), Time Off Lower Limit (0 vs. -16), Unpaid Time Allowed? |
What Breaks If a UI Guesses Instead of InspectingStatic “current balance” badges lie about December availability or fail to warn before hitting a 0 floor. |
| Tenant Configuration Dimension6. Required Reasons, Comments & Attachments | Real-World Variation Inside One TenantBereavement requires a Reason code; Jury Duty or 3+ consecutive Sick days requires a document attachment |
What Breaks If a UI Guesses Instead of InspectingGeneric forms omit conditional attachment uploaders or reason pickers, causing HTTP 400/500 validation rejections. |
| Tenant Configuration Dimension7. Business Process Routing & Custom Labels | Real-World Variation Inside One TenantApproval by Manager, skip rules, custom translations (translated plan descriptors) |
What Breaks If a UI Guesses Instead of InspectingConfirmation screens cannot tell the worker who actually approves next. |
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), Leaf’s agents query your tenant’s live metadata:
- Absence & Time Off Configuration: Reads configured
Time Offtypes, planUnit of Timedefinitions (Hoursvs.Days), lower limits, reason requirements, and whether multi-job position selection is active. - Business Process Definition (
Request Time Off): Inspects initiation actions (SubmittedWIDd9e4223e446c11de98360015c5e6daf6), conditional routing steps (Approval by Manager,HR Partnerreview thresholds), and custom validation rules. - Translations & Terminology: Checks enabled languages on
Edit Tenant Setup - Globaland verifies Spanish translations onTranslate Business Objectso 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 LeaveandCore Navigation/Systemscopes—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:
# 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.1Look 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.
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 offersFull Day (1.0)/Half Day (0.5). If their plan usesHours, it defaults to their scheduled daily hours (8.0or10.0on a 4x10 shift) with clean partial-hour steppers. - Conditional Prompts Only When Needed: If the worker holds only one position, no confusing
Positiondropdown 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 is live today on Mac and Windows, while Kiweely 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.