<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=2740041&amp;fmt=gif">
Skip to content
English
  • There are no suggestions because the search field is empty.

Working Contracts Parameters – User Manual

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 (Annual Vacation Entitlement)

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: (individually defined per Working Contract)

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: No

Description:
Controls whether remaining vacation can be carried over into the new year.

Example:
If set to Yes, remaining vacation can be taken during the defined carryover period.
If set to No, unused vacation expires at the end of the year.


Start of Carryover Phase (Beginning of Carryover Phase)

Technical Name: A_CO_PHASE_START
Type: Date
Default Value: (individually defined per Working Contract)

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: (individually defined per Working Contract)

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.


Carry Over Phase Priority

Technical Name: A_CO_PHASE_PRIORITY
Type: Number
Default Value: Not defined

Defines the order in which vacation entitlements are deducted. During the applicable period, the Carry Over Phase entitlement can be given priority, for example by assigning priority 0.

Example:
Value 0 → Vacation requests within the Carry Over Phase period are deducted from the Carry Over Phase entitlement first.

_______________________________________________________________________________

Vacation Phase Priority

Technical Name: A_ST_PHASE_PRIORITY
Type: Number
Default Value: Not defined

Defines the order in which vacation entitlements are deducted. The standard annual vacation entitlement can be given priority within the applicable period, for example by assigning a specific priority value.

Example:
Value 1 → Vacation requests within the applicable period for standard annual vacation are deducted according to the defined priority.
If the Carry Over Phase has priority 0 and Standard Annual Vacation has priority 1, the vacation entitlement with priority 0 is deducted first, followed by the entitlement with priority 1.
The priority always applies within the respective periods for which the vacation entitlements are valid.

_________________________________________________________

Allow Vacation Overbooking (Allow Vacation Overbooking)

Technical Name: A_ALLOW_VACATION_OVERBOOKING
Type: Boolean (Yes/No)
Default Value: No

Description:
Allows employees to request more vacation days than are available. When activated, a warning dialog with confirmation appears.

Example:
Yes → the employee can request more vacation days than available but will receive a warning message.


Min Number of Vacation Days (Minimum Number of Vacation Days)

Technical Name: A_MIN_VACATION_DURATION
Type: Number (days)
Default Value: (individually defined per Working Contract)

Description:
Defines the minimum number of working days that must be taken as vacation.

Example:
Value 2 → Vacation must be at least 2 days long.

_______________________________________________________________________________

Min Days to Apply for Vacation (Minimum Advance Notice for Vacation Requests)

Technical Name: A_MIN_DAYS_BEFORE_VACATION_APPLY
Type: Number (days)
Default Value: (individually defined per Working Contract)

Description:
Defines how many working days in advance an employee must submit a vacation request.
This prevents spontaneous vacation requests that could lead to short-term staffing shortages

Example:
Value 10 → Vacation can only be requested at least 10 working days in advance.

_________________________________________________________

Maximum Vacation Duration in a Single Apply (Maximum Vacation Length per Request)

Technical Name: A_MAX_VACATION_DURATION
Type: Number (days)
Default Value: (individually defined per Working Contract)

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.

_______________________________________________________________________________

Can Take Absence Without Approval (Vacation without approval)

Technical Name: A_CAN_TAKE_LEAVE_WITHOUT_APPROVAL
Type: Boolean (Yes/No)
Default Value: No

Description:
Defines whether an employee can take vacation without requiring approval.

Example:
If Yes → the employee can take vacation without approval.

_______________________________________________________________________________

Department Leader Direct Absence Input (Vacation Input from Departement Leader)

Technical Name: A_DEPARTMENT_LEADER_DIRECT_INPUT_ALLOWED
Type: Boolean (Yes/No)
Default Value: No

Description:
Defines whether a department leader is allowed to directly enter absences for employees.
(This applies to all types of absences.)

Example:
If Yes → the department leader can enter absences for employees.

_______________________________________________________________________________

Vacation request comment mandatory (Mandatory comment when submitting a vacation request)

Technical Name: A_REQUEST_COMMENT_MANDATORY
Type: Boolean (Yes/No)
Default Value: No

