The PostProcessEventRuleset operands are used to add a “Post Process” event to a person’s timecard after the person clocks out, adding extra time to the day. For example, an employee may receive bonus hours at the end of the day after working a minimum number of hours. Or, an employee may receive additional time after clocking out to account for time needed to clean up before going home. See Post Process Event for more information.
Post Process Event Rules are also used with California Meal Rules. According to these rules, when an employee is not provided with a required meal or break, the employee may receive an extra hour of pay. This extra hour of pay is posted as a "penalty" event after clock out. The penalty event is configured in the Post Process Event Rules.
Post Process Event Rules are created on the Calc Rule form. Each rule is expressed as an IF-THEN statement. The IF portion contains one or more conditions, and the THEN portion contains one or more actions. When the condition is met, the action is executed.
The individual rules are combined into rulesets using the Rulesets form. The ruleset is then assigned to the Person or Person Group's Pay Policy.
The following is a list of the available operands for the PostProcessEventRuleset context.
This operand checks to see if a specific event is being processed. The operand will return True if the action currently being processed matches both parameters (Event Type and Event Stage).
Parameters:
Event Type = Select the type of event for which the operand should check. Currently only ATTENDANCE:CLOCK event types can be chosen.
Event Stage = Select the stage for the Event Type that the operand is checking (Elapsed, End, None, or Start). For example, if you want the operand to check for a Clock Out event, select ATTENDANCE:CLOCK as the Event Type parameter and End as the Event Stage parameter.
Example:
This operand is part of a ruleset that adds 15 minutes of “clean time” to the employee’s timecard after clock out, provided the employee has worked a minimum number of hours. This operand stops processing the ruleset if the clock out event is not being posted or if the CLEAN_TIME event has already been posted.
IF Clause:
Not( Currently Processing Event( ATTENDANCE:CLOCK, End ) )
Or
Is Event Posted( Project (CLEAN_TIME) )
THEN Clause:
Stop Processing( )
Get Scheduled Split Half Ind By Event
This operand may be necessary if you are using 9-80 schedules. It returns the split half indicator (FIRST HALF, SECOND HALF, or NO SPLIT) of a scheduled event. The split half indicator is defined in the Half Indicator field in the Other Properties tab of the Person Schedule or Schedule Cycle form.
This operand is typically used with the Post Elapsed With Split Half operand to post an event on the first or second half of a split day based on how another event is configured in the person's schedule. For example, the following operand will post the Pay for Missed Meal event for 1 hour and it will post this event to the half of the day that has the Meal1 event scheduled. It will post the Pay for Missed Meal event with zero points:
Post Elapsed With SplitHalf( Pay for Missed Meal (Pay for Missed Meal), 1, Get Scheduled Split Half Ind By Event( Meal1 (Meal1) ), 0 )
Parameters:
Event Name = Name of the event for which you want to obtain the split half indicator.
Example:
The Get Scheduled Split Half Ind By Event operand is used in the THEN clause of this rule to determine which half of a split day to post the Pay for Missed Meal event. The Get Scheduled Split Half Ind By Event operand finds the split half indicator (first or second half of the day) configured for the Meal1 event in the person's schedule. The Pay for Missed Meal event will be posted to this half of the day.
IF Currently Processing
Event( ATTENDANCE:CLOCK, End )
And Reached Minimum by Pay Policy( 5 )
And( Not( Has Occurred Before Clock Start Offset By Event( Meal1 (Meal1),
1, 5 ) )
Or Not( Has Occurred With Minimum Duration By Event( Meal1 (Meal1),
1, 0.5 ) ))
And Not( Is Penalty Waived With Reason( Meal1 (Meal1), 1, Waived Missed
Meal or Break Pay ) )
THEN Post Elapsed With SplitHalf( Pay for Missed Meal (Pay for Missed
Meal), 1, Get Scheduled Split Half
Ind By Event( Meal1 (Meal1) ), 0 )
Get Scheduled Split Half Ind By Event Type
This operand may be necessary if you are using 9-80 schedules. It returns the split half indicator (FIRST HALF, SECOND HALF, or NO SPLIT) of an event type in the person's schedule. The split half indicator is defined in the Half Indicator field in the Other Properties tab of the Person Schedule or Schedule Cycle form.
This operand is typically used with the Post Elapsed With Split Half operand to post an event on the first or second half of the split day based on how another event is configured in the person's schedule. For example, the following operand will post the Pay for Missed Meal event for 1 hour and it will post this event to the half of the day that has the second occurrence of an ATTENDANCE:MEAL event scheduled. It will post the Pay for Missed Meal event with zero points:
Post Elapsed With SplitHalf( Pay for Missed Meal (Pay for Missed Meal), 1, Get Scheduled Split Half Ind By Event Type( ATTENDANCE:MEAL, 2 ), 0 )
Parameters:
Event Type = Type of the event for which you want to obtain the split half indicator.
Occurrences = The nth occurrence of the specified Event Type for which you want to obtain the split half indicator if these Event Types were numbered in ascending timestamp order. For example, the schedule is for a split day. Both the First Half and the Second Half have scheduled ATTENDANCE:MEAL events. If you set Occurrences to 2, the operand will select the split half indicator of the second meal event in the schedule, which in this case is Second Half.
Example:
The Get Scheduled Split Half Ind By Event Type operand is used in the THEN clause of this rule to determine which half of a split day to post the Pay for Missed Meal event. The Get Scheduled Split Half Ind By Event Type operand finds the split half indicator (first or second half of the day) configured for the second occurrence of an ATTENDANCE:MEAL event in the person's schedule. The Pay for Missed Meal event will be posted to this half of the day.
IF Currently Processing
Event( ATTENDANCE:CLOCK, End )
And Reached Minimum by Pay Policy( 5 )
And( Not( Has Occurred Before Clock Start Offset By Event( Meal1 (Meal1),
1, 5 ) )
Or Not( Has Occurred With Minimum Duration By Event( Meal1 (Meal1),
1, 0.5 ) ))
And Not( Is Penalty Waived With Reason( Meal1 (Meal1), 1, Waived Missed
Meal or Break Pay ) )
THEN Post Elapsed With SplitHalf( Pay for Missed Meal (Pay for Missed
Meal), 1, Get Scheduled Split Half
Ind By Event Type( ATTENDANCE:MEAL, 2 ), 0 )
Has Occurred Before Clock Start Offset By Event
This operand checks to see if the nth occurrence of an event in the day has a start rounded timestamp that is within a certain number of hours after the first clock in of the day.
For example, the operand below returns a value of True if the second occurrence of the Meal1 event has a rounded start timestamp that is no more than 5 hours after the rounded timestamp of the first clock in of the day:
Has Occurred Before Clock Start Offset By Event( Meal1 (Meal1), 2, 5 )
The operand below checks to see that the first occurrence of the Meal1 event did not post within 5 hours after clock in:
Not( Has Occurred Before Clock Start Offset By Event( Meal1 (Meal1), 1, 5 ) )
Parameters:
Event Name = Name of the event to be checked.
Occurrences = The nth occurrence in the day of the specified Event Name if the events were numbered in ascending timestamp order.
Minimum Threshold = Minimum number of hours required between the rounded timestamp of the first clock in of the day and the start rounded timestamp of the nth occurrence of the Event Name. The Has Occurred Before Clock Start Offset By Event operand will be True if the start of the nth occurrence of the event is before the first clock in plus this threshold.
Example:
The following rule may be used to post a "penalty" of one hour of regular pay to the employee's timecard if the employee does not receive a 30-minute meal period after working 5 hours.
The Not( Has Occurred Before Clock Start Offset By Event( Meal1 (Meal1), 1, 5 ) operand checks to see that the first occurrence of the Meal1 event did not post within 5 hours after clock in.
IF Currently Processing
Event( ATTENDANCE:CLOCK, End )
And Reached Minimum by Pay Policy( 5 )
And ( Not( Has Occurred Before Clock
Start Offset By Event( Meal1 (Meal1), 1, 5 ) )
Or Not( Has Occurred With Minimum Duration By Event( Meal1 (Meal1),
1, 0.5 ) ))
And Not( Is Penalty Waived With Reason( Meal1 (Meal1), 1, Waive Missed
Meal or Break Pay ) )
THEN Post Elapsed( Pay for Missed Meal (Pay for Missed Meal), 1, None,
0 )
Has Occurred Before Clock Start Offset By Event Group
This operand checks to see if the nth occurrence in the day of an event in a specific Event Group has a start rounded timestamp that is within a certain number of hours after the first clock in of the day.
For example, the operand below returns a value of True if the first occurrence of an event in the Labor_Events Event Group has a rounded start timestamp that is no more than 5 hours after the rounded timestamp of the first clock in of the day:
Has Occurred Before Clock Start Offset By EventGroup( Labor_Events, 1, 5 )
The operand below checks to see that the first occurrence of an event in the Labor_Events Event Group did not post within 5 hours after clock in:
Not( Has Occurred Before Clock Start Offset By EventGroup( Labor_Events, 1, 5 ) )
Parameters:
Event Group = Name of the Event Group to be checked.
Occurrences = The nth occurrence in the day of an event in the specified Event Group if the events were numbered in ascending timestamp order.
Minimum Threshold = Minimum number of hours required between the rounded timestamp of the first clock in of the day and the start rounded timestamp of the nth occurrence of an event in the specified Event Group. The Has Occurred Before Clock Start Offset By EventGroup operand will be True if the start of the nth occurrence of an event in the specified Event Group is before the first clock in plus this threshold.
Example:
The following rule may be used to post a "penalty" of one hour of regular pay to the employee's timecard if the employee does not receive a 30-minute meal period after working 5 hours.
The Not( Has Occurred Before Clock Start Offset By EventGroup( Labor_Events, 1, 5 ) operand checks to see that the first occurrence of an event in the Labor_Events Event Group did not post within 5 hours after clock in.
IF Currently Processing
Event( ATTENDANCE:CLOCK, End )
And Reached Minimum by Pay Policy( 5 )
And ( Not( Has Occurred Before Clock
Start Offset By EventGroup( Labor_Events, 1, 5 ) )
Or Not( Has Occurred With Minimum Duration By Event( Meal1 (Meal1),
1, 0.5 ) ))
And Not( Is Penalty Waived With Reason( Meal1 (Meal1), 1, Waive Missed
Meal or Break Pay ) )
THEN Post Elapsed( Pay for Missed Meal (Pay for Missed Meal), 1, None,
0 )
Has Occurred Before Clock Start Offset By Event Type
This operand checks to see if the nth occurrence in the day of an Event Type has a start rounded timestamp that is within a certain number of hours after the first clock in of the day.
For example, the operand below returns a value of True if the second occurrence of an ATTENDANCE:MEAL event has a rounded start timestamp that is no more than 5 hours after the rounded timestamp of the first clock in of the day:
Has Occurred Before Clock Start Offset By EventType( ATTENDANCE:MEAL, 2, 5 )
The operand below checks to see that the first occurrence of an ATTENDANCE:MEAL event did not post within 5 hours after clock in:
Not( Has Occurred Before Clock Start Offset By EventType( ATTENDANCE:MEAL, 1, 5 ) )
Parameters:
Event Type = Type of event to be checked.
Occurrences = The nth occurrence in the day of the specified Event Type if the events were numbered in ascending timestamp order.
Minimum Threshold = Minimum number of hours required between the rounded timestamp of the first clock in of the day and the start rounded timestamp of the nth occurrence of the Event Type. The Has Occurred Before Clock Start Offset By EventType operand will be True if the start of the nth occurrence of the event type is before the first clock in plus this threshold.
Example:
The following rule may be used to post a "penalty" of one hour of regular pay to the employee's timecard if the employee does not receive a 30-minute meal period after working 5 hours.
The Not( Has Occurred Before Clock Start Offset By EventType( ATTENDANCE:MEAL, 1, 5 ) operand checks to see that the first occurrence of an ATTENDANCE:MEAL event did not post within 5 hours after clock in.
IF Currently Processing
Event( ATTENDANCE:CLOCK, End )
And Reached Minimum by Pay Policy( 5 )
And ( Not( Has Occurred Before Clock
Start Offset By EventType( ATTENDANCE:MEAL, 1, 5 ) )
Or Not( Has Occurred With Minimum Duration By Event( Meal1 (Meal1),
1, 0.5 ) ))
And Not( Is Penalty Waived With Reason( Meal1 (Meal1), 1, Waive Missed
Meal or Break Pay ) )
THEN Post Elapsed( Pay for Missed Meal (Pay for Missed Meal), 1, None,
0 )
Has Occurred Before Clock Start Offset By Pay Policy
This operand checks to see if the nth occurrence in the day of an event in the employee's Pay Policy with the Post Process Event context has a start rounded timestamp that is within a certain number of hours after the first clock in of the day. You can define these events using the Events, Event Types, and Hours Class tabs in your Pay Policy.
For example, the operand below returns a value of True if the second occurrence of a Post Process Event configured in the Pay Policy has a rounded start timestamp that is no more than 5 hours after the rounded timestamp of the first clock in of the day:
Has Occurred Before Clock Start Offset By PayPolicy( 2, 5 )
The operand below checks to see that the first occurrence of a Post Process Event configured in the Pay Policy did not post within 5 hours after clock in:
Not( Has Occurred Before Clock Start Offset By PayPolicy( 1, 5 ) )
Parameters:
Occurrences = The nth occurrence in the day of a Post Process Event configured in the Pay Policy if the events were numbered in ascending timestamp order.
Minimum Threshold = Minimum number of hours required between the rounded timestamp of the first clock in of the day and the start rounded timestamp of the nth occurrence of a Post Process Event configured in the Pay Policy. The Has Occurred Before Clock Start Offset By PayPolicy operand will be True if the start of the nth occurrence of a Post Process Event configured in the Pay Policy is before the first clock in plus this threshold.
Example:
The following rule may be used to post a "penalty" of one hour of regular pay to the employee's timecard if the employee does not receive a 30-minute meal period after working 5 hours.
The Not( Has Occurred Before Clock Start Offset By PayPolicy( 1, 5 ) operand checks to see that the first occurrence of a Post Process Event configured in the Pay Policy did not post within 5 hours after clock in.
IF Currently Processing
Event( ATTENDANCE:CLOCK, End )
And Reached Minimum by Pay Policy( 5 )
And ( Not( Has Occurred Before Clock
Start Offset By PayPolicy( 1, 5 ) )
Or Not( Has Occurred With Minimum Duration By Event( Meal1 (Meal1),
1, 0.5 ) ))
And Not( Is Penalty Waived With Reason( Meal1 (Meal1), 1, Waive Missed
Meal or Break Pay ) )
THEN Post Elapsed( Pay for Missed Meal (Pay for Missed Meal), 1, None,
0 )
Has Occurred With Minimum Duration By Event
This operand checks to see whether a minimum number of occurrences of a specific event have posted and that each occurrence posted for a minimum number of hours.
For example, the operand below returns a value of True if the Meal1 event occurred at least twice in the day and each occurrence was for at least 0.5 hours:
Has Occurred With Minimum Duration By Event( Meal1 (Meal1), 2, 0.5 )
The operand below checks to see that at least one occurrence of the Meal1 event with at least a 0.5 hour duration did not post:
Not( Has Occurred With Minimum Duration By Event( Meal1 (Meal1), 1, 0.5 ) )
Parameters:
Event Name = Name of the event to be checked.
Minimum Occurrences = Minimum number of occurrences in the day of the Event Name.
Minimum Duration = Minimum duration (in hours) for each occurrence of the Event Name.
Example:
The following rule may be used to post a "penalty" of one hour of regular pay to the employee's timecard if the employee does not receive a 30-minute meal period after working 5 hours.
The Not( Has Occurred With Minimum Duration By Event( Meal1 (Meal1), 1, 0.5 ) ) operand checks to see if at least one occurrence of the Meal1 event with a duration of 0.5 hours did not post.
IF Currently Processing
Event( ATTENDANCE:CLOCK, End )
And Reached Minimum by Pay Policy( 5 )
And ( Not( Has Occurred Before Clock Start Offset By Event( Meal1 (Meal1),
1, 5 ) )
Or Not( Has Occurred With Minimum
Duration By Event( Meal1 (Meal1), 1, 0.5 ) ))
And Not( Is Penalty Waived With Reason( Meal1 (Meal1), 1, Waive Missed
Meal or Break Pay ) )
THEN Post Elapsed( Pay for Missed Meal (Pay for Missed Meal), 1, None,
0 )
Has Occurred With Minimum Duration By Event Group
This operand checks to see whether a minimum number of occurrences of an event in a specific Event Group have posted and that each occurrence posted for a minimum number of hours.
For example, the operand below returns a value of True if an event in the Meal_Events Event Group occurred at least twice in the day and each occurrence was for at least 0.5 hours:
Has Occurred With Minimum Duration By EventGroup( Meal_Events, 2, 0.5 )
The operand below checks to see that at least one occurrence of an event in the Meal_Events Event Group with at least a 0.5 hour duration did not post:
Not( Has Occurred With Minimum Duration By EventGroup( Meal_Events, 1, 0.5 ) )
Parameters:
Event Group = Name of the Event Group to be checked.
Minimum Occurrences = Minimum number of occurrences in the day of an event in the Event Group.
Minimum Duration = Minimum duration (in hours) for each occurrence of an event in the Event Group.
Example:
The following rule may be used to post a "penalty" of one hour of regular pay to the employee's timecard if the employee does not receive a 30-minute meal period after working 5 hours.
The Not( Has Occurred With Minimum Duration By EventGroup( Meal_Events, 1, 0.5 ) ) operand checks to see if at least one occurrence of an event in the Meal_Events Event Group with a duration of 0.5 hours did not post.
IF Currently Processing
Event( ATTENDANCE:CLOCK, End )
And Reached Minimum by Pay Policy( 5 )
And ( Not( Has Occurred Before Clock Start Offset By Event( Meal1 (Meal1),
1, 5 ) )
Or Not( Has Occurred With Minimum
Duration By EventGroup( Meal_Events, 1, 0.5 ) ))
And Not( Is Penalty Waived With Reason( Meal1 (Meal1), 1, Waive Missed
Meal or Break Pay ) )
THEN Post Elapsed( Pay for Missed Meal (Pay for Missed Meal), 1, None,
0 )
Has Occurred With Minimum Duration By Event Type
This operand checks to see whether a minimum number of occurrences of a specific event type have posted and that each occurrence posted for a minimum number of hours.
For example, the operand below returns a value of True if an ATTENDANCE:MEAL event occurred at least twice in the day and each occurrence was for at least 0.5 hours:
Has Occurred With Minimum Duration By EventType( ATTENDANCE:MEAL, 2, 0.5 )
The operand below checks to see that at least one ATTENDANCE:MEAL event with at least a 0.5 hour duration did not post:
Not( Has Occurred With Minimum Duration By EventType( ATTENDANCE:MEAL, 1, 0.5 ) )
Parameters:
Event Type = Type of event to be checked.
Minimum Occurrences = Minimum number of occurrences in the day of the Event Type.
Minimum Duration = Minimum duration (in hours) for each occurrence of the Event Type.
Example:
The following rule may be used to post a "penalty" of one hour of regular pay to the employee's timecard if the employee does not receive a 30-minute meal period after working 5 hours.
The Not( Has Occurred With Minimum Duration By EventType( ATTENDANCE:MEAL, 1, 0.5 ) ) operand checks to see if at least one occurrence of the Meal1 event with a duration of 0.5 hours did not post.
IF Currently Processing Event( ATTENDANCE:CLOCK, End
)
And Reached Minimum by Pay Policy( 5 )
And ( Not( Has Occurred Before Clock Start Offset By Event( Meal1 (Meal1),
1, 5 ) )
Or Not( Has Occurred With Minimum
Duration By EventType( ATTENDANCE:MEAL, 1, 0.5 ) ))
And Not( Is Penalty Waived With Reason( Meal1 (Meal1), 1, Waive Missed
Meal or Break Pay ) )
THEN Post Elapsed( Pay for Missed Meal (Pay for Missed Meal), 1, None,
0 )
This operand checks to see whether a minimum number of occurrences of an event with the Post Process Event context in the employee's Pay Policy have posted and that each occurrence posted for a minimum number of hours.
For example, the operand below returns a value of True if a Post Process Event configured in the Pay Policy occurred at least twice in the day and each occurrence was for at least 0.5 hours:
Has Occurred With Minimum Duration By PayPolicy( 2, 0.5 )
The operand below checks to see that at least one Post Process Event configured in the Pay Policy with at least a 0.5 hour duration did not post:
Not( Has Occurred With Minimum Duration By PayPolicy( 1, 0.5 ) )
Parameters:
Minimum Occurrences = Minimum number of occurrences in the day of a Post Process Event configured in the Pay Policy.
Minimum Duration = Minimum duration (in hours) for each occurrence of a Post Process Event configured in the Pay Policy.
Example:
The following rule may be used to post a "penalty" of one hour of regular pay to the employee's timecard if the employee does not receive a 30-minute meal period after working 5 hours.
The Not( Has Occurred With Minimum Duration By PayPolicy( 1, 0.5 ) ) operand checks to see if at least one occurrence of a Post Process Event configured in the Pay Policy with a duration of 0.5 hours did not post.
IF Currently Processing
Event( ATTENDANCE:CLOCK, End )
And Reached Minimum by Pay Policy( 5 )
And ( Not( Has Occurred Before Clock Start Offset By Event( Meal1 (Meal1),
1, 5 ) )
Or Not( Has Occurred With Minimum
Duration By PayPolicy( 1, 0.5 ) ))
And Not( Is Penalty Waived With Reason( Meal1 (Meal1), 1, Waive Missed
Meal or Break Pay ) )
THEN Post Elapsed( Pay for Missed Meal (Pay for Missed Meal), 1, None,
0 )
Checks to see if the person’s assigned shift (the shift that is in effect on the post date) matches the shift in the parameter. See How Shop Floor Time Determines an Employee's Shift.
Parameters:
Shift Num = Select the shift for which you want this operand to check. Available options are defined in the Shift Definition form.
This operand checks to see if the event in the Event Name parameter has already been posted on the day being processed.
This operand may be used with the Stop Processing operand to stop processing the ruleset if an event is already posted. It can also be used to prevent an event from posting if the event has already been posted.
Parameters:
Event Name = Indicates which event the operand will look for on the post date. Select an event name from the drop-down list.
Example:
IF Clause:
Not( Currently Processing Event( ATTENDANCE:CLOCK, End ) )
Or
Is Event Posted( Project (CLEAN_TIME) )
THEN Clause:
Stop Processing( )
This IF operand checks if the post date has no schedules or contains schedules with a non-zero gap day number.
Checks if the current post date has a schedule with the indicated Gap Day number. A gap day is a post date that:
Contains one or more schedules with a Gap Number that is greater than zero.
Contains no schedules at all or just schedules that do not require the person to work, such as Ad Hoc Placeholder, Availability, Exclusion, and Optional schedules.
Contains only Overtime schedules.
Parameters:
Gap Day Number = Indicates the gap day number to check for. Enter a numeric value.
If you are using California Meal Rules, a "penalty" of one hour of regular pay may post to an employee's timecard if the employee does not receive the required meals and break periods. In some cases, the employee will waive this penalty by posting the meal or break with a specific reason code.
This operand is used to determine whether a meal or break event was posted with a specific reason code a maximum number of times.
For example, the operand below returns a value of True if the event Meal1 has been waived (posted with the Reason Code Waive Missed Meal or Break Pay) once:
Is Penalty Waived With Reason( Meal1 (Meal1), 1, Waive Missed Meal or Break Pay )
Parameters:
Event Name = Name of the event to be checked.
Max Waivers = Maximum number of times the Event Name can be posted with the Reason Code (see below). This parameter defines the maximum number of waivers allowed for the Event Name before the penalty event must be posted.
Reason Code = Reason Code that posted with the specified Event Name.
Example:
The following rule may be used to post a "penalty" of one hour of regular pay to the employee's timecard if the employee does not receive a 30-minute meal period after working 5 hours.
The Not( Is Penalty Waived With Reason( Meal1 (Meal1), 1, Waive Missed Meal or Break Pay ) ) operand checks to see if the Meal1 event with the Reason Code Waive Missed Meal or Break Pay did not post once.
IF Currently Processing Event( ATTENDANCE:CLOCK, End
)
And Reached Minimum by Event Group( Labor_Events, 5 )
And ( Not( Has Occurred Before Clock Start Offset By Event( Meal1 (Meal1),
1, 5 ) )
Or Not( Has Occurred With Minimum Duration By Event( Meal1 (Meal1),
1, 0.5 ) ))
And Not( Is Penalty Waived With Reason(
Meal1 (Meal1), 1, Waive Missed Meal or Break Pay ) )
THEN Post Elapsed( Pay for Missed Meal (Pay for Missed Meal), 1, None,
0 )
Checks if the post date is on, before, or after a specific day of the week.
Parameters:
Week Day Options = Determines which day to check. Available options are:
Post Date – The operand will check the current post date.
Day Before Post Date - The operand will check the day before the post date.
Day After Post Date - The operand will check the day after the post date.
WeekDay = Determines which day of the week to check for. Select a day of the week from the drop-down list.
Example:
If you set the parameters to "Day Before Post Date" and "Friday," this operand will return “True” when hours post to the timecard on Saturday.
IsPostDateDayofWeek(Day Before Post Date, Friday)
This operand checks to see if the duration of all non-cancelled labor transactions is greater than a Minimum Duration. This operand only checks for labor transactions.
Parameters:
Minimum Duration = Enter the minimum duration that this operand will check for across all non-cancelled labor transactions (e.g., 0.01).
This IF operand checks if the post day is a scheduled day. It is the opposite of Is Gap Day.
This operand returns the opposite of the value in the parameter.
Parameters:
Value = Enter a value in this field or right-click and choose an operand to calculate this value.
For example, use the operand Not( Is Scheduled Day() ) to require a Gap Day.
This operand posts the specified Event Name and other parameters as an elapsed event for the person and post date that is being processed.
Parameters:
Event Name = Indicates which event to post. Select an event from the drop-down list. Holiday, Vacation, Sick, and Time Off event types cannot be used. The Post Process Event will be posted as an elapsed event, so the event you select must not require a timestamp.
Duration = Enter the duration (hourly amount) of the event you are posting.
Split Half = For a 9-80 schedule, this parameter indicates which half of a split day the event will post on. Select First, None, or Second. If you are not using 9-80 schedules, set this parameter to None. Otherwise you must select First or Second. The Post Process Event cannot be split across both halves of the split day.
Points = Number of points to post for the event. Enter zero (0) if the event will not include penalty points.
This operand may be necessary if you are using 9-80 schedules and California Meal Rules. It will post an elapsed event for a specified duration and with a specified number of penalty points on the first or second half of the split day.
You can use the Get Scheduled Split Half Ind By Event or Get Scheduled Split Half Ind By Event Type operand with the Post Elapsed With Split Half operand to determine which half of a split day to post the event.
For example, the following operand will post the Pay for Missed Meal event for 1 hour to the half of the day that has the Meal1 event scheduled. It will post the Pay for Missed Meal event with zero points:
Post Elapsed With SplitHalf( Pay for Missed Meal (Pay for Missed Meal), 1, Get Scheduled Split Half Ind By Event( Meal1 (Meal1) ), 0 )
Parameters:
Event Name = Indicates which event to post.
Duration = Number of hours for which the Event Name will be posted.
Scheduled Split Half = Right-click this field and select the Get Scheduled Split Half Ind By Event or Get Scheduled Split Half Ind By Event Type operand. This parameter determines the half of the split day (First Half or Second Half) to which the Event Name should post.
Points = Number of points to post for the Event Name. Enter zero (0) if the event will not include penalty points.
Example:
The Post Elapsed With SplitHalf operand is used in this rule to post the Pay for Missed Meal event for 1 with no penalty points. The Pay for Missed Meal event will post to the split half indicator (first of second half of the day) configured for the Meal1 event in the person's schedule.
IF Currently Processing
Event( ATTENDANCE:CLOCK, End )
And Reached Minimum by Pay Policy( 5 )
And( Not( Has Occurred Before Clock Start Offset By Event( Meal1 (Meal1),
1, 5 ) )
Or Not( Has Occurred With Minimum Duration By Event( Meal1 (Meal1),
1, 0.5 ) ))
And Not( Is Penalty Waived With Reason( Meal1 (Meal1), 1, Waived Missed
Meal or Break Pay ) )
THEN Post Elapsed With SplitHalf(
Pay for Missed Meal (Pay for Missed Meal), 1, Get Scheduled Split
Half Ind By Event( Meal1 (Meal1) ), 0 )
This operand checks to see if the sum of the durations for a specific event is greater than or equal to the Minimum Duration parameter.
Parameters:
Event Name = Select the event this operand will check for.
Minimum Duration = Enter the minimum duration that must be met by sum of the durations for the specified Event Name.
This operand checks to see if the sum of the durations for events in a particular Event Group is greater than or equal to the Minimum Duration parameter.
Parameters:
Event Group = Select the Event Group this operand will check for.
Minimum Duration = Enter the minimum duration that must be met by sum of the durations for the events in the specified Event Group.
Example:
IF Clause:
Reached Minimum by Event Group( BONUS_EVENTS, 6.2 )
THEN Clause:
Post Elapsed( Day Worked (BONUS_HOURS), 1.5, First, 0 )
And
Stop Processing( )
This operand checks to see if the sum of the durations for events with a particular Event Type is greater than or equal to the Minimum Duration parameter.
Parameters:
Event Type = Select the Event Type this operand will check for.
Minimum Duration = Enter the minimum duration that must be met by sum of the durations for the events with the specified Event Type.
This operand checks the Pay Policy’s Event, Event Types, and Hours Classes for the Post Process Event context, and then looks at the sum of the durations of transactions for those events. It checks to see if the sum of these durations is greater than or equal to the Minimum Duration parameter.
Parameters:
Minimum Duration = Enter the minimum duration that must be met by transactions for Event, Event Types, and Hours Classes with the Post Process Event context in the Pay Policy.
This THEN operand will stop processing all rules in the ruleset for the person and post date, even if there are more rules in the ruleset that are sequenced after this rule.
The True operand always returns a value of True. For example, to make sure that a rule is executed in all circumstances, create an IF clause with only the True operand.