With this new year, new exciting things are coming to our system and one of these is a new feature geared towards employees that work on different time zones.
The way it used to be was that if you switched to a different time zone, the application showed a message notifying you about this and you had to correct the time zone to be able to continue, but we have made it smarter so that you only need to worry about changing time zones and Timecard will adapt to your changes.
The way it used to be was that if you switched to a different time zone, the application showed a message notifying you about this and you had to correct the time zone to be able to continue, but we have made it smarter so that you only need to worry about changing time zones and Timecard will adapt to your changes.
Here is how it goes, this is the example profile we'll be using, notice he was set on US/Pacific time:
Here is a screenshot to show that this device has been setup in Pacific time as well and a sample of the History in the Timecard app:
The user had clocked in at 8:00 AM and changed to a different task at 11:20 AM Pacific Time, but if he had to take a flight to the East Coast and were to change the time zone either manually or have the device do it automatically, the next time Timecard GPS is launched, something new will happen:
The device will give you a message telling you that the timezones have been changed and a reboot is required. You can wait for the timer and have the app shutdown automatically or tap on "REBOOT" and the app will restart right then.
Now, if you check your History, you will notice it will be showing the same original punches but on Eastern time:
One important thing to keep in mind is that the web portal will show the punches using the original time the user was setup with, so, as we saw in the beginning, he was set to Pacific Time, so when we generate one of the reports, it will show the punches in US/Pacific to make things consistent:
That's all for now, leave us a comment in case you have any questions!
--Econz Team
No comments:
Post a Comment