Example: Importing a new requirement specification for the unstructured document

The following example shows importing the ReqSpec1.doc unstructured Word document as a new import to Teamcenter. The option to create trace links for the import was selected. The rules you define in the flat file configuration files determine the identifier tag format and its behavior.

For this example, the flat file configuration file for Word contains the following common settings and parser rule settings:

<Common Settings>
<add key = "Parser" value = "Teamcenter.TcIDToIDParser.WordIDParser;
C:\Program Files (x86)\Siemens\Teamcenter 9\TcWord2K7DocImp\TcIDToIDParser.dll"/>
<add key = "PropDebugComments" value = "false"/>
<add key = "LinkDebugComments" value = "false"/>
<add key = "DefaultSpecType" value="RequirementSpec" />
<add key = "IDValidationPattern" value="[[]*:[A-Za-z0-9_]{1,}-[0-9]{6}[]]"/>
<add key = "IDPrefix" value = "ID,ID2,ID3,CID" />
<add key = "IDProperty" value = "object_name" />
<add key = "Default Saved Query" value = "Item ID" />
<add key = "Search" value="OOTBSearch" />
</Common Settings>

<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 = "FND_Tracelink"
PrimaryKeyword = "[[]ID:ENG-[0-9]{6}[]]"
PrimaryKeywordType = "Requirement Revision"
CreatePrimaryKeyword = "true"
SecondaryKeyword = "[[]CID:ENG-[0-9]{6}[]]"
SecondaryKeywordType = "Paragraph Revision"
CreateSecondaryKeyword = "false"
LinksAs = "Complying"/>
</ParserRules>

The following steps are performed:

• Using rule 1, the REQ-000100 requirement revision and PAR-000102 paragraph revision identifiers are assigned in the unstructured ReqSpec1.doc Word document.
• Using rule 2, the ENG-000102 requirement revision and the ENG-000202 paragraph revision identifiers are assigned.

The contents of the unstructured document now contain the following identifiers:

[ID:REQ-000100]
[CID:PAR-000101]
[ID:ENG-000102]
[CID:ENG-000202]

The unstructured document is imported as a new import, with the option to create trace links selected.

After the import to Teamcenter, the following occurs:

• The ReqSpec1 dataset is created with links to the requirement objects in the 143/A;1–ReqSpec1 requirement specification.
• The 143/A;1–ReqSpec1 requirement specification is created in Teamcenter containing:
  • The new REQ-145/A;1-REQ-000100 requirement revision.
  • The new 146/A;1-PAR-000101 paragraph revision.
  • The REQ-147/A;1-ENG-000102 requirement revision.
• Because CreateSecondaryKeyword is set to True in the parser settings for rule 1 and the 146/A;1-PAR-000101 paragraph revision does not exist in Teamcenter, an internal T1 trace link is created between the REQ-145/A;1-REQ-000100 requirement revision and the 146/A;1-PAR-000101 paragraph revision.
• Because CreateSecondaryKeyword is set to False in the parser settings for rule 2 and the 148/A;-ENG-000202 paragraph revision already exists in Teamcenter, an external T2 trace link is created between the REQ-147/A;1-ENG-000102 requirement revision and the 148/A;-ENG-000202 paragraph revision.
• Because the IDProperty setting in the flat file configuration file is set to object_name, the item IDs for the requirement objects are automatically assigned by Teamcenter after the import.
• The body text of the requirement objects in the ReqSpec1 requirement specification is set to the URL of the ReqSpec1 dataset.

Related Topics

• Previewing the import file for accuracy and errors