How do I keep previous versions of a document?
Configure FormKiQ's commercial Document Versioning capability to track supported content and metadata revisions. Use the version APIs to inspect history and retrieve or promote an earlier version. Verify what your deployment retains and how lifecycle rules affect older objects. Application version history, visual comparison tools, legal hold, and disaster recovery are separate capabilities with different operating requirements.
Preserve revision identity
When content changes, retain the document identity and inspect its version history. Use the documented version operations rather than creating unrelated documents with similar filenames. Where approvals or signatures depend on a revision, record that version with the decision or envelope association.
The module builds on S3 versioning and application metadata history. Confirm the actual bucket and lifecycle configuration; deleting old storage versions can affect what remains recoverable.
Restore and validate
Use a fictional document with two clearly different content revisions and changed metadata. List versions, retrieve the intended prior revision, and follow the supported promotion/revert operation. Confirm the resulting current content and metadata rather than inferring success from a request status alone.
Validate the reader's permission to view historical content. Version storage does not automatically provide a redline UI for every format, immutable evidence, or a complete backup/restore process for the deployment.
Edition and configuration
Document Versioning is included in Essentials, Advanced, and Enterprise. Configure storage/version lifecycle and check the exact backend/Web behavior and permissions for the installed release.