TimePunch 3.6

Download

Standalone Version:http://www.timepunch.de/download/TimePunch_3.6.211.0.exe
Server Version:http://www.timepunch.de/download/server360/TpAppServer_3.6.208.0.exe

Finally it’s time: TimePunch 3.6 is online!

The following features were implemented in the application server:

  • FS#1005 – Multi-client capability
    As of TimePunch 3.6, it is possible to run multiple clients on a single application server. Thus different companies can be installed and administered independently on one server. This is important when several companies share the same IT infrastructure.
    The subitems FS#742, FS#968, FS#1006 to FS#1014 also belong to this point.

The following features were implemented in the management module:

  • FS#1003 – New payment method: Wages paid up to max. hours
    Starting from this version, the hourly wage can also be paid up to a maximum number of hours. If the employee works less than the maximum number of hours, he or she is paid only the number of hours that he or she worked.
  • FS#1032 – Pause bookings also without target time
    In TimePunch TEN, the mandatory break can now also be stored for days without an explicit target time. This means that the mandatory break can also be booked on Saturdays or Sundays, for example.
  • FS#1031 – Export to DATEV wage and salary with monthly data
    To standardize the data export, the monthly data is exported to DATEV Wages and Salaries instead of the daily data from this version on.
  • FS#1019 – Display of the current daily working time
    The current time entry for the current day is now also added to the analysis in the “Working time on” field.
  • FS#1016 – Illegal import of time data
    When importing time data from a CSV file, the system now also checks whether the imported data lies within the permissible booking frame of the project.
  • FS#1004 – Working time posting to previous project (TP TEN)
    For TimePunch TEN, it is now also possible to book working time bookings at the terminal for the last selected project. Thus, activities started at the studio, after a break at the terminal, can be continued without selecting the project again.

The following errors were fixed in the Datafox module/cutter module:

  • FS#1033 – Zombie Transaction
    For customers the Datafox Service and/or the Cutter Service was partially terminated without motivation. The problem was a zombie transaction that caused the service to crash. This problem has now been fixed.

Comments are closed.