In this article in The Rules Series, we show how to configure the rules engine to use the Timesheet matches an above rule condition.
How the Timesheet matches an above rule condition works
Overview
The Timesheet matches an above rule condition matches the portion of timesheets that have been matched by any conditions that have preceded it.
Only the portions of time that match in previously evaluated conditions are matched in this condition.
When combined with a ‘category’ specification, the condition matches time that has been tagged with a category. (see How to: Configure actions: Category ).
When used without a category, the condition will use all matches from all previous conditions.
This condition is useful as a ‘catch all’ condition at the end of a rule specification, to ensure that any conditions not matched above are paid to the employee.
Often this condition is combined with the ‘When none of these conditions are met’ container to catch any portions of time that cannot be matches with other conditions.
Of course, this condition can also be used to ensure that timesheets have not already met a previous condition, when evaluating other conditions. This might be useful when evaluating normal pay hours having already evaluated and matched leave timesheets or public holidays.
Configuration options
Name | Description | Data Type | Example value |
---|---|---|---|
Category | The name of the category to recall from matches that are tagged with that category | Text | ordinary |
An example: using the condition to recall and pay from a category
A common use case might be to combine multiple conditions to a single pay type later on. In this case, we have a combination of shifts on Monday - Friday and Saturday conditions all contributing to be paid ordinary hours. (we could combine those to a single condition, but whatever). In this case, we incorporate the two conditions at the start of the process, and then pay on those conditions at the very end.
In this example, the employee is paid ordinary hours for their Thursday and Friday shifts, and paid Saturday hours for their Saturday shift (being part of a separate condition).
An example: using the condition as a catch-all
In this example, this condition is used as a classic ‘fallback’ to ensure that any time portions not matched by conditions above.
In this example I’ve tweaked the other conditions to allow shifts / timesheets that fall on a Thursday and Friday to fall through to this rule, and have created a specific pay type to highlight the rule being used.
In most scenarios the pay type when matching on this rule is likely to be the employee’s Ordinary hours pay type, or similar.
Note that the payment for this condition is on top of other payments, in this case the employee is paid both for Sunday hours, time above consecutive hours, and for the shift / timesheet falling on Boxing Day.
Instructions
Create a Pay Rule and Pay Rule Version. (see: How to: Create a new Global Pay Rule, and How to: Create a new Global Pay Rule Version for examples)
Navigate to edit the pay rule version, and expand the Rules
In the conditions section, select Timesheet matches an above rule
Enter the category to select matches from (to select all matches regardless of category, leave the category field blank)
Configure the action you want to take for this condition.
Save your pay rule version.
Comments
0 comments
Please sign in to leave a comment.