Retained document revisions
A Document Revision is a retained, immutable copy of an exact document file used as evidence. It records the original document and file, title, language, retained bytes, checksum, administering company, audience, and the person who preserved it.
A normal document can have its current file replaced. A retained revision preserves what a reviewer or publication actually relied on. Replacing or removing the ordinary current file must not rewrite the evidence attached to an older release or published passport.
Example
A battery release is approved with test report edition 3. The supplier later sends edition 4 and the current document file is updated. The retained revision referenced by the earlier release still contains edition 3. New reviewed information can reference edition 4 without making it appear that the earlier decision used a report that did not yet exist.
Where to create a retained revision
The current interface provides Retain a document revision as a supporting panel in Logistic → Quality, rather than as a separate primary-entity tab. Retain the exact supporting revision for the relevant quality or evidence record.
- Find the original document in the normal media/document workflow and ensure the correct file and language are available.
- Open the relevant Quality create or detail form and locate Retain a document revision.
- Search for the Source document file by its displayed name.
- Choose Audience, then select Retain a document revision.
- Select the retained revision in the evidence, batch, assignment, or other form that needs it. Preserving a file and linking that revision to a business record are separate steps.
When a Product Release captures associated product documents, Actualog also retains those exact files as part of the release capture.
Who may preserve and read evidence
Retention requires authority to contribute evidence for the administering company, normally held by a Product Editor, Product Governance Manager, or Company Administrator. The user also needs access to the original source document; a permitted product action does not bypass another company's media permissions. An explicit, applicable delegation can cover access where supported.
Restricted, Authorized, and Public identify intended audiences for consuming workflows. Retention cannot promote a private source document to Public. Choosing an audience does not independently publish the document or grant every reader download rights. The referencing workflow and its authorization rules determine permitted access.
Maintain evidence without rewriting history
Retain a new revision when the content changes. Link it to the new or corrected business statement and preserve the old reference for historical review. A checksum confirms the identity of stored bytes; it does not establish that the statement is true, independently verified, or legally sufficient.
If retention fails, check source access, file availability, selected audience, and whether the source changed during copying. Refresh and select the intended source again. A missing file should be reported and corrected; another unrelated document is not a substitute.