It is possible to associate an attendance reason with clockings by checking the "Visible in clockings" option within the selected reason.

When the employee clocks in with a specific reason, it will appear in the time slots and in the details of the day the clocking was made (instead of the reason configured in the attendance model).

Functionality in clockings

If one or more attendance reasons are flagged to be associated with clockings, a menu will appear when clicking the new virtual clocking button for choosing the relevant reason.

The "Entry" element is automatically added and represents the clocking without any reason.

At this point, the employee will have the ability to enter multiple consecutive clock-ins to indicate the start of the activity corresponding to that reason. For example: an entry clocking without a reason at 9:00 and an entry clocking with a business trip reason at 11:00 to indicate that the business trip started at that hour. In this case, from 9:00 to 11:00 the regular attendance will be attributed, and from 11:00 onward the business trip.

Of course, if only one activity is performed during the day, a single clocking with the relevant reason will be sufficient. For example: an entry clocking with a business trip reason at 9:00 if the employee was on business trip all day, or an entry clocking without a reason at 9:00 if the employee was in the office all day. In this case, only the reasons related to the executed clocking will be attributed (or regular attendance if there was no reason in the clocking).

The clock-out works as usual and interrupts any attendance reason (regardless of whether it was associated with a clocking with a reason or not).

If no attendance reason has the option "Visible in clockings" checked (or if for that employee no reasons are available in case they don't meet the criteria of the "Available for: Only employees who meet the criteria of the selected filter" option), the new virtual clocking button works as usual (i.e., with a direct click, no sub-menu).

Setting in clockings

When attendance reasons are activated for clockings in a company, it is necessary to also add the reasons field in the clocking entity to all the views of the clocking entity.

Typically, the clocking views used in the backoffice are:

• Subview of the table mask of the clocking entity inside the attendance edit: remember to set the permissions for the new field so that it is editable only in the "non-processed" and "anomaly" status.
• List view of clockings in the clocking section.
• Mask view of clockings in the clocking section.

Functionality in the processing of clockings

When the "clockings" of a day are processed and are associated with one or more "clockings with reasons", the attendance slots will be created following the same rules (rounding, allowances, application of requests, etc.) that are applied "normally", that is, as if the day were associated with clockings without reasons, except for some aspects:

• Consecutive clockings in the same direction are allowed as long as they are associated with different reasons (or no reason).
• As the last operation in processing, the reasons associated with the clockings will overwrite the attendance slots already created based on the clocking times. 
  N.B. Attendance slots are overwritten even if they were generated by approved attendance requests.
• The slots of the day thus converted will be applied, maintaining the same percentage if the sum of the details is not equal to that of the slots (for example, due to rounding applied directly to the details), to the details of that day.