| Status | ||||
|---|---|---|---|---|
|
| Table of Contents |
|---|
Introduction
Audit Trail function allows enables users to track changes in objects or documents. This functionality is available accessible in conjunction with with Version Management. To achieve full ensure complete traceability, a Strict versioning mode must be used.As a resultemployed. Consequently, no changes alterations can be made in the master archive without going passing through a Draft and publishing a new system version.
To activate the function, select this icon:
A new window is opened where you can select multiple search options. The window can be maximized to provide maximum viewing area for the complex data presented.
Audit Trail Search Options
The Audit Trail window consists of several search options as presented below:
These options include:
Option Name | Allowed Values | Description |
|---|---|---|
Search by |
| Desired date search range can be specified either in regard relation to datetwo specific dates:
|
From / To | Date fields containing any valid date. | A date range is needed to indicate when the objects were modified or published. A date can be specified between This can span any time in the past up to nowthe present. |
Last |
| A convinience functions to set convenient function is available to automatically set the date range automatically to the last day, week, month, or year. Using Utilizing this function will overwrite any values previously set in the From/To fields. |
Search Class | Use class picker to select one of object classes available in the system. | Since the Audit Trail presents changes in object metadata, it will use a schema dedicated to a specific object class. The search must be narrowed to a single object class. |
Fields modified | Use class fields picker to select from one to all metadata fields. | When nothing is selected in this field, all changes are taken into account. Note, Please note that in that this case, a full metadata schema will be displayed that , which can make reading the results a bit hard challenging for large schemas. If you are interested in changes only in a specific fields, please select them from a multi-select list. Records that had this these specific fields modified will be presented. |
Modified by | Select one or more users from a multi-select list. | When nothing no selection is selectedmade, records modified by any user will be taken into accountconsidered. IF you are interested in If you want to focus on records modified by one or more specific users, please select choose their names from a multi-select list. |
Search Button | Use this button to perform Audit Trail Search. |
Results
The Audit Trail search results are presented displayed in a nested grid. The first top level contains provides only basic information about each found ( modified ) object found.
The summary row represents the last operation that was founddetected. If the an object was Addedadded, then modified, and at last Deleted, a finally deleted, the summary row will present display the Deleted status.
Additional An additional requirement for that kind this type of result is that all of the listed operations must match the selected filter like , such as date or user that has who performed the operation.
Results The results list will containinclude:
a A "View" action column that allows to allowing preview of the object in within the main object structure (given provided that the object still exists).
Object label (as configured in the system class settings)
Name of the user that who made the change
Data source indicating either manual input or import package
Dates of record modification and publish date of the Draftdraft
Operation
Insert (Add)
Update (Change)
Delete (Object was deleted and is not visible in the main archive, but it is still available in the versioning system)
The expanded view that is available after selecting Selecting Plus icon next to a summary row will reveal opens an expanded view revealing a detailed change-log:.
The change-log groups consolidates all changes made in within a given particular search frame to into a single object and it contains . It includes the same base fundamental information as the summary row , but extended by is expanded with object metadata.
If specific fields were selectedchosen, only these those fields are listed displayed for easier viewing. However, but other columns are still there present and can be accessed by using a header menu and columns sub-menu:
The base information columns remain locked, so that allowing for easy scrolling through a longer list of metadata columns can be easily scrolled without loosing without losing sight of the base information from sight.
| Tip |
|---|
Compare valuesValues for number fields might seem to be unchanged between modified records. This happens when a value change was below display precision for number fields, and the rounded value looks the same. A display precision can be changed by a system administrator and is typically set to two decimal places. |
| Tip |
|---|
Number of resultsA Total number of results is calculated based on actual "hits" and not a number of unique objects. For example, when 200 modifications were found for five objects, they will be displayed only as five summary rows. Other results remain hidden as change log.  |
