Example: How are the color assignments used?

This example uses the following values for the parser rules and color assignments section of the configuration file for Word.

<ParserRules>
<add
RuleID="1"
LinkType = "FND_Tracelink"
PrimaryKeyword = "[[]ID:REQ-[0-9]{6}[]]"
PrimaryKeywordType = "Requirement Revision"
CreatePrimaryKeyword = "true"
SecondaryKeyword = "[[]CID:PAR-[0-9]{6}[]]"
SecondaryKeywordType = "Paragraph Revision"
CreateSecondaryKeyword = "true"
LinksAs = "Complying"/>
</ParserRules>

<ColorAssignments>
<add key ="NewItem" value ="0,255,0"/> <!--green-->
<add key ="ExistingItem" value ="255,153,204"/> <!--pink-->
<add key ="DuplicateItem" ="255,0,0"/> <!--red-->
<add key ="InternalLinks" value ="255,255,0"/> <!--yellow-->
<add key ="ExternalLinks" value ="255,102,0"/> <!--orange-->
</ColorAssignments>

The following information shows how some of the settings are used in the color assignments section.

Scenario 1: In the unstructured document, you assign the [ID:REQ-000111] requirement revision identifier and the [CID:PAR-000111] paragraph revision identifier. Neither exists in Teamcenter. You perform Import New, click Preview, and do not select the option to create trace links. Both objects are highlighted in green because they do not exist in Teamcenter and no trace links are created between them.

Scenario 2: In the unstructured document, you assign the [ID:REQ-000222] requirement revision identifier and the [CID:PAR-000222] paragraph revision identifier. Neither exists in Teamcenter. You perform Import New, click Preview, and select the option to create trace links. The [ID:REQ-000222] requirement revision is highlighted in green because it is a new object and does not exist in Teamcenter. The [CID:PAR-000222] paragraph revision is highlighted in yellow because it is an internal defining trace link and the requirement revision is the complying link — it is internal because both the requirement objects and the trace links are created by the document.

Scenario 3: In the unstructured document, you assign the [ID:REQ-000333] requirement revision identifier and the [CID:PAR-000333] paragraph revision identifier to the ReqSpec1 requirement specification. Both already exist in a different requirement specification in Teamcenter. You perform Import New, click Preview, and do not select the option to create trace links. Both objects are highlighted in red because there is a duplicate object that exists in a different requirement specification in Teamcenter.

Scenario 4: In the unstructured document, you assign the [ID:REQ-000444] requirement revision identifier and the [CID:PAR-000444] paragraph revision identifier to the ReqSpec2 requirement specification. Both already exist in Teamcenter in the ReqSpec2 requirement specification. You perform Import Update, click Preview, and select the option to create trace links. Both objects are highlighted in pink because they exist in Teamcenter in the same ReqSpec2 requirement specification.

Scenario 5: In the unstructured document, you assign the [ID:REQ-000555] requirement revision identifier and the [CID:PAR-000555] paragraph revision identifier. In the parser rules, CreateSecondaryKeyword is set to false so the secondary object is not created. The [ID:REQ-000555] requirement revision does not exist in Teamcenter; the [CID:PAR-000555] paragraph revision already exists in Teamcenter. You perform Import New, click Preview, and select the option to create trace links. The [ID:REQ-000555] requirement revision is highlighted in green because it does not exist in Teamcenter (it is created after the import). The [CID:PAR-000555] paragraph revision is highlighted in orange because it is an external defining trace link and the requirement revision is the complying link — it is external because the paragraph revision resides in a different requirement structure than the requirement revision.

Related Topics

• Previewing the import file for accuracy and errors