Rules
The following rules govern command line entries in Creo Packages:
• The command line is case sensitive, except when specifying a location.
• If a string contains a space or any special characters (for example, commas), enclose the string in quotation marks. For example, if the folder name is test folder, then it is presented as:
“test folder”
• All directory paths can be either absolute or relative.
• If multiple values are allowed, use a comma (,) to separate them.
|
Some objects, such as the Windchill baseline, allow a comma in a name. In this instance, use the backslash escape character (\) to distinguish the comma from the multivalue separator.
|
• The prefixes used in the wpc_preferences.txt file are the following:
◦ %o—Indicates what operation is being performed. Values can be export or import.
◦ %u—The username for Creo Packages.
• The directory separator is platform-specific. On Windows the indicator is two slashes (\\) 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 in wpc_preferences.txt, $ is replaced with \\. The \\ and the ${dir.sep}separators can be used in combination. For example:
#export.default.recipefile=c:\\ptc\\wpc${dir.sep}recipes\
\defaultRecipeFile.rcp
• Conflict resolution is specified as the following:
conflict.<ConflictType>=<ResolutionType>
There can be multiple resolution type values. The conflict type can have keywords assigned.
In this example, OVERRIDE_FIRST_ITERATION is the conflict type and INCLUDE is the resolution type. 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