This topic explains how to import cross-references between requirements, available through the Knowledge module. Cross-references are provided by Modulo, they can be created manually in the system, or they can be imported through a specially prepared import template.
For details on viewing existing cross-references, see Chapter 8: Knowledge -> Compliance Knowledge -> Authoritative Documents -> Viewing Authoritative Documents and Cross-Referenced Requirements -> How to View a Cross-Reference Report. For details on managing cross-references between requirements in the system itself, see Chapter 8: Knowledge -> Compliance Knowledge -> Authoritative Documents -> Creating and Editing Authoritative Documents and Cross-References -> How to Manage Cross-References between Requirements.
There are 3 worksheets in this template:
•Instructions: This worksheet provides instructions on how to complete each field from each worksheet and does not require completion.
•Authoritative Documents: This worksheet must be completed with information on the authoritative documents whose requirements are being cross-referenced to each other.
•Mapping: This worksheet must be completed with the cross-references between the requirements and is where they are mapped using the requirement IDs.
Once completed correctly, the spreadsheet containing the information on the cross-referenced requirements can be imported through the Knowledge module in the Authoritative Documents section. The imported cross-references are then used to generate the Cross-Reference Report, in cross-reference queries, and are also displayed for individual requirements when viewing an authoritative document. Note that only cross-references from two authoritative documents can be imported at a time.
Also note that cross-references are only created in the system in the direction in which they are registered. In other words, if a cross-reference was created from "Authoritative Document 1" to "Authoritative Document 2", the reverse of this association ("Authoritative Document 2" -> "Authoritative Document 1") is not automatically registered. This affects the results of system queries to cross-references, for example, which only display one-way results for these mappings. For this reason, it could be useful to import cross-references both ways, entering an opposite mapping for each cross-reference being registered.