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

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

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

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 5 changed one line
This rule will create offset records if the time is less than the value defined on the time rule band. Any gap in time will reset the calculation. This rule will solve the need where employees are not entitled to any compensation for periods of overtime of less than X min per day. This rule works in conjunction with TOP UP AFT GAP.
A negative entry for the value of the transaction entered is created in the Time Code Sets. This rule will create offset records if the time is less than the value defined on the time rule band. Any gap in time will reset the calculation. This rule will solve the need where employees are not entitled to any compensation for periods of overtime of less than X min per day. This rule works in conjunction with TOP UP AFT GAP.
At line 7 added one line
%%information Note that with this type of off set transactions, the 'From and 'To' times will match the entered times. The limit on the number of minutes that a transaction was produced up to is provided in the Band field. This time rule works with the time prior to the time used in the Time Rule TOP UP AFT GAP.%%
At line 8 changed 2 lines
Note:\\
In case the time codes that are offset by this rule, are also used by other time rules, it is recommended that this rule be the last one to fire (change the order using sequence and/or cycle) so the offset records will not have any impact on other time rule calculations.
%%information In case the time codes that are offset by this rule, are also used by other time rules, it is recommended that this rule be the last one to fire (change the order using sequence and/or cycle) so the offset records will not have any impact on other time rule calculations.%%
At line 11 changed 2 lines
The Apply Time Code Set needs to be defined only when not allof the records that contribute to the calculation should be offset
*e.g. Travel time should not be offset, so "target" will contain Travel and OT time codes and "apply" will contain only OT time codes
The Apply Time Code Set needs to be defined only when not all of the records that contribute to the calculation should be offset.
*e.g. Travel time should not be offset, so "target" will contain Travel and OT time codes and "apply" will contain only OT time codes.
At line 14 removed 4 lines
At line 22 removed one line
At line 27 removed one line
At line 30 changed 4 lines
[{InsertPage page='Internal.TR_OFFSET_BFR_GAP' default='Click to create a new discussion page'}]
}]
[{InsertPage page='Internal.TR_OFFSET_BFR_GAP' default='Click to create a new notes page'}]