Versions and Attachments
Documents may have versions and related attachments. Versions preserve changes over time, while attachments connect supporting files such as e-mails, confirmations, specifications, or related invoices.
Use relations and attachments when documents belong to the same business context but should remain separate records.
Versions
Versions represent changes to the main file or document content over time. They are useful when a document is replaced, corrected, or updated while preserving history.
Typical examples:
- corrected contract PDF,
- updated offer,
- rescanned invoice,
- revised document after quality check.
Version handling is installation-specific. Some systems keep all versions visible; others show only the latest file by default.
Attachments
Attachments are supporting files connected to a document. They do not usually replace the main file.
Examples:
- original e-mail,
- delivery note,
- approval confirmation,
- calculation sheet,
- payment proof,
- related correspondence.
Relations
Relations connect two or more objects. A relation is useful when each object should remain independent but the business context belongs together.
Examples:
- invoice related to purchase order,
- contract related to correspondence,
- e-mail related to customer document,
- payment file related to exported invoices.
Version vs. Attachment vs. Relation
| Use this | When |
|---|---|
| Version | The main document file is replaced or corrected. |
| Attachment | A supporting file belongs to the document. |
| Relation | Another document or object is linked but remains independent. |
Practical Guidance
Use versions carefully when the latest file should represent the current authoritative document. Use attachments for evidence and supporting material. Use relations when the linked object has its own lifecycle, metadata, permissions, or reporting value.
If users cannot see an attachment or relation, check permissions on the related object as well as the main document.