Setting Import Preferences

Import preferences must be set before using Creo Packages to import a package from the source PLM system. You can specify the import preferences in the wpc_preferences.txt file that was created in the Creo Packages installation directory during the installation. This file is created in the installation directory during the installation process.

The wpc_preferences.txt file contains the import, mapping, and the conflict overriding preferences for importing a package.

You can modify the wpc_preferences.txt file in any text editor. By removing the comment symbol, #, you activate the default preference. Additional preference commands can be added to the wpc_preferences.txt file.

Once mapping preferences are set in the wpc_preferences.txt file, they continue to be used each time you want to import a package. You can modify the wpc_preferences.txt file if you want to change any of the import preferences.

You can set import preferences for the following entities.

This example indicates the folder location where mapping files for each source PLM system are stored in the PLM system based on the source system ID of the objects.

If you want to apply the same resolution to all objects, you can specify this resolution while settings the import preferences. You can specify resolutions in the wpc_preferences.txt file for the following types of conflicts:

For more information about conflicts, see Conflict Handling and Resolution.

Specify the baseline folder in a mapping file as follows:

Specify the baseline prefix as follows:

The %o stands for the operation that you are performing.

After the default comment line, ## Preferences for baseline creation upon import/export, in the wpc_preferences.txt file, add the baselines information for the file being imported to the target PLM system. For example:

##Preferences for baseline creation upon import / export
baseline.prefix=WPC_%o
baseline.folderpath=/ptc/Library/mig_tesxt//Assembly
## Reports location

The prefixes used in the wpc_preferences.txt file are the following:

The directory separator is platform specific. On Windows, the indicator is double backslash (\\) when specifying the paths for a recipe file location or a command line argument location. You can also use the syntax ${dir.sep} as a directory separator. When ${dir.sep} is used inwpc_preferences.txt file, $ is replaced with \\. The \\ and the ${dir.sep} separators can be used in combination:

#export.default.recipefile=c:\\ptc\\wpc${dir.sep} recipes\\defaultRecipeFile.rcp.

Conflict resolution is specified as follows:

The resolution type can have multiple values. The conflict type can have keywords assigned.

In this example, OVERRIDE_FIRST_ITERATION is the conflict type and INCLUDE is the resolution type that is assigned. Multiple values for OVERRIDE_FIRST_ITERATION could be INCLUDE, SKIP, USE_LATEST_ON_PREVIOUS.

## Possible resolutions for OVERRIDE_FIRST_ITERATIONS CONFLICT
ARE include, skip, use_latest_on_previous

#conflict.OVERRIDE_FIRST_ITERATION=INCLUDE

To specify which context (namespace) in projects to work with, enter a unique value per PLM system with organization information.

Automatic Association Upon Check In When Importing Objects Into Windchill PDMLink

The following import preferences can be set in wpc_preferences.txt file for automatic association upon check in when importing objects into Windchill PDMLink.

• Create a WPT part by importing the Windchill package. Change the following default value from false to true:

• To create an overridable conflict for SAR link creation failure, use the following syntax:

• To supply an attribute filter for automatic association, use the following syntax:

If Creo Packages will be used with a Windchill server that uses forms-based authentication (FBA), you must set a preference on the Creo Packages client. In the wpc_preferences.txt file, set the preference as follows:

If an object has been moved in the source PLM system, it not automatically moved in the target PLM system upon import. To control this behavior, you can uncomment the following preference in the wpc_preferences.txt file and set it as follows:

If you want the objects to be automatically moved in the target PLM system when they are imported, set this preference to true. Note that a location change in the mapping file overrides the new location on the source PLM system, and the objects are moved according to the mapping file. If you set this preference to true, you might need to update your mapping file.

If an object has been moved from one context to another, all the revisions of that object (for example, a.prt A.1 and B.1) are moved to the target context. For moves within a context (subfolder move), only the selected revision is moved; other revisions of the object remain in their current folder.

If you do not want the objects to be moved automatically in the target PLM system, set this preference to false. When this preference is set to false, the user is notified of the new location of objects in the package details report.

PTC recommends the following:

• Do not change this preference frequently, as changes to this preference require a change to the mapping definition.

• If you have multiple client environments, set this preference consistently across all environments.

If the wpc.export.secured.version preference was set to true when exporting the package, use the wpc.export.secured.version preference to import the incomplete package successfully.

If this property is set to true, the import process searches for CAD documents by global ID. This preference applies only to dependent CAD components that were imported with identity information only because the wpc.export.secured.version preference is enabled.

It is recommended to keep this preference value set to false. Use this preference sparingly and carefully. If you need to use this preference, it is recommended that you change enable it temporarily and then disable it again.