This is version 1 2 3 4 5 6 7 8 9 10 11 . It is not the current version, and thus it cannot be edited.

Back to current versionRestore this version

Time Rule Improvements#

Time Rule Overview#

Our intent is to improve the flexibility and ease of the set up required for Time Rules.

Requirements / Features #

• The Time Rule Frequency indicates how often a particular time rule will be processed by the time rule engine. These frequencies are pre-defined for each time rule supplied with Wiki.
• The Time Rules Tab on IDWR has been modified to show the Time Rule Frequency along with the override sequence.
• When a time rule has been entered in IDWR the frequency will default in. Users will not have to manually update the current time rules in IDWR, the frequency will automatically be brought in.
• Frequencies which have been implemented are:
  • Every Entry
  • Every Shift
  • Every Day
  • Every Week
  • Once for Period
  • Never (informational only)

Frequency Sequence#

• Time Rules that share the same frequency can now be sequenced to process in a specified order by the clients.
• If no sequence is supplied it will be given a default sequence of 999999

Disable Option#

• Time Rules can now be disabled rather than the user having to remove the time rule from IDWR. Once a time rule has been disabled, it will not be processed by the time rules engine.

Day of the Week Column#

• Day of the week has been turned into a column on the time rules table. The new column is labeled DAY. The Value field will no longer be used to hold the day of the week.
• New lexicon values for Weekdays and Weekends that will apply the rule according if it is the week day or a weekend

Waive Time Rules#

• A new toggle has been added to Time Rules to signify that the rule can be waived for the employee. This toggle can be found in IDWR under Time Rules, the toggle is called "Can Be Waived".
• Once this has been turned on for a time rule, the waive time rule option is then made available to the data entry clerk in DTEDC for any employee who has that time rule associated to them via their work rule.

2sc Iteration features: #

New Time Rule Logic#

• Rules like Call In and Min Hours worked will look at the shift totals not the total hours worked in a day
• A shift is determined by the total time between worked time slots. The value is hard coded to 2 hours currently but can be turned into a time rule if the value needs to be variable

New Cycle Column#

• Allow us to process Time Rules in cycles. In this way we can process OT Weekly before OT Daily and so on.
• We support maximum 10 cycles.
• If the cycle is not defined by default it is the cycle number 5
• We not support cycles for Never frequency
• Since we implement cycles every record frequency rules are not fire any more after each other frequency time rules applies. The costumer can decided when they need every record frequency to fire using cycles.

New Apply Time Code Set Column#

• It is optional and this should be defined when there are any time codes in a target time code set that should be exclude when we apply the rule. In other words this time codes should be contribute to the rule but should not be changed when the rule is apply
• For example work holiday is pay double time. This time should be contribute to the number of hours worked to qualify for OT Weekly(that apply 1.5) but should not be replace by 1.5 time code

New Special Condition (User define Time Rules) with Time Exception support From/To/Day #

• These are applied before any other rules apply and just before the default time code applies(in the processor)
• This feature is not suitable for dialogs(W%TTS)
• Start of the day it is determines base on the min Start Time of Time Exceptions in a day. This probably should be changed in the future… It is working fine for Ad hoc Time Exception used for GES and PXP

Instance of the time rule#

• An new instance of the time rule is created for the same time rule type base of a unique combination of Cycle, Target Time Code Set, From and Day.