Description:
Defines whether users are required to enter a comment for every vacation request (excluding sick leave requests).

Example:
If set to Yes → the comment field becomes mandatory.

_______________________________________________________________________________

Vacation approval comment mandatory (Mandatory comment when approving vacation requests)

Technical Name: A_REQUEST_APPROVE_COMMENT_MANDATORY
Type: Boolean (Yes/No)
Default Value: No

Description:
Defines whether users are required to enter a comment when approving vacation requests (excluding sick leave requests).

Example:
If set to Yes → the comment field becomes mandatory.

_______________________________________________________________________________

Vacation rejection comment mandatory (Mandatory comment when rejecting vacation requests)

Technical Name: A_REQUEST_REJECT_COMMENT_MANDATORY
Type: Boolean (Yes/No)
Default Value: No

Description:
Defines whether users are required to enter a comment when rejecting vacation requests (excluding sick leave requests).

Example:
If set to Yes → the comment field becomes mandatory.

_______________________________________________________________________________

Vacation cancellation comment mandatory (Mandatory comment when deleting vacation)

Technical Name: A_CANCEL_COMMENT_MANDATORY
Type: Boolean (Yes/No)
Default Value: No

Description:
Defines whether users are required to enter a comment when requesting the cancellation of an already approved absence (excluding sick leave requests).

Example:
If set to Yes → the comment field becomes mandatory.

_______________________________________________________________________________

Vacation cancellation rejection comment mandatory (Mandatory comment when rejecting the deletion of vacation)

Technical Name: A_CANCEL_REJECT_COMMENT_MANDATORY
Type: Boolean (Yes/No)
Default Value: No

Description:
Defines whether users are required to enter a comment when rejecting the cancellation of an already approved absence (excluding sick leave requests).

Example:
If set to Yes → the comment field becomes mandatory.

_______________________________________________________________________________

Vacation cancellation approval comment mandatory (Mandatory comment when approving the deletion of vacation)

Technical Name: A_CANCEL_APPROVE_COMMENT_MANDATORY
Type: Boolean (Yes/No)
Default Value: No

Description:
Defines whether users are required to enter a comment when approving the cancellation of an already approved absence (excluding sick leave requests).

Example:
If set to Yes → the comment field becomes mandatory.

______________________________________________________________________

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: No

Description:

Defines whether a reason from a predefined list must be selected when recording a sick day.

Example:
If set to Yes → the employee must specify a reason, e.g., cold or accident.
If set to No → selecting a reason is optional.

_______________________________________________________________________________

Sick Leave Upload Document Mandatory

Technical Name: A_SICK_LEAVE_DOCUMENT_UPLOAD_MANDATORY
Type: Boolean (Yes/No)
Default Value: No

This parameter defines whether employees are required to upload a document when submitting a Sick Leave entry.

When enabled, a Sick Leave entry cannot be submitted without uploading a document.

This parameter only applies when an active SharePoint integration is configured.

Example:
YES: The employee must upload a document when submitting the Sick Leave entry.

_______________________________________________________________________________

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: No

Description:

Defines whether a reason from a predefined list must be provided when requesting special leave.

Example:
If set to Yes → specifying a reason is required (e.g., wedding, birth of a child, relocation).
If set to No → the request can be submitted without a reason.

_______________________________________________________________________________

Minimum Number of Special Leave Days (Minimum Number of Days for Special Leave request)

Technical Name: A_MIN_SPECIAL_ABSENCE_DURATION
Type: Days
Default Value: (individually defined per Working Contract)

Description:
Defines the minimum number of consecutive days that must be requested for special leave.

Example:
Value 2 → At least 2 days must be requested.

_______________________________________________________________________________

Maximum Number of Special Leave Days (Maximum Number of Days for Special Leave request)

Technical Name: A_MAX_SPECIAL_ABSENCE_DURATION
Type: Days
Default Value: (individually defined per Working Contract)

Description:
Defines the maximum number of consecutive days that may be requested for special leave.

Example:
Value 2 → Maximum of 2 days may be requested at once.

