Concept: Configuration Change Tracker
The
Configuration Change Tracker
(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. After making changes to configuration data in a Sandbox tenant and verifying that the changes work well, you want to migrate the changes to your Production tenant. First you need a list of the changes you made so you know what to migrate. Rather than recording each change manually, you use Configuration Change Tracker to provide a report for changes made:
- During the date range you specify.
- By you and any other users you want to include.
- Using or not using web services.
Ready to Migrate
and Not Ready to Migrate
.Configuration Change Tracker
only returns changed instances that belong to an implementation type that Workday can migrate. When a changed instance doesn't have an implementation type, Change Tracker doesn't report the change to the instance and Workday doesn't migrate the instance.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: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:
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:
For each instance, you can click View Changes to see an audit trail of changes for the Primary Instance. |
Access to Configuration Change Tracker
Security administrators can enable user access to
Configuration Change Tracker
by making them part of the security group that has access to 1 of these domains:
Domain | User Access | Permissions |
|---|---|---|
Manage: Configuration Change Management - Restricted
| Self auditor
Enables users to access Configuration Change Tracker and view and create their own reports. | View and Modify |
Configuration Change Management
| Global auditor
Enables users to access Configuration Change Tracker, create their own reports, and view other's reports. | View and Modify |
Manage: Configuration Change Management Migrations - Restricted
| Self packager
Enables users to create and edit thier own Advanced configuration packages from Change Tracker. | View and Modify |
Manage: Configuration Change Management Migrations
| Global packager
Enables users to create and edit thier own and other's Advanced configuration packages from Change Tracker. | View and Modify |
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
. Migrating Configuration Changes
You can use
Configuration Change Tracker
to package the change lists from reports and migrate the changes to Workday tenants in any environment. It's an effective and safe method of synchronizing populated tenants with changes made by specific users and timeframes.Migrating from
Configuration Change Tracker
has the added advantage of enabling you to package objects of any implementation type. It reports only migratable instances, which you select, validate, and revise to create an Advanced configuration package. Object Transporter doesn't add dependent instances to the package during the migration process as it does with standard configuration packages. Thus, you migrate only the instances you've vetted and have access to, ensuring a safer and less problematic migration.To migrate Advanced configuration packages from
Configuration Change Tracker
, a Customer Central security administrator must grant you access on the Maintain Access to Customer Central Tooling
task by selecting the OX Migration: Full Object Coverage
check box.Configuration Package Filtering
When you create a configuration package in Configuration Change Tracker, you can select to include all instances from a report or create a targeted package that contains only new or modified instances. This filtering capability provides more precise control over configuration package migrations, which saves time and reduces the manual effort required to prepare packages. By including only new or modified instances, you can synchronize configurations between tenants more efficiently and lower the risk of errors that result from manually editing large packages after you create them.
Audit Trails
You can leverage the powerful auditing capabilities of
Configuration Change Tracker
with your other auditing processes. View the details on configuration changes made in a tenant by selecting View Changes
for a primary instance. Configuration Change Tracker
reports all direct changes to objects. It doesn't report any behavioral changes as a result of the direct change to the object. Example: You make a change to a calculated field that also results in a change to a condition rule associated with that calculated field. Change Tracker only reports the change to the calculated field. It doesn't report the change to the condition rule, which is a behavioral change.
Example
Watch the video
4m 19s