Hello @Snowdeveloper03 ,
The check-in/check-out process is managed through the use of the “Check-in/out reminder”-scheduled job. The job uses the following properties: “sn_wsd_rsv.time_before_check_in_out_reminder” and “sn_wsd_rsv.time_when_reservation_cancelled_without_check_in”.
- Ensure check-in is required on the module or space level
- This can be enforced through the reservable module (set “Override check-in policy” on the reservable module to “always require check-in”)
- This can be managed by the space itself (space is indicated as check-in required, set “Override check-in policy” on the reservable module to “no override”)
- On the reservation, the check-in state must be set to “awaiting_check_in” (this is done if a check-in is required as set on module or space level, the previous step)
- Reservations are only being cancelled when “Cancel reservations exceeding check-in time” is set to true on the reservable module (system property)
- The “Check-in/out reminder”-scheduled job runs every 30 minutes (OOB) and it finds all reservations that require check-in or check-out, and validate the next action.
Check-out is not enforeced. The daily task job (Reservation daily tasks) will mark the check-in state of a reservation based if the employee checked out or not.
Only if a reservation is checked out before the end time of the reservation, the time is adjusted. Checking-in out after the end time will not impact the reservation. It will only update the check-in state in that case.
Kind regards,
Arvid
