Previewing the import file for accuracy and errors

Before you import the unstructured document to Teamcenter, you can preview the import file to check for accuracy or errors. This enables you to make any corrective changes to the unstructured document before the import. You have the option of previewing the import file with or without trace links.

If you are importing the unstructured document for the first time, you preview the import file as a new import. If you are reimporting the unstructured document, you preview the import file as an updated or revised import.

Note: If the IDProperty setting located in the flat file configuration files is not set to a unique property, but you still want to ensure identifier uniqueness when creating new requirement objects in Teamcenter, preview the import file before you import the unstructured document to Teamcenter after the first import. Any subsequent imports will display errors indicating the requirement objects already exist in Teamcenter.

For example, the IDProperty setting located in the flat file configuration files is set to object_name, which is not a unique property. You preview the import file first before the actual import, and then import it as a new unstructured document to Teamcenter. You make changes to the requirement objects and import it a second time as a new import. Teamcenter displays an error message indicating the requirement objects exist.

If you did not preview the import file first and import the unstructured document a second time as a new import, a new requirement specification containing new requirement objects is created in Teamcenter with the same object names but different item IDs than the first import.

What happens after preview

A preview document is created with a requirements pane and has the text -Preview appended to the original filename and is stored in your local temp directory. When you import the unstructured document to Teamcenter, the preview document is also imported to maintain any corrective actions you made to the unstructured document after the preview.

Requirement objects are highlighted with different colors in the content pane for the following conditions:

Condition	Description	Default color
New requirement object	Highlights the object in the preview document if it doesn't exist in Teamcenter.	0,255,0 (green)
Existing requirement object	Highlights the object in the preview document if it exists in Teamcenter in the same requirement specification when you reimport the unstructured document to Teamcenter to revise or update requirement information.	255,153,254 (pink)
Duplicated requirement object	Highlights the object in the preview document if there is a duplicate in Teamcenter that was created in a different requirement specification when you import the unstructured document.	255,0,0 (red)
Internal trace link	Highlights the object in the preview document if it contains an internal trace link (links to objects within the same structure).	255,255,0 (yellow)
External trace link	Highlights the object in the preview document if it contains an external trace link (links to objects outside the structure).	255,102,0 (orange)

Indicators are displayed next to the requirement object in the requirements pane for the following conditions:

• A symbol next to the requirement object indicates the object already exists in Teamcenter.
• A red asterisk (*) next to the requirement object indicates the object does not exist in Teamcenter.
• A symbol next to the requirement object indicates the object is an unresolved trace link. You resolve the conflict by selecting the revision of the requirement object to resolve the trace link.
• A symbol next to the requirement object indicates the object trace link has been resolved.

Related Topics

• Configuring the color assignments
• Generate the preview document and resolve any conflicts