Skip to main content
Documentation
Documentation
Administrator Guide
Last Updated: 2024-07-26
Concept: Configuration Change Tracker

Concept: Configuration Change Tracker

The
Configuration Change Tracker
 report is an implementation tool that reports changes to configuration data in a tenant over a selected timeframe and by selected users. It frees you from having to track your tenant changes manually in preparation for later migration. It also enables you to see who else has made changes in a tenant.
Example: You've been making changes to objects in your sandbox tenant for the last week or so. You've verified that each change works well in the sandbox tenant and now want to migrate your changes to a production tenant. In the sandbox tenant, you access the
Configuration Change Tracker.
 You name the report, First week in July, and include your name in the title. You select the last 7 days as the date range. You select yourself on the
Filtered by Users
 prompt. You leave the
Include Changes Made via Web Services
 check box clear because you didn't make changes through web services or an Enterprise Interface Builder (EIB) integration system.
You run the
Configuration Change Tracker
 report. It returns all instances of objects that you modified in the specified date range. If the object that you modified was also modified by another user in the same timeframe, it returns the name of that user, too.
Configuration Change Tracker
 only returns a changed instance when it belongs to an Implementation Type that Workday can migrate. If a changed object doesn't have an Implementation Type, or Workday can't migrate the Implementation Type,
Configuration Change Tracker
 doesn't include it.
Configuration Change Tracker
 can include up to 2 million configuration changes in a report. This limit is based on the total number of changes in the tenant, not the number of configuration changes.

Report Organization

Configuration Change Tracker
 displays and organizes this information to help you prepare for migration:
We plan to enable
Configuration Change Tracker
 to migrate changes in a future release.
Tab
Contents
Ready to Migrate
Lists changed instances in the tenant that you can migrate without further modification. Depending on the type of change, the report might display:
  • The last modified date of the change.
  • The Implementation Type and the Primary Instance.
  • The Reference ID of the Primary Instance.
  • The method of change: Manually in Workday or through a web service.
  • A change flagged as a new instance.
  • The user making the change.
For each instance, you can click
View Changes
 to see an audit trail of changes for the Primary Instance.
Not Ready to Migrate
Lists changes that you probably don't want to migrate, such as deleted instances. It also includes instances that might cause problems, such as missing reference IDs or instances that might not work correctly with the web service.
Depending on the reason an instance isn’t ready for migration, the report might display:
  • The timestamp for the last change.
  • The Implementation Type, Related Implementation Type, and Primary Instance.
  • The Workday task used to make the change.
  • The Reference ID of the Primary instance.
  • The method of change: Manually in Workday, through a web service, or unclassified.
  • The tool used to make the change, such as Object Transporter (OX) or Enterprise Interface Builder (EIB).
  • A change flagged as a new instance.
  • The user making the change.
For each instance, you can click
View Changes
 to see an audit trail of changes for the Primary Instance.

Access to Configuration Change Tracker

Workday Security Administrators can grant users access to
Configuration Change Tracker
 by making them part of the security group that has permissions to  the
Configuration Change Management
 domain. Configure access for each tenant in which you want to run the
Configuration Change Tracker
.
To view previously run reports, users can access the report,
View Change Tracker Reports
.

Audit Trails

You can view the details on any configuration changes made in a tenant by selecting
View Changes
 for a Primary instance. Workday recommends that you don't use
View Changes
 as the only method for auditing tenant changes because
Configuration Change Tracker
 reports only direct changes to objects. It doesn't report changes to processes or other behavioral changes. 
Examples: You make a change to a calculated field. The change affects how an associated Condition Rule behaves. It also changes a business process step and how a custom report behaves. 
Configuration Change Tracker
 reports your direct change to the field. It also reports changes to the business process step. However, it doesn't report the changes in behavior in the Condition Rule or custom report. Viewing the change details in
Configuration Change Tracker
  therefore doesn't always provide you with a complete audit trail.

Example

Watch the video
 6m 09s