WaspTime Upgrades and Patches

Back to Upgrades and Patches

 

 

WaspTime 6.1.14 Patch

6.1.14 - July 14, 2011 (Server: 4.1.10 Database: 6.1.0.3 Client: 6.1.14)
NOTE: This patch requires you to update each client and the server machine before the clients will connect to the server.

 

Bugs Fixed:

1. Added support for email servers using TSL/SSL on port 587. Now WaspTime supports both the implicit security mode on port 465 as well as port 587 for TSL/SSL email servers. Also fixed the test email dialog when the connection requires a user name and a password.
2. Fixed an issue where punches from previous week would be deleted as a result of an error in processing the user specific schedule.

 

Quick Details File Name: WaspTime6Patch.exe Version: 6.1.14 Date Published: 7/14/2011 Language: English Download Size: 29 MB

 

WaspTime 6.1.11 Patch

6.1.11 - May 11, 2011 (Server: 4.1.8 Database: 6.1.0.3 Client: 6.1.11)
NOTE: This patch requires you to update each client and the server machine before the clients will connect to the server.

 

Bugs Fixed:

1. Fixed the group and department selection combo boxes to properly filter the list of employees (Payroll Export window).
2. Fixed the Tardy report to take Grace settings correctly from Group’s settings. If a Penalty is set in Group’s settings the Tardy report no longer takes it into consideration, since the tardy report only makes it's computations based on the Grace Group’s settings only.
3. Fixed Schedule Override window to properly display the week data when previous or next buttons are used.
4. Fixed California Overtime processing of absences set as paid and not included in overtime calculation. 
5. Fixed ADP payroll export processing of absences marked as unpaid to not be included in ADP export files.
6. Fixed the host name / IP resolution to properly resolve IP/host name on the machine where wasptimeserver is installed.
7. Included a mechanism to filter punches coming from Biometric clocks that are flagged invalid because they occurred outside the specified allowed time intervals enforced on the Biometric clocks. To enable this feature a registry entry “AllowAllPunchStates” of type “REG_DWORD” and  value=0 needs to be present under the Options key in wasptime registry hive.
8. Fixed the issue when an employee group membership is changed to another group with a new group schedule so that the timecards are recalculated according to the new group schedule.
9. Fixed “Incomplete Absence Report” to correctly display “Didn’t show” according to group schedule settings.
10. Fixed the Import process of groups and employees from CSV files.
11. Fixed the “Custom Date Timecards” report parameters so that the report is showing data correctly.
12. Fixed the UI of timecard approval user interface when the pay period is bi-weekly and both weeks needs to be approved.
13. Fixed Sage50 payroll export to correctly include California Overtime in the exported hours.
14. Fixed the “Time Summary Details” report to not include inactive employees in the report.
15. Fixed the issues with filtering by department/group when processing holidays.
16. Fixed Tardy report to not include penalty settings. In the Group settings when a Penalty or Grace is selected, now only if a Grace amount is selected is included in the Tardy report calculations. Penalty amounts are not included in Tardy report calculations.
17. Fixed display issues in Schedule Override window display to accurately display the schedule override corresponding to the current selected week.
18. Fixed California overtime calculation to not include paid absence/vacation hours when the absence/vacation is configured to not be included in overtime calculation.
19. Fixed ADP Payroll export to not include unpaid absence time in the exported hours to ADP.

 

WaspTime 6.1.3 Patch

6.1.3 - December 10, 2010 (Server: 4.1.4 Database: 6.1.0.1 Client: 6.1.3)
NOTE:This patch requires you to update each client and the server machine before the clients will connect to the server.

 

Bugs Fixed:

1. If the pay period start date was changed, sometimes for bi-weekly pay periods only, depending on the new date selected the effective pay period start would be set a week earlier than the intended selected date.
2. Downloading punches from a biometric clock in some cases would return “Finished getting punches from the clock” showing “Retrieved 0 punches from the clock” when there are still punches on the clock to be downloaded.
   This has been corrected by polling for the biometric clock log data, and if after several tries the clock log data still cannot be retrieved an error message will be displayed and the error verbosely logged in the wasp time server log files.
