Reviewing ReqIF import validation reports
Note: ReqIF import only supports requirements and requirement documents. Other item types, such as test cases, are not supported.
After you upload a ReqIF and mapping file for a ReqIF import, a validation report is displayed. This report gives you a preview of the import, including mappings between the ReqIF file and Helix ALM that will be used during the import and messages to help with troubleshooting any problems.
Validation reports contain the following sections.
Tip: Some report sections have an Import status column, which tells you at a glance if a mapping is valid or if there is a problem.
Header
Displays:
- ReqIF file selected to import
- Mapping file selected for the import based on the ReqIF file
- Mapping summary of the number of items that will be imported
- Number of errors and warnings identified, including links to the detailed messages in the report
Mapping Summary
Displays a list of the ReqIF types and Helix ALM field mappings that will be used for the import, including links to view more details.
Item Mapping Errors
Displays a list of ReqIF types that were not mapped correctly to Helix ALM and will not be imported.
Document Mappings
Displays a Document type mapping section, which indicates if the ReqIF Specification Type is mapped to a Helix ALM field. Specification Type is always mapped to a Helix ALM requirement document because Helix ALM only has one requirement document type, but you can map Specification Type to a Helix ALM custom field if you want to preserve the Specification Type values from the ReqIF file.
Also displays a section for fields for each ReqIF document type in the mapping file. Each section contains a list of mapped and unmapped fields. The number of items that will be imported is also displayed for each document type.
Requirement Mappings
Displays a section for each mapped requirement type in the mapping file. Subsections are named ReqIF <name of requirement type in mapping file> to Helix ALM <name of mapped requirement type in Helix ALM>. Each section contains a list of mapped and unmapped fields. The number of items that will be imported is also displayed for each type.
Link Mappings
Displays a list of ReqIF links mapped to Helix ALM link definitions.
Unmapped Items
Displays a list of ReqIF types in the mapping file that are not mapped to a Helix ALM item type. These items will not be imported.
Messages
Displays a list of messages generated when validating the ReqIF file and import mappings. Information is displayed in the following columns.
Severity
Severity | Description |
---|---|
Fatal Error | A serious problem occurred that prevents the ReqIF Exchange Service from processing the ReqIF file. The file cannot be imported. |
Error | A problem occurred that does not stop the processing of the ReqIF file, but may result in imported data being skipped or changed. |
Warning | A potential problem was identified, but it may not affect the import. |
Informational | No problem was identified, but information may be useful to understand how data will be imported. |
Source
Source | Description |
---|---|
Helix ALM | A problem occurred in Helix ALM. |
ReqIF file | A problem occurred with the ReqIF file. For example, an issue occurred when loading data from the file, data is missing in the file, or a formatting issue exists. |
Mapping file | A problem occurred with the mapping file. For example, a mapping to an invalid value exists. |
Resolution
Resolution | Description |
---|---|
Auto-corrected | A problem occurred, but it was likely automatically fixed and will import correctly. For example, a text field had to be truncated because of character limits in a field. |
Not imported | A problem occurred and the data will not be imported. For example, a numeric value exceeded the maximum length in the mapped Helix ALM field and could not be truncated. |
No change | Informational message. For example, the mapping file contains an identifier that does not exist in the ReqIF file and will be ignored during import. |