Audit logs - Absences

Updated by Leigh Hutchens

Audit logs are records of past actions within Quinyx. There are two types of absence-related audit logs that can be extracted from Quinyx: 

  1. Absence request audit logs
  2. Absence audit logs (this page)

They provide a transparent history of who performed an action on an absence, what the action was, when it occurred, and so on. This functionality helps managers:

  • Resolve disputes or questions related to absences.
  • Access historical activity data for self-service insights into team management.
  • Derive key information for workforce planning and unit-level analysis.
This page focuses only on the audit logs for absences. To see details about audit logs for absence requests, click here.

Absence audit logs

For absences, audit logs provide a clear history of actions and can help answer questions such as (not limited to):

• When was the absence created?

• Attestation data for the absence

• Absence rate applicable for the absence

• Scheduled shifts impacted by the absence and what was the impact (deleted, keep shift, unassign, etc.).

• What comments were added; by the employee and/or manager

To see the audit logs for absences, navigate to:

Audit logs > Adjust view > [Item type] Absence.

The "Adjust view" panel allows you to refine your search for audit logs using the following filters:

Filter

Description

Example

Groups

This tree allows you to select groups for which Quinyx fetches audit logs. 

  • It contains a free text field that helps find groups. 
  • The tree is collapsed by default & can be expanded.
  • Selecting a group automatically includes its child groups, though these can be deselected.

Item Type

  • You can select the specific items for which Quinyx should fetch logs using this field. This is a mandatory field. 
  • Select ‘Absence’ in this field. 

Item start/ end date

  • These dates define the start and end of the period in which the items you are searching for begin.
  • They are optional fields.
  • The maximum period you’re able to specify is three months.
  • The search carried out considers the business daybreak of the group the item takes place on.

Type of action

  • Use this field to filter the logs by the possible actions associated with an item.
  • Currently, you're able to perform any, several, or all of the following action for absence requests:
    • Created
    • Deleted
    • Updated
  • The field will read "All" by default, meaning that logs for all of the above-listed actions will be fetched by Quinyx.

Action Start/end date

  • These date fields allow you to set the start and end date of the period within which the action on the item you're looking for was carried out in Quinyx.
  • This is a mandatory field and by default, the "Action start date" is set to three months prior to the current date, while the "Action end date" is set to today's date.
  • These are always in the same time zone as the group currently selected in the group selector of the top bar.

Action made by

  • This field can be used to filter out items to display based on which user has carried out an action. 
  • The default value of the field will be “All” text, meaning all managers/employees (as defined above) are included in the search by default. The dropdown values will be sorted alphanumerically.
  • The field is searchable via a text field. 
  • If an integration caused the action, the displayed data depends on the Quinyx API used:
    • REST Web Services: The integration credentials' name or UUID.
    • SOAP Web Services: "SOAP."

Action made for

  • This field can be used to filter out items to display based on which user has been impacted by an action in Quinyx. 
  • This field allows you to search for any user with an employee role in the group(s) selected. This means that editing your selections in the group's tree after populating the Action made for the field will reset the field.
  • Each employee in the field’s drop-down will display as per the following format: [first name] [last name] [badge number]
  • You may search for a specific employee by typing their name(s) or badge number and/or by scrolling the list that adapts to what you’ve typed. The employees in the list are sorted alphabetically.
  • The default value is “All” meaning that if you leave this field blank when clicking “Apply” in the Adjust view panel, log results will show for all employees in that group. 

Interpreting absence audit logs: A guide to understanding results

Once you've applied the filters in the adjust view panel, you will see the audit logs page displaying your results and you can see details such as what action was done, who did it, date and time of the action, etc. 

Column Header

Explanation

Time stamp

  • This column shows the date and time of actions in Quinyx. You can sort by timestamp (newest to oldest by default). 
  • Dates and times follow Quinyx language settings and are displayed in the time zone of the selected group.

Groups affected

Displays the units and sections affected by the item.

Item type

Displays the type of item affected by a given action.

Item

Displays information to help identify which absence has been actioned and the actions made.

This will always show the latest state of that item   aligned with the schedule view i.e. the date and time, absence type of that item. 

Action

Identifies the type of action carried out.

Action made by

Identifies who performed the action. Shows their [first name] [last name] ([badge number]).

If the employee was deleted, it displays "Employee has been deleted from Quinyx." The reason for this is that the system no longer holds that information.

Action made for

Identifies who was affected by the action. The person carrying out the action is indicated as: [first name] [last name] ([badge number]).

If the affected person has been deleted, it displays "Employee has been deleted from Quinyx." The reason for this is that the system no longer holds that information.

Trail

(!) This feature is currently under development for absence item types.

Property table

Most absence items (based on the action) have more details inside a sub-table called the property table, accessed by clicking the chevron on the leftmost column of the main table.


How Did We Do?