Auditing is stored in the qp_auditing database, in the events table. This table contains the following columns:
• id (integer)
• event_date_time (timestamp without time zone)
• category (text) - example: login
• old_value (text)
• new_value (text)
• principal (text) - Describes the User in the local custom fashion.
• remote_host (text)
• server_host (text)
• origin_code (text) - The source code location for the place where the action of the event audited is taking place.
• entity_name (text)
• entity_id (text) - For example the Branch Id.
• description (text) - May only be null if either of the columns old_value or new_value have content. Example “A failed login attempt occurred.”
For CREATE events, old_value is stored as null and new_value is stored as a shallow JSON string of the created object.
For UPDATE events, old_value contains the detected updated parameters with the value before the change and new_value is stored as a shallow JSON string of the updated object.
For DELETE events, the old value is a shallow JSON string of the deleted object and the new_value is stored as null.
A shallow JSON string means that referenced objects will be presented as a list of id:s.
Calendar
Auditing is stored in the database qp_calendar, in the calendar_audit table. This table contains the following columns:
• id (bigint)
• branch_id (bigint)
• change (text)
• entity_id (bigint)
• entity_type (character varying, 255)
• audit_operation (character varying, 255)
• time_stamp (character varying, 255)
• user_name (character varying, 255) - the name of the logged in User. QP_PUBLIC means that no User was logged in when the event took place.