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

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

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
8 26-Nov-2021 10:22 1 KB mmcfarland to previous
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 mmcfarland to previous | to last
3 26-Nov-2021 10:22 1 KB mmcfarland to previous | to last
2 26-Nov-2021 10:22 1 KB mmcfarland to previous | to last
1 26-Nov-2021 10:22 1 KB mmcfarland to last

Page References

Incoming links Outgoing links
TR_OFF_DAY_LATENT_SHIFT
TR_OFF_DAY_LATENT_SHIFT

Version management

Difference between version and

At line 3 changed one line
This time rule is not really a time rule, but a shift set up on the [IDWC] form, to generate time only if an employee shows up at work on a scheduled day off. \\
This time rule is not really a time rule, but a shift set up on the [IDWC] form, to generate time only if an employee shows up at work on a scheduled day off, with the time required for the day. \\
At line 7 changed one line
NOTE: A clock punch exception is generated only when the IN/OUT clock punches are paired. \\
NOTE: A clock punch exception is generated only when the IN/OUT clock punches are paired. This type of shift __will not generate time until there is at least one clock punch for a shift.__
At line 9 removed one line
__This type of shift will not generate time until there is at least one clock punch for a shift.__
At line 11 removed one line
At line 17 added 2 lines
__Development Approach__ \\
* Create a new scheduled shift status (X_SCHEDULED_SHIFT_STATUS) named Latent. This will be used when the scheduled shift is created for the shift defined on IDWC on a day off.
At line 24 changed 2 lines
* __For each scheduled day off, a shift should be defined in the Assigned To field on IDWC.__
* __If the time needs to be generated under another time code, this can also be defined on IDWC.__
* For each scheduled day off, a shift should be defined in the Assigned To field.
* If the time needs to be generated under another time code, this could also be defined on the IDWC form.
At line 28 removed 7 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| | | | | | | | | | | |
__Development Approach__ \\
* Create a new scheduled shift status (X_SCHEDULED_SHIFT_STATUS) named Latent. This will be used when the scheduled shift is created for the shift defined on IDWC on a day off.
This page (revision-8) was last changed on 26-Nov-2021 10:22 by mmcfarlandTop