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 3 changed 2 lines
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.
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.
At line 6 changed 4 lines
* Frequency predefined as Never
* Must be used with Time Sheets generated with type "TS-Shift Pattern"
[Frequency |FREQUENCY]
*predefined as ‘Never’
At line 11 changed one line
The time rule should be set up in [IDWR] as shown below.
The time rule should be set up in [IDWR] as shown below. See [Time Rule Improvements|TIME_RULE_IMPROVEMENTS] for additional information regarding [IDWR].
At line 13 changed 2 lines
||[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
||[Band|QUALIFYING_BAND]||[From|FROM_CLOCK_TIME]||[To|TO_CLOCK_TIME] ||[Value|TIME_RULE_VALUE]||[Day Of Week |DAY_OF_WEEK]||[Time Code|TIME_CODE]||[Premium |PREMIUM_CODE]||[Action|TIME_RULE_ACTION]||[Targeted Time Code Sets |DTCS_ID_TARGET]||[Apply Time Code Sets|DTCS_ID_APPLY]
|0|No|No|No|No|Required|No|Replace|Allowed|No
At line 16 changed one line
[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.
The [Targeted Time Code Set |DTCS_ID_TARGET] 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 [Targeted Time Code Set |DTCS_ID_TARGET] 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