Daylight Saving Rule

Overview

The Daylight Saving Rule is applied on days where the server applies a Daylight Saving Time (DST) transition. The rule applies the final schedule of the employee on the transition day to their native time zone and then simulates the application of reader-based clocks to that schedule. Any difference between the regular and simulated schedule is compensated with premiums. Multiple premiums for compensation are created where differences exist. Discrepancies at the same rate are combined into a single premium.

The rule works as follows:

  • When the Daylight Saving Rule cannot safely apply a schedule to the native time zone that is specified for the simulation, then the rule does not apply changes and does not create premiums. Then the rule unauthorizes the work summary and displays a message stating that the Daylight Saving Rule has highlighted this day for manual inspection.
  • In the preceding case, if the authorization status has been set manually by a user in the work summary, then the rule does not take effect and the work summary remains authorized.
  • The rule does not take action if clock overrides exist on the timesheet.
  • The rule takes effect on the day of a DST transition, the day before the transition, and the day after the transition. These days are included in the rule to ensure that compensation is applied appropriately for over-midnight cases and other scenarios. The rule does not affect the other days of the year.
  • The Daylight Saving Rule also supports the Pay Representation parameter. This parameter provides these options:
    • Rates: The premiums are paid out based on the differences of minutes that are allocated to individual rates and the REG hour type. This option is the default.
    • Hour Types: The premiums are paid out based on the differences of minutes that are allocated to individual hour types, using those hour types and a rate of 0 (zero).

The rule has these restrictions:

  • Rules cannot be used in conjunction with the DST Rule if the rules do both of these actions:
    • Run at the “After LTA Overrides Applied” or “Rounding Clocks” execution points.
    • Modify the start, end, duration, or rate of any work detail, schedule detail, or clock.
  • The rule does not support the following registry configurations:
    • /system/WORKBRAIN_PARAMETERS/APPLYTODETAILS_MAKE_ONE_BIG_UAT = true
    • /system/WORKBRAIN_PARAMETERS/LTA_RUN_LOCATION = 'AFTER CLOCKS'
  • The rule must be configured to run at the "AFTER CLOCKS APPLIED" execution point.
  • The rule will not take effect when clock overrides are present.