Create Configuration Packages for Object Transporter
Security: These domains in the Implementation functional area:
- OX for Non-Implementers
- Special OX Web Services
You create a configuration package by selecting implementation types and specific instances of those types. Object Transporter can migrate a configuration package containing up to 300 instances and their dependencies.
During migration, Workday prompts you to specify the effective dates for any instances that have effective dates. Any dependencies of an instance with an effective date also inherit this effective date. However, when an instance doesn't have an effective date but its dependencies do, those dependencies inherit the date of migration as their effective date during the migration process. You can change inherited effective dates after migration. Workday can't migrate instances with effective dates in the future.
- Sign in to the source tenant where you want to create a configuration package.
- Access theCreate Configuration Packagetask.
- Select 1 or more object types to migrate from theImplementation Type(s) to Migratedrop-down list.If you're migratingIntegration Systems, see Reference: Best Practices for Migrating Integrations with Object Transporter.
- As you complete this task, consider:
Option Description Add Implementation Type(s)Click to add 1 or more additional object types to the package.Add/Edit InstancesClick to change instances for an Implementation Type. You can filter Instances based on 1 or more condition rules. When you migrate a filtered configuration package, Object Transporter includes all instances that match the condition rules. It includes even those instances that you create after you create the rules.RemoveClick to remove an Implementation Type from the configuration package.DoneClick to save the configuration package for later migration. - (Optional) ClickMigrateto migrate the configuration package.