Like the older version of the Design Import Tool, the new Configuration Transfer Utility (CTU) allows users to transfer the current design that was created on your development TeamConnect instance to a different design version in your Production instance.
Use the CTU to make small incremental changes (e.g. add a rule for a custom object), medium changes (create a set of workflows), and large changes (provision a new server).
The process for using the new CTU is slightly different and changes have been made on how artifacts and design dependencies are handled.
For instance, in an example scenario a user has added a rule and then later made modifications three separate times. All entries are captured automatically by the tool, and in order to export the change the user needs to include all four entries (the initial rule creation and subsequent changes; i.e. the dependencies) in the export package. Packages can be in one export file or split up, but the import must follow the sequence that creates the object first, then the rules on which they depend. This differs from the old Design Import Tool in that, previously, the package would have only one entry for that rule creation.
Note: The previous Design Import Tool could sometimes be used as a design backup, in that if an upgrade failed users could revert back to the old design, removing any partial changes. CTU does not have this capability.
The Old Way: Design Migration Tool |
The New Way: Configuration Transfer Utility |
---|---|
1. Make changes in Development environment |
1. Make changes in Development environment |
2. Export entire configuration as a design snapshot |
2. Filter and select only the changes you want |
3. Edit XML files in the snapshot to select the changes |
3. Export the changes to a .zip package |
4. Import the edited snapshot |
4. Import the package by uploading it |
5. If import fails, repeat steps |
Click the links below for instructions on using CTU:
•Troubleshooting and Best Practices
•Artifacts Captured for Custom Designs
Important Note: In order to use the CTU, the user's Group must have Contact, Document, and View Rights for Admin Settings. If the user does not have Contact Rights they cannot see the Changed By nor the Create By values; if the user does not have Document Rights they are unable to view Export Packages.