Appendix C

Default Object Types Recognized by 
the Pro/INTRALINK Data Migrator
The following section contains all of the PI type definitions that are defined 
in the default configuration of the pitdmapping.properties file. Some of 
the PI type definition names can appear multiple times in this file with type 
being 0 and/or 1 or 0 and/or 2. If this happens, migrator will first try to 
migrate the object with the PI type definition as secondary content( if the PI 
type definition appears with type 2) if not possible, then CAD Document( if 
the PI type definition appears with type 0) or WTDocument( if the PI type 
definition appears with type 1).
CAD Documents
The following is the standard format for CAD Document PI type definitions:
pitypedefname=0/@AuthoringApplication/@EPMDocumentType/@SubType/@Category
The following is a list of CAD Document PI types that are recognized by the 
Pro/INTRALINK Data Migrator:

Animation Playback File=0/@PROE/@OTHER/@NULL/@ANALYSIS_RESULTS
AnsysOut=0/@OTHER/@OTHER/@NULL/@NULL
Appearance=0/@PROE/@OTHER/@NULL/@PROE_UGC
AssemMembInfo=0/@PROE/@OTHER/@NULL/@PROE_UGC
Assembly=0/@PROE/@CADASSEMBLY/@NULL/@PROE_UGC
BendOrder=0/@PROE/@OTHER/@NULL/@PROE_UGC
BumpMapTexture=0/@OTHER/@OTHER/@NULL/@NULL
CableParams=0/@PROE/@OTHER/@NULL/@PROE_UGC
CATIA=0/@CATIA/@OTHER/@NULL/@EXPORT
CATIAFacets=0/@CATIA/@OTHER/@NULL/@EXPORT
CGM=0/@OTHER/@OTHER/@NULL/@EXPORT
CLData=0/@PROE/@OTHER/@NULL/@EXPORT
ColorMap=0/@PROE/@OTHER/@NULL/@PROE_UGC
ColorTexture=0/@OTHER/@OTHER/@NULL/@NULL
Config=0/@PROE/@OTHER/@NULL/@PROE_UGC
Connector_Terminator_Table=0/@PROE/@OTHER/@NULL/@EXPORT
ConnectorParams=0/@OTHER/@OTHER/@NULL/@NULL
CurveData=0/@PROE/@OTHER/@NULL/@EXPORT
DecalTexture=0/@OTHER/@OTHER/@NULL/@NULL
Designer Environment=0/@PROE/@OTHER/@NULL/@PROE_UGC
Designer Light=0/@OTHER/@OTHER/@NULL/@NULL
Desktop_ATB=0/@OTHER/@OTHER/@NULL/@IMPORT
Diagram=0/@PROE/@DIAGRAM/@NULL/@PROE_UGC
Diagram_Component_Group=0/@OTHER/@OTHER/@NULL/@NULL
Diagram_Multi-view_Components=0/@PROE/@OTHER/@NULL/@PROE_UGC
Draft=0/@PROE/@OTHER/@NULL/@PROE_UGC
Draw_Table=0/@PROE/@OTHER/@NULL/@PROE_UGC
Drawing=0/@PROE/@CADDRAWING/@NULL/@PROE_UGC
DrawingSetup=0/@PROE/@OTHER/@NULL/@PROE_UGC
DWG=0/@PROE/@OTHER/@NULL/@EXPORT
Dwgform=0/@PROE/@FORMAT/@NULL/@PROE_UGC
DXF=0/@PROE/@OTHER/@NULL/@EXPORT
EDM=0/@OTHER/@OTHER/@NULL/@NULL
External Simplified Rep=0/@PROE/@CADASSEMBLY/@EXTERNALSIMPREP/@PROE_UGC
FEM=0/@PROE/@OTHER/@NULL/@PROE_UGC
Fem_Neutral=0/@PROE/@OTHER/@NULL/@PROE_UGC
Graph_Report=0/@PROE/@REPORT/@NULL/@PROE_UGC
Graph Tabular File=0/@OTHER/@OTHER/@NULL/@NULL
Group=0/@PROE/@UDF/@NULL/@PROE_UGC
HolemakParams=0/@PROE/@OTHER/@NULL/@PROE_UGC
IGES=0/@PROE/@OTHER/@NULL/@EXPORT
Input=0/@PROE/@OTHER/@NULL/@PROE_UGC
Insulation=0/@PROE/@OTHER/@NULL/@PROE_UGC
Interch_Domain=0/@PROE/@OTHER/@NULL/@PROE_UGC
Layout=0/@PROE/@LAYOUT/@NULL/@PROE_UGC
Light=0/@PROE/@OTHER/@NULL/@PROE_UGC
Linestyle=0/@PROE/@OTHER/@NULL/@PROE_UGC
MachDB=0/@PROE/@OTHER/@NULL/@PROE_UGC
Machine=0/@PROE/@OTHER/@NULL/@PROE_UGC
Markup=0/@PROE/@MARKUP/@NULL/@PROE_UGC
MassProp=0/@PROE/@OTHER/@NULL/@PROE_UGC
Material=0/@PROE/@OTHER/@NULL/@PROE_UGC
Mechanica_Assembly=0/@PROE/@CADASSEMBLY/@NULL/@PROE_UGC
Mechanica_Part=0/@PROE/@CADCOMPONENT/@NULL/@PROE_UGC
Mechanica_Table=0/@PROE/@OTHER/@NULL/@PROE_UGC
Mechanism Frame File=0/@PROE/@OTHER/@NULL/@ANALYSIS_RESULTS
Mechanism Playback File=0/@PROE/@OTHER/@NULL/@ANALYSIS_RESULTS
Medusa=0/@CADDS5/@OTHER/@NULL/@EXPORT
Medusa Sheet=0/@CADDS5/@OTHER/@NULL/@EXPORT
Mfg_Assem=0/@PROE/@MANUFACTURING/@NULL/@PROE_UGC
MillGrvParams=0/@PROE/@OTHER/@NULL/@PROE_UGC
MillParams=0/@PROE/@OTHER/@NULL/@PROE_UGC
Mipmap=0/@OTHER/@OTHER/@NULL/@NULL
Neutral=0/@PROE/@OTHER/@NULL/@EXPORT
NeutralWireList=0/@PROE/@OTHER/@NULL/@EXPORT
OperationParameter=0/@PROE/@OTHER/@NULL/@PROE_UGC
OptegraVis=0/@CADDS5/@OTHER/@NULL/@EXPORT
Part=0/@PROE/@CADCOMPONENT/@NULL/@PROE_UGC
PatranFile=0/@OTHER/@OTHER/@NULL/@NULL
PatranOut=0/@OTHER/@OTHER/@NULL/@NULL
PatternTable=0/@PROE/@OTHER/@NULL/@EXPORT
Piping_Line_Stock=0/@OTHER/@OTHER/@NULL/@NULL
Plot=0/@PROE/@OTHER/@NULL/@PROE_UGC
RoomFile=0/@OTHER/@OTHER/@NULL/@NULL
RS_Base_Design=0/@OTHER/@OTHER/@NULL/@INFORMATION
RSDesign=0/@OTHER/@OTHER/@NULL/@INFORMATION
RS_Single_Sheet=0/@OTHER/@OTHER/@NULL/@INFORMATION
Render=0/@OTHER/@RENDERING/@NULL/@INFORMATION
Room=0/@PROE/@OTHER/@NULL/@PROE_UGC
RouteSheet=0/@PROE/@OTHER/@NULL/@PROE_UGC
SceneDescr=0/@OTHER/@OTHER/@NULL/@NULL
Section=0/@PROE/@SKETCH/@NULL/@PROE_UGC
SET=0/@OTHER/@OTHER/@NULL/@EXPORT
Site=0/@OTHER/@OTHER/@NULL/@NULL
SLA=0/@OTHER/@OTHER/@NULL/@EXPORT
Snapshot=0/@PROE/@OTHER/@NULL/@INFORMATION
SplinePoints=0/@PROE/@OTHER/@NULL/@EXPORT
SpoolParams=0/@PROE/@OTHER/@NULL/@PROE_UGC
STEP=0/@OTHER/@OTHER/@NULL/@EXPORT
SUPERTAB=0/@OTHER/@OTHER/@NULL/@EXPORT
Symbol=0/@PROE/@OTHER/@NULL/@INFORMATION
Symbol_Parameters=0/@PROE/@OTHER/@NULL/@PROE_UGC
TapeFile=0/@PROE/@OTHER/@NULL/@INFORMATION
TolTable=0/@PROE/@OTHER/@NULL/@PROE_UGC
WireEDMParams=0/@PROE/@OTHER/@NULL/@PROE_UGC
Wiring_Strip_Length_Table=0/@PROE/@OTHER/@NULL/@EXPORT
VerificationResults=0/@PROE/@OTHER/@NULL/@PROE_UGC
VRML=0/@PROE/@OTHER/@NULL/@EXPORT
Xhatch_Style=0/@PROE/@OTHER/@NULL/@PROE_UGC
XML=0/@OTHER/@OTHER/@NULL/@EXPORT

