Importing content into web client streams

This topic describes the process of importing content into appropriate web-client streams.

Once you have selected the appropriate stream, use Create > Import Artifact > Import requirements from a ReqIF file to import the ReqIF file. Following are some important considerations:

Always import into the top level folder of the web client, so that the top level folders are the plug-ins. For all other options, use the default values.
For more information, see Importing artifacts from ReqIF files to a requirements project or component.

The web client sometimes fails to import elements and the following error message appears: Error importing artifact - ReqIF ID xxx. The cause of this error is HTML incompatibility. To resolve this error, complete these steps:

Identify the problem element IDs from the web client import error messages.
Identify the problem element in the rich client by using the ID in the previous step.

Use one of the options listed in the following table to identify the element:

Quick option	Reliable option
In the rich client, click Search > Search and then click Method Search. Copy the ReqIF ID from the error message into the Text field. Click Search. Note: This option helps to find all elements that contain the ReqIF ID. However, the search results might include extra elements that reference the problem element.	Export a report of IDs and element names. Click File > Report and note the file name. Click Finish. Open the file in a spreadsheet application such as Microsoft® Excel. Search for the ReqIF ID to find the problem element. Note: This option may not be quick but is reliable.

For each problem element, you can use one of the following options:
- Change the rich text in the rich client to make it compatible with the web client.
- Move the problem element to a different plug-in, to exclude it from the ReqIF export.
- Fix the element manually in the web client.

To manually fix an element in the web client, complete the following steps:

Navigate to each of the problem elements in the rich client.
Copy the rich text content into the web client.
Manually fix the hyperlinks and images.

Note: If an element does not have a presentation name, in the web client it is defined as [mecFilename]. After re-importing such an element into the rich client, the presentation name of the element is set to blank. For example, a contributing role with name system_engineer.assign_workproduct adds a relationship from a system engineer role to a work product it is responsible for. These contributing elements do not have presentation names. If you import the contributing elements in the web client, the file name in the web client is [system_engineer.assign_workproduct]. When you re-import the element back in the rich client, the element has the same file name with no presentation name.