_______________________________________________________________________________

Minimum Number of Days Ahead to Take Special Leave (Minimum Number of Days ahead for Special Leave request)

Technical Name: A_MIN_DAYS_BEFORE_SPECIAL_ABSENCE_APPLY
Type: Days
Default Value: (individually defined per Working Contract)

Description:
Defines how many days in advance special leave must be requested.

Example:
Value 10 → The request for special leave must be submitted at least 10 days in advance.

_______________________________________________________________________________

Allow Special Leave Overbooking

Technical Name: A_ALLOW_SPECIAL_ABSENCE_OVERBOOKING
Type: Boolean (Yes/No)
Default Value: No

Description:
Allows employees to request more Special Leave days than are available. When activated, a warning dialog with confirmation appears.

Example:
Yes → the employee can request more Special Leave days than available but will receive a warning message.


Special Leave Approval Process Required

Technical Name: A_SPECIAL_ABSENCE_APPROVAL_REQUIRED
Category: Absences – Special Leave
Type: Boolean (Yes/No)
Default Value: False

Description:
This parameter defines whether special leave requests require a multi-step approval process.
When set to “Yes”, the system activates the two-step approval workflow between the line manager and the HR department.
In this mode, the approval process for special leave differs from the standard approval process used for regular vacation requests.

If the parameter is set to “No”, special leave requests follow the same process as regular leave – with a single approval and no separation between HR and management roles.

When multi-step approval is enabled (“True”), the detailed behavior is defined by the following parameters:

  • A_SPECIAL_ABSENCE_APPROVAL_OPERATOR → specifies the type of approval logic (Steps / AND / OR).

  • A_SPECIAL_ABSENCE_APPROVAL_GROUP_SETTING_1 and A_SPECIAL_ABSENCE_APPROVAL_GROUP_SETTING_2 → define the approval sequence when the operator is set to Steps.

This parameter serves as the central switch determining whether special leave requires a simplified or an extended approval process, depending on data protection policies and internal procedures.

Example:
A company requires that special leave requests involving personal documents (e.g., a marriage certificate) go through a two-step approval process for data protection reasons.
Therefore, A_SPECIAL_ABSENCE_APPROVAL_REQUIRED is set to True, and the system applies the subsequent parameters to define the approval logic and sequence between HR and the line manager.


Special Leave Approval Operator

Technical Name: A_SPECIAL_ABSENCE_APPROVAL_OPERATOR
Category: Absences – Special Leave
Type: Selection (Steps | AND | OR)
Default Value: company-specific

Description:
This parameter defines how special leave requests are approved, particularly in companies that require a multi-step approval process for data protection reasons.

In some organizations, employees must attach personal documents when applying for special leave – for example, a marriage certificate or proof of relocation.
According to internal data protection policies, such documents may only be viewed by the HR department, not by the line manager.
To meet these requirements, the parameter allows for different approval logics.

Available Options:

  • Steps (two-step process):
    The request is approved in two consecutive steps.
    First, one of the two instances (HR team or line manager) approves; then, the other one follows.
    The sequence of approvals (who approves first) is defined in another setting.
    This option is typically used when personal documents are involved that cannot be shared with all approvers.

  • AND (both must approve):
    The request is considered fully approved only when both – the HR team and the line manager – have approved it.
    This ensures that both administrative and organizational checks are completed.

  • OR (one approval is sufficient):
    The request is approved immediately once either the HR team or the line manager approves it.
    This option is suitable for organizations with simple approval processes where no sensitive data is handled.

Example:
An employee applies for special leave to get married and uploads their marriage certificate.

  • With Steps: First, one instance (e.g., HR) approves; then, the other (e.g., manager). The request is confirmed only after both approvals.

  • With AND: Both must approve; the request remains pending until both have confirmed.

  • With OR: One approval is enough – the request is immediately approved.


Special Leave Approval Group Setting 1 / 2 (Approval Sequence for Special Leave)

Technical Name:
A_SPECIAL_ABSENCE_APPROVAL_GROUP_SETTING_1
A_SPECIAL_ABSENCE_APPROVAL_GROUP_SETTING_2