WTDocuments
The following is the standard format for WTDocument PI type definitions:

WTDocument pitydefname=1/@SoftType/@FormatName

Note: SoftTypes names should be entered completely and not abbreviated. 
For example:

wt.doc.WTDocument, wt.doc.WTDocument|com.ptc.ReferenceDocument 
etc.
The following is a list of WTDocument PI types that are recognized by the 
Pro/INTRALINK Data Migrator:

Bmp=1/@wt.doc.WTDocument/@Bitmap Image
CDRS=1/@wt.doc.WTDocument/@NULL
CDRSAnim=1/@wt.doc.WTDocument/@NULL
CDRSRenderedImg=1/@wt.doc.WTDocument/@NULL
Desktop_Album=1/@wt.doc.WTDocument/@NULL
Desktop_Design=1/@wt.doc.WTDocument/@NULL
Desktop_Drawing=1/@wt.doc.WTDocument/@NULL
Document=1/@wt.doc.WTDocument/@Microsoft Word
ECO=1/@wt.doc.WTDocument/@NULL
EPS=1/@wt.doc.WTDocument/@Text File
Environment=1/@wt.doc.WTDocument/@NULL
GIF=1/@wt.doc.WTDocument/@GIF Image
HTML=1/@wt.doc.WTDocument/@HTML File
Image=1/@wt.doc.WTDocument/@NULL
Inventor=1/@wt.doc.WTDocument/@NULL
Java Archive=1/@wt.doc.WTDocument/@Zip
JPEG=1/@wt.doc.WTDocument/@JPEG Image
Manual=1/@wt.doc.WTDocument/@NULL
NCCheckImage=1/@wt.doc.WTDocument/@NULL
Picture=1/@wt.doc.WTDocument/@PIC
Plot=1/@wt.doc.WTDocument/@NULL
PNG=1/@wt.doc.WTDocument/@NULL
RAWImage=1/@wt.doc.WTDocument/@NULL
RLAImage=1/@wt.doc.WTDocument/@NULL
RLBImage=1/@wt.doc.WTDocument/@NULL
RTAImage=1/@wt.doc.WTDocument/@NULL
RTBImage=1/@wt.doc.WTDocument/@NULL
SGIImage=1/@wt.doc.WTDocument/@NULL
ShadedView=1/@wt.doc.WTDocument/@NULL
TGAImage=1/@wt.doc.WTDocument/@NULL
Text=1/@wt.doc.WTDocument/@Text File
TiffImage=1/@wt.doc.WTDocument/@TIFF

