Reference: Best Practices for Migrating Integrations with Object Transporter
To migrate integration systems successfully to target tenants using Object Transporter, Workday recommends these guidelines.
Item to Migrate | Best Practice | Link |
|---|---|---|
Pretty Good Privacy (PGP) | Workday's security model prevents the migration of PGP private keys. If you need private keys for the data you migrate, create them first in your Production or Gold tenants. Then, refresh your tenant from Production so that it has the private keys. | |
X.509 private keys | Use the Migrate x509 Private Key Pair task in Customer Central to migrate X.509 private key pairs between non-Production tenants. | |
Integration system users (ISU) Integration system Security Segments, also known as Groups (ISSG) | Before you perform a migration using the implementation type, Integration Systems , set up the ISU account or ISSG in the target tenant.
When the integration completes successfully, Workday automatically attaches the ISU to the integration system. | |
Business Process Definitions | If your integration uses 1 or more Business Process Definitions, add Business Process Definitions as a separate implementation type in the Configuration Package you’re creating for the Integration Systems implementation type. | |
Custom Reports | If your integration uses Custom Reports, add Custom Reports as an implementation type in the Configuration Package you're creating for the Integration Systems implementation type. | |
Workday Studio project Cloud Archive (CLAR) file | When Workday migrates CLAR files, it doesn't update the Deployed DateTime or Deployed By values to the date and time or person of migration. This value remains unchanged by design because it represents the original date and time of deployment from Workday Studio rather than the date and time of migration.
To audit project migration dates, use the View User or Task or Object Audit Trail task to display date changes. | As designed. |