TimePunch Patch 3.3.405.0



This patch for TimePunch 3.3 fixes some minor problems that occurred during different installations.

The following issues have been fixed:

  • FS#919 – Profile change can lead to errors in the role of data protection officer

    When switching to another profile, an error was displayed to the data protection officer if the employee to whom the change was to be made had an active time entry running. This problem has been fixed with the current patch.

  • FS#921 – Working time models cannot be deleted

    In the current version it was no longer possible to delete once created working time models of an employee. This problem has also been solved.

  • FS#922 – Link to reset password was faulty

    If an employee has his password reset, a confirmation e-mail including a link to reset the password is sent to him. This link was generated incorrectly in several modules. This problem is now fixed.

Read More

TimePunch v3.3


Standalone Version:http://www.timepunch.de/download/TimePunch_3.3.314.1.exe
Server Version:http://www.timepunch.de/download/server330/TpAppServer_3.3.314.1.exe

Finally it’s time: TimePunch 3.3 is online!

The following features have been implemented:

  • FS#902 – Lock the account in case of multiple incorrect password inputs

    Starting with this version, the server has a new security feature that takes effect when a user tries to log on to the server as administrator with the wrong password several times in a row.

    In this case, the administration access is blocked and can only be activated via a confirmation link sent by the server to the deposited administrator.

    For more information see page 8 – Blocking the administration access (TimePunch-Server-3.3-en.pdf)

  • FS#840 – Notification if a module update is available

    The application server checks daily for new module updates of TimePunch from this version on. If a new update is available, an information mail is sent to the email address stored in the application server. This facilitates the administration of the server.

    For more information see page 23 – Update check (TimePunch-Server-3.3-en.pdf)

  • FS#836 – Login to administration from local network only

    Since more and more customers are using TimePunch via the Internet, we have added an option to protect the administration of the server against unwanted access via the Internet. In the future, it will only be possible to administer the server via the Internet with an explicit option.

    By default, the server only offers logon to the administration interface in the internal company network.

    For more information see page 24 – Login to application server (TimePunch-Server-3.3-en.pdf)

  • FS#835 – Mails with successful login on the administration page

    In order to directly detect unauthorized access to the administration side of TimePunch, the current version of Application Sever has the option of notifying the legitimate administrator immediately as soon as a user logs on to the administration side of TimePunch.

    This allows unauthorized access to be directly detected and tracked.

    For more information see page 24 – Login to the application server (TimePunch-Server-3.3-en.pdf)

  • FS#824 – Prompt when resetting the password

    In the current version, when resetting the password using the link “I forgot my password”, a security feature has been added that prevents employees from accidentally resetting the password of other employees.

    Before the password is actually reset, an email is sent to the employee concerned. The employee must first confirm the link contained in the email before the password is reset for him or her.

  • FS#823 – Integrated Windows Authentication

    TimePunch now also supports Windows integrated logon via the Active Directory. This means that employees within the company network are now automatically logged on to TimePunch Management and all TimePunch web modules without having to enter a separate password.

    For more information see page 20 – Automatic login with the help of the integrated Windows authentication (TimePunch-Server-3.3-en.pdf)

  • FS#820 – Module login without selection list of employees

    As a further security feature the possibility was implemented to have to log in directly via the user name. This prevents the suggestion list of employee names when typing in the first letters and thus the tapping of employee names by potential attackers. This option is useful if the server can be reached via the Internet.

    For more information see page 24 – TimePunch employee login (TimePunch-Server-3.3-en.pdf)

