Importing Changes
After exporting changes from the source system, you should move the resulting ZIP file to the target system. For example, if changes were implemented and tested on a development system, you would then import those changes into an integration system.
Conflicts can occur when importing changes into a target system. You can specify what action you want taken when a conflict arises. For example, if a domain associated with policy access control rules does not exist on the target system, you can specify a domain to which all of those rules are assigned. Some conflicts cannot have a solution specified and cause the import to fail. For example, if a life cycle state associated with a policy access control rule is not found on the target system, the import fails.
When the import is complete, a log file is generated that lists any conflicts that occurred and the resolution selected. If the import completed successfully, the changes are available in the target Windchill system. The imported changes can be modified in the target system. There is no indication that the imported changes originated in the source system. The imported administrative object changes function as though the updates were made manually in the target system.
* 
When you delete a type definition or when you delete any attribute information associated with a type definition during import, the import process may take an extended period of time to complete.
Was this helpful?