USE_EMPLOYEE_EFFECTIVE_DATE

Description:

This parameter determines whether timesheets can be created or viewed before the employee's effective date (EMP_EFFECTIVE_DATE).

When set to true, employees are prevented from viewing timesheets or applying time off before their effective date. In addition, work details and work summaries cannot be created before this date and timesheets cannot be recalculated before this date.

If the employee's effective date is later than their hire date, timesheet records for the employee can be created and viewed only after the effective date. If the employee's hire date is later than their effective date, timesheet records for the employee can be created and viewed only after the hire date.

Note: If timesheet records for the employee have already been created before setting this registry to true, those records will continue to show. However, no overrides can be applied to records before the employee's effective date.

With this setting, on initial import of employees, the OVR_START_DATE field is used to populate the EMP_EFFECTIVE_DATE field, unless the EMP_EFFECTIVE_DATE is explicitly provided in the import. On subsequent overrides to an existing employee, the EMP_EFFECTIVE_DATE value is updated automatically if the OVR_START_DATE value is earlier than the existing EMP_EFFECTIVE_DATE value and the EMP_EFFECTIVE_DATE is not explicitly provided. When the employee's effective date is provided in the import, then that value is used instead of the OVR_START_DATE value.

When set to false, timesheets can be created or viewed as of the employee's hire date. Time off requests are validated against the employee's hire date. This is the default.

With this setting, on initial import of employees, the OVR_CREATE_DATE field is used to populate the EMP_EFFECTIVE_DATE field. On subsequent overrides to an existing employee, the EMP_EFFECTIVE_DATE value cannot be changed.

Valid Values:

true, false

Default Value:

false

Location:

system/WORKBRAIN_PARAMETERS/

Effective:

2022.02.00