Skip to content
KiweelyKiweelyKiweely

Versioning and Rollback for AI-Built Employee Screens

Leaf stores screen layouts and shows a change the next time someone opens the app, after you publish. The public page does not describe a numbered history or a one-click rollback. Keep the last approved description and republish it.

  • By Kiweely
  • 2 min read
On this page

An employee screen built from a sentence can be changed with another sentence. That is the point, and it is also how a bad change reaches every phone before lunch. The control is the publish step, not a hope that the model remembers yesterday.

Kiweely Leaf (coming next) says nothing reaches employees until you say so. A change you publish is there the next time they open it. Leaf stores app layouts, branding, and tenant connection settings. It does not store worker records. The public page does not describe version numbers, a diff of two layouts, or a one-click rollback. This note stays inside that description.

What you can do with what is published

Treat the published layout as the only employee-facing copy. The sentence you approved is the source you can hand back. When a change is wrong, describe the previous screen again, review it the way you reviewed the first one, and publish that. Until you publish, employees keep the last published layout.

Workday is untouched by that rollback. Elections, expense reports, learning completions, and job applications already submitted went through Workday business processes. Putting the old layout back does not rescind those events. If the bad layout submitted the wrong process, you correct the events in Workday. The screen history is not the system of record.

Two people editing the same screen produce one published result. The last publish is what employees open next. There is no documented merge of two drafts. Agree who publishes before two admins describe changes on the same day. That role split is an operating rule; the public Leaf page does not yet list a requester role and a publisher role. See who can publish.

Where to try the change

Workday’s own open enrollment guidance is the pattern: test in a non-production tenant, including the business process you are about to call, before workers in production see it. Connect the screen to that tenant first. A layout that looks right and calls the wrong event type is not a cosmetic defect. Publish to production after the non-production submit lands on the process you intended.

Because Leaf keeps no worker payload, you also do not have a server-side recording of who saw the broken layout. If you need that for an incident, it has to come from Workday’s business process history (who submitted) rather than from a Kiweely log of page views. The product statement is that reads are gone when the request ends.

A small habit that replaces a version browser

Keep a short record outside the employee app: the date, the sentence you approved, and which Workday process the screen submits. When you roll back, you are republishing that sentence, then checking one worker in the non-production tenant. That is the rollback that exists today in the public design.

Tell us the screen you want built. Say if a published change must wait for a named approver. Coming next means that behavior is not on your tenant yet.

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.