The Recurrence component defines on which calendar dates a configuration applies.

It is used across AristoTelos configurations that require recurring calendar-based applicability. Instead of maintaining individual dates, users can define a regular pattern and adjust it for Public Holidays, specific dates, and a limited validity period.

The associated feature defines what the configuration represents, while Recurrence determines when it applies.

HOW RECURRENCE WORKS

A Recurrence combines several types of calendar rules:

Weekdays define the regular repeating pattern, such as Monday–Friday.

Public Holiday handling determines whether Working and Non-working

Public Holidays follow the regular weekday pattern, are included, or are excluded.

Specific date changes allow individual dates to override the regular pattern.

An Inclusion adds a date, while an Exception removes one.

Validity can limit the entire pattern to a defined period.

These rules are combined to produce the actual dates on which the associated configuration applies.

The Calendar and Resulting Days provide a preview of these dates, making it possible to verify the result before the recurrence is used by the associated configuration.

PUBLIC HOLIDAYS

Recurrence uses the organization's Public Holiday configuration to recognize Working and Non-working Public Holidays.

It does not define or classify Public Holidays itself. Instead, it determines how the associated configuration should behave when a Public Holiday occurs:

• Follow weekdays – the regular weekday pattern remains decisive.
• Exclude – the corresponding Public Holiday is removed from the applicable dates.
• Include – the corresponding Public Holiday is added even if its weekday is not normally applicable.

Working and Non-working Public Holidays can be handled differently within the same Recurrence.

For example, a Monday–Friday configuration can continue to apply on Working Public Holidays while automatically excluding Non-working Public Holidays.

INDIVIDUAL DATE CHANGES

Recurring patterns do not need to be changed because of individual calendar deviations.

For example, a configuration that normally applies Monday–Friday can:

• exclude one particular Wednesday using an Exception;
• include one particular Saturday using an Inclusion.

The underlying Monday–Friday pattern remains unchanged.

Individual changes can also be managed directly from the Calendar, providing a visual way to adjust exceptional dates.

TEMPORARY AND SEASONAL RECURRENCE

A Recurrence can have a defined Start and End, allowing the same recurring logic to be used only during a particular period.

For example, a seasonal configuration can apply Monday–Friday from 1 June to 31 August without affecting dates before or after that period.

This is useful for temporary operating schedules, seasonal rules, or other configurations that should repeat regularly only for a limited time.

USE ACROSS ARISTOTELOS

Recurrence is a shared component. The meaning of its resulting dates therefore depends on the configuration in which it is used.

For example, Recurrence can determine when a Time Off Type, Shift Template, Requirement, Activity Type, or another scheduling configuration applies.

This allows the same calendar logic to be used consistently across different areas of AristoTelos while each feature retains its own business behavior.

Content example

This sample document is designed to showcase various formatting styles and structural elements in a way that feels like a functional project brief.

Academy Overview

Navigation

Docs

Types

Docs look like this page, and they may have a content, which you are reading right now. It may be styled as

• bold
• italics
• underscores
• strikethroughs
• code

• quotes

There are also two ways of referencing other fields

1. links
2. tooltipsExample key-value-pairThis is an example keyValuePair