(Please click on the hexagons for more information)
Absence Management refers to the process of managing absences.
Simple Absence Management:
Employees use absences as a simple absence table. There is no formal approval process. Employees just enter absences into the database.
Absence Management with Approval:
A formalized workflow process controls the approval of absences.
Timesheet Entry Variants:
Absences Replace Timesheet Hours:
Once a user has registered an absence for a specific day, he doesn't need to log hours for this day. Instead, the "duration_days" of the absence are multiplied with the parameter TimesheetHoursPerAbsence are used to calculate weekly timesheet times.
Absences as Absence Requests:
In this variant the parameter TimesheetHoursPerAbsence is set to "0". In addition to logging an absence, users need to log hours on an "absence project" representing the various types of absences. Absence projects have to be set up manually, usually starting the 1st of January of every year until the 31st of December of the same year.
Bank Holiday Calendar:
By defining "Bank Holiday" absences per user group it is possible to define workable time for groups of users. This variant can be used in addition with any of the above variants.
An employee enters an absence or applies for an absence
Optionally: A supervisor reviews the absence request and confirms or rejects the request
Manual input of the absence data by an Employee
Accepted or rejected absences or absence requests.
AbsenceNewPageWfDeleteButtonPerm The name of the procedure that should return "1" if the "Delete" button of the AbsenceViewPage should be available. The procedure should accept a single "-absence_id" parameter.
AbsenceNewPageWfEditButtonPerm The name of the procedure that should return "1" if the "Edit" button of the AbsenceViewPage should be available. The procedure should accept a single "-absence_id" parameter.
TimesheetHoursPerAbsence Specifies the equivalent hours of a day of absences. 8 by default.