Technical Support Blog

February 3, 2016

Virtual TimeClock 15 Review & Recap

In 2015 we released one major Virtual TimeClock upgrade and six significant maintenance releases throughout the year. The final release was made available on December 21, 2015. Virtual TimeClock upgrades are always free for customers enrolled in our software Maintenance & Support program. Non-enrolled registered users can always purchase an upgrade at 50% off.

It’s easy to miss important new features or fixes along the way. If you've already upgraded, or are planning to upgrade, here’s a recap of the new and improved features you’ll find in Virtual TimeClock 15:

SecurityWe added over a dozen security features in Virtual TimeClock 15. Database files are now encrypted by default. A new option to display text when entering passwords helps in troubleshooting wrong entries. Optional password rules can be enforced for user password length and strength. Connections for the Network Edition can now use TLS encryption.

Electronic Timecard ApprovalFor Pro and Network Edition users, we streamlined the payroll process with the option for employees and managers to electronically approve timecards. The addition of a new Payroll Approval dashboard (and Payroll Report) makes it easy to review timecard entries, export entries, and close the period.

Network AdministrationWe added several enhancements to make managing Virtual TimeClock Network Edition even easier. Mac administrators can now Add, Remove, or Restart the Server right from the Server Manager. A new option maintains administrator mode for each startup on administrative computers. Network Edition Administrators can now conveniently verify, compact, and reindex the TimeClock database from any Pro Client.

Other Enhancements

The default employee signature line for timecards to include meals/break acknowledgement. (Great for California Users!)

The In/Out Board now updates time and status when the TimeClock window is in the background.

We fixed an issue where deleting entries and inserting breaks in large databases was painfully slow.