This prompt automatically generates structured and clearly written manual entries for all parameters used in the Working Contracts within Can Do.
General Introduction
In Can Do, individual employees or entire groups can have specific agreements related to topics such as vacation, special leave, or sickness.
To represent these different regulations, each person is assigned a so-called Working Contract.
A Working Contract consists of a set of parameters that define exactly how the software behaves in specific situations — for example, when calculating vacation entitlements, handling sick days, or recording working hours.
These parameters are called Working Contracts Parameters.
They define the concrete conditions and rules according to which Can Do operates for an employee.
Vacation Days Per Year (Jahresurlaubsanspruch)
Technical Name: A_ANNUAL_VACATION_DAYS
Category: Absences – Regular Vacation
Type: Number (days)
Default Value: (individually defined per Working Contract)
Description:
This parameter defines how many vacation days an employee is entitled to per year.
The value is expressed in days and serves as the basis for calculating the annual vacation entitlement within the software.
The parameter determines how many days the employee can request as regular vacation within a calendar year.
Changes to this value directly affect the calculation of remaining vacation, carryover periods, and planning horizons.
Example:
An employee with 30 annual vacation days receives the value 30 in the parameter A_ANNUAL_VACATION_DAYS.
Number of Years Creating Annual Planning (Vacation Planning Horizon)
Technical Name: A_YEARS_TO_INITIALIZE
Type: Number (years)
Default Value: 3
Description:
Specifies how many years in advance the vacation planning is automatically generated.
Example:
Value 3 → planning includes the current year plus two subsequent years.
Carry-Over Phases Exist (Enable Carryover Phases)
Technical Name: A_CARRY_OVER_PHASES
Type: Boolean (Yes/No)
Default Value: True
Description:
Controls whether remaining vacation can be carried over into the new year.
Example:
True → remaining vacation can be taken until the end of the defined carryover phase.
Start of Carryover Phase (Beginning of Carryover Phase)
Technical Name: A_CO_PHASE_START
Type: Date
Default Value: 01.01.
Description:
Specifies when the period starts in which remaining vacation from the previous year can be used.
Example:
An employee can start using the previous year’s remaining vacation from January 1st.
End of Carryover Phase (End of Carryover Phase)
Technical Name: A_CO_PHASE_END
Type: Date
Default Value: 31.03.
Description:
Marks the end of the carryover phase. After this date, unused vacation from the previous year expires.
Example:
After March 31st, unused vacation from the previous year can no longer be requested.
Allow Absence Overbooking (Allow Vacation Overbooking)
Technical Name: A_ALLOW_ABSENCE_OVERBOOKING
Type: Boolean (Yes/No)
Default Value: False
Description:
Allows employees to request more vacation days than are available. When activated, a warning dialog with confirmation appears.
Example:
True → the employee can request more vacation days than available but will receive a warning message.
Min Number of Vacation Days (Minimum Lead Time for Vacation Requests)
Technical Name: A_MIN_VACATION_DURATION
Type: Number (days)
Default Value: 10
Description:
Defines the minimum number of working days that must be observed as lead time before submitting a vacation request.
Example:
If the minimum lead time is 10 days, a vacation request made only 5 days in advance will be rejected.
Maximum Vacation Duration in a Single Apply (Maximum Vacation Length per Request)
Technical Name: A_MAX_VACATION_DURATION
Type: Number (days)
Default Value: 15
Description:
Determines how many consecutive working days can be requested in a single vacation request.
Example:
If the value is 15, an employee can request a maximum of 15 consecutive working days of vacation.
Absences – Sickness
Sick Leave Reason Mandatory (Mandatory Sickness Reason)
Technical Name: A_SICK_LEAVE_REASON_MANDATORY
Category: Absences – Sickness
Type: Boolean (Yes/No)
Default Value: (e.g., False)
Description:
This parameter defines whether employees are required to select a sickness reason from a predefined list when entering a sick day.
If set to 'Yes' (True), the employee must choose an appropriate reason (e.g., cold, accident, medical appointment) from the predefined list before saving the sickness record.
The entry cannot be completed without a selected reason.
If set to 'No' (False), selecting a sickness reason is optional, and employees can record sick days without providing a reason.
Example:
When A_SICK_LEAVE_REASON_MANDATORY is set to True, an employee cannot save a sickness entry without selecting a reason from the list.
When False, the entry can be saved without any reason.
Absences – Special Leave
Special Leave Reason Mandatory (Mandatory Special Leave Reason)
Technical Name: A_SPECIAL_ABSENCE_REASON_MANDATORY
Category: Absences – Special Leave
Type: Boolean (Yes/No)
Default Value: (e.g., False)
Description:
This parameter defines whether employees must select a reason from a predefined list when applying for special leave.
If set to 'Yes' (True), providing a special leave reason is mandatory.
In that case, the employee must choose a predefined reason — for example, wedding, birth of a child, or relocation — before the application can be saved.
If set to 'No' (False), providing a reason is optional, and the application can be submitted without selecting one.
Example:
When A_SPECIAL_ABSENCE_REASON_MANDATORY is set to True, the employee must select a reason (e.g., "wedding") before saving the request.
When False, the request can be submitted without specifying a reason.