3. Fixed the issue when a schedule is set from 12:00AM to 11:59PM every day, entering punches from biometric clock or PC Punch  in a day that is the first day of the week, would cause punches from the first day of the previous week to be deleted.
4. Added new payroll export type “PayChex / Sum Hours” which follows the same file format as the "PayChex / Time in a Box Export", instead we report the sum of the hours reported per pay code, per employee (example: total regular hours) instead of showing the hours and pay codes for each day in the pay period for every employee. This is recommended if groups use weekly overtime.
5. Fixed ADP payroll export so if there is an overtime 2 code, this will appear in the export file only when there are overtime 2 hours to be exported.
6. Fixed ping diagnostics to recognize ‘Destination Unreachable’ message when pinging an unused IP address. This was preventing users to assign the Wx100 clock an IP address outside the current subnet. This applies to Windows Vista and Windows 7 operating systems.
7. Fixed the case when absences submitted from the WaspTime webpage would show with the wrong color code in the timecards. Now, the WaspTime webpage is consistent with the WaspTime PC client timecards display.
8. Fixed the case when Salary group would display 12:00AM for all In/Out schedule entries after changing the pay period start date in System Setup.
9. Added more error checking for payroll export to QuickBooks to detect when the payroll codes are not imported properly or setup properly.

 

WaspTime 6.1.0 Patch

6.1.0 - July 22, 2009 (Server: 4.1.1 Database: 6.1.0.0 Client: 6.1.0)
NOTE: This patch requires you to update each client and the server machine before the clients will connect to the server.

 

This patch requires you to update each client and the server machine before the clients will connect to the server.

New Features:

1. If you are logged in as an admin, the reports that can be run for a manager now have all the managers in the list. This way an admin can run reports for any manager.

2. When an employee changes groups, the user is prompted for how many prior pay periods to apply the change.

3. A new Anniversary report was added that does not page break after each department.

4. A new group setting allows up to 60 minutes before a schedule starts or after the schedule ends as unpaid buffer. Employees who punch in within the buffer will get paid as if they punched in or out at the scheduled time.

5. Rounding can now happen after 0 minutes for in, out, break and meal rounding.

6. A new group setting allows up to 60 minutes of penalty for arriving late or leaving early.

7. There is now a new button on the Employee Security tab that removes all fingerprints from the database. This button causes prints to be deleted from the clock the next time a clock is updated through the BioUtility.

 

Bugs Fixed:

1. The Anniversary email will no longer include employees who are inactive, on leave or archived.

2. The Birthday email will no longer include employees who are inactive, on leave or archived.

3. The Reviews email will no longer include employees who are inactive, on leave or archived.

4. In some cases punches were not processed or processed in the wrong half of the day due to regional date time settings. This has been fixed. Older punches may not be corrected automatically but new punches will be correct.

5. The CSV Payroll export had an error showing multiple absences.

6. Inactive employees and archived employees were still getting pushed to the biometric clocks. Now when an employee is set to inactive they will be marked for deletion from the biometric clocks. Existing inactive and archived employees will be marked for deletion the next time the biometric utility updates a clock after the patch.

7. There was a problem storing some fingerprints to the database. The print would work on the clock it was recorded on but not on a new clock the print was pushed to. The bug is fixed but you will need to pull the prints for these employees from a clock that the print is working on again before sending it to the other clocks. This did not effect all prints.

8. ** Semi Monthly pay periods with the first day of the week also the last day of the pay period were not including the last day in the pay period totals. After the patch you can recalculate the employee's timecard that has this problem to get the correct totals.

9. The PayChoice payroll export has been updated to work better.

10. When an employee changes groups, the group schedule change was automatically applied to the previous pay period. Now the change only applies to the current pay period unless the user specifies more.

