Let’s say a published authoritative document A version 1.0 is published and was associated with requirements from published authoritative document B version 1.0 (see figure below).
When the Cross-Reference Report is generated for authoritative document A and B, the system will detect that there is an association between one or more requirements from these documents and will allow the report to be generated.
If authoritative document A version 1.0 is edited, a new version 1.1 will be published. However, all cross-references previously established with version 1.0 of authoritative document B will be lost. These are not transferred automatically to the new version 1.1 of authoritative document A (see figure below).
As cross-references are not transferred when either of the cross-referenced documents is edited, there will be no relationship between requirements from version 1.1 of document A and requirements from version 1.0 of document B unless these cross-references are recreated manually. Thus, there will be no option to generate a Cross-Reference Report between these two document versions. However, the cross-references between the previous version (1.0) of document A with requirements from version 1.0 of document B are preserved.