Exclusion and Remove Rules
Exclusion rule and remove rules are very similar in that neither contain the content files of the excluded or removed Creo Parametric files. However, these rules do have the following important differences:
• Exclusion rules—Create packages which include the metadata of the excluded objects, but not the content files of the excluded objects. When an incremental package is imported, excluded objects are expected in the target PLM system. Because the package created with exclusion rules contains the metadata of the excluded objects, Creo Packages knows which objects are expected in the target PLM system, as well as, which specific iterations are required for the dataset being imported. If the specific iteration of objects that were excluded from the package are not in the target PLM system, the import fails. Using incremental packages created with exclusion rules ensures that the identical configuration of iterations is available in both the source and target PLM systems.
• Remove rules—Create packages which do not include the metadata of the removed objects and do not include the content files of excluded or removed Creo Parametric files. Because the package created with remove rules does not include the metadata of the excluded objects, Creo Packages does not know the specific iterations of the expected objects in the target PLM system. If the specific iteration of the object that was excluded from the package is not in the target PLM system but exists in the target PLM system a difference of the same object, then the import succeeds. Using incremental packages created with remove rules allows for the possibility that configurations consisting of differing iterations might be available in the source and target PLM systems.
Exclusion Rules
Exclusion rules are used to specify a set of objects that are not to be included as part of the collected objects.
• Metadata—The metadata for these excluded objects are still part of the package, and these objects are considered to be expected to exist in the target PLM system. Exclusion is post processing after inclusion is specified through flexible or static rules.
• Name of baselines—The name of baselines can be specific, or it can be a rule to search and collect more than one baseline, using “*”.
If the recipe file does not specify an exclusion rule, then no exclusion occurs.
Remove Rules
Remove rules are used to specify a set of objects that are not to be included as part of the collected objects.
• Metadata—The metadata for these removed objects will not be in the package. Removal is post processing after inclusion is specified either through flexible or static rules.
• Name of baselines—The name of baselines can be specific, or it can be a rule to search and collect more than one baseline, using an asterisk (*).
If the recipe file does not specify a remove rule, then no exclusion occurs.
baseline1 -number 1234
baseline2, baseline3