The Document Audit Trail in QM10 lists the actions performed on each version of a document. Every entry for document approved (approved or approved for retirement) shows a Date.
This article explains how to interpret it, and which date is reported in the Document Dataset.
In short: For the approval and retirement entries listed below, the Date is when the document version was created or its metadata was last modified.
Audit Trail entries
An entry is added to the Audit Trail as soon as a document is approved, or approved for retirement.
| Entry type | What the Date means | Who is shown in Username | In the Dataset? |
Version entries • Document Approved • Document Approved & Effective • Retirement of Document Approved and Awaiting Retire Date • Document Retired | The date and time this version was created, or the date of the last Modify action on its metadata, if one was done after creation. This date represents the creation date of the official record for a specific major document version (e.g., 1.0). Since QM10 does not retain the complete history of edits made during the review/approval process, the system records the creation date of the approved document as its official record creation date. | The person who created the version or made the last metadata modification. | Yes. This is the date shown in the dataset (Document Metadata). |
In cases where the effective date is set at the time of last approval, the 'Date' shows the date the version was created or last modified - as per above explanations.
In cases where the effective date is set in the future (after the last approval), an entry named Document Approved is created. The 'Date' shows the date the version was created or last modified, and the name of the person who did it - as per above explanations.
Example: reading the Audit Trail
For internal version 12.0 in the screenshot above:
- Document Approved – 17-Feb-2026 05:30:33 UTC-05:00: internal version 12.0 was created (or last modified) by Martine Boire on this date. This is the version's creation date.
- Document Set Effective by the System – 10-Mar-2026 02:41:19 UTC-04:00: the system made version 12.0 effective on this date. This is an event date only; it does not change the version's creation date.
The same logic applies to version 11.0: its creation date is 15-Feb-2024 (Document Approved), and it became effective on 20-Mar-2024.
Where this date appears in the Document Dataset
The creation/modification date from the version entries is the value reported in the Document Dataset, in these two columns:
- documentCreateModifyDate
- documentCreateModifyDate_DateTimeFormatted
Tip: The dataset does not show seconds, and its times can differ from the Audit Trail because of the time zone. For example, version 12.0 shows 05:30 UTC-05:00 in the Audit Trail and 10:30 in the dataset. Both refer to the same moment; the dataset value is expressed in UTC.
Comments
0 comments
Article is closed for comments.