The following errors have been fixed:

  • FS#912 – Calculation of continued pay

    There were inconsistencies in the calculation of continued pay in special cases because overtime was not correctly included in the calculation. This problem has been solved in the current version.

  • FS#905 – Customer assignment during project import does not work

    If a customer reference was set in Excel for the projects to be imported, it was ignored when the data was imported. This problem is now solved.

  • FS#903 – click on the watcher icon does not open the watcher

    Due to an unfavourable arrangement of the Windows windows, the TimePunch Watcher became partially invisible when clicking on the icon of the TimePunch Watchers. This problem is corrected with the current version.

  • FS#900 – Exception: System.NullReferenceException

    In the TimePunch Watcher an exception error may have occurred. This was fixed in the current version.

  • FS#893 – DATEV export need automatic post calculation of monthly data

    To ensure that the export database to DATEV is always up-to-date, an automatic recalculation of the times is triggered in the current version before the export.

  • FS#831 – Module change not only in the App Server, but in all modules

    In the current version of TimePunch, it is possible to switch to other TimePunch modules installed on the server in each module. This was previously only possible via the detour of the application server.

  • FS#827 – automatic re-login

    The individual web modules of TimePunch now have an improved session handling, which automatically detects the course of a session and automatically forwards the user to the login page. This prevents errors caused by expired sessions.

  • FS#642 – Logon to new module destroyed or session of first module

    In the previous version of TimePunch only one module could be opened at a time. The start of the second module caused problems in the first module. This behavior was corrected. In the future, all modules can be opened and used multiple times by all employees.

Read More

TimePunch Release v3.2.602.0



This patch for TimePunch 3.2 fixes minor issues that have occurred in various installations.

The following problems have been fixed:

  • FS#898 – Integrated Windows Security and SSL

    Automatic login via Integrated Windows Security did not work correctly with the management module, the watcher and the Datafox module if the API was switched to SSL. This problem has now been solved.

  • FS#894 – Timeout at the autostart of TimePunch Watcher

    When the Watcher is started, employees are sometimes shown errors that prevent TimePunch from being started again. The problem could be traced back to a timeout that was fixed in the current patch.

  • FS#891 – Error quitting the watcher before logging in

    If the watcher was stopped before the employee actually logged on, an error message was also displayed. This problem has now also been solved.

Read More

TimePunch Patch 3.2.421.0



This patch for TimePunch 3.2 fixes minor issues that have occurred in various installations.

The following issues have been fixed:

  • Inconsistent database

    If several employees had the “Update” dialog open and the database was updated several times, the database went into an inconsistent state. With this patch, this problem is a thing of the past.

Read More

TimePunch Patch 3.2.404.0



This patch for TimePunch 3.2 fixes minor issues that have occurred in various installations.

The following issues have been fixed:

  • Overall stability improvements

    This fix contains stability improvements in all Windows Clients of TimePunch.

Read More

TimePunch Patch 3.2.329.0



This patch for TimePunch 3.2 fixes minor issues that have occurred in various installations.

The following issues have been fixed:

  • Employee selection in project reports

    The selection of employees was restricted in the original version of TimePunch 3.2, or not functional, since only the employee currently logged on was displayed. This problem has now been solved.

  • Applying the report filter

    The report filter set in TimePunch was not fully applied to a report. This problem has been resolved, especially with regard to the selected tasks. When tasks are filtered in TimePunch, this filter is also applied to a newly opened report.

  • FS#839 – DATEV Lodas Export – Extrapolation may not contain surcharges

    To ensure better transparency for the payment of wages to employees, times relevant to bonuses are only exported for months that have already elapsed.
    This prevents overtime etc. from being paid in the extrapolation, which will need to be corrected in the following month.

  • Revised error handling in TimePunch Watcher

    The error handling in TimePunch Watcher has been revised. This means that in case of a program error TimePunch handles it better and does not crash or get stuck.

Read More

TimePunch v3.2.325.2



TimePunch 3.2 is finally online!

