by kathryn@timeclockmts.com | May 25, 2009 | New Releases, News
A minor release today with just one fix. I’ve finally tracked down and fixed a bug that caused the last clock in/out details for the selected employee to not display properly. There was a reasonably complex sequence of steps you had to make to actually get the bug to show up and it’s taken me a while to figure out what those steps were. Finally pinned them down and fixed up the problem. It was a display only problem and didn’t effect the data being recorded, despite what the screen said!
by kathryn@timeclockmts.com | May 3, 2009 | New Releases, News
I’ve just released version 2.2.12 of the software. This version contains some new logging and a new report. When an employee clocks in or out Time Clock MTS now records the Network Name and the Network Card MAC address of the computer along with the time data. There’s also a new payroll report (the Time Location Report) that displays this information along with each time. The idea behind this report is to allow administrators to detect any odd clocking behavior among employees. For example, if your employees are supposed to clock in and out from their own computers and one employee consistently clocks in an out from another PC then there may be some buddy punching happening.
For more detailed information covering the application of this new feature please read this how-to article.
by kathryn@timeclockmts.com | May 1, 2009 | New Releases, News
A small release today fixing up a couple of issues and adding some formatting to a couple of reports.
- Employees on a fortnightly salary period had their hours calculated incorrectly. This is now fixed up.
- If you unchecked all of the employees on the report configuration screen and then tried to run a report by department or shift an incorrect warning was displayed and you could not run the report. This is now fixed.
- The minimize button on the report display screen has been de-activated. If you clicked on this it caused a hard crash.
- The punchard and detailed punch card reports now have blocks of data separated by weeks. This is just to make for easier reading of the report.
by kathryn@timeclockmts.com | Apr 21, 2009 | New Releases, News
A new minor release of Time Clock MTS today fixing up a few problems. Details of the fixes are below:
- Some fixes to the way resizing of the application window works. In some cases the bottom employee on the employee list wouldn’t be visible, I think this is because of the scroll bars appearing on the list of employees. This should be fixed up now, along with the maximize window button being disabled when you’re using the keypad interface.
- A fix to the mySQL database creation script, for some reason LONGTEXT fields were being set to VARCHAR(255). Now all fixed.
- Fix to all payroll reports where the monthly pay amount was more than $9,999.99. Wages now display and print correctly.
- Employees using the ‘View My Information’ button can no longer view the time location report and the departmental wages report.
Additionally, Time Clock MTS Version 2.3.1 (released about a month ago) included a fix for the shift restriction feature which was working for a long time and then stopped working.
by kathryn@timeclockmts.com | Apr 14, 2009 | New Releases, News
A couple of minor releases in the last few days fixing up some small problems and putting in some new logging code to try to track down some errors that have started surfacing for some reason.
Version 2.2.9
Fingerprint support was re-enabled and the method used to check for correct fingerprint driver installation was changed. This is the resolution to the hard crash that was fixed up in the last release. There were also a couple of minor feature changes including adding last 14 days selection to the edit times screen and allowing administrators to setup web camera image capture on a client by client basis.
Version 2.2.10
A fix to the type 13 mismatch error that was caused by the release of Version 2.2.10. I’ve also added a bunch of new logging code to try to track down why people are suddenly (and mysteriously) getting Element Not found Errors. This is particularly baffling because this area of the software has not been touched in well over a year.
