Functionality Differences Between Online and Offline Web Clock

Some functionality acts differently depending on whether Web Clock is online or offline.

Elapsed Time Counter

The counter for time elapsed since the most recent button tap is accurate when Web Clock is online. The counter isn't accurate when offline. People who are offline can't use the elapsed time to make sure they're complying with regulations. For example, they can't tell if they rested for the required periods between work periods.

Button Logic

Enabled button logic applies only when Web Clock is online. This means that when people are online the earlier buttons they tapped are now unavailable. When they're offline, the buttons are still available. People can inadvertently tap the same button multiple times during a day, which can cause time entry errors. People need to fix these errors before submitting the corresponding time card. You can use time entry profiles to identify if individuals, their managers, or both can correct the errors.

Time to Use for Clock Events

If the layout has server time enabled, it applies to only online clock events. When Web Clock is offline, the clock events always use device time. This difference in the time used might lead to time entry errors that people need to fix before they submit the corresponding time card.

More Fields

If the layout includes more fields for specific buttons, when Web Clock is online, people can see the fields. When Web Clock is offline, they can't. The corresponding time card might be incomplete or in error if people don't complete these more fields.

Data Sync Time

The time it takes to sync data between the device and the time repository is completely dependent on the device, network bandwidth, and connection stability. To keep time events on Web Clock current, people need to let the data sync completely when they're back online. Then they use Web Clock to report their latest time.