TimePunch Management 3.0.1107/1111.0

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.

The patch can be installed within the TimePunch Application Server.

Read More

TimePunch Server 3.0.1106/1111.0

The following issues have been fixed:

  • Provide the name for the Last Update By / Created By field in Reporting

    The employee name of the last update and the Created by could not be evaluated in the reports up to now. This problem has now been solved.

Download:
http://www.timepunch.de/download/server300/TpAppServer_3.0.1106.0.exe

Read More

TimePunch Cutter v3.1.1106.0

The following issues have been fixed:

  • FS#865 – Cutting on the date line

    When crossing the date line, the cutter could no longer correctly assign the working time model in some cases. This led to faulty cutting of the times. The problem is now solved.

  • The patch can be installed within the TimePunch Application Server.

    Read More

TimePunch Patch 3.0.1010.0

Download

http://www.timepunch.de/download/TimePunch_3.0.1010.0.exe

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

The following issues have been fixed:

  • FS#845 – Mandatory break in employment relationship “Pure working time”

    If the employment relationship is set to “Pure working time”, then no mandatory breaks may be calculated in TimePunch Core.

    Up to now, it was the case that a previously set mandatory break, after changing to “Pure working time” the mandatory break was nevertheless taken into account. This is not permitted in the “Pure working time” employment relationship and has therefore been corrected in the current release.

  • FS#846 – Changing the TimePunch API URL in the login screen

    The profiles were not reloaded when changing the TimePunch API URL in the login screen. This prevented the fast change of the TimePunch Server. This problem is now fixed.

  • Stability improvement

    The current version contains general stability improvements.

  • FS#849 – Project list does not report projects without booked times

    No projects for which no working time has yet been posted have been listed in the Project List report. This problem is now fixed.

Read More

TimePunch Server 3.0.1010.0

The following issues have been fixed:

  • FS#845 – Mandatory break in employment relationship “Pure working time”

    If the employment relationship is set to “Pure working time”, then no mandatory breaks may be calculated in TimePunch Core.

    Up to now, it was the case that a previously set mandatory break, after changing to “Pure working time” the mandatory break was nevertheless taken into account. This is not permitted in the “Pure working time” employment relationship and has therefore been corrected in the current release.

  • FS#849 – Project list does not report projects without booked times

    No projects for which no working time has yet been posted have been listed in the Project List report. This problem is now fixed.

Download des Servers:
http://www.timepunch.de/download/server300/TpAppServer_3.0.1010.0.exe

Read More

TimePunch Datafox 3.0.1010.0

The following issues have been fixed:

  • FS#802 – Start of time recording with last selected project

    In the Datafox module it is now not only possible to book the working time on a previously defined project, but also dynamically always on the last project used by the employee.

    This prevents the employee from logging off during the break and booking another project after the break.

    This scenario is especially useful for employees who combine the Datafox time recording terminal with the project booking of the Watcher or TimePunch Online.

  • FS#848 – Localization of balance display

    The balance display has been localized and now depends on the display language set in the server settings.

The patch can be installed within the TimePunch Application Server.

Read More

TimePunch Management 3.0.1010.0

The following issues have been fixed:

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

    In order to ensure greater transparency for the payroll of employees, bonus-relevant times will only be exported for months that have already been completed.
    This avoids the risk of overtime or similar payments in extrapolation, which need to be corrected in the following month.

  • FS#846 – Changing the TimePunch API URL in the login screen

    The profiles were not reloaded when changing the TimePunch API URL in the login screen. This prevented the fast change of the TimePunch Server. This problem is now fixed.

The patch can be installed within the TimePunch Application Server.

Read More

TimePunch Watcher 3.0.1010.0

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 More

TimePunch Calendar 3.0.927.0

The following issues have been fixed:

  • FS#837 – Leave requests with pure online module license not possible

    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 More

TimePunch Online v3.0.921.0

The following issues have been fixed:

  • FS#799 – Improved filtering of project, task and customer

    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.

  • FS#798 – Improved selection of the task when selecting projects

    If a project has only one task to choose from, this task is displayed by default after the project has been selected.

  • FS#797 – Preset customer is not taken over

    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 More
Page 3 of 30«12345»102030...Last »