Example: How are the parser rules used?

This example uses the following values for the parser rules 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"/>

<add
RuleID="2"
LinkType = "BZ_FND_Tracelink"
PrimaryKeyword = "[[]ID:B-FNC-TSC[0-9]{1,}[]]"
PrimaryKeywordType = "Requirement Revision"
CreatePrimaryKeyword = "true"
SecondaryKeyword = "[[]ID:B-FNC-TSR[0-9]{1,}[]]"
SecondaryKeywordType = "Paragraph Revision"
CreateSecondaryKeyword = "false"
LinksAs = "Defining"/>
</ParserRules>

The following information shows how some of the settings are used in the parser rules section.

Text in parser settings section	How is the setting used?
RuleID="1", RuleID="2"	In the unstructured Word or Excel document, you assign an identifier for the requirement information you want to import to Teamcenter. In the Assign ID dialog box, the list of valid rules from the parser settings is displayed when you click the Rule box. You specify the rule that you want to use for assigning the requirement identifiers and types, and determining the trace link behavior. (Note: If there is only one rule defined for a specific type, the Rule box is not displayed in the Assign ID dialog box.)
PrimaryKeywordType = "Requirement Revision", SecondaryKeywordType = "Paragraph Revision"	In the Assign ID dialog box, the list of valid types is displayed when you click the Type box. The valid types are determined by the rule you specify in the Rule box. In this example, Requirement Revision and Paragraph Revision are valid types for rule 1.
PrimaryKeyword = "[[]ID:REQ-[0-9]{6}[]]"	In the Assign ID dialog box, you type the valid values to create a requirement or paragraph identifier. In this example, using rule 1 and Type set to Requirement Revision, the identifier must match the [[]ID:REQ-[0-9]{6}[]] regular expression value set for the Primary Keyword setting. The green check mark is displayed to indicate the [ID:REQ-000100] identifier is a valid identifier.
LinkType = "FND_Tracelink", LinksAs = "Complying"	In the unstructured document, you import the following identifiers validated from rule 1 to Teamcenter: [ID:REQ-000100] requirement revision, [CID:PAR-000100] paragraph revision. In this example, the REQ-000100 requirement revision is the primary object and the PAR-000100 paragraph revision is the secondary object. After importing the unstructured document to Teamcenter, a requirement structure is created (e.g. 000070/A-ReqSpec > REQ-000073/A;1–REQ-000100 > 0000071/A;1–PAR-000100). A FND_Tracelink trace link is created between the REQ-000100 requirement revision and the PAR-000100 paragraph revision. Because LinksAs is set to Complying, the requirement revision is the defining link and the paragraph revision is the complying link. The trace link is classified as an internal trace link since the paragraph revision is within the same structure as the requirement revision.

Note: If the CreateSecondaryKeyword setting was set to false, the PAR-000100 paragraph revision would have to exist in Teamcenter for the trace link to be created. The trace link is then classified as an external trace link since the paragraph revision is not within the same structure as the requirement revision.

Related Topics

• Defining the requirement objects by assigning identifiers in the unstructured document
• Assign identifiers for new requirement objects in the unstructured document
• Insert identifiers for existing requirement objects in the unstructured document