This page (revision-31) was last changed on 26-Nov-2021 10:22 by mmcfarland

This page was created on 26-Nov-2021 10:22 by JMyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
31 26-Nov-2021 10:22 3 KB mmcfarland to previous
30 26-Nov-2021 10:22 3 KB mmcfarland to previous | to last
29 26-Nov-2021 10:22 3 KB mmcfarland to previous | to last
28 26-Nov-2021 10:22 3 KB mmcfarland to previous | to last
27 26-Nov-2021 10:22 3 KB mmcfarland to previous | to last
26 26-Nov-2021 10:22 3 KB mmcfarland to previous | to last
25 26-Nov-2021 10:22 3 KB mmcfarland to previous | to last
24 26-Nov-2021 10:22 3 KB mmcfarland to previous | to last
23 26-Nov-2021 10:22 3 KB mmcfarland to previous | to last
22 26-Nov-2021 10:22 3 KB mmcfarland to previous | to last
21 26-Nov-2021 10:22 3 KB mmcfarland to previous | to last

Page References

Incoming links Outgoing links
TR_OT_CONSECUTIVE
TR_OT_CONSECUTIVE

Version management

Difference between version and

At line 18 added one line
At line 22 added one line
This time code set must include Regular and the Consecutive OT Time Codes. If no time code sets are defined, the rule will target all work rule time codes that have the [CONSECUTIVE OT|CONSECUTIVE_OT_ELIGIBLE] toggle checked.
At line 22 removed 3 lines
*The [Value|TIME_RULE_VALUE] field will no longer be used to hold the day of the week, instead the day of the week has been turned into a column labeled DAY. The OT CONSECUTIVE time rule has been updated to handle this new feature.
*This rule has been modified to look at the new time code sets when specified. This time code set needs to include Regular and the Consecutive OT Time Codes. If no set is defined it will target all work rule time codes that have the [CONSECUTIVE OT|CONSECUTIVE_OT_ELIGIBLE] toggle checked.
This page (revision-31) was last changed on 26-Nov-2021 10:22 by mmcfarlandTop