Defining the requirement objects by assigning identifiers in the unstructured document

You define the requirement objects in the unstructured document by assigning identifiers. Teamcenter validates the identifiers by the rules you define in the flat file configuration files. When you assign an identifier that is not valid, an error displays that the identifier does not match the configuration rules. The configuration rules also specify if trace links are created between the primary and secondary requirement objects after the import to Teamcenter. An internal trace link is linked to requirement objects within the same requirement structure. An external trace link is linked to requirement objects in a different requirement structure.

Note: In Excel, there is a limitation when assigning multiple IDs.

You can perform the following when you assign identifiers:

• Assign identifiers for new requirement objects that do not exist in Teamcenter. If the configuration parser rules specify that trace links are created between the primary and secondary requirement objects, internal trace links are created after the import to Teamcenter.
• Search for and insert identifiers for requirement objects that already exist in Teamcenter. If the configuration parser rules specify that trace links are created between the primary and secondary requirement objects, external trace links to existing objects in different structures are created after the import to Teamcenter.

Note: To avoid errors during the import for requirement objects that already exist in Teamcenter, in the flat file configuration files, do the following:

• For existing primary requirement objects, set the CreatePrimaryKeyword setting to false.
• For existing secondary requirement objects, set the CreateSecondaryKeyword setting to false.

You use the Assign ID dialog box to create the identifiers. In the Assign ID dialog box, values such as Type, Rule, Prefix, ID, and Name are checked for validation according to the configuration rules set up in the flat file configuration files. Once the values are validated, a green check mark displays next to the identifier tag at the bottom of the dialog box.

Note: You can customize these properties by modifying the DisplayName business constant using the Business Modeler IDE. The Assign ID dialog is automatically resized based on the list of display properties. Properties on persistent objects such as item revision properties are supported. Properties on runtime objects are not supported.

The Assign ID dialog box elements:

1. Type of requirement object. The list of valid requirement object types is specified by the PrimaryKeywordType and SecondaryKeywordType settings in the configuration parser rule section for a specified rule ID. You select the rule ID from the Rule box.
2. Rule — parser rule used for validating identifiers for the requirement objects and creating trace links. The list of valid rule IDs is specified by the RuleID setting for the configuration parser rule. If there is only one parser rule defined, the Rule box is not displayed.
3. Prefix of the requirement object. The list of valid prefixes is specified by the IDPrefix setting in the configuration common settings section.
4. Property values for creating a valid identifier for the requirement object. The valid identifier is defined by the PrimaryKeyword or SecondaryKeyword settings in the configuration parser rule section for the specified rule ID. If you set the PrimaryKeywordType setting as the type, the identifier is validated by matching the regular expression defined by the PrimaryKeyword setting; if SecondaryKeywordType, by the SecondaryKeyword setting. Delimiters in the regular expression Value designate where a property begins and ends; property values are validated by matching the regular expression for the property. (Example: ID, Revision, Sequence Id, and Name properties validated against [[]ID:REQ/[A-Z]{1};[0-9]{1}-[0-9]{6}[]].)
5. Search for existing requirement objects in Teamcenter. Clicking Search launches a Search dialog box that enables you to search for existing requirement objects in Teamcenter and insert the existing objects in the unstructured document. The IDProperty setting in the configuration flat file is used for the search criteria property.
6. Green check mark indicates valid identifier.

Related Topics

• Overview of the flat file configuration files
• Configuring the common settings
• Configuring the parser rules
• Configuring the property assignments