The tags in the <validations> section represent the different tests and checks that the Dayforce Clock Pro and Clock+ perform to verify clock entries. The clocks perform these validations when they’re operating in standalone mode (that is, the <local_punch_validation> tag in the <system> section is set to yes). The clocks reject invalid clock entries with a message describing the validation issue.
When the clocks are operating in online mode (that is, the <local_punch_validation> tag is set to no), clock entries are validated in Dayforce using the validations specified in System Admin > Clocking Sequence Validation.
Each validation described below has the following attributes:
id: The validation name. Don’t edit this value.active: The validation’s active status. Set to yes to enable the validation, or no to disable it.order: The validation’s place in the hierarchy. Enter the relative order that the validation is performed. For example, the clock runs the validation with order="10" before one with order="20".supervisor: Set to yes to enable the validation even for functions in the supervisor mode menu, or no to disable it in supervisor mode.
Consider this example:
<validation id="EmployeeBadgeValidation" active="yes" order="20" supervisor="yes" />This entry gives the validation name ("EmployeeBadgeValidation") and then specifies that the validation is active, the order is 20, and supervisors can override the validation.
Note: Some validations are available only for the Dayforce Clock Pro, specifically the ones that validate pictures and relay control.
| Thread Tags | Description |
|---|---|
| StartSystemValidation | Validates that the clock time is correct. |
| SupervisorBadgeValidation |
Validates that the badge swiped to enter into supervisor mode belongs to a supervisor. Managers, or other users set up as supervisors, can use supervisor mode to override other clock validations. An example of an override is when a supervisor needs to clock in on an employee’s behalf if they weren’t scheduled, or if they’re trying to clock in late. Supervisors can also perform enrollment tasks, such as enrolling users for biometric verification or picture capture. |
| EmployeeBadgeValidation | Validates employee badge numbers. |
| EmployeeStatusValidation | Validates that the employee performing a clock entry has a time entry policy assignment and is active in Dayforce. |
| BiometricValidation | Validates that the employee’s finger scan matches the template that’s saved in the database. |
| PictureValidation |
(Dayforce Clock Pro only) Validates that the Dayforce Clock Pro was able to capture a picture of the employee with their clock entry. The clock itself doesn’t compare the employee’s picture with the picture stored in the database. Managers must manually compare the pictures in Dayforce using the Clock Entry Audits feature or in Timesheets in the Clock Data panel. |
| EmployeePINValidation | Validates employee and supervisor PINs. The clock uses this validation only if it’s configured to prompt for PINs in the <system> section. |
| BioConsentValidation | Validates that the employee clocking in with biometric verification agreed to submit their fingerprint templates after reviewing the legal disclaimer. If the employee didn’t consent to the submission of their fingerprint templates, the clock entry is rejected. |
| ConsecutivePunchValidation | Filters out consecutive clock entries of the same type that are time-stamped within a specified time (for example, when two directionless clock entries occur within a short time). These times are derived from the employee’s time entry policy in Dayforce. |
| PunchOrderValidation |
Validates the order in which employees perform clock entries. For example, when enabled, the clock doesn’t allow employees to clock out before they’ve clocked in for the day. This validation has an additional attribute that’s enabled by default: |
| MealSubsidyValidation | Validates the meal subsidy entered by the employee on the clock based on your organization’s time entry policy. |
| ShiftStartValidation | Validates employees’ shift start times when they clock in. When enabled, the clock doesn’t allow employees to clock in for a shift unless they’re scheduled. |
| ShiftEndValidation | Validates employees’ shift end times when they clock out. When enabled, the clock doesn’t allow employees to clock out for a shift if it violates their time entry policy (for example, clocking out too early). |
| MealStartValidation | Validates employees’ meal start times when they clock out for a meal. When enabled, the clock doesn’t allow employees to clock out for a meal unless they’re scheduled for one. |
| BreakStartValidation | Validates employees’ break start times when they clock out for a break. When enabled, the clock doesn’t allow employees to clock out for a break unless they’re scheduled for one. |
| MealEndValidation | Validates employees’ meal end times when they clock back in from a meal. When enabled, the clock doesn’t allow employees to clock in from a meal when they aren’t scheduled to. |
| BreakEndValidation | Validates employees’ break end times when they clock back in from a break. When enabled, the clock doesn’t allow employees to clock in from a break when they aren’t scheduled to. |
| MealLengthValidation | Validates employees’ meal lengths. When enabled, the clock doesn’t allow employees to clock in from a meal if the meal they took didn’t meet the scheduled duration. |
| BreakLengthValidation | Validates employees’ break lengths. When enabled, the clock doesn’t allow employees to clock in from a break if the break they took didn’t meet the scheduled duration. |
| ShiftOverrideValidation | Not a validation, but used to return a message to the clock stating that a shift override is in effect. |
| DocketValidation | Validates the docket that employees select when recording docket transfers. This validates that the docket has a clock code and hasn’t expired. |
| EmployeeDocketValidation | Checks that the docket is valid for the employee. |
| ProjectValidation | Validates the project that employees select when recording project transfers. |
| EmployeeProjectValidation | Validates that an employee is assigned to the project that they select when recording a project transfer. |
| QuantityValidation | Validates the quantity that employees select when recording a docket transfer. |
| TransferValidation | Validates the transfer code that employees enter. |
| EmployeeTransferValidation | Validates that an employee can transfer to the work assignment that they selected for a work transfer. |
| OutWithMealBreakValidation | Validates the information that employees record when they clock out for a meal break, and makes sure that the meals and breaks the employees recorded fall within the shift times. |
| TipTypeValidation | Validates the tip type that the user selects when recording tips. |
| RelayControlValidation |
(Dayforce Clock Pro only) Shows a confirmation message when employees perform clock entries that involve relay control. |
| RelayControlEmployeeScheduleValidation |
(Dayforce Clock Pro only) Validates that the employee is scheduled to work. When enabled, it doesn’t allow employees to perform clock entries that involve relay control outside of their schedule. |
| LaborMetricsTypeValidation | Validates that employees enter a valid labor metrics type when recording a labor metrics transfer. |
| LaborMetricsCodeValidation | Validates that employees enter a valid labor metrics code when recording a labor metrics transfer. |
| LaborMetricsPunchPolicyValidation | Validates that the labor metrics type specified by the employee during a labor metrics transfer is assigned to their time entry policy. |
| LaborMetricsEmployeeCodeAssignmentValidation | Validates that an employee is assigned to the labor metrics code they select when recording a labor metrics transfer. |
| MultipleTransfersValidation | Validates the multiple transfer codes that employees enter. |
| InWithTransferValidation | Validates that an employee can clock in and transfer to the work assignment they selected for a work transfer. |