Skip to main content

New Features in 4.61

Fingerprint Management for Webdesk Administrators​

It is now possible to authenticate at the kiosk tablet using a fingerprint as well. This requires a fingerprint scanner, which you can order from us. It is mounted in place of the previous NFC reader and takes over its login function.

To use the fingerprint scanner, the respective kiosk endpoint must be enabled. Please contact our support team for information about the exact configuration.

Once the fingerprint scanner is mounted and the kiosk has been restarted, the device is automatically in fingerprint mode.

After a finger is scanned, you will see either your usual kiosk page (e.g. when clocking in with an NFC chip) or a message that the fingerprint is unknown. In this case, kiosk administrators can log in with their user name and password to assign a fingerprint. Simply follow the instructions on the screen. Click "Finish" to confirm the assignment.

As a Webdesk administrator, you can view a person's fingerprint sets in their configuration. Next to the familiar "NFC" tab, there is now a new "Fingerprint" tab in which you can see all assigned fingerprint sets. If you open a set, you can also delete individual fingerprints from it. Currently, older sets are also stored (for historization). However, this historization may be discontinued in the future so that only the current set is retained.

Important note regarding GDPR:
The fingerprints themselves are not stored. The scanner generates a so-called hash, i.e. an encoded summary of the fingerprint data, directly in the device. Only this hash is stored in the system. For each authentication, only this hash value is compared. Real fingerprint data is therefore never stored or transmitted over the internet.

Improved Display of Field Groups in the Client Settings​

In a client's time tracking settings, the personal fields are now displayed in a much more structured and clearer way. Previously, there were only two unconnected lists (groups and fields) with no recognizable association.
With the new layout, it is now immediately visible which group each field belongs to. This makes administration considerably easier and provides a clearer presentation.

New Public API Interfaces​

This version provides three new API endpoints. They allow you to retrieve:

  • absences,

  • time entries, and

  • the current estimated working time of a person.

In addition, a further interface is currently being developed with which you can query the list of persons of a client. Once it is available, you can use this list of persons to retrieve the corresponding data from the system in a targeted way.

Regional Language Variants​

It is now possible to define regional sublanguages. This means, for example:

  • German (Germany), German (Austria), German (Switzerland)

  • English (British), English (American)

In the system, a language can be defined as the main language to which the sublanguage refers.
If a user uses a sublanguage, the system first loads the texts of this variant. If no module is available for a particular text, the text from the main language is automatically used.

New Progress Indicator in Travel Expense Reports​

The progress indicator in the travel expense report has been redesigned and is now particularly mobile-friendly.
It can now be operated with a swipe gesture. In addition, the display switches automatically when the "Next" button is used. The current step is highlighted in color so that it is always clear which processing step you are in.

SSO Login and Logout​

Two new parameters can now be defined per client in the "Options" tab that control the login and logout behavior when using SSO/SAML:

  • Application URL for SSO/SAML login
    If this parameter is set, a user is automatically redirected to the URL specified here after entering their user name. This should contain the login page of the respective SSO provider.

  • External URL for SSO/SAML logout
    If this parameter is set, the user is redirected to the specified link on logout instead of the default Webdesk login page.

This function is particularly relevant for Personalwolke customers who want to log in via SSO.