Steps: Translate and Migrate Objects
Configure Customer Central:
- Create Customer Central accounts.
- Enable Customer Central to access non-Production tenants.
- Enable Customer Central access to Production tenants and create a Customer Central session for authentication.
Using Object Transporter (Object Transporter) 2.0, you can migrate any instance of a supported Implementation Type that contains translated values in their translatable fields. As you migrate, you can use the premigration Diff report to view the translation values in source and target tenant before migration. Workday never overwrites the translated values in the target tenant before migration. After migration completes, you can use the postmigration summary report to confirm migration success.
- Enable the relevant languages in your source tenant and any tenant to which you want to migrate.Security:Set Up: Tenant Setup - Globaldomain in the System functional area.
- Enter translations in your source tenant for a migratable instance.For a list of Workday objects and how to add translations to them, see Reference: Translations.
- To ensure that the Implementation Types for the instances you want to translate can migrate, view the tenantedObject Transporter Supported Objects (OX)report.
- If you’re adding translations to an object that you want to package with other objects, create a configuration package.
- Migrate the object with translated values in either of these ways:
- Migrate Single Instances with Object Transporter 2.0.Use this method when you've added translation values to a single instance.
- Migrate Packages with Object Transporter 2.0Use this method when you've added translation values to 1 or more instances and have bundled the instances in a configuration package.
- (Optional) As you migrate, click to see the premigration status of translated values in the source and target tenants.TheAttribute Diffreport displays translation status by color.
- Orange: You’re changing an existing translation value in the target tenant.
- Blue: You’re adding a translation value to the target tenant.
- Green: You’re merging any new or changed values without overwriting already matching values in the target tenant. Example: Your source tenant has a translation value for English and 2 new values for French and Italian. The target tenant has a matched existing value for English. Object Transporter 2.0 adds the French and Italian values to the target tenant. It doesn’t overwrite the English value because they already match.
If you don't want to include translated values in a migration, clear the Include Translations? check box during the migration process in Customer Central. - (Optional) When migration completes:
- ClickView Post Migration Report.
- ClickViewto verify that the instances migrated successfully.