The following Features have been implemented:

  • FS#828 – New Report “GDPR-Information Sheet”

    A new report “GDPR GDPR-Information Sheet” has been implemented in order to fulfil the obligation to provide information to employees. This contains information stored in TimePunch about each employee, concentrated on two pages.

    More information on page 70 – GDPR-Information Sheet (TimePunch-Client-3.2-en.pdf)

  • FS#830 – Possibility to delete data after a period of time

    The administrator or data protection officer can now delete employees’ time data from TimePunch after X years. TimePunch offers the possibility to delete data for historical employee data.

    More information on page 71 – Perform GDPRdata deletion (TimePunch-Client-3.2-en.pdf)

  • FS#829 – New role “Data Protection Officer” in TimePunch

    In TimePunch a new role was created, which will be the “Data Protection Officer”. The data protection officer has read access to all data within TimePunch. He can thus check compliance with the deletion deadlines and order data deletion, as well as execute the corresponding reports of the GDPR.

    More information on page 73 – Role of the Data Protection Officer (TimePunch-Client-3.2-en.pdf)

  • FS#878 – Enable project booking via Datafox Terminal

    Project bookings can also be made via the Datafox terminal with version 3.2. However, this requires a special device setup adapted to the customer. Optionally, a barcode reader connected to the terminal is also supported.

    If you are interested in this possibility, please send us a short message to support@timepunch-info.de

  • FS#879 – Support of a barcode reader in TimePunch Studio

    The TimePunch Studio module has been extended so that a connected barcode reader can be used for project booking. For this purpose, each master data record (employee, project, activity and customer) can be stored with a booking code and then scanned and booked via a barcode reader in TimePunch Studio.

    More information on page 74 – Booking code(TimePunch-Client-3.2-en.pdf)

  • FS#805 – No creation of projects/activities when importing time data

    This option prevents accidental creation of projects and/or activities when importing CSV time data.

    More information on page 107 – Employee settings (TimePunch-Client-3.2-en.pdf)

  • FS#806 – Free text field “Further billing modalities”

    In the project master data in the ” Accounting ” tab, another multiline free text field with the name “further accounting modalities” has been inserted. This can be used to record special project modalities. By default, the field is not used in any integrated report. However, it can be used to create customer-specific reports.

    More information on page 42 – Account-relevant data (TimePunch-Client-3.2-en.pdf)

  • FS#823 – Integrated Windows authentication

    In version 3.2 of TimePunch, the client modules can work together with the integrated Windows authentication. This allows a user to log in to TimePunch without entering a password. This works in the current version only with the Windows clients. We are currently working on a solution for the corresponding web modules.

    More information on page 15 – Authentication(TimePunch-Client-3.2-de.pdf)

  • FS#821 – Use of the external Windows State Service

    To prevent the problem of an early session timeout, the session state information is now kept in the external Windows State Service. This enables, for example, the use of the presence list on a pure display device, e.g. a wall monitor in the lounge.

  • FS#838 – Schleswig-Holstein and Hamburg get a new holiday

    Customers in Schleswig-Holstein and Hamburg will receive Reformation Day on October 31 as a regular holiday from 2018. The holidays will be added with this year’s update.

  • FS#850 – Project list contains no projects that cannot be booked

    In TimePunch, the problem was that projects that could not be booked were not listed in the “Project List” report. This affected projects for which the “Project cannot be booked” option was activated or to which no active employees were assigned. This problem has now been solved.

  • FS#868 – The need to change the password must be dispensed with

    The need to reassign the password as soon as the user name was changed often led to misunderstandings in the past. With version 3.2 it is no longer necessary to change the password if the user name is changed.

  • FS#880 – Integration of the Austrian Regions

    The Austrian regions are now integrated into TimePunch as standard. The change does not affect existing databases, but only applies to the creation of a new TimePunch database. This was chosen for compatibility with existing installations.

  • Read More

TimePunch Studio 3.0.1222.0

The following issues have been fixed:

  • FS#877 – Change of employee is no longer possible

    Due to an error in the current version, the employee could not be changed in TimePunch Studio. This problem is solved with the current patch.

The patch can be installed within the TimePunch Application Server.

Read More

TimePunch Patch 3.0.1122.0



This patch for TimePunch 3.0 eliminates minor issues that have occurred in different installations.

The following issues have been fixed:

  • FS#870 – Incorrect overtime calculation for vacation and 13 week average

    An error occurred when calculating overtime

    a) if the employee works on an “hourly rate”
    b) and in the options “final vacation pay for wage earners corresponds to the average earnings of the last 13 weeks”.
    c) and the wage payment has been stored with a fixed number of hours.

    In this case, the difference between target time and average earnings was not added to overtime. This can lead to a changed overtime calculation for the above case.

    The problem is solved with the current patch.

Read More

TimePunch Patch 3.0.1107/1111.0



This patch for TimePunch 3.0 eliminates minor issues that have occurred in different installations.

The following issues have been fixed:

  • FS#866 – Incorrect balance display in the project list and project status reports

    In certain situations, the balance display (remaining hours / traffic light) in the project reports was incorrect or inconsistent. This problem is solved with the current patch.

Read More
Page 2 of 30«12345»102030...Last »