With version-specific relationships, you can relate specific source document versions with specific target document versions to reduce compliance risk and improve the traceability of your supporting materials. These options are:
- Source version-specific: Target documents relate to specific source document versions
- Target version-specific: Source documents relate to specific target document versions
A given document relationship can be source version-specific, target version-specific, or both.
In this article, we will use the Supporting Documents relationship type as an example. Our source document is SOP v0.1. Our supporting (target) document is Form v0.1.
Version-Specific Relationships with Auto Carry Forward
Vault supports the following version-specific relationship configurations with auto carry forward:
Source Version-Specific Relationships with Carry Forward
With automatic carry forward of source version-specific relationships, when you version your source document, Vault carries forward all outbound relationships to the new document version, including relationships to other versions of the same target document. For example, SOP v0.1 is related to Form v0.1 and Form v.0.2. When you version SOP v0.1, SOP v0.2 receives all supporting documents from SOP v0.1, including Form v0.1 and Form v0.2.
In SOP v0.2, you can then click X in the Relationships panel of the Doc Info page to remove any supporting documents that do not relate to SOP v0.2. Removing supporting documents from SOP v0.2 does not remove those documents from SOP v0.1.
If Veeva Support configures source version-specific relationships without automatic carry forward, Vault does not carry forward the target document when you version your source document. For example, SOP v0.2 would not have any supporting documents.
Target Version-Specific Relationships with Carry Forward
With automatic carry forward of target version-specific relationships, when you version a target document, Vault automatically assigns the new version of the target document to the current source document version. Previous or future document versions do not receive the new version of the target document. For example, Form v0.1 is a supporting document for both SOP v0.1 and SOP v0.2. When you version of Form v0.1, Form v0.2 automatically relates to SOP v0.2.
Vault automatically carries forward target relationships for attachments when the Attachments relationship type is configured to be target version-specific.
Source Version-Specific Relationships with Carry Forward & Target Version-Specific Relationships without Carry Forward
In this configuration, when you version your source document, Vault carries forward the document relationships, including all related versions of the target document. However, when you version your target document, Vault does not relate the new target version to the source document. For example, when SOP v0.1 has Form v0.1 and Form v0.2 as supporting documents, SOP v0.2 also receives Form v0.1 and Form v0.2 as supporting documents. However, if you version Form v0.2, Vault does not relate Form v0.3 to any version of SOP.
Note that this configuration is not available for the Attachments relationship type.
Source & Target Version-Specific Relationships with Auto-Carry Forward
In this configuration, when you version your source document, Vault only carries forward the latest version of the target (supporting) document. When you version the target document, Vault assigns the new target document version only to the latest version of the source document.
For example, when you version SOP v0.1, SOP v0.2 receives Form v0.1 and Form v0.2 as supporting documents. Then, updating Form v0.2 to v0.3 assigns Form v0.3 as a supporting document only for SOP v0.2.
Note: When you enable Source Version-Specific with Carry Forward, it does not work retroactively on source documents that were versioned prior to enablement. It only affects source documents that are versioned after you enable it.
About the Doc Info Page
With source version-specific relationships, the Doc Info page lists only the relationships associated with the current source document version. Adding or removing a related document only affects the source document version in which you are currently working.
With target version-specific relationships, the Doc Info page lists only the versions of the target document that are related to the current source document version.
Configuring Version-Specific Relationships
Contact Veeva Support to enable and configure version-specific relationships with or without automatic carry forward in your Vault.