Implementation Tools used across different Workday HCM Modules for Customers

Implementation Tools in Workday are used to build Tenants while executing the projects. They are also useful for Workday customers, Certified Workday Consultants, and Partners. Being a Workday HCM Professional who has completed the Workday HCM Training and mastered the Workday HCM course contents, it is essential to know these tools thoroughly and the ways in which they can be implemented in projects. These tools are not only useful in HCM but are customizable for different products across Workday inclusive of Finance, Integration, Payroll, and Benefits.

This article only provides an overview of these tools. To gain comprehensive analysis and gain conceptual knowledge of all the tools, one has to take up Workday Training with any of the prominent institutes like ERP Cloud Training. Following are the different implementation tools used across Workday Products:

• Customer Central Guide: It is used by customers and implementers mainly to ease and align the implementation process in a hierarchy that is easy to maintain, observe, analyze, and evaluate the process of deployment. It does not store any confidential data of the customer. 

With regard to Non-Production Tenants, Customer Central takes care of different functions like management, comparison of data, migration of data, enrichment of default configurations and the management of Implementer Accounts.

• Configuration Catalog Guide: To build the Tenant, preconfigured contents are given a catalog of configuration packages, which is called the Configuration Catalog Guide. It can be transferred into the Customer Tenant without any costs involved. Its main usage consists of migration of contents from WDSetup into implementation and sandbox tenants.

The Configuration Catalog Guide is inclusive of configuration content, reports, integrations, and dashboards. The main function of this Catalog is to simplify the procedure of implementation by saving time and effort of customers and implementers. This Catalog Guide is maintained and monitored by Workday’s ISE Implementation Tools Team.

• WDSETUP Preconfigured Content: The Factory Default Data, housed by Workday, which is used to build the Foundation Tenant, is contained in the WDSETUP.  It also serves as the source of data for the Configuration Catalog Guide.  Customization of customer’s requirements can also be done using this tool. 

It can be implemented across various cross products in Workday and can be interlinked with other modules of HCM during implementation. Though these tools are common across all products of Workday, emphasis is provided on HCM as it is more widely used than other Workday modules. WDSETUP is also mainly used for Data Audit, Delivery Assurance Exception reports along with its DART tool that serves multiple purposes.

• Object Transporter: Object Transporter is an implementation tool mainly used for the transfer of objects between various Workday products and to change their dependencies between Tenants.  It is an analytical tool used to perform functions like Dependency and Prerequisite Analysis and monitor the use of objects with respect to such analytical reports.

It is user–friendly and contains ‘instances’, which need not be separately created in the Target Tenant.  It performs checking of dependencies and perquisites, differential analysis, migrates instances with simplification between the Tenants. Whether it is a single-instance migration or a package of instances, Object Transporter can handle it all.

The completion of the project does not end with the building of the Tenant. Implementing these tools in the last stage successfully and monitoring post-production success is very important. This stage determines whether or not the implementer of the project has had a successful Workday HCM Training. Only a true professional can use these tools effectively in the implementation of Workday Projects for Customers.

Usage of these tools requires in-depth knowledge, effective practice in the Tenant, knowledge of building, and creating Tenants successfully and customizing them for customer needs. Some customers may be very particular about their required configurations in the Tenant and it is the duty of the implementer to take care that the satisfaction of such customers has been gained.