Synchronization to shift plan

The source-specific behavior on this page applies to the currently documented Czech eNeschopenka integration.

Creating and updating period time-off

A newly created or changed eNeschopenka can create or update the related period time-off.

The synchronization considers changes to:

• employee association;
• the start of the period time-off;
• the end of the period time-off; and
• the period time-off type.

A period time-off created from eNeschopenka remains linked to that eNeschopenka.

Administrator changes

An Administrator can change the start, end, or period time-off type of a linked period time-off.

When the Administrator changes one of these components, subsequent eNeschopenka updates no longer automatically update that same component:

• a changed start is no longer synchronized automatically;
• a changed end is no longer synchronized automatically; and
• a changed period time-off type is no longer synchronized automatically.

The three components are handled independently. A manual change to one component does not itself stop synchronization of the other components.

The Administrator can enable synchronization again in eNeschopenka administration.

Compatible period time-off

Before creating or updating the eNeschopenka period time-off, AristoTelos checks whether a compatible period time-off already exists.

Compatible period time-off starts on the same date and at the same time

The compatible period time-off is removed and a period time-off linked to eNeschopenka is created.

Compatible period time-off starts on the same date at a different time

When the compatible period time-off covers shifts, the start time of the eNeschopenka period time-off is adjusted to the compatible period time-off start time.

Automatic synchronization of the start is then disabled for the eNeschopenka.

Compatible period time-off starts earlier

When the compatible period time-off starts earlier and protects shifts before the eNeschopenka start, the earlier part remains in the shift plan and is shortened to cover those shifts.

When it does not protect shifts, the compatible period time-off is removed.

Compatible period time-off starts later

In an open roster period, the compatible period time-off is removed and the eNeschopenka period time-off is created.

If the gap before the compatible period time-off contains shifts, the result is recorded as a warning.

No compatible period time-off

When no compatible period time-off exists, the eNeschopenka period time-off is created in an open roster period.

If shifts are present, the result is recorded as a warning.

Finished roster periods

An eNeschopenka change that would hide or reveal shifts in a finished roster period is not applied automatically and requires manual resolution.

When no compatible period time-off exists and shifts are present in the affected finished roster period, the eNeschopenka period time-off is not created automatically.

When no shifts are affected, the eNeschopenka period time-off can still be created even if it overlaps a finished roster period.

An end-date change in a finished roster period can be applied when no shifts are affected by the changed part of the interval. If shifts are affected, the end-date change is not applied automatically.

An eNeschopenka that lies entirely in the past can still be added when it does not affect shifts in a finished roster period.

Shift-plan display

A period time-off linked to eNeschopenka is identified in the shift plan by an icon before the absence abbreviation.

Users with the required right can see the eNeschopenka number in the shift tooltip. The tooltip also shows whether the start, end, or period time-off type is not automatically synchronized.

Attendance closing

During attendance closing, the Manager is informed when the employee has sickness absence without a supporting document.

The message explains that the absence will be exported as unpaid sickness. Attendance can then be closed.

Employee contract end and extension

When an employee contract ends, linked period time-offs are ended with the employee contract.

When an existing employee contract is extended, a linked period time-off can be extended again if:

• it was previously ended with the employee contract;
• it is linked to eNeschopenka;
• the eNeschopenka ends after the original employee-contract end date; and
• synchronization of the period time-off end remains enabled.

If end synchronization is disabled, the linked period time-off is not extended automatically.

Shift-plan publishing and history

During shift-plan publishing, overlapping period time-offs are normally connected. This connection is not performed if one of the period time-offs is linked to eNeschopenka.

Changes to period time-offs create standard shift history. Changes to eNeschopenka information are recorded in the audit log.