April 6, 2012
What we’ve been working on for this update: A much faster Daily View, Weekly View, and Today Page. Should load in around 2 – 4 seconds in most cases.
Request number 1152 (Attendance Copied)
The issue: When copying an employee’s scheduled shifts into their attendance (this is used for employees who don’t need to clock in, but their pay should be calculated in attendance costs), there was an issue while copying them nightly.
The fix: “Copied” Attendance entries work fine now, with no known issues!
Request number 1155 (New Upload Tool)
The issue: We needed a newer upload tool for uploading data.
The fix: Jose, Daniel, and Rodrigo built a beautiful data upload tool.
Request number 1155 (Scheduled Reports)
The issue: When scheduling reports to be automatically emailed to you, the subject line was ambiguous, so if you had several reports scheduled, you had no way of knowing which report you were opening until you opened it!
The fix: The name of the report is in the subject line of the email!
Request number 1204 (Admin Termination)
The issue: Occasionally, the account holder in TimeForge (the one who signed up for the account/ receives the “payment notification” emails) would terminate himself. If an account holder is terminated (this could only be done by the account holder), the account is no longer considered active, and all other employees would be unable to access the account – because there was no “accountable” person for the account.
The fix: If you are the account holder, you cannot terminate yourself. You must first give someone else the “account holder” responsibility, then you can terminate yourself.
Request number 1205 (IP Recording)
The issue: Some users would like to know from which IP addresses users who modify attendance are doing the modifying. Basically, if a user (who has been granted permission to modify attendance) is modifying attendance entries for an employee, management wants to know which IP address the user is modifying from – whether the “modifying” user is making changes from home or work, etc.
The fix: TimeForge now records the IP address of any changes made to attendance for auditing.
Request number 1210 (Department Payroll Approval)
The issue: Some users with departments were approving payroll with shifts that had no departments assigned to them. This can hinder payroll processing, depending on which payroll provider and export method you use.
The fix: You cannot approve payroll if you have departments and there are shifts that aren’t assigned to a department. Additionally, there are alerts on the Today page if this is the case.
Request number 1211 (POS Positions Sync)
The issue: Some POS systems were taking longer than we’d like to synchronize. This was caused by some tiny things that could be improved, like syncing all positions instead of just syncing the positions that have changed since the last sync. (If nothing has changed, there’s no reason to look for changes, right?)
The fix: Some of the POS systems can sync only the positions that have changed – making the sync faster!
Request number 1212 (POS Employees Sync)
The issue: Just like Request 1211, some POS systems were taking longer than we’d like to synchronize. This was caused by some tiny things that could be improved, like syncing all employees instead of just syncing the employees that have changed since the last sync. (If nothing has changed, there’s no reason to look for changes, right?)
The fix: Some of the POS systems can sync only the employees that have changed – making the sync faster!
Other items that we worked on:
Some customers were finding that when they tried to save Attendance Options, the page was “locking up” because of Bid Shift email settings. This should be resolved with a much faster sending of data on our end. When we say much faster, we mean TimeForge went from about 10 hours to send out Bid Shift emails, to less than 30 minutes to send these out!
SurePayroll export should be working again!