11. If for some reason the database\<instance name> slash is the wrong slash we detect it and fix it.

12. If the database name has (local)\<instance name> a log message is entered to help identify this problem.

13. ** When an absence or holiday was applied to a week with no time entered yet, the schedule was not entered properly and tardies and early in and late out was not properly calculated. The only way to fix this is to manually enter the schedule into the schedule override window on each time card. After the patch the schedules are properly maintained.

14. The default backup file name is now WaspTime6_<date>.bkp

15. Timecard by supervisor report was showing picked dates as the report range instead of the time period it was reporting. This report will show all days in the weeks indicated by the days you pick when opening the report. Time Summary and Time Summary Details had the same problem.

16. The employee list now saves your settings properly.

 

WaspTime 6.0 Upgrade

Released April 16, 2009
No patches or updates available at this time.

If you currently have WaspTime 5.x or earlier and would like to upgrade to version 6.0 please

 

 

WaspTime 5.5.2 Patch

5.5.2 - September 12, 2008 (Server: 3.7.0 Database: 5.5.0.0 Client: 5.5.2)
NOTE: This patch requires you to update each client and the server machine before the clients will connect to the server.

 

1. In some cases, punches on the last day of the week for overnight shift groups were being placed on the wrong day. After this patch is applied new punches will be put on the correct days.
2. Importing employees from QuickBooks after deleting the default group and department caused imported employees to not be visible in the employee list. This will no longer happen.
3. In the TimeCard if you had more punches for one day than could be shown in the window and you wanted to manually enter another one if you scrolled down and clicked on the next cell you would sometimes encounter a crash. This has been fixed.
4. Automatic clock time syncs, if done for all clocks, were always reporting that they failed even if they succeeded. WaspTime will now properly report success or failure of clock time syncs.

 

 

WaspTime 5.5.1 Patch

5.5.1 - August 28, 2008 (Server: 3.6.0 Database: 5.5.0.0 Client: 5.5.1)
NOTE: This patch requires you to update each client and the server machine before the clients will connect to the server.
 
The 5.5.0 patch caused groups that had no schedule to improperly report the day boundaries. This caused times to be put on the wrong days for employees in those groups with no schedule.
 
We are sorry for the problems this has caused. This patch fixes this issue for new punches after the patch is applied. Unfortunately this fix will not correct the timecards that already have punches on the wrong day. You will have to manually update each of those timecards. We apologize for this inconvenience.

 

1. Groups with no schedule will now properly place punches on the right day.

 

 

WaspTime 5.5.0 Patch

WaspTime 5.5.0 - August 12, 2008 (Server: 3.5.0 Database: 5.5.0.0 Client: 5.5.0)
NOTE: This patch requires you to update each client and the server machine before the clients will connect to the server.

 

1. Reports showing deleted absences have been fixed.
2. Additional checks have been put in place before the QuickBooks payroll export to check that the properly imported payroll codes are being used in groups.
3. Some versions of QuickBooks Canada are still not working properly. Due to the many different versions of QuickBooks we have put some additional messages in place to help us diagnose QuickBooks Export and Import problems.
4. If all absences for a day have been deleted, the timecard and timecard reports no longer show an absence code with no hours.
5. You can now add additional employee licenses to the standard version. Additional admin/manager licenses will also be accepted but can not be used until the version is upgraded to pro or enterprise.
6. A menu item in the clock setup called "Realtime" was a test feature and has been removed.
7. Improved Group scheduling to better handle schedules with large time differences from day to day.
8. Added a visual day calculator to the group schedule tab so you can see how a schedule will effect punches that come in from the clock or from PCPunch.
9. Moved the Regular payroll code selection box to the overtime tab.
10. The progress meter on the import wizard will now go away if the export fails.
11. In the Bio-Utility, when you enter the update clock window, you must select a clock from the list before any clock communication is done. Also at the end of the update, the clock selection is set back to none so you can select the next clock. This change should speed up multiple clock updates.
12 ** The ADP and CSV payroll exports were not totaling correctly if you used the new multiple absences feature. This has been corrected but you will want to check your payroll since the last patch. The errors tended to be in the employee's favor.
13. Makeup Time for California overtime compliance had a problem saving the data. It is now working again.
14. The Custom Date Timecard report was not calculating the dates to show properly if you only picked 7 days outside of your normal pay period. The report now properly shows times only within the dates you specify. It will still start the week on the same day as your normal timecards.

 

