!!Basic Configurations of a Time Rule *[Frequency|FREQUENCY] **Describes how and when the time rule is used by the system **Existing frequencies are: ***Never - used by the system or other time rules ****Used to default in values into a time sheet when the time sheet is generated ***Every - called by the time rule engine after changes are saved to a time sheet ****Entry ****Shift ****Day ****Week ****Period *[Band|QUALIFYING_BAND] **Used as a threshold, for example used to hold a minimum number of hours before the employee qualifies for overtime. *[Value|TIME_RULE_VALUE] **May be used as a variable or fixed amount **The context in which this column is used may change depending on the time rule type ***For example, for the time rule [Daily Top Up|TR_DAILY_TOP_UP], the column name for Value changes to Max Top Up Hrs since it holds the number of hours to top up to. The time rule, [OT Consecutive|TR_OT_CONSECUTIVE], uses the Value to hold the number of consecutive days worked. *[Day Of Week |DAY_OF_WEEK] **Allows for filtering of Daily and Never time rules **Allows for definition of first day of week for weekly time rules *[From|FROM_CLOCK_TIME] /[To|TO_CLOCK_TIME] times **Allows for filtering of Daily and Never time rules *[Time Code|TIME_CODE]/[Premium |PREMIUM_CODE] **Most time rules use these to put the qualifying time into them **Some time rules use them as a filter *[Action|TIME_RULE_ACTION] **Tells the Time Rule Engine how to apply to the time rule ***Add or Replace *[Targeted Time Code Sets |DTCS_ID_TARGET] **Determines what types of time (set of time codes) should qualify for the rule **Replaces the use of the toggles for the time codes listed on the Time Code tab in [IDWR] *[Disabled |DISABLE_RULE] **Can be used to help debug time rules *[Trace|TRACE_LEVEL] **Controls the level of messaging that the server logs in the OC4J default log file **6-Internal Level is more than enough **[IMST] server trace might also need to be switched on for added tracing *Banding Time Rules **Rules of the same type can be combined to complement one another **Must share the same targeted/apply to time code set, start/end times and day of the week **Only rules that use the band as a threshold can support this **Most commonly used for [OT DAILY|TR_OT_DAILY] and [OT WEEKLY|TR_OT_WEEKLY] **For example: [OT DAILY|TR_OT_DAILY] is banded twice; first band is for 8 hours where the employee would receive OT 1.5 for hours worked after 8 hr reg time, the second band is for 12 hours where the employee would receive OT 2.0 for hours worked after 12 hrs reg time. !!Advanced Configurations of a Time Rule The following list of optional configurations allows the administrator to make a time rule more powerful and advanced. *[Apply Time Code Sets|DTCS_ID_APPLY] **Usually a subset of the [Targeted Time Code Set|DTCS_ID_TARGET] **Most commonly used in Daily or Weekly time rules **For example: Vacation time may contribute as hours towards [OT WEEKLY|TR_OT_WEEKLY] but may not be paid out as Overtime. The [OT WEEKLY|TR_OT_WEEKLY] would 'target' the vacation hours in the [Target Time Code Set|DTCS_ID_TARGET], but would exclude the vacation time code from its [Apply Time Code Set|DTCS_ID_APPLY] *[Can Be Waived|CAN_BE_WAIVED] **Allows the user to flag that a time rule should not be applied **Allows the user to turn on a currently disable time rule *[Time Rule Sequence|PROCESSING_SEQUENCE] **Used when the default ordering is not getting the desired results **Used to change the order of time rules within the same frequency **Most common when layering the same time code types *Specifying the [Cycle|CYCLE_NUMBER] **Standard cycle is every Entry > Shift > Day > Week > Period **The default cycle is 5 **May be used to change the order of time rules of different frequencies. ***For example, override the cycle of OT Weekly to be 1 so that it will come before OT Daily