Rules
Following are the rules for incremental package export:
• Exclude—Users can specify a set of objects that can be filtered from the collected objects. The metadata about these excluded objects is included in the package, and these objects are considered as expected to exist in the target system.
• Remove—Users can specify a set of objects that can be filtered from the collected objects. The metadata about these removed objects is not included in the package.
|
|
The remove option is to be used only when the sender is absolutely sure that objects have been already sent to the receiver, and the receiver still has the objects. Then by not processing these objects upon import, it can potentially aid in performance as it does not mandate these expected objects to be added to the workspace.
|
• Incremental package export is supported by using baselines to specify the set of already exported objects:
◦ You can specify one or more baselines to subtract.
◦ You can provide some sort of pattern rules to search for multiple baselines.
• PTC customers that have Windchill ProjectLink in a bundled server environment co-installed with Windchill PDMLink, an incremental package export to export objects from Windchill ProjectLink and then import them into Creo Packages.
◦ You can find the baseline-related to a previously exported package by locating an object that was included in the last package. For example, finding the top-level object that is at a later iteration than what is currently in the target PLM system.
◦ If objects that are part of the baseline get unshared, they maintain the references from the objects in Windchill PDMLink. Those references are visible only by the user who has access to those objects in Windchill PDMLink. For example, deleting an object from Windchill PDMLink can be prevented, unless baselines in projects become deleted.
