Example: Reimporting a modified dataset a revision

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"/>
</ParserRules>

The following steps are performed:

1. The following identifiers are assigned in the unstructured ReqSpec1.doc Word document:

   [ID:REQ-0001001]
   [CID:PAR-0001001]
   [CID:PAR-0001002]
   [ID:REQ-0002001]
   [CID:PAR-0002001]
   [CID:PAR-0002002]
   

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

3. The following modifications to the ReqSpec1 dataset are performed:

   • The [CID:PAR-0001002] paragraph revision identifier is deleted.
   • The [CID:PAR-0002002] paragraph revision identifier is deleted.
   • The new [ID:REQ-0002002] requirement revision identifier is assigned.
   • The new [ID:PAR-0002003] requirement paragraph identifier is assigned.

   The updated contents of the ReqSpec1.doc unstructured document contain the following identifiers:

   [ID:REQ-0001001]
   [CID:PAR-0001001]
   [ID:REQ-0002002]
   [CID:PAR-0002001]
   [CID:PAR-0002003]
   

4. The unstructured document is reimported as a revise import, with the option to create trace links selected.

After the reimport to Teamcenter for revise, the following occurs:

• The ReqSpec1 dataset is updated with links to the requirement objects in the 143/B;1–ReqSpec1 requirement specification.
• The 143/B;1–ReqSpec1 requirement specification is revised to the next revision in Teamcenter and contains the following changes:
  • The REQ-145/B;1-REQ-001001 requirement revision is revised to the next revision in Teamcenter.
  • The 146/B;-PAR-001001 paragraph revision is revised to the next revision in Teamcenter.
  • The 149/B;-PAR-002001 paragraph revision is revised to the next revision in Teamcenter.
  • The new REQ-151/A;1-REQ-002002 requirement revision is created in Teamcenter.
  • The new 152/A;-PAR-002003 paragraph revision is created in Teamcenter.
• Because the [CID:PAR-0001002] paragraph revision identifier was deleted in the unstructured document, the 147/A;-PAR-001002 paragraph revision and the T2 trace link are deleted in Teamcenter.
• Because the [CID:PAR-0002002] paragraph revision identifier was deleted in the unstructured document, the 150/A;-PAR-002002 paragraph revision and the T4 trace link are deleted in Teamcenter.
• Because CreateSecondaryKeyword is set to True in the parser settings for rule 1, an internal T5 trace link is created between the REQ-151/A;1-REQ-002002 requirement revision and the revised 149/B;-PAR-002001 paragraph revision.
• A new internal T6 trace link is likewise created between REQ-151/A;1-REQ-002002 and the revised 149/B;-PAR-002001 paragraph revision.
• A new internal T7 trace link is created between REQ-151/A;1-REQ-002002 and the 152/A;-PAR-002003 paragraph revision.

Related Topics

• Previewing the import file for accuracy and errors