Audit log origin

Updated by Victor Jespersen

Origin overview

This feature provides additional insight into where the action reviewed took place. For example, when reviewing a shift that’s been created, you’d be able to understand whether it was created in the manager portal or, in the mobile app.

The origin information is located in smaller text below the main value in the Action made by column of the view, as highlighted in the image below.

The table below contains an exhaustive list of the various origin values you may encounter as you browse your log search results, as well as the cases in which said values will display. The logic in the origin naming aims to support you in resolving disputes or issues concerning workforce planning and attendance and is as follows: 

  • In most cases, it reflects the Quinyx “platform” where the action got triggered, such as the Manager portal, Mobile, Webpunch, or Integration. 
  • However, suppose the action has been triggered by a specific feature that has cascading effects on other parts of Quinyx, such as changing an employee’s home unit or ending their employment, this will display as origin instead. 
Due to technical limitations, auto-assign and auto-schedule aren't currently available as origin values. Relevant Quinyx teams are currently actioning this to improve it in the medium term. 

Action

Origin

Case(s)

Creation

Via Manager portal

When a shift is created in Schedule within the manager portal.

Creation

Via base schedule rollout

When a shift is created in the schedule due to a base schedule rollout.

Creation

Due to absence

  1. When a shift is converted into an absence shift as a result of an absence being created on top of a shift. Note: This also applies to when an absence is added on top of part of a shift.
  2. When an absence is deleted and an absence shift is reinstated as a result. This applies regardless of which shift action out of delete/unassign/reassign was selected at absence creation.

Creation

Due to absence using absence schedule

When an absence is created using an absence schedule and, as a result, existing shift(s) in the Schedule are removed, and later the same absence is deleted, and the user chooses to reinstate the shifts, the shifts that were deleted when the absence was created are created anew, hence this origin.

Creation

Via Mobile

  1. Employee adding shift in Mobile
  2. Manager adding shift in Mobile

Creation

Via integration

When a shift is created using an integration, be it using our SOAP APIs or - in the future - REST APIs.

Regarding auto-schedule and auto-assign: Refer to the description above this table.

Update

Via Manager portal

When a shift is updated in the schedule within the manager portal.

Update

Via base schedule rollout

When a shift is updated in the schedule upon a base schedule re-rollout.

Update

Due to absence

  1. When an absence is created, and the selected shift action is unassigned or reassigned, Quinyx unassigns/reassigns the original shift. (Under the hood, Quinyx simultaneously creates a new shift for the absence shift.)
  2. When a part-time absence is created for an existing shift, and as a result, either then start or end time of said shift is updated.
  3. When a part-time absence is deleted and, as a result, the first part of the existing absence is extended to reflect the time of the initial shift. Example: 
    1. Initial shift 8 am-4 pm
    2. Absence is added 10 am-2 pm
    3. The absence is removed
    4. As a result, the end time of the 8 am-10am changes to 4 pm
  4. When the employee punches out early or late and selects an absence reason, which in turn converts the corresponding part of the shift to an absence and thereby changes the shift start or shift end time accordingly.

Update

Due to "Update shifts" feature

When a shift is updated as a result of the update shifts feature in Account settings or Group settings respectively.

Update

Due to employee deletion

When a shift is unassigned because an employee is deleted. Note that in this case, the State of salary type rules requiring approval property becomes null due to this.

Update

Via Mobile

  1. When an employee updates a shift in Mobile
  2. When a manager updates shift in Mobile

Update

Due to agreement selection logic

When the agreement of the shift is updated as per any of the cases where Quinyx applies its agreement selection logic (as described here).

Update

Due to end of employment

When a shift is unassigned due to the assignee's end of employment date being changed to before said shift’s start date. 

Update

Due to change of home unit

When the home unit of an employee is changed, which means the following changes are triggered as a result by the system:

  1. The employee's future scheduled shifts are unassigned (but remain on the same unit)

Update

Due to agreement deletion

When the agreement used for a given shift is deleted.

Update

Due to shift unassignment approval / Via Manager portal

When the shift property employee is changed due to a shift unassignment request being approved.

Note that specifically for log actions prior to March 20, 2024, the copy “Via Manager portal” is used due to technical constraints.

Update

Due to shift booking approval / Due to shift booking request

When the shift property employee is changed due to a shift booking being approved.

Note that specifically for log actions prior to March 20, 2024, the copy “Due to shift booking request” is used due to technical constraints.

Update

Due to shift assignment on away unit approval / Due to booking request

When the shift property employee is changed due to a home unit manager approving the request of an away unit manager to assign an employee.

Note that specifically for log actions prior to March 20, 2024, the copy “Due to booking request” is used due to technical constraints.

Update

Due to shift swap approval / Due to shift swap request

When the shift property employee is changed due to a shift swap being approved by the manager.

Note that specifically for log actions prior to March 20, 2024, the copy “Due to shift swap request” is used due to technical constraints.

Update

Due to re-calculated salary outcome

When a salary calculation is triggered by some actions in the schedule, leading to a shift’s State of salary types requiring approval being updated to Unapproved.

One example of an action in schedule that can trigger the salary re-calculation is opening the time card in schedule. Note that this only triggers the calculation being run, the actual cause for the change will rather be due to a change in the factors configured in Quinyx to affect the employee’s salary output.

Update

Via integration

When a shift is updated using an integration, be it using our SOAP APIs or - in the future - REST APIs.

Regarding auto-schedule and auto-assign: Refer to the description above this table.

Deletion

Via Manager portal

When a manager deletes a shift in the Schedule in the manager portal.

Deletion

Via base schedule rollout

When a shift is deleted in the Schedule upon a base schedule re-rollout.

Deletion

Via Mobile

When a manager deletes a shift in Mobile.

Deletion

Due to absence

When a shift is deleted due to an absence being added. Note that this happens in the following cases:

  1. When an absence is created and shift action is deleted.
  2. When an absence is created using an absence schedule where the absence schedule is configured to replace "scheduled days" or "all days", meaning some of the existing shifts in the schedule are deleted as a result of said absence creation.
  3. When a part-time absence is deleted, and the absence shift (that was created by Quinyx in the background specifically to ensure that said part-time absence contained an absence shift) is removed from the system as a result.

Deletion

Via integration

When a shift is deleted using an integration, be it using our SOAP APIs or - in the future - REST APIs.

Regarding auto-schedule and auto-assign: Refer to the description above this table.

 

Currently, origin will display for the actions relating to the “shift” item type. You can expect origin information to be released for the remaining item types during the coming months.

Note that we’re currently working on adding “Via Webpunch” for updates of shifts that occur as a result of an employee adding an unplanned task using Webpunch.

How Did We Do?