Skip to content
KiweelyKiweelyKiweely

Using an AI Agent to Document an Inherited Workday Studio .lar Before Touching It

For inherited Studio assemblies, use AI to inventory components and risks first. Do not rewrite XSLT until fixtures and AUnit exist.

  • By Kiweely
  • Updated
  • 1 min read

Inherited CLARs rarely include author notes. Before modernization:

  1. Ask the assistant to list components, XSLT assets, Java beans, and outbound endpoints from the project files.
  2. Mark secrets that must live in the tenant, not the assembly (Studio docs warn against passwords in integrations).
  3. Capture one golden message per major branch.
  4. Add AUnit skeletons.
  5. Only then triage Orchestrate vs keep-in-Studio.

Documentation without fixtures still leaves you blind at deploy time.

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.