Workday Extend
Built for Extend. Proven in your tenant.
From a sentence to a tested app in your Development tenant, then promoted when it is proven. One closed loop. You approve every step that touches Workday.
The loop
- 01
Describe it
Type it, or drop the requirement documents you already have. kiweely asks its questions before it designs.
Real kiweely screens with example data. - 02
It builds
It reads how your other apps are put together and writes the object model, the pages and the orchestration the same way, naming what it does.
Real kiweely screens with example data. - 03
Workday validates
Check for errors sends the app to your tenant's own validation. What Workday rejects comes back in plain language, and kiweely fixes it and asks again.
Real kiweely screens with example data. - 04
You approve the deploy
Deploying to your Development tenant stops for a card that names the app and the tenant. Allow it once, or for that conversation.
Real kiweely screens with example data. - 05
Tested in a browser you can watch
kiweely opens the app in a visible browser, walks the flow as the employee and the manager, fixes what it finds, and tests again.
Real kiweely screens with example data. - 06
Promoted when it is proven
One level at a time, Development to Implementation to Sandbox, each with its own approval. Production stays yours in the Developer Site.
Real kiweely screens with example data.
What it writes
The same artifacts Workday Extend uses, in your own account.
You will not be asked to read any of them. They are there for your technical consultant to review, in the same tenant, under the same names Workday uses.
- App model definitions
- The business objects and fields your app stores.
- Page definitions
- The screens people use, with their layout and actions.
- Orchestrations
- The steps that move a request between statuses and call Workday.
- Workday queries
- The data your pages and reports read from the tenant.
Two things it always stops for
Even when you have told it not to ask.
-
Changes to the app's model once it lives beyond Development.
A field or object change to an app that is already in Implementation or Sandbox can never be undone in Workday. kiweely shows you the full list of model changes and waits. No session grant answers this one.
-
Production, and an app's first install in a tenant.
Neither is something kiweely's tools can do. Both stay your own action in the Workday Developer Site, with your review and change control.
Version history
Every turn is a version. Restore any of them.
kiweely records the app and the project's documents after each turn and before every save, publish or delete. "Restore everything to an earlier version" puts the whole project back; each document offers its own previous versions. No repository in your folder, nothing to set up.
Production
Whatever you build still moves to Production through your own path.
The same review, transport and change control any Extend app goes through today. kiweely does not create a side door around that, and it should not.
For Extend work you need a Workday Extend subscription and a Development-level tenant. Everything else on this site works with a normal Workday sign-in.
Ask. Approve. Done.
kiweely is a secure desktop app with an AI agent that works inside your real Workday tenant. Ask it anything, hand it admin work, or describe an Extend app and it builds, deploys and tests it in your tenant, and fixes what it finds. Nothing changes without your approval.
kiweely never grades its own homework. Workday does.