Introduction:
In FBO One, every modification is recorded in the audit log. This log serves as a comprehensive record of all changes made within the system, allowing administrators to review and track the specifics of each alteration and its corresponding timestamp. The audit log serves multiple purposes, including aiding in recovery from any undesirable consequences resulting from a change and providing an opportunity for knowledge enhancement and understanding for the person responsible for the modification.
Audit Log for settings:
To access the logs pertaining to changes made in the Administration settings, you have two options.
- First, you can utilize the 'View log' link available within the individual setting record.
- This allows you to directly access the log specific to that particular setting, providing detailed insights into the changes made and their timestamps.
- Alternatively, you can utilize the 'View log' link located in the header of a table to see all changes.
- This log includes deleted records.
Here is an example of the audit log for an individual setting.
Audit Log For Orders:
To see who made changes to an order, use the Audit Log Icon in the Handling header or the breadcrumbs to open the dropdown menu options as shown below.
The Audit Log will open within the Order frame as shown below. Checking the 'Include system changes (calculations)' will increase the log detail to include system price calculation relating to any change made in the Order. Select the "X" to close the log and return to the Order.
Accessing the Audit Log for an individual Product or Service can be accessed by selecting the line item and 'Audit log' in the drop-down.
Audit Log For Registrations and Organisations:
It is also possible to see changes made to an aircraft or organization record by using the Log tab in the record. The example below is the log for aircraft registration N12345.
There is also an option to run an Audit report available from the Reports tab.
Audit Log storage times:
NOTE: The Audit Log is only retrievable for a limited period of time. This ensures that the storage of data does not slow down the system. Once this pre-defined period is surpassed, audit changes can no longer be found.
The number of days for which the audit log is stored can be found under Application Settings > AuditLogExpirationDays. The maximum recommended value for this setting is 180-days.
Audit Log reporting:
Reporting on Audit changes is also possible by running an 'Audit' report. The report contains all changes made in FBO One over the selected period.
- Given the potential size for this report, it is recommended to run the report for short periods so that the report generates in a reasonable amount of time.
- It is also possible to filter the report by User or by Table (e.g. audit changes made only to Orders, Aircraft Types, Contacts etc.).
In the below example, audit changes to 'Orders' but only those made by the 'Accounting' User Account are being requested for the given period.
Comments
0 comments
Please sign in to leave a comment.