WaspTime 5.4.1 Patch

WaspTime 5.4.1 - June 20, 2008 (Server: 3.4.1 Database: 5.4.1 Client: 5.4.1)
NOTE: This patch requires you to update each client and the server machine before the clients will connect to the server.

 

1. **** FREE ENHANCEMENT: Each employee may now have multiple absences per day. This means that if an employee takes a half day of paid vacation and a half day of paid conference time, both can be added to the timecard for that day. The number of absences per day is unlimited.
2. The save button on the employee window is now properly enabled when you change the job title or the emergency contact information.
3. A bug that incorrectly calculated the pay period when the first day of the pay period was the last day of last month and was also the first day of the week was fixed. This bug only effected monthly and semi-monthly pay periods and did not effect payroll.
4. **** FREE ENHANCEMENT: Time zones have been added to clocks, the server, and employees. This allows WaspTime to handle clocks in multiple time zones. You will be asked to set a system time zone the first time you log in after the patch.
5. A bug was fixed in the calculation of the pay week that prevented certain timecard weeks from opening. This was causing the timecard window to fail to open.
6. Several reports have been modified to better serve semi-monthly pay periods. See below for the changes.
7. The payroll export window will now default to Last Period instead of This Period.
8. The employee now has a check box on the security tab called Never Export Payroll that will prevent this employee from being on the payroll export list.
9. A bug in the calculation of the overnight shifts that was preventing certain shift times from working has been fixed.
10. Fixed a bug where badge numbers with the same number but a different number of leading zeros (00140, 140) was preventing the list of employees from loading into the BioUtility. Badge numbers for biometric clocks can not have leading zeros.
11. Fixed a problem with the Edit Reports window that caused certain reports to fail to open after the name had been changed or they had been set to inactive.
12. Fixed a bug causing punches to fail to process due to regional date time settings being different than what SQL expects.
13. Fixed bugs in PCPunch that were causing the pay period and week date ranges to display improperly for semi-monthly and monthly users
14. Fixed a bug in PCPunch that caused the first day of the week to not get included in pay period totals when the first day of the week was also the first day of the pay period
15. PCPunch now includes absences time when displaying the daily, weekly and pay period totals. Only paid absence time is shown.
16. Absences default to 8 hours to help speed up absence input time.
17. The Clock on the main WaspTime window shows local time and server time if they are in different time zones.
18. Restoring a database from an older version of WaspTime v5 will update the restored database to the latest version.
19. The Biometric Utility was enhanced to better support multiple biometric clocks. See below for details.
20. Fixed a bug in the payroll export when using Export Only Scheduled Regular Hours for an overnight shift that caused no regular time to be exported.
21. Fixed a bug when using the arrow keys or tab to move around the timecard grid. Often you had to use the scroll bar to find the cell you were editing. Now if you change cells the scroll bar follows.
22. Fixed a bug when manually adding a bunch of times to one day in the timecard grid that caused the vertical scroll bar to disappear.
23. Absences can no longer be included in overtime if they are not paid. Existing absences will be changed to conform to this rule automatically.
 
