wpc_preferences.txt Example
The wpc_preferences.txt file contains the default preferences for both exporting and importing, the mapping information for importing, and the conflict overriding preferences for exporting and importing a package.
## Creo startup command
##
#proe.start.cmd="parametric.bat 0 -g:no_graphics -i:rpc_input"
##
## Creo startup mode.
##
proe.startup.mode=exclusive
##
## Preferences for baseline creation upon import / export
##
baseline.prefix=WPC_%o
baseline.folderpath=<folder path>
##
## Preferences for baseline creation upon ownership transfer
ownership.baseline.folderpath="/
"
## Reports location
##
#reports.location=
##
## Set up a non-default context
##
#wpc.context=
##
## Export preferences
##
##
## Any path separator for windows in the locations should be provided as double
## backward slash instead of single backward slash.
##
#export.package.name=%u_%t
#export.package.location=${wpc.home}${dir.sep}packages
#export.default.recipefile=${wpc.home}${dir.sep}samples${dir.sep}recipe$
##{dir.sep}defaultRecipeFile.rcp
##
## Description of the source system.
#source.system.description=""
##
##
## Import preferences
##
##
## Preference to enable move action during import/synch import of cad
## documents. Expected values are true or false.
## If this value is not set, import would WARN the user about remote system
## location change; if it
## is set to true import moves the CAD document for new location by applying MOVE
## action. It always honours mapped locations.
## Move action can be applicable to move CAD documents across containers
## or across folders.
#import.move.caddocuments=false
##
##
#import.mapping.files.location=${wpc.home}${dir.sep}mapping
##
##
## Default conflict resolutions.

