This article provides the overview of the ConfigBot Modules which helps in workday documentation and data analysis.

Impact Analysis Security

The Impact Analysis Security module provides an overall analysis of your security configuration. It helps identify similarities and differences between security groups and their permissions, as well as the impact of security groups associated with Business Process (BP) Security Policies.
There are two ways to analyze your security configuration:

1. Matching Analysis

The Matching analysis helps you identify security groups and domain security permissions that are similar across instances. This allows you to quickly identify groups with matching permissions and determine whether they need to be updated, consolidated, or deactivated.

2. Difference Analysis

The Difference analysis helps you compare security configurations across multiple instances. It identifies whether differences exist and highlights the specific fields where those differences occur.
This provides a quick overview of your BP Security Policies, Security Groups, and Permissions across different instances, helping you understand the potential impact before migrating, updating, or modifying your security configuration.

Health Check

The Workday Health Check module helps you identify potential configuration and data issues across your Workday instance. It provides ready-to-review reports covering areas such as job applications, employees, managers, compensation, security groups, and other key configuration areas.

The module helps identify issues such as:

• Active job applications without a primary recruiter
• Active applications on closed or filled requisitions
• Duplicate SSNs
• Employees assigned as their own HR Partner or Manager
• Employees missing SSNs or Managers
• Employees missing compensation packages or hourly/salary plans
• Employees assigned to inactive roles
• Inactive job requisitions with active postings
• Security groups that are not referenced in any security policy

By generating the Health Check workbook, you can quickly review these findings in a structured format and identify areas that may require correction or cleanup in your Workday instance. This helps improve data quality, configuration accuracy, security, and overall system health.

Integration Dependency

The Integration Dependency module provides a detailed view of the fields and configurations used by integrations in your Workday instance. It helps administrators understand which integration configurations are dependent on specific fields and how those fields are configured within the integration.

For each integration, ConfigBot provides information such as the Integration Name, Field Configuration Name, Field, Override Default Values, Include in Output, Required Field, and Maximum Length.
For example, the integration “Cloud Connect Worker - PeopleSoft Person Basic Sync” uses the field configuration “CCW - Workers for DIS”, which contains the “Name” field. ConfigBot shows that the field is not configured to override its default value, is included in the integration output, is not marked as required, and has no defined maximum length.

This information helps administrators understand integration dependencies, review field-level configurations, identify important integration requirements, and assess potential impacts before making changes to Workday configurations. It provides a consolidated view of integration dependencies that would otherwise require manually reviewing individual integration configurations.

Impact Analysis

The Impact Analysis module provides a consolidated view of dependencies across key Workday configurations. It helps administrators identify where an object is being used, what other objects depend on it, and what areas may be impacted before making changes, updating configurations, or migrating objects between Workday instances.
The module contains five analysis sheets, covering different areas of Workday configuration and usage. These sheets help provide visibility into dependencies across areas such as Compensation, Calculated Fields, Custom Reports, HCM, and Recruiting.

For each dependency, ConfigBot provides information such as the Object Category, Object Identifier, Dependency Category, and Dependency/Usage, allowing administrators to quickly understand the relationship between objects.

Example – Compensation:
In the Compensation sheet, ConfigBot can identify dependencies between compensation objects. For example, the Compensation Plan "Hourly - Exception Hourly" has a dependency on "Compensation Basis - Adjustable Compensation". Similarly, the Compensation Basis "Total Base Pay" is associated with the Compensation Grade "Executive".
This information helps administrators understand where a configuration is being referenced or used before modifying it. For example, if an administrator plans to update or remove a Compensation Basis, they can first review the Impact Analysis results to identify the Compensation Grades or Compensation Plans that depend on it. This helps prevent unintended configuration issues and allows teams to assess potential downstream impacts before making changes.

Overall, Impact Analysis reduces the need for manually checking dependencies across Workday, providing a faster and more reliable way to assess configuration relationships and make informed decisions before updates or migrations.

Impact Analysis – Business Process

The Impact Analysis – Business Process sheet helps administrators identify differences in Business Process configurations between Workday instances. It provides a detailed, field-level comparison of Business Processes, making it easier to understand what has changed between the source and destination instances.
For each Business Process, ConfigBot displays the Business Process Name, Sheet Name, Column Name, Instance, Source Value, and Destination Value.

Example:
For the Business Process “1099 Adjustment (Default Definition)”, ConfigBot identifies differences in the Effective Date across the Business Process configuration. The Source Value is 07/27/2026, while the Destination Value is 07/29/2026. It also identifies the same difference within Steps – Effective Date and Related Links By Definition – Effective Date.

This allows administrators to quickly identify exactly which fields differ between instances, rather than manually reviewing each Business Process. It is particularly useful before or after migrations to validate configurations, identify unexpected changes, and ensure that Business Processes are aligned across environments.

Dependency Graph

The Dependency Graph provides a visual representation of the relationships and dependencies identified through the Impact Analysis. Instead of reviewing dependency data only in workbook sheets, it allows administrators to visually trace how a selected Workday object is connected to other objects and understand its potential downstream impact.

Administrators can select a root object and choose the dependency types they want to analyze, such as Company, Cost Center, Cost Center Hierarchy, Job Family, Job Profile, Location Hierarchy, Region Hierarchy, and Supervisory Organization. ConfigBot then generates a graphical dependency map showing the selected object and its related configurations.

For example, if Job Family Group: JobFamilyGroup_PlatformEnablement is selected as the root object, ConfigBot can identify its related dependencies and display them as connected nodes in the graph. The example shown identifies 5 dependencies, allowing the administrator to quickly see which Workday objects may be affected.

The Impact List, shown alongside the graph, provides a detailed list of the identified dependencies, while the graphical view makes it easier to understand the overall relationship between objects.
This provides a quick visual overview of configuration impact, helping administrators trace dependencies, identify potential downstream effects, and make more informed decisions before modifying, migrating, or removing Workday configurations.

Updated on: 08/11/2026