Example: Previewing import file scenarios

Scenario 1: The REQ-000200 requirement revision object already exists in Teamcenter. The PAR-000201 paragraph revision object does not exist in Teamcenter.

You: assign [ID:REQ-000200] primary requirement revision identifier and [CID:PAR-000201] secondary paragraph revision identifier in the unstructured document; set CreatePrimaryKeyword and CreateSecondaryKeyword parser settings to True; save the unstructured document as ReqSpec100; perform Import New, click Preview, select the option to create trace links.

Result: [ID:REQ-000200] requirement revision is highlighted red because there is a duplicate object that exists in a different requirement specification in Teamcenter. [CID:PAR-000201] paragraph revision is highlighted yellow because it is an internal defining trace link and the requirement revision is the complying link — internal because the paragraph revision is contained within the same requirement structure as the requirement revision. In the requirements pane (ReqSpec100 > REQ-000200 > PAR-000201), a symbol displays next to REQ-000200 indicating the object already exists in Teamcenter.

Scenario 2: The REQ-000200 requirement revision object does not exist in Teamcenter. Multiple revisions of the PAR-000201 paragraph revision object exist in Teamcenter.

You: assign the same identifiers; set CreatePrimaryKeyword and CreateSecondaryKeyword to False; set LinksAs to Complying; save as ReqSpec100; perform Import New, click Preview, select the option to create trace links.

Result: [ID:REQ-000200] requirement revision is highlighted green because it does not exist in Teamcenter. [CID:PAR-000201] paragraph revision is highlighted orange because it is an external defining trace link and the requirement revision is the complying link — external because the paragraph revision resides in a different requirement structure than the requirement revision. A symbol displays next to PAR-000201 because it is an unresolved trace link: since there are multiple revisions of the paragraph revision, Teamcenter does not know which revision to use as the defining trace link.

Scenario 3: You resolve the trace link from scenario 2 by clicking the symbol next to PAR-000201 in the requirements pane, and in the Conflict Resolution dialog box selecting the paragraph item revision you want to use to resolve the trace link.

Result: the same highlighting as scenario 2 (REQ-000200 green, PAR-000201 orange), but now the symbol displays next to PAR-000201 indicating you have resolved the trace link conflict by selecting the specific paragraph revision.

Related Topics

• Configuring the color assignments
• Import the unstructured document for the first time
• Reimport the modified dataset