Category: Absences – Special Leave
Type: Number (1 = Line Manager, 2 = HR Department)
Default Value: company-specific

Description:
These two parameters define the order of approval for special leave requests when the operator is set to Steps (see parameter Special Leave Approval Operator).

In this two-step approval process, the request is reviewed consecutively by two parties – the line manager and the HR department.
The parameters A_SPECIAL_ABSENCE_APPROVAL_GROUP_SETTING_1 and A_SPECIAL_ABSENCE_APPROVAL_GROUP_SETTING_2 specify which group approves first and which one follows.

Functionality:

  • The value 1 represents the line manager.

  • The value 2 represents the HR department.

Both parameters must be configured to form a clear approval sequence:

  • Example 1:

    • A_SPECIAL_ABSENCE_APPROVAL_GROUP_SETTING_1 = 2

    • A_SPECIAL_ABSENCE_APPROVAL_GROUP_SETTING_2 = 1
      → HR approves first, then the line manager.

  • Example 2:

    • A_SPECIAL_ABSENCE_APPROVAL_GROUP_SETTING_1 = 1

    • A_SPECIAL_ABSENCE_APPROVAL_GROUP_SETTING_2 = 2
      → Line manager approves first, then the HR department.

This configuration allows each organization to tailor the approval workflow according to its internal processes or data protection requirements.

Example:
An employee applies for special leave for a wedding.
The system is set to operator Steps, and the parameters are configured as follows:

  • A_SPECIAL_ABSENCE_APPROVAL_GROUP_SETTING_1 = 2

  • A_SPECIAL_ABSENCE_APPROVAL_GROUP_SETTING_2 = 1
    → The request is first sent to the HR department for document verification, and then to the line manager for final approval.

_______________________________________________________________________________

Special Leave Upload Document Mandatory

Technical Name: A_SPECIAL_ABSENCE_DOCUMENT_UPLOAD_MANDATORY
Type: Boolean (Yes/No)
Default Value: No

This parameter defines whether employees are required to upload a document when submitting a Special Leave request.

When enabled, a Special Leave request cannot be submitted without uploading a document.

This parameter only applies when an active SharePoint integration is configured.

Example:
YES: The employee must upload a document when submitting the Special Leave request.

_______________________________________________________________________________

Vacation – Special Phases with Deduction Logic

Additional Vacation Phases BA–BJ

In addition to the standard annual vacation entitlement and the Carry Over Phase, additional vacation phases BA through BJ are available.

These phases are used to manage additional vacation entitlements with their own validity period and priority. A total of ten additional phases are available:

BA, BB, BC, BD, BE, BF, BG, BH, BI, and BJ

When each phase is created, a standard entitlement of 2 PT (person-days) is automatically assigned to the phase.

Each phase is controlled by four parameters:

  • Enable Phase: Defines whether the respective phase is active and used.
  • Phase Start: Defines the date from which the entitlement assigned to the phase is valid.
  • Phase End: Defines the date until which the entitlement assigned to the phase is valid.
  • Phase Priority: Defines the order in which the entitlement is deducted in relation to other vacation entitlements that are valid at the same time.

The priority is defined by a number. A lower priority number is considered before a higher priority number. The priority only applies within the validity period defined for the respective entitlement.

Example:
The BA Phase is valid from January 1 through March 31 and has priority 0. The standard annual vacation entitlement is valid during the same period and has priority 1.
→ For a vacation request within this period, the available entitlement from the BA Phase is deducted first. Once this entitlement has been used, the standard annual vacation entitlement is deducted.

Technical Parameters

BA Phase

  • A_BA_PHASES
  • A_BA_PHASE_START
  • A_BA_PHASE_END
  • A_BA_PHASE_PRIORITY

BB Phase

  • A_BB_PHASES
  • A_BB_PHASE_START
  • A_BB_PHASE_END
  • A_BB_PHASE_PRIORITY

BC Phase

  • A_BC_PHASES
  • A_BC_PHASE_START
  • A_BC_PHASE_END
  • A_BC_PHASE_PRIORITY