## Format: conflict.<ConflictType>=<ResolutionType>
##
##
## conflict resolution when user has ended up collecting more than one
## version of same object for export.
## Possible resolution for OVERRIDE_MULTIPLE_VERSIONS is USE_LATEST
#conflict.OVERRIDE_MULTIPLE_VERSIONS=USE_LATEST
##
## conflict resolution(s) when the package contains first iteration of
## subsequent Revision.
## Possible resolutions for OVERRIDE_FIRST_ITERATION conflict are INCLUDE,
## SKIP, USE_LATEST_ON_PREVIOUS
#conflict.OVERRIDE_FIRST_ITERATION=INCLUDE
##
## conflict resolution(s) when the collection of object for export contains
## checkout objects.
## Possible resolution for OVERRIDE_WHEN_RESERVED conflict is YES_WHEN_RESERVED
conflict.OVERRIDE_WHEN_RESERVED=YES_WHEN_RESERVED
##
## conflict resolution overrides failure of target folder not found.
## Possible resolution for OVERRIDE_FOLDER_NOT_FOUND is CREATE_TARGET_FOLDER
#conflict.OVERRIDE_FOLDER_NOT_FOUND=CREATE_TARGET_FOLDER
##
## conflict resolution overrides existing later versions in target system.
## Possible resolution for OVERRIDE_LATER_VERSION is LASTEST_VERSION_REUSE
#conflict.OVERRIDE_LATER_VERSION=LASTEST_VERSION_REUSE
##
## conflict resolution(s) overrides missing optional expected version on
## target system.
## Possible resolutions for OVERRIDE_MISSING_REF conflict are IGNORE_MISSING_
## REF, REUSE_OR_IGNORE_MISSING_REF
#conflict.OVERRIDE_MISSING_REF=IGNORE_MISSING_REF
##
## conflict resolution when the object to be exported is a part of the family
## table object version which is not compatible with the version already
## included in the package.
## Possible resolution for OVERRIDE_INCOMPATIBLE_INSTANCE conflict is SKIP
#conflict.OVERRIDE_INCOMPATIBLE_INSTANCE=SKIP
##
## conflict resolution when package contains objects with different revision,
## and objects have already been PDM checked in.
## Possible resolution for OVERRIDE_NEW_REVISION conflict is REVISE_IN_PDMLINK
## using which user may perform revise in PDMLink.
#conflict.OVERRIDE_NEW_REVISION=REVISE_IN_PDMLINK
##
## conflict resolution when the collected objects contain one ore more objects
## that were created in the project and never have been PDM checked in
## Possible resolution for OVERRIDE_NEW_IN_PROJECT conflict is SKIP which would
## create a package without the conflicting objects.
#conflict.OVERRIDE_NEW_IN_PROJECT=SKIP
##
## conflict resolution when the collected Objects that are PDM checked out to
## project, have at least one iteration created in Project, and are owned by
## the source site
## Possible resolution for OVERRIDE_MODIFIED_IN_PROJECT conflict is SKIP which
## would create a package without the conflicting objects.
#conflict.OVERRIDE_MODIFIED_IN_PROJECT=SKIP
##
#
#
#
######################
#
# Following are the preferences for Windchill set up only.
#
######################
#
#
#
## By default, Creo will try to assign location upon Upload (proe.folder.
## assign=true).
## User can change the behaviour so that initial location assignment will be
## done by Windchill upon check-in.
## To do that, set the following preference to false.
#proe.folder.assign=false
##
## The following option specifies which secondary content category should be
## included in the package (Windchill only)
## This preference takes multiple values separated by comma. Each value should
## be in the following format
## @<file extension>":@<category>
#export.secondary.content.category=@"*.xls":@GENERAL,@"*.step":@EXPORT
##
## Creo missing references resolution preference
## If no value is specified then default behaviour is to not do any auto
## resolution of missing references.
## IGNORE and REUSE_OR_IGNORE are values allowed to change default behaviour.
##
#proe.missing.references.resolution=IGNORE
##
##
## The following option specifies whether or not Auto Associate is performed
## upon import.
## This option is applicable for importing into Windchill only.The value
## is Boolean.
## Default value is false.
##
#import.associate=false
##
##
## If the 'import.associate' option is on,optionally,the user can define
## IBA name that
## controls the auto associate behaviour per object basis. This option has
## no effect if
## 'import.associate' option is off.
## By default,every object is subject to auto associate if 'import.associate'
## is on.
#import.autoassociate.filter.attribute=
##
## User can define whether WTPart should also be revised together with
## CAD Document.
## By default,if this option is not specified, WTPart will always be revised
## together (true),
## or else import will fail.
## This option should be honoured regardless of the auto associate option. As
## long as CAD Doc that is to be revised has associated WTPart, this option
## will be honoured
##
#wtpart.revise=false
##
##
## IBA to use for setting 'modifier' on CAD Document in PDMLink when iterations
## of CADDocuments are getting created during
# import of package.
## If IBA is not present on the CADDocument logged in WPC user name will be
## set as modifier of the document.
##
#wpc.modifier.attribute=
##
## The following option specifies the CAD adapter configuration to be used for
## the client.
## LOCAL_CAD_ADAPTER is the default configuration but can be changed to use
## REMOTE_CAD_ADAPTER as well.
##
wpc.cad.config=<cad_config>
##
##
#Export Template file for remote cad adapter. User can change the default
## template file
wpc.remote.cad.export.process.template=WPCEXPORT
##
##
#Import Template file for remote cad adapter. User can change the default
## template file
wpc.remote.cad.import.process.template=WPCIMPORT
##
##
##
###wpc.modifier.attribute=
##
##
##
## User can define whether to export the secured version along with the
## permitted CAD documents or not.
## By default, if this option is not specified, the export will throw an error
## in case secured CAD
## document is one of the dependent
##
#wpc.export.secured.version=
##
## This preference is used to block export of configured additional attributes.
## One or more attribute handler keys can be configured with comma separator.
## Following are the valid values for this
## preference.
## NUMBER - Block export of Number attribute.
## NAME - Block export of Name attribute.
## ORGID - Block export of Organization Id attribute.
## MASTER_IBA - Block export of attributes for master CAD documents.
#export.pdmobject.attribute.block
##
##
##
## This preference is used to block export of attributes on master CAD documents. One or
## more attributes can be configured with comma separator.
## Note: In case of continuous exchange of these attributes; PTC recommends
## to block export of ownername attribute which are used in import mapping.
#export.pdmobject.master.iba.block

도움이 되셨나요?