How to: Configure conditions and actions for a pay rule version

Pay rules and pay rule versions need conditions and actions that are evaluated by the rules engine to cost shifts or timesheets.

The rules engine takes a collection of timesheets or shifts for a single employee as input, runs through all of the conditions in the rule set to create matches, then turns matches into a collection of pay items.

Once all of the pay items have been created, they are costed using the pay level or pay rate for the employee, and additional information on the pay type, or on the higher level position if applicable.

Instructions

1. First, create a pay rule and pay rule version.

   1. If you’re a sudo admin, and working with global pay rules and pay rule versions see:

      1. How to: Create a new Global Pay Rule

      2. How to: Create a new Global Pay Rule Version

2. Edit the pay rule version
   

   

3. Anatomy of a rule

   1. Rule name

      1. This is the name of the rule, and provides a handy description of what the rule should do. This is particularly useful when combining conditions together, or when referring to a specific condition in an award document

   2. Logic

      1. Conditions (see below) can be combined together to perform complex operations. The kinds of logic you can use are:

         1. {any} of the following

         2. {all} of the following

         3. {none} of the following

   3. Conditions

   4. Actions

4. To add a new set of conditions

5. To configure a condition

6. To combine conditions

7. To add a set of child conditions

8. To add an action