Skip to content
KiweelyKiweelyKiweely

Put a Workday Extend App in Git from Day One

Local disk sync writes App Builder and Orchestration Builder edits to a folder and reads edits back. Put that folder in Git. Commit before an agent session, because Discard Changes destroys the browser session and a promoted model component cannot be removed.

  • By Kiweely
  • 6 min read
On this page

Workday does not host your Extend pull requests. App Hub hosts the app version you saved. Git becomes useful the day you turn on local disk sync, which is the feature Workday documents for this. You download the app from App Hub into a folder, open that folder, and from then on App Builder and Orchestration Builder write their edits to disk. Edits you make in the folder show up in those builders. Workday names Git as the version-control system this is meant to feed.

Do it before the first long Developer Agent session, not after the first diff you wish you could undo. Discard Changes in App Builder throws away the browser session and returns to the version saved in App Hub. Workday says that discard cannot be undone. A commit made before you prompted is the copy Discard Changes cannot delete.

The folder Workday expects

The IntelliJ plugin concept publishes the layout. Use it even if you never open IntelliJ, because App Builder is editing the same kinds of files.

apps/
└── {appID}/
    ├── attributes/
    │   └── default.attributes
    ├── model/
    ├── orchestration/
    └── presentation/
        ├── pods/
        └── scripts/

Presentation files are the AMD, the SMD, and the PMDs, plus pods and scripts in those subfolders. Model files are business objects, business processes, security domains, attachments, tasks, and reports. applicationID in the AMD is read-only. The plugin shows an error if you change it. Do not “normalize” it in a commit.

The same page marks the orchestration folder read-only. Local disk sync, on a different page, says changes in the local folder outside the browser are reflected in Orchestration Builder as well as App Builder. Those two sentences are both published. Practically: let Orchestration Builder own orchestration edits so they sync down, and do not hand-edit files the plugin has already told you are read-only. If a local edit and a builder edit disagree, you will find out at the next sync, not at code review. Commit small, and look at the diff before you upload.

wdcli app download with --latest-version is the command that pulls an app into a directory. wdcli app upload sends the directory back to App Hub. wdcli app copy copies a local app to a new directory with a new reference ID. wdcli app preview serves a local preview, and it is wrong if local disk sync is pointed at a different folder than the CLI. Preview from the folder you cloned.

What belongs in the first commit

Commit the app source the moment the copy or the scratch app has a name. The reference ID is the painful part. It is the id you chose plus an account id, and you cannot reuse it even if you delete the app. A catalog copy spends an ID the first time you click Copy. Put that copy in Git under a directory named for the reference ID so nobody creates a second copy “because the first one was just an experiment.”

Leave out:

  • The tenant sign-in the tutorials email you. It is not source.
  • Anything the CLI stored for wdcli auth login. The install page has you sign in through the browser. That session is not an app file.
  • A second copy of the app with a slightly different reference ID, unless you mean to maintain two apps.

Include the attributes file. Workday says that when you download an app or deploy it to another account or tenant, App Builder includes the app attributes. If they are not in the commit, the next machine’s upload is a different app than the one you tested.

A rhythm that survives an agent

Developer Agent can rewrite many files in one invocation. Green means added, yellow means updated, and Apply Changes is what lands them in the session. The Git rhythm that matches those buttons:

  1. Sync so the folder matches App Hub. Commit. The message should say what this version is for, not “agent.”
  2. Prompt once, for one outcome, with real component names.
  3. Read the disk diff, not only the chat’s “What was built” list. The disk diff is the AMD route that appeared, the business object that appeared, and the page you asked for.
  4. If the diff adds a model component you did not ask for, reject it before you save. After a model component has deployed in a promoted version, Workday does not let you remove it. Git can revert the file on Development. Git cannot delete the object from a tenant that already received it on Friday.
  5. Validate, then save or wdcli app upload. Commit the saved result as a second commit if the agent changed more than you will remember from the prompt.
  6. Deploy to a development tenant from that commit, not from an uncommitted buffer.

Two people in App Builder on the same app, without this folder, are sharing a session and App Hub. Two people with two clones are in Git, and they still have one App Hub version when they upload. Agree who uploads. The hub does not merge PMD files for you. A later upload replaces the version.

The CLI promote command is how a reviewed commit moves to Implementation. It does not skip the Thursday deadline for model components, and it does not skip the one-level rule. Merging to your default branch is not a Workday promotion. Say that in the README of the repo so a new developer does not think git push deployed Sandbox.

Failure modes

  • You discarded the session and the good prompt went with it. There was no commit. Run the prompt again, and start committing.
  • Preview and App Builder disagree. Local disk sync and wdcli app preview are not on the same folder. Point them at the clone.
  • The orchestration file will not stay edited. The IntelliJ layout marks that folder read-only. Make the change in Orchestration Builder and let sync write the file, then commit what sync wrote.
  • A reverted Git file did not revert Sandbox. Sandbox has the promoted version. Reverting main changes what you can upload next. It does not roll back a weekly service update.
  • The reference ID in the folder was edited to look nicer. App Hub already bound the old ID. You cannot switch to an ID that was used before, and you should not expect a renamed folder to rename the app.

Frequently asked questions

Does App Hub replace Git?

No. App Hub stores the builds you save and the versions you promote. Git stores the review history Workday tells you to attach through local disk sync. You want both. Hub without Git means Discard Changes is your only undo. Git without an upload means the tenant never sees the commit.

Can I start the repo from a catalog copy?

Yes. Create Copy, download or sync that app into a folder, and commit before you prompt Developer Agent to amend it. The copy’s reference ID is already spent. Do not delete the app and recreate it to “start clean.” That ID is gone.

Should orchestrations be in the same repository?

They are part of the app folder Workday syncs. Keep them in the same repo as the PMD and the model. Edit them in Orchestration Builder. Treat a hand-edit of a read-only orchestration file as unsupported, because the plugin concept says the folder is read-only even though sync will reflect external edits back into the builder.

When do I commit relative to Validate?

After the diff looks right, and again after Validate is clean and you have saved to App Hub. A commit of a file that fails Validate is a useful “this is what the agent proposed” snapshot only if the message says it does not build. Do not tag that commit as the version you deployed.

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.