Object Transporter 2.0, the successor to Object Transporter 1.0, boasts improved scalability, offering more efficient ways to move objects and their dependencies between tenants in the Workday HCM environment. While it excels at migrating configuration data and related dependencies, it does not transfer transactional or reference data, ensuring a streamlined migration process. For instance, during the migration of a report definition, the associated calculated field may be included but not the linked location.

One of the notable enhancements in Object Transporter 2.0 is its expanded support for migration use cases that were previously inaccessible. This includes the migration of Security Configuration Packages and Custom objects, broadening its applicability within various scenarios. Moreover, it empowers Customer Central Security Administrators to select specific users authorized to conduct Security Configuration Package migrations, reinforcing data security protocols.

Customer Central, an independent Workday tenant, simplifies and centralizes the deployment process for users. It serves as a comprehensive platform that aids in managing tenants, facilitating data comparison between tenants, and enabling the seamless migration of configurations through Object Transporter 2.0. Customers can also utilize Customer Central to enrich tenants with factory default configurations and manage implementer and customer accounts. New Workday HCM customers are automatically provided with a Customer Central tenant while existing customers can request access through the Workday Customer Centre with no additional costs involved.

When migrating instances with Object Transporter 2.0, adhering to best practices can optimize the process. Firstly, for integrations involving Business Process Definitions, it is recommended to add these definitions as a separate implementation type within the Configuration Package. Similarly, for integrations utilizing Custom Reports, including Custom Reports as an implementation type in the Configuration Package can ensure a seamless migration process.

To create Configuration Packages with Object Transporter 2.0, several prerequisites must be met. Enabling the "OX for Non-Implementers" and "Special OX Web Services" domains and granting relevant security groups access to these domains is essential. Once these prerequisites are in place, Workday users can create Configuration Packages by selecting specific implementation types and instances. Object Transporter 2.0 facilitates the migration of Configuration Packages comprising up to 300 instances and their associated dependencies. Users can modify the selected implementation types, add, or remove instances, and save the package for future migration as needed.

Furthermore, Object Transporter 2.0 enables the creation of security configuration packages, further enhancing its capabilities in managing and transferring crucial data securely. You can migrate BP and domain security policies using the security configuration packages.

We hope this article helped you learn something new about OX 2.0 and its utility. Reach out to us for in-depth consultation on similar topics within Workday HCM and Finance suites.