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

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
9 26-Nov-2021 10:22 1 KB khiggs to previous
8 26-Nov-2021 10:22 1 KB mmcfarland to previous | to last
7 26-Nov-2021 10:22 1 KB mmcfarland to previous | to last
6 26-Nov-2021 10:22 1 KB mmcfarland to previous | to last
5 26-Nov-2021 10:22 1 KB mmcfarland to previous | to last
4 26-Nov-2021 10:22 1 KB JEscott to previous | to last
3 26-Nov-2021 10:22 1 KB JEscott to previous | to last
2 26-Nov-2021 10:22 1 KB JMyers to previous | to last
1 26-Nov-2021 10:22 864 bytes JMyers to last

Page References

Incoming links Outgoing links
TR_UNSCHEDULED_TM
TR_UNSCHEDULED_TM

Version management

Difference between version and

At line 1 changed 3 lines
!!!UNSCHEDULED TM
!!Time Rule Overview
This time rule will apply the time code that is defined on the time rule, overriding any time code defined in the Target Time Code Set, if the time is not associated with a scheduled shift.
UNSCHEDULED TM
Time Rule Overview
This time rule will apply the time code that is defined on the rule over any time code defined in the Target Time Code Set if that time is not associated with a scheduled shift.
Additional Info
Frequency
predefined as ‘Never’
Implementation
The time rule should be set up in IDWR as shown below. See Chapter 3 - Time Rule Improvements for additional information regarding IDWR.
At line 5 changed 3 lines
!!Additional Info
* Frequency predefined as Never
* Must be used with Time Sheets generated with type "TS-Shift Pattern"
Band From To Value Day Time Code Premium Action Target Time Code Set Apply Time Code Set
0 No No No No Required No Replace Allowed No
At line 9 changed 13 lines
!!Implementation
The time rule should be set up in [IDWR] as shown below.
||[Cycle|CYCLE_NUMBER]||[Frequency|FREQUENCY]||[Seq|SEQUENCE]||[Time Rule Type|TIME_RULE_TYPE_TEXT]||[Band|QUALIFYING_BAND]||[From|FROM_CLOCK_TIME]||[To|TO_CLOCK_TIME]||[Value|VALUE]||[Day|DAY_OF_WEEK]||[Time Code|TIME_CODE_VALUE]||[Premium|PREMIUM_CODE]||[Target Time Code Set|TARGET_TIME_CODE_SET]|| [Apply Time Code Set|APPLY_TIME_CODE_SET]||[Action|TIME_RULE_ACTION]
| |Never|42| |No|No|No|No|No|Required|No|Allowed [1]|No|Replace
[1] The [Target Time Code Set |DTCS_ID_TARGET] is no longer mandatory, however it is strongly recommended to define this field due to the complexity of the time code engine applying layers during the time generation process. Example: The Target Time Code Set MUST be defined when special conditions are used with time exceptions.
----
![Notes|Edit:Internal.TR_UNSCHEDULED_TM]
[{InsertPage page='Internal.TR_UNSCHEDULED_TM' default='Click to create a new notes page'}]
The target time code set is no longer mandatory; however, it is strongly recommended due to the complexity of the time code applying layers during the time generation process. One example where the target time code set is required is when special conditions are used with time exceptions.
This page (revision-9) was last changed on 26-Nov-2021 10:22 by khiggsTop