Report Changes:
* Custom Date Timecards - Shows punches and daily totals for the days you specify. (Replaces the Raw Timecard Report)
* Weekly Timecards - Shows punches, daily totals and weekly totals for all days of all weeks around the dates you specify (Replaces the Timecard Report)
* Pay Period Timecards - Shows punches and daily totals for all days within the pay period you specify (New Report - solves semi-monthly report problems)
* Payroll Summary - Days outside the pay period will no longer be included in totals. The correct pay period dates must be specified.
* Vacation Report - Managers can now view their employee's time.
* Timecard By Supervisor - The Employee number no longer shows a comma separator.
* Absence Summary Report - This is a new report that shows the absences for an employee in a date range grouped by absence code. This report will help employers keep track of used employee vacation time.
* Roll Call report is now available at the manager login level
* Early out report - a calculation problem was preventing some employees who were leaving early from showing up on the report. This has been fixed and is retroactive.
* Absence reports have been updated to take the multiple absences per day feature into account.
* Overtime report works again with the % of worked hours and shows the proper number of days worked.
** NOTE: For all timecard reports that show Absence Code, if there is only once absence on a day or if all the absences for that day are the same code, that code will be shown. Otherwise the absence code for that day will show as "Mixed Codes"
** NOTE: There have been several requests for a report that shows the timecard with all punches for an entire pay period with totals. Due to current limitations of WaspTime this is not possible but we intend to correct this in a future version.
 
Biometric Utility Changes:
1. Add New User button has been removed from the main window because all employees are now automatically loaded into the list.
2. Refresh button has been removed from the main window for the same reason.
3. When the Bio Utility opens all employees who are not archived are added to the main window employee list
4. If the badge number has leading zeros (0123) he is not added to the list and can not be added until the leading 0s are removed. A popup message alerts the user of this when the app runs.
5. If a badge number is larger than the max badge number allowed the user is warned when the application opens and tries to add it.
6. When updating clocks the clock name and IP address are shown to make clock ID easier.
7. Some tool tips on the main window have been improved
8. A Select All button has been added to the action list when updating clocks.
9. A Deselect All button has been added to the action list when updating clocks.
10. When updating clocks if no action is required, those employee rows are hidden by default. There is a Show/Hide No Action button that toggles showing and hiding the No Action rows.
11. The Action grid is sorted by action when it first opens.
12. When updating clocks, when the user selects a row in the action list, some text above the list details what is going to happen considering the listed action
13. The bio utility user can now manually change the action in the action list when updating clocks
14. In the main screen an employee can be excluded from one or all biometric clocks. This means that if they are not already on the clock the bio utility to not add or update them.
15. A log file for each bio clock is placed in the common application folder that details the bio clock settings
16. In the main window only employees who are no longer in WaspTime can be deleted.
** NOTE: The Biometric Utility documentation has not been fully updated. It will be updated in the next full release.

 

 

 

WaspTime 5.3.0 Patch

WaspTime 5.3.0 - January 8, 2007 (Server: 3.3.0 Database: 5.2.0.0 Client: 5.3.0)
NOTE: This patch requires you to update each client and the server machine before the clients will connect to the server.

 

1. Fixed a bug in JobTrack that caused the punches to fail to post sometimes. The symptoms included punches taking a very long time to process or the client sometimes showing (not responding) or punches downloaded but not posted to JobTracking or WaspTime timecards.
2. Fixed an issue in the JobTrack rules that was causing slow calculation performance. JobTrack punch processing is faster.
3. Fixed a problem in the Groups where the Weekly Overtime Hours and Weekly Overtime 2 Hours were not saving the decimal portion of the input value.
4. Fixed a problem causing some incorrect log and user messages. Some startup error messages will now be more descriptive.
5. Raw Timecard Report - Added a timecard report that shows time for the exact dates specified instead of the pay period that includes the specified dates. This report does not have totals because we can not provide accurate totals for dates that do not match the specified pay period.
6. Fixed a problem where inactive QuickBooks Payroll Codes (Items), and Employees where being imported from QuickBooks.
7. Fixed a bug causing the employee and group grids to load slower and slower over time. Clicking the Clear Grid Settings button from the System Setup -> Options fixed the problem temporarily. It is fixed permanently in this patch.
8. Semi-Monthly pay period users no longer have the problem where pay periods with more weeks than the previous pay period do not properly display all days. This problem would cause the last partial week in the pay period to be absent in the timecards window. It did not effect payroll but prevented manual editing.
9. Semi-Monthly pay period users can now use the previous pay period button to see all pay periods. This bug was causing the timecards window to display no grid when the previous week button was pressed. This also caused a crash sometimes when clicking next employee. This bug did not effect payroll it just made manual editing impossible for previous pay periods.
10. The serial number is now automatically populated into the registration page when the link to activate is pressed.
11. The number of days allowed for the trial / demo evaluation was increased to 30
12. The FRED (Fingerprint Reader Enrollment Device) can now be installed and used on Vista. The driver must be installed separately from the CD \E100 Directory. Run setup.exe.

