The following issues have been fixed:
-
Stability improvement
The current version contains general stability improvements.
The patch can be installed within the TimePunch Application Server.
Read MoreThe following issues have been fixed:
The current version contains general stability improvements.
The patch can be installed within the TimePunch Application Server.
Read MoreThe following issues have been fixed:
In the current version it was not possible to create new leave requests with the pure online license. This problem has been fixed.
The patch can be installed within the TimePunch Application Server.
Read MoreThe following issues have been fixed:
Filtering of projects, tasks and customers has been improved. With the current patch, individual text passages within the selection are also found during the search.
If a project has only one task to choose from, this task is displayed by default after the project has been selected.
Until now, the customer’s default settings for a project were not correctly applied in TimePunch Online. This problem has been fixed. If a customer is pre-set in the project, this is also taken over during the project selection.
The patch can be installed within the TimePunch Application Server.
Read MoreThe following issues have been fixed:
If half a working day has been requested (i. e. seminar or similar) by an employee, a whole day has been written into TimePunch at the time of approval. This problem is fixed with the current patch.
For leave requests, the end date is now preset according to the start date. If the employee selects a leave with start on 07/23, the end date is also selected on this day. This simplifies the selection of holidays and makes the selection more intuitive.
The patch can be installed within the TimePunch Application Server.
Read MoreThe following issues have been fixed:
In version 3.1 of the cutter, the database check indicated an inconsistent database state. This problem only occurred when the server was completely reinstalled. The problem is fixed with the current patch.
The patch can be installed within the TimePunch Application Server.
Read MoreToday we release the new module version, the TimePunch Cutter v3.1.
The new version brings improvements in functionality and flexibility.
The following points have been implemented
The framework time model can now be assigned a transitional period in which the working time model is valid. This increases the flexibility of the model, since it is now possible to implement frame times that are only valid for certain periods of time.
As an example, the frame time from 7:00 to 16:30 + 30 min. transition could be defined. A reduction is only made if the employee stamps “check out” between 4:30 pm and 5:00 pm.
This variant also allows individual rounding settings, e. g. using frame time intervals or cascades.
In the new version, different frame time models can be implemented per weekday. This makes it possible, for example, for employees to work overtime from Monday to Thursday, so that they can start the weekend earlier on Fridays.
The following issues have been fixed:
This patch for TimePunch Studio Module 3.0 eliminates minor issues that have occurred in different installations.
The following issues have been fixed:
TimePunch Cutter 1.95 – Fixed
The following issues have been fixed:
The second break booking did not take into account the break time of the first break. I. e. the second pause might have been booked too early.
Following features have been added:
The mathematical rounding of time stamping times in TimePunch TEN has been changed to an employer-friendly rounding.
In order to implement an employee-friendly regulation if desired, it was possible to specify a waiting period. If the employee logs on or off within this time, the logon or logoff time is rounded to his or her favor.