(no) Audit Trail
- Maciej Zabielski
- Martin SWG (Unlicensed)
Translation needed
The content of this page was copied from another page tree and needs to be translated or updated.
When you finish translation, make sure to
-
Replace the label NEEDS-TRANSLATING with TRANSLATED
-
Remove this macro from the page
SINCE 3.2.0
Introduction
Audit Trail function allows users to track changes in objects or documents.
This functionality is available in conjunction with (no) Versjonshåndtering. To achieve full traceability, a Strict versioning mode must be used.
As a result, no changes can be made in the master archive without going 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 to date:
|
From / To | Date fields containing any valid date. | A date range when the objects were modified or published. A date can be specified between any time in the past up to now. |
Last |
| A convinience functions to set date range automatically to last day, week, month or year. Using this function will overwrite values set in From / To fields.
|
Search Class | Use class picker to select one of object classes available in the system. | Since Audit Trail presents changes in object metadata, it will use a schema dedicated to specific object class. The search must be narrowed to 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, that in that case a full metadata schema will be displayed that can make reading the results a bit hard 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 specific fields modified will be presented. |
Modified by | Select one or more users from a multi-select list. | When nothing is selected, records modified by any user will be taken into account. IF you are interested in records modified by one or more specific users, please select their names from a multi-select list. |
Search Button |
| Use this button to perform Audit Trail Search. |
Results
Audit Trail search results are presented in a nested grid. The first level contains only basic information about each found (modified) object.
The summary row represents the last operation that was found. If the object was Added, modified and at last Deleted, a summary row will present Deleted status.
Additional requirement for that kind of result is that all of the listed operations match selected filter like date or user that has performed the operation.
Results list will contain
a "View" action column that allows to preview the object in the main object structure (given that the object still exists).
Object label (as configured in the system class settings)
Name of the user that made the change
Data source indicating either manual input or import package
Dates of record modification and publish date of the Draft
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 Plus icon next to summary row will reveal a detailed change-log:
The change-log groups all changes made in a given search frame to a single object and it contains the same base information as the summary row, but extended by object metadata.
If specific fields were selected, only these fields are listed for easier viewing, but other columns are still there and can be accessed by using a header menu and columns sub menu:
The base information columns remain locked, so that a longer list of metadata columns can be easily scrolled without loosing base information from sight.
Compare values
Values 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.
Number of results
A 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.