NOTE: It has been noted that Semi-Monthly pay period reports need some changes. These changes are being made but did not make it into this patch. The Raw Timecard report did make it into this patch and there are more to come. The others will be released soon. Thank you for your patience on this issue.

 

WaspTime 5.2.1 Patch

WaspTime 5.2.1 Patch addresses the following issues:
1) Reports will now pick up your default printer settings and try to use them despite the settings sent to them.
2) Scheduling a download from all clocks now properly reports success.
3) Deleting or archiving employees then reusing their badge number no longer causes problems when processing punches.
4) Schedule Override now properly allows you to set the override back to the group schedule time.
5) Grid settings are cleared when each patch is installed to avoid errors in grids after a patch.
6) Biometric Utility - Added progress meters so you can see progress of clock updates.
7) Biometric Utility - Deleting users from the clock will no longer delete the user from the database. You must delete users from the first Biometric Utility before updating clocks to get the utility to delete the user.
8) Biometric Utility - After you use the clock option Clear All Data the next time you use the Biometric Utility it will push all the data back to the clock.
9) Biometric Utility - The Update Clock window no longer closes after one clock is updated.
10) Fixed a problem in the Wage Report when trying to run the report including weeks that have no time the rate and wage would be 0 even if some of the days had time.
11) Some punches were not getting processed as soon as they were downloaded from the clocks. This issue has been fixed. The punches were processed on the next download.
12) Fixed a problem causing payroll Codes that were numeric only to get exported in the payroll export incorrectly.
13) Added a button in Settings -> Options to reset the grids to defaults. For instance if you hide columns on the employee grid, you can use this button to put them back. This button causes all client users to be reset.
14) Added an option to the Settings -> Options to turn off the automatic check for updates when the program starts. This setting is set for each user.
15) Fixed a bug that caused manual punches to be deleted under some conditions when new punches were downloaded.
16) ** Fixed a problem calculating overnight boundaries that was causing punches outside the overnight schedule to be placed on the wrong day. If you were asked to put in schedule times even on days that your employees did not work you can now remove them.
17) Fixed an issue that allowed more than 24 hours to be recorded when absence time and overnight rules were involved.

NOTE: In the Biometric Utility the update clock window only updates one clock at a time. You must select each clock from the list one at a time and update each one.

Known Issues: The FRED for the Biometric Clock system will not install on Vista. You can use it on any other supported operating system. We hope to have a working Vista driver soon.

 

 

WaspTime 5.2 Patch

***** WaspTime Enterprise is now available. This version is installed on your existing SQL Server and will then allow as many concurrent connections as your server is licensed for. The current WaspTime Pro allows 5 concurrent connections. Upgrade licenses and conversion instructions from www.waspbarcode.com.

