- As the audit log table could be very large, it can be stored separately from the other data tables.
- The log database could be optimized separately for inserting records, as audit logging is primarily inserting records into the log.
- Separate backup or archive strategy for the audit log database.
- Optimal performance - The tracking feature does decrease performance. The speed impact on the solution largely depends on the back-end database the developer is using.
Once the database server has been decided, check the Log Server box and click the Create Log Table button. A table named 'log' will be created in the database server. Now audit logging is available for any table in the resources project (or on the application server for Servoy Server).
To log any changes or views for a table, do the following:
- open the table in the table editor
- select the
- Security tab, and select the desired group
- select the Explicit settings and enable the Tracking(Insert/Update/Delete) and/or Tracking(Select) option.
If Tracking(Insert/Update/Delete) option is enabled any adds, edits, or deletes to the table will be tracked for the selected group.
If Tracking(Select) is enabled any views of data to the table will be tracked for the selected group
Tracking views of data is HIPAA Security Rule compliant.
Using Audit Log Data
As the log table is simply another database table, a developer can builds build forms against the log table to allow users the ability to read and work with the data. Data within the audit log could also be used to access any changed record in the database.