The following are some commonly used PDMlink format types that are 
present in the pitdmapping.properties file but are commented out by default. 
To use these format types, you must first uncomment these lines in the 
pitdmapping.properties file, then delete the text to the left of the “=” sign and 
enter the exact name of the Pro/INTRALINK pitypedef.

Microsoft Excel(ex.XLK XLC CSV DIF SLK XLT XLV IQY XLB XLS XLW)=1/@wt.doc.WTDocument/@Microsoft Excel
Microsoft PowerPoint(ex. PPA PPT PPS POS PWZ)=1/@wt.doc.WTDocument/@Microsoft PowerPoint
Microsoft Word(ex. WLL WBK DOC DOT WIZ)=1/@wt.doc.WTDocument/@Microsoft Word
Microsoft Project(ex. MPP)=1/@wt.doc.WTDocument/@Microsoft Project
MPEG Movie Clip(ex. M1V MP2 MPA MPE MPEG)=1/@wt.doc.WTDocument/@MPEG Movie Clip
PDF=1/@wt.doc.WTDocument/@PDF

Secondary Content
Rules for Handling Secondary Content
A user can specify that certain PI Types be migrated as secondary content 
(note that some Pro/ENGINEER specific PI types, such as accelerator files 
are already hard-coded to be handled as secondary content). In addition, 
these same PI Types can be defined to migrate as primary content. This 
means that for a given PI Type it is possible that it will be listed twice in the 
pitdmapping.properties file, once as secondary content and a second time as 
primary content (CAD Document or WT Document).
 When a PI Type is configured to be migrated as both primary and secondary 