WaspTime 5.2 Patch addresses the following issues:
1) PCPunch now properly searches for the Time Server if it is not found.
2) The bio-utility properly detects the presence of a FRED when it first opens.
3) When exporting payroll to QuickBooks, WaspTime will now show a useful warning if QuickBooks is not set up to take payroll export or if an employee is not set up to take payroll export.
4) The payroll summary report properly sorts by employee name.
5) PCPunch properly displays the In / Out status of the employee.
6) For new installs, the clocks are now set up to allow auto-polling on install. For existing installs go to Clocks->Options->Server Settings and change Auto Polling to True.
7) Documentation updates were made to remove some incorrect information carried over from WaspTime 4.
8) Fixed a problem when installing on a drive other than C:
9) Failed logins no longer add the name of the last person who failed to log in to the title bar.
10) Custom payroll export now exports time for all the selected days. Note: California overtime will not total properly if partial weeks are exported.
11) The Birthday list and Anniversary list reports now show all the employees that are active and who do not have a termination date.
12) Fixed a bug in restore database.
13) Fixed additional misspellings and grammar errors.
14) Semi-Monthly pay period now properly calculates if the end of the second pay period is on the last day of the month.
15) The Overtime and Incomplete Timecard reports now allow entry of a date range.
16) The employee demographics report now shows all active employees.
17) The text on the report list now properly reflects the actions of the Active check box.
18) All reports that show Wage or hours now properly handle the "California And" overtime method. This means the reports may not total if you add up the columns and rows but the totals are correct.

 

WaspTime 5.1 Patch

WaspTime 5.1 Patch is now available. This patch has some critical fixes in it that you need for proper operation of WaspTime. Install the patch on every machine that has a WaspTime, JobTrack, PCPunch or BioUtility client and on the machine with the Time Server.
** Bugs that were fixed that may effect payroll totals.

WaspTime 5.1 Patch addresses the following issues:
1) Fixed the problem preventing reports from printing from the timecard print button.
2) ***** Free Enhancement: The Pro version now allows more than 5 manager licenses to be installed. Only 5 managers or admins can be logged into the application at one time. Additional Admin/Manager licenses may be purchased separately in packs of 5 or 1.
3) When using the Logout menu option the user is now removed from the list of logged in employees freeing that license and allowing another person to log in.
4) Several small user interface issues like formatting, wrong labels on grids and incorrect or incomplete wording have been corrected.
5) Fixed a problem where timecard adjustments were showing up more than once in the adjustments list. They were only being applied once but recorded multiple times. This error did not effect actual time totals. To fix this for a past pay period you must force the pay period to recalculate by making a manual change to each timecard, downloading a time for each employee or making a change to a group and applying that change to the pay period.
6) * Fixed a problem with overtime override introduced in v5.0.0 that caused the group overtime all and none settings to be ignored for any pay period where the overtime override window was opened and saved. The next time the pay period is calculated after the 5.1 patch the totals will be correct. If the overtime override window was not opened and saved the override all settings should be fine.
7) Fixed a problem with the adjustments window where the adjustment time was reported incorrectly. The calculations were deducting the correct amounts but the adjustments window was displaying the incorrect amount.
8) * Unpaid absences were being subtracted from ADP and CSV payroll export regular time. This has been fixed but may have effected payroll exports.
9) * Fixed a problem with the schedules that may have caused times to get put on the wrong day. This would have been most pronounced for overnight shifts. After the patch no action is needed to fix times going forward but any old times that are incorrect must be manually fixed for each timecard. There is a script to repost punches if you have many. Call support for details on how to use this script.
10) Fixed a problem in the Process Holidays screen that incorrectly reported that a holiday on the first or last day of a pay period was not part of the pay period.
11) The Timecard report must report on whole weeks. If you input dates that are not exactly multiples of 7 the program will round up to the nearest week.
12) The Timecard report is now sorted by last name, first name, middle initial then employee number.
13) Fixed a bug preventing processing of reused badge numbers.
14) * Grace for Shift Out is now working properly.

• Barcode Software
• Barcode Scanners
• Barcode Printers
• Mobile Computers
• Time and Attendance
• Point of Sale (POS) Systems
• Asset Tracking
• Inventory Tracking