Why upgrade to TimePunch 3.x?

TimePunch is constantly under development. The following list shows the most important features and innovations of the individual versions within the main version 3 of TimePunch.

TimePunch 3.3

In this version, the main focus was on security features and the usability of TimePunch in the web modules.

  • TimePunch now internally uses the integrated Windows authentication in all TimePunch modules. Within the domain, passwords are no longer required.
  • TimePunch now actively checks and informs about upcoming module and server updates. For this purpose, an e-mail address can be stored to which the corresponding info mails are sent.
  • Security features have been implemented to secure the operation of TimePunch on the Internet. These include the prevention of the administration login on the Internet, the locking of the account if the password is entered incorrectly several times, and the prevention of the tapping of employee data by the optional deactivation of the suggestion list for employee names.

TimePunch 3.2

To meet the requirements of the DSGVO and to increase the user-friendliness of TimePunch, we have implemented the following features:

  • The new report “GDPR information sheet” shows compactly which data about an employee is stored in TimePunch and which employees can access it.
  • The new role “Data Protection Officer” can be assigned to selected employees in TimePunch with version 3.2. The new role can therefore monitor compliance with the deletion deadlines, delete data, and call up the “GDPR information sheet” for all employees.
  • The update 3.2 gives the administrator or data protection officer the possibility to delete data after a certain period of time. For the first time, it is now possible to delete employee data in accordance with the requirements of the new GDPR.
  • With the update to TimePunch v3.2 you have for the first time the possibility to provide projects or orders with a barcode and to scan them by a barcode reader at the terminal or at the PC. For this purpose, a booking code can be stored for each master data record (employee, project, activity and customer) and then scanned and booked via a barcode reader in TimePunch Studio or Datafox Terminal.

TimePunch 3.1

The following features have been implemented:

  • The new version of the “TimePunch Cutter” module allows you to implement different framework time models per weekday. This makes it possible, for example, for employees to work overtime from Monday to Thursday in order to be able to start the weekend earlier on Fridays.
  • The framework time model can now be assigned a transition period in which the working time model is valid. This increases the flexibility of the model, since frame times can now be implemented that are only valid in certain periods.

    As an example, the frame time from 7:00 to 16:30 + 30 min. transition could be defined. A reduction only takes place if the employee stamps “Go” between 16:30 and 17:00 hours. With this variant, individual rounding settings, e.g. frame time intervals or cascades, are also possible.

TimePunch 3.0

The following features have been implemented:

  • The “TimePunch Watcher”, “TimePunch Studio” and “TimePunch Management” modules no longer require a separate installation – with TimePunch 3.0, the individual modules can be conveniently used anytime and anywhere via the website of the application server.
  • To make employee administration even easier for you, TimePunch 3.0 allows team and department managers to access employee working times directly and no longer need to use reports.
  • Holidays can also be displayed as regular working days with TimePunch 3.0. This makes it possible to record hours normally even when working regularly on public holidays and to remunerate them with a separate hourly wage if required.
  • To ensure that project management better reflects reality, TimePunch 3.0 no longer gives project managers change rights to all projects, but assigns them to their projects and then only allows them to edit them.
  • To simplify the handling of the reports, they no longer have to be reinstalled after each patch update, but simply remain in place.