Summary
- A report can have multiple revisions. Each revision represents a specific version of the report.
- Snapshots help ensure that reviewed and approved revisions are based on the data that existed when the report was submitted.
Why revisions matter
Technical reports often change during preparation, review or after client comments. Revision control makes it possible to keep a clear history instead of overwriting previous documentation.
Users should be able to identify the current revision and access historical revisions when permitted.
What a snapshot protects
A snapshot can preserve report-critical data such as template structure, customer/project/work-order metadata, selected assets, attachments, validation context and report content.
This prevents an approved report from silently changing if referenced master data is edited later.
Recommended lifecycle
- Draft report uses current editable data.
- Submit for review creates or refreshes the controlled snapshot.
- Review and approval use the submitted snapshot.
- Approved view shows the approved revision state.
- Later changes are handled through a new revision.