content the migrator will first attempt to migrate this data as secondary 
content. In order for a particular PI to be eligible for migration as secondary 
content the following considerations must apply:
. This PI is a child of a user-defined dependency 
. This PI has only one parent 
. All PIVs of this PI have no children Otherwise 
. If the mapping file also has this PI Type defined as “Primary” content, 
then publish the file to its own Windchill object. 
. Else, an error should be written to the migration log, and migration 
should continue.

If the given PI meets the criteria for being migrated as secondary content, the 
next step is to determine which particular version (PIV) of the child object 
should be applied as secondary content to the appropriate version of the 
parent object.
. The migration tool will evaluate the as-stored configurations that are 
common between the given PIVs of both the parent and child of this user 
defined relationship. When it finds a version of the child with the same 
as-stored configuration as a particular version of the parent it will take 
this version of the child and apply it as secondary content.

Otherwise,
. If no version (PIV) of the PI is deemed to be a valid attachment, then it 
will try to migrate the whole PI as primary content. This will only be 
possible if the PI Type Def is also in the Primary Content section of the 
object mapping file. If it is not also defined as primary content, then the 
objects should not be migrated, and an error put to the migration log.

NOTE: A side effect of using the as-stored configuration to match parent and 
child version for the application of secondary content there may be particular 
versions of the child that do not have a corresponding matching parent based 
on this as-stored configuration rule. In this case, these particular PIVs for 
the child will not be migrated.
The following is a list of Secondary Content PI types that are recognized by 
the Pro/INTRALINK Data Migrator:

FEM Mesh Part=2/@MESH
FEM Mesh Assembly=2/@MESH
Inst_Assembly=2/@Instance Acelerator File
Inst_Part=2/@Instance Acelerator File
Mechanica Mesh Part=2/@MESH
Mechanica Mesh Assembly=2/@MESH
Animation Playback File=2/@ANALYSIS_RESULTS
Bmp=2/@IMAGE
CDRSRenderedImg=2/@IMAGE
EPS=2/@IMAGE
FEM=2/@MESH
GIF=2/@IMAGE
Image=2/@IMAGE
Inventor=2/@IMAGE
JPEG=2/@IMAGE
Mechanism Frame File=2/@ANALYSIS_RESULTS
Mechanism Playback File=2/@ANALYSIS_RESULTS
NCCheckImage=2/@IMAGE
Picture=2/@IMAGE
Plot=2/@IMAGE
PNG=2/@IMAGE
PTC Bumpmap=2/@IMAGE
PTC Color Texture=2/@IMAGE
PTC Decal=2/@IMAGE
RAWImage=2/@IMAGE
Render=2/@INFORMATION
RLAImage=2/@IMAGE
RLBImage=2/@IMAGE
RS_Base_Design=2/@INFORMATION
RSDesign=2/@INFORMATION
RS_Single_Sheet=2/@INFORMATION
RTAImage=2/@IMAGE
RTBImage=2/@IMAGE
SGIImage=2/@IMAGE
ShadedView=2/@IMAGE
Simpl_Rep_Accel=2/@INFORMATION
Snapshot=2/@INFORMATION
Symbol=2/@INFORMATION
TapeFile=2/@INFORMATION
TGAImage=2/@IMAGE
TiffImage=2/@IMAGE
ToolParams=2/@INFORMATION
Trail=2/@INFORMATION
TurnParams=2/@INFORMATION
VDA=2/@IMPORT
VerificationResults=2/@INFORMATION 
