Examples

These examples describe the processing for scenarios where the FORCE_CLOCK_ON_DAY parameter is FALSE.

Example 1: Directionless clock is within DIRLESS_PROXIMITY

This example includes this scenario:

  • On February 9, the employee is scheduled from 8:00AM (08:00) - 4:00PM (16:00).
  • On February 10, the employee is scheduled from 9:00AM (09:00) - 5:00PM (17:00).
  • On February 11, the employee is scheduled from 8:00AM (08:00) - 4:00PM (16:00).
  • The DIRLESS_CLOCK_OFFSET value is 0.
  • The DIRLESS_PROXIMITY value is 300.

These steps describe the process:

  1. The processing of a directionless clock punch for February 10 at 8:00AM (08:00) is started.
  2. February 10 is checked to determine if the clock is within the scheduled time.
    1. Because it is not, the system determines if it is within the DIRLESS_PROXIMITY of the schedule.
    2. This calculation is performed: |08:00 - 09:00| = 60 minutes, which is < 300 minutes. The score for this day is 60.
  3. February 9 is checked to determine if the clock is within the scheduled time.
    1. Because it is not, the system determines if it is within the DIRLESS_PROXIMITY of the schedule.
    2. This calculation is performed: |08:00 - 08:00 + 24 hours| = 1440 minutes which is > 300.
  4. February 11 is checked to determine if the clock is within the scheduled time.
    1. Because it is not, the system determines if it is within the DIRLESS_PROXIMITY of the schedule.
    2. This calculation is performed: |08:00 - 08:00 - 24 hours| = 1440 minutes, which is > 300.
  5. Because February 10 has the lowest positive difference, the clock is placed on the February 10 work summary.

Example 2: Directionless clock is not within DIRLESS_PROXIMITY

This example includes this scenario:

  • On February 9, the employee is scheduled from 8:00AM (08:00) - 4:00PM (16:00).
  • On February 10, the employee is scheduled OFF.
  • On February 11, the employee is scheduled from 8:00AM (08:00) - 4:00PM (16:00).
  • The DIRLESS_CLOCK_OFFSET value is 0.
  • The DIRLESS_PROXIMITY value is 300.
  • The CLOCKING_DAY_START value is 00:00.

These steps describe this process:

  1. The processing of a directionless clock punch for February 10 at 8:00AM (08:00) is started.
  2. February 10 is checked and no schedule is found.
  3. February 9 is checked to determine if the clock is within the scheduled time.
    1. Because it is not, the system determines if it is within the DIRLESS_PROXIMITY of the schedule.
    2. This calculation is performed: |08:00 - 08:00 + 24 hours| = 1440 minutes, which is > 300.
  4. February 11 is checked to determine if the clock is within the scheduled time.
    1. Because it is not, the system determines if it is within the DIRLESS_PROXIMITY of the schedule.
    2. This calculation is performed: |08:00 - 08:00 - 24 hours| = 1440 minutes, which is > 300.
  5. The clock is placed based on the CLOCKING_DAY_START time. This is the same processing as when the FORCE_CLOCK_ON_DAY parameter value is TRUE.
  6. Because the CLOCKING_DAY_START value is between 00:00 and 11:59 and the clock time is later, the clock is associated with the day that the clock came in, which is February 10.