Setting Conflict Overriding
You can overrule a given policy for individual objects by using conflict overriding. Creo Packages allows for conflict overriding by packaging an iteration (version) with conflict rules contained in the wpc_preferences.txt file.
You can modify the wpc_preferences.txt file in any text editor. By removing the comment symbol (#) you activate the preference.
Once conflict overriding preferences are set in the wpc_preferences.txt file, they continue to be used each time you want to export a package. You can modify the wpc_preferences.txt file if you want to change any of the export preferences.
Rules
• You can package only one iteration (version) of the same object into a single package. If there are conflicting rules specified at the command line or in a recipe file to collect different iterations (versions) of the same objects and these rules are applied, the export of the package fails.
• If a recipe file specifies conflicting rules for collecting a different set of objects, a union of all the rules is collected.
• You can specify multiple seeds with a single recipe. You cannot specify a single seed with multiple recipes for an individual package.
• The source PLM system rules apply when processing a collection or configuration, except for family tables and external simplified representations (ESRs):
◦ Family table—Family table members are inseparable. The package must contain all members, and the behavior cannot be configured.
◦ External simplified representations—When dealing with an external simplified representation (ESR), follow these Creo Packages export and import rules:
▪ When all dependents are specified, Creo Packages collects the ESR, its master design assembly, and all of its dependents.
▪ When required dependents are specified, Creo Packages also includes the master design assembly and its dependents even if ESR is selected as the seed object.
• You can specify either model-centric or part-centric configuration language.
By default, model-centric processing with absolute latest is used.
Model-centric processing supports the following criteria:
◦ Latest—Life cycle state
◦ As stored
◦ Managed baseline
• The Windchill default configuration is generally latest, but if the seed is not specified as latest, then the default is as stored. Optionally, part-centric (best effort) processing can be used instead of model-centric processing. Part-centric processing allows for the following criteria to be set: Latest, View Life Cycle State, Managed Baseline, and Effectivity.
• When collecting parents, such as drawings, by default Windchill processes all of the children of the parent. You can configure whether or not to further process its dependents. By default, Windchill does not process drawing dependents.
Requirements
If you do not have read access to the objects you want to export, and the wpc.export.secured.version preference has not been enabled, the export fails and an error message occurs.
If you have read access to the objects you want to export, you can perform conflict overriding for that collection of objects by specifying criteria in an export package. If you do not have access to seed objects, Creo Packages does not find them and no error message is generated.