BD Phase

  • A_BD_PHASES
  • A_BD_PHASE_START
  • A_BD_PHASE_END
  • A_BD_PHASE_PRIORITY

BE Phase

  • A_BE_PHASES
  • A_BE_PHASE_START
  • A_BE_PHASE_END
  • A_BE_PHASE_PRIORITY

BF Phase

  • A_BF_PHASES
  • A_BF_PHASE_START
  • A_BF_PHASE_END
  • A_BF_PHASE_PRIORITY

BG Phase

  • A_BG_PHASES
  • A_BG_PHASE_START
  • A_BG_PHASE_END
  • A_BG_PHASE_PRIORITY

BH Phase

  • A_BH_PHASES
  • A_BH_PHASE_START
  • A_BH_PHASE_END
  • A_BH_PHASE_PRIORITY

BI Phase

  • A_BI_PHASES
  • A_BI_PHASE_START
  • A_BI_PHASE_END
  • A_BI_PHASE_PRIORITY

BJ Phase

  • A_BJ_PHASES
  • A_BJ_PHASE_START
  • A_BJ_PHASE_END
  • A_BJ_PHASE_PRIORITY

_________________________________________________________

Absence - Work Time Model

Work Time Model – Working Days per Week

Technical Name: AZ_WORKING_DAYS_PER_WEEK
Type: Days
Default Value: No

This parameter defines how many days per week an employee is present at work.

Example:
An entry of 5 days means that the employee works 5 days per week.

_______________________________________________________________________________

Work Time Model – Working Hours per Week

Technical Name: AZ_WORK_HOURS_PER_WEEK
Type: Hours
Default Value: No

This parameter defines how many hours per week an employee is present at work.

Example:
An entry of 35 hours means that the employee works 35 hours per week.

_______________________________________________________________________________

Work Time Model – Planning Horizon for the Work Time Model

Technical Name: AZ_YEARS_TO_INITIALIZE
Type: Number
Default Value: No

This parameter defines how many years into the future the work time model is created for an employee. The initialization takes place when the contract is assigned for the first time.

Example:
An entry of 4 means that 4 years are created: the current year plus the following 3 years.

_______________________________________________________________________________

Work Time Model – Working Hours Monday

Technical Name: AZ_WORKHOURS_1_MONDAY
Type: Hours
Default Value: No

This parameter defines how many hours an employee is present at work on Monday. If the employee does not work on Mondays, the value is set to 0.

Example:
An entry of 4 means that the employee works 4 hours on Monday.

_______________________________________________________________________________

Work Time Model – Working Hours Tuesday

Technical Name: AZ_WORKHOURS_2_TUESDAY
Type: Hours
Default Value: No

This parameter defines how many hours an employee is present at work on Tuesday. If the employee does not work on Tuesdays, the value is set to 0.

Example:
An entry of 4 means that the employee works 4 hours on Tuesday.

 

_______________________________________________________________________________

Work Time Model – Working Hours Wednesday

Technical Name: AZ_WORKHOURS_3_WEDNESDAY
Type: Hours
Default Value: No

This parameter defines how many hours an employee is present at work on Wednesday. If the employee does not work on Wednesdays, the value is set to 0.

Example:
An entry of 4 means that the employee works 4 hours on Wednesday.

 

_______________________________________________________________________________

Work Time Model – Working Hours Thursday

Technical Name: AZ_WORKHOURS_4_THURSDAY
Type: Hours
Default Value: No

This parameter defines how many hours an employee is present at work on Thursday. If the employee does not work on Thursdays, the value is set to 0.

Example:
An entry of 4 means that the employee works 4 hours on Thursday.

______________________________________________________________________________

Work Time Model – Working Hours Friday

Technical Name: AZ_WORKHOURS_5_FRIDAY
Type: Hours
Default Value: No

This parameter defines how many hours an employee is present at work on Friday. If the employee does not work on Fridays, the value is set to 0.

Example:
An entry of 4 means that the employee works 4 hours on Friday.

 

_______________________________________________________________________________

Work Time Model – Overtime Allowed

