Skip to content
KiweelyKiweelyKiweely

How do I build a Configuration Change Tracker package by user and time?

Configuration Change Tracker builds a change list for selected users and a timeframe. Package Ready to Migrate instances as an Advanced configuration package, run blank reference ID and exception audits, then launch Object Transporter. Advanced packages migrate only what you selected.

  • Checked against Workday on
  • Applies to Workday Configuration Change Tracker
  • 3 min read
  • Published
  • By Kiweely
On this page

Configuration Change Tracker reports configuration changes in a tenant for the users and timeframe you select, then lets you turn that list into an Advanced configuration package and migrate it with Object Transporter. Workday positions it as the easy, safe way to synchronize changes made by specific people in a window.

Prerequisites

  1. Maintain Access to Customer Central Tooling set up for Advanced package migration, including OX Migration: Full Object Coverage.
  2. Customer Central Object Transporter access configured.
  3. Configuration Change Tracker security domains assigned (auditor and packager as needed). See Configure Security for Configuration Change Tracker.
  4. Sign in to the tenant that holds the changes you want to sync.

Build the change list

  1. Open the Configuration Change Tracker task.
  2. Set report criteria:
Option What to enter
OptionFrom Moment / To Moment What to enterDate and time range for the changes
OptionFiltered by Users What to enterOne or more users who made the changes
OptionInclude Changes Made via Web Services What to enterCheck if any selected user changed config through SOAP web services
OptionInclude Changes Made via REST What to enterCheck if any selected user changed config through REST
  1. Optional: filter by implementation type under Additional Filters, or open an existing saved report.
  2. Run or refresh until the report populates. Workday saves it as a Configuration Change Tracker report.
  3. Review Ready to Migrate versus Not Ready to Migrate. Use View Changes on a primary instance when you need the audit trail.

Ready to Migrate can be packaged without further edits. Not Ready to Migrate is omitted from the package unless you add rows manually later. Deleted or Do Not Use instances usually stay out.

Create the Advanced package

  1. Click Create Configuration Package for Ready to Migrate instances.
  2. Rename, describe, or add an external change request ID if you track approvals outside Workday.
  3. Choose instance filter:
Option Result
OptionAll Instances (default) ResultEverything on Ready to Migrate
OptionNew Instances Only ResultOnly instances created in the window by the selected users
OptionModified Instances Only ResultOnly instances edited in the window by the selected users
  1. Configure Package Instances to add or remove instances or implementation types. Add a Not Ready row here only when you have a deliberate reason.
  2. On Review and Prepare for Migration, run:
    • Blank Reference IDs, then View and Fix Errors when Workday can populate blanks.
    • System Generated Ref IDs, and rename only when you fear overwrite or accidental create on the target.
    • Exception Audits: Calculated Field Exception, Custom Report Exception, Report Specific Calculated Field Exception, Worklet Mappings Exception.
  3. Prepare for Migration. Workday redirects you to Customer Central.
  4. Launch Object Transporter. Advanced packages use manual dependency behavior: OX does not auto-add dependents after migration starts. You may add dependents later if Pre-Migration Diff reports them missing.

Migrate

Complete the Object Transporter flow: Include Translations if needed, resolve Pre-Migration Check (first 50 prerequisites at a time), review Pre-Migration Diff, set effective dates, choose Merge or Override for differing security policies, then Start Migration. Keep the Post-Migration report (retained 2 years).

Limits to remember

  • Change Tracker reports only migratable implementation types. Instances without an implementation type do not appear and will not migrate.
  • Reports can include up to 2 million configuration changes based on total tenant changes.
  • Change Tracker reports direct object changes, not behavioral side effects. Example: a calculated field change that also affects a condition rule reports the calculated field only.

Frequently asked questions

Who can see whose reports?

Self auditors see and create their own reports. Global auditors can view others’ reports. Packaging needs the matching packager domain. Details are on Configure Security for Configuration Change Tracker.

Why is my deletion on Not Ready to Migrate?

Workday lists deletions and other risky rows on Not Ready to Migrate and excludes them from the automatic package. Add them manually only when you intend to migrate that risk.

Sources checked

Related guides

All guides

Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.

We’ll email you once to confirm. Unsubscribe in one click from any issue.