Skip to content

20251124.2 (EN)

New Feature

FTE Demand Counting

Demands can now be managed based on FTE (Full Time Equivalent) . By default, one FTE equals 8 working hours, however, this value can be adjusted client-specifically.

With this counting method, demands can be represented more flexibly:
For example, a demand of 3 FTE  can also be covered by four part-time employees each working 6 hours . This allows for even more demand-oriented scheduling of full-time and part-time employees.

Due to the underlying logic, the FTE counting method is exclusively available for full-day demands on shift or shift type .

Improvements

Improved Header Summary Controls in Scheduler

The header summary display options in the scheduler have been clearly separated and enhanced. The settings menu now provides two independent controls:

  • Show headcount summary in header

  • Show FTE summary in header

Full-day view:
Both summaries can be enabled independently — headcount, FTE, or both.

Intra-day view:
The display is based on a headcount-style ratio. Either option (headcount or FTE) enables the display, but no dedicated FTE view is shown.

Dashboard: Live Update for Planning-Relevant Tiles

The dashboard now supports a live update for planning-relevant tiles. Changes in the planning are thus automatically displayed in the corresponding dashboard tiles, such as 'Present Employees' or 'Early Shift Employees', without manual refresh.

Role Permissions for Personnel Master Vacation Register

In the personnel master in the vacation register, the functions for annual vacation entitlements (add, update, delete) as well as the function "recalculate vacation account" are now controllable by permissions.

Optimization Personnel Master: Column Selection

In the personnel master, users can now make a individual column selection . The selected columns will be saved user-specifically, so that each user can permanently use his personal view.

Bug Fixes

Error in Creating a Standby Type

There could have been problems when creating new standby types if the underlying permission profiles were not configured appropriately. The behavior has been corrected so that standby types can be created with any configuration of permission profiles.