This section describes the Generic CSV Import Function and it is currently available for Requirements and Requirements Validation functionality. Any user with Create and Edit Permissions can import data from a CSV file.

The function has three essential steps, but some of them may be skipped, depending upon the type of data provided by the user. The import process sequence is described below using Planned Requirements Import as an example:

Importing Data into RMsis

Important : Prepare for CSV Import

Step 1 : Specify the Input File

Step 2 : Map the Fields

Step 3 : Map Options

Creating new records vs. updating records

Please note that the general philosophy is that

Use of ID Alias

The primary mechanism available today is to export data as CSV file and import it in another installation in the CSV format.

However, when we migrate data across installations

hence it becomes essential to store a map of the old ID's vs new ID's; so that either can be used, when required.

The CSV import process, now provides a mechanism to store old ID's as Alias. This should be selected, if the old references will be required (for example, in importing traceability).

Creating new options for Categories and Custom Lists

If the system identifies new options for Categories and Custom Lists, then the system will prompt user to either create a new option or to map it to an existing option.

Specific Information related to importing of Test Cases

Handling of Requirement Hierarchy

The indentation levels are exported alongwith the CSV export and automatically used while importing to create Requirement Hierarchy.