Mapping File Rules
PTC recommends that you follow these rules for creating a mapping file to ensure valid mapping.
 |
PTC recommends that you do not modify the entries in the mapping file once they have been created. Modifying the entries may not provide the desired results during the import. Ensure that the new entries do not conflict with the existing entries.
|
Location Rules
This mapping should be either one-to-one or many-to-one. Do not map a single folder in a source PLM system to multiple folders in a target PLM system. However, you can map multiple folders in a source PLM system to a single folder in a target PLM system, as shown in the following examples:
• Invalid mapping
location /Root Folder/a/b = /myOrg/Product/myProd//a/b
location /Root Folder/a/b = /myOrg/Product/myProd//x/y
location /Root Folder/a/b = /myOrg/Product/myProd//x/y
• Valid mapping
location /Root Folder/a/b = /myOrg/Product/myProd/a/b
location /Root Folder/x/y = /myOrg/Product/myProd/a/b
location /Root Folder/x/y = /myOrg/Product/myProd/a/b
|
|
Ensure that you follow this rule consistently across a mapping file. There should be no ambiguity in a block or across blocks.
|
Revision Rules
Following are the mapping rules for revision:
• You can map one revision label to only one revision label.
• In a given block, you cannot map one revision to multiple revisions, or multiple revisions to one revision.
• The position of the revision cannot be crossed. For example, if revision AA is positioned before BB in the target release scheme, and if revision A is mapped to revision BB, the revision B cannot be mapped to revision AA.
Life Cycle Rules
Following are the rules for life cycle mapping:
• In one block, one combination of a life cycle scheme and life cycle state can be mapped to only one combination of a life cycle scheme and life cycle state. For example:
◦ In one block, one combination of a life cycle scheme and life cycle state can be mapped to only one combination of a life cycle scheme and life cycle state:
▪ Invalid mapping
Begin
lifecyclestate Release shceme1::RL1 = Default::INWORK
lifecyclestate Release scheme1::RL1 = Basic::INWORK
lifecyclestate Release scheme1::RL1 = MyLifecyle::RELEASED
End
lifecyclestate Release shceme1::RL1 = Default::INWORK
lifecyclestate Release scheme1::RL1 = Basic::INWORK
lifecyclestate Release scheme1::RL1 = MyLifecyle::RELEASED
End
▪ Valid mapping
Begin
lifecyclestate Release shceme1::RL1 = Default::INWORK
End
Begin
lifecyclestate Release scheme1::RL1 = Basic::INWORK
End
Begin
lifecyclestate Release scheme1::RL1 = MyLifecyle::RELEASED
End
lifecyclestate Release shceme1::RL1 = Default::INWORK
End
Begin
lifecyclestate Release scheme1::RL1 = Basic::INWORK
End
Begin
lifecyclestate Release scheme1::RL1 = MyLifecyle::RELEASED
End
◦ In one block, multiple combinations of a life cycle scheme and life cycle state can be mapped to one combination of a life cycle scheme and life cycle state. For example:
Begin
lifecyclestate RL1::Concept = LC1::Working
lifecyclestate RL1::In Work = LC1::Working
lifecyclestate RL2::In Work = LC1::Working
End
lifecyclestate RL1::Concept = LC1::Working
lifecyclestate RL1::In Work = LC1::Working
lifecyclestate RL2::In Work = LC1::Working
End
◦ The position of the life cycle state in a given life cycle scheme cannot be crossed. For example, if the life cycle LC1::Conceptual is positioned before LC1::Working in the target release scheme, and if RL1::In Work is mapped toLC1::Working, you cannot map RL1:: Released to LC1::Conceptual.