Technical Name: AZ_IS_OVERTIME_ALLOWED
Type: Boolean (Yes/No)
Default Value: No

This parameter defines whether an employee is allowed to work overtime.

Example:
Yes: More than the defined daily working hours may be recorded.
No: Recording more than the defined daily working hours is not permitted.

 

_______________________________________________________________________________

Work Time Model – Maximum Daily Working Hours

Technical Name: AZ_MAX_DAILY_WORKED_HOURS
Type: Number
Default Value: No

This parameter defines the maximum number of hours an employee is allowed to record per day.

Example:
A configured value of 10 means that the employee can record a maximum of 10 hours per day.

 

_______________________________________________________________________________

Work Time Model – Overtime Rule

Technical Name: AZ_MAX_DAILY_WORKED_HOURS_ENFORCE
Type: Boolean (Yes/No)
Default Value: No

This parameter defines how exceeding the maximum daily working hours is handled. If the maximum is exceeded, either a warning is displayed or exceeding the limit is prohibited.

Example:
Yes: It is not possible to record more than the configured maximum number of hours.
No: More than the configured maximum number of hours may be recorded, but a warning is displayed.

 

_______________________________________________________________________________

Work Time Model – Time in Lieu Entry

Technical Name: AZ_IS_TIME_IN_LIEU_ALLOWED
Type: Boolean (Yes/No)
Default Value: No

This parameter defines whether an employee is allowed to enter time in lieu.

Example:
Yes: Entering time in lieu is permitted.

 

_______________________________________________________________________________

Work Time Model – Break Rule – First Break Threshold

Technical Name: AZ_FIRST_THRESHOLD_BREAK_HOURS
Type: Number
Default Value: No

This parameter defines after how many working hours the first break must be taken.

Example:
A configured value of 6 means that after the first 6 hours of attendance, a break is entered automatically.

 

_______________________________________________________________________________

Work Time Model – Break Rule – Duration of the First Break

Technical Name: AZ_FIRST_THRESHOLD_BREAK_DURATION
Type: Number
Default Value: No

This parameter defines the duration of the first break when the employee meets the first break threshold.

Example:
A configured value of 30 means that once the employee meets the first break threshold, a 30-minute break is entered.

 

_______________________________________________________________________________

Work Time Model – Break Rule – First Break Is Mandatory

Technical Name: AZ_FIRST_THRESHOLD_BREAK_MANDATORY
Type: Boolean (Yes/No)
Default Value: No

This parameter defines whether the first break is mandatory.

Example:
Yes: The configured break minutes are included in the attendance time.
No: The configured break minutes are not included in the attendance time.

 

_______________________________________________________________________________

Work Time Model – Break Rule – Second Break Threshold

Technical Name: AZ_SECOND_THRESHOLD_BREAK_HOURS
Type: Number
Default Value: No

This parameter defines after how many working hours the second break must be taken.

Example:
A configured value of 8 means that after the first 8 hours of attendance, a break is entered automatically.

 

_______________________________________________________________________________

Work Time Model – Break Rule – Duration of the Second Break

Technical Name: AZ_SECOND_THRESHOLD_BREAK_DURATION
Type: Number
Default Value: No

This parameter defines the duration of the second break when the employee meets the second break threshold.

Example:
A configured value of 60 means that once the employee meets the second break threshold, a 60-minute break is entered.

 

_______________________________________________________________________________

Work Time Model – Break Rule – Second Break Is Mandatory

Technical Name: AZ_SECOND_THRESHOLD_BREAK_MANDATORY
Type: Boolean (Yes/No)
Default Value: No

This parameter defines whether the second break is mandatory.

Example:
Yes: The configured break minutes are included in the attendance time.
No: The configured break minutes are not included in the attendance time.

_______________________________________________________________________________

Skill Management – Approval Process

Technical Name: SK_ASSIGN_APPROVAL_REQUIRED
Type: Boolean (Yes/No)
Default Value: No

This parameter activates the approval process for Skill Management. When enabled, skills cannot be assigned directly to employees by the employees themselves or by their supervisors.

Example:
Yes: Skill assignments require the complete approval process.
No: No approval process is activated.