Time Collection Device Integration Options on Time Entry Profiles

You can specify whether people can edit the time entries generated for them from their time collection devices, including Web Clock. You can also enable geolocation for Web Clock.

Geolocation

The collected geolocation information includes the Web Clock device used to report the time, such as Desktop, Mobile Offline, or Mobile Online. It also includes the latitude and longitude accuracy in meters, and any exceptions, such as rejected location requests.

Note: You can record geolocation information and generate geolocation addresses for most, but not all countries. We recommend that you test the countries where you work with geolocation information to make sure you can generate the correct addresses from the geolocation coordinates.

GPS is a country-specific service. A time reporter's location, device, and other factors decide the accuracy and availability of their geolocation information. For most accurate information, we recommend that you enable this functionality for people who use Web Clock on mobile devices because they've dedicated GPS sensors. Because desktop devices don't have GPS sensors, their location is derived from the network, and it's likely to be less accurate. Desktops that use VPN connections are most likely to provide incorrect location information. Oracle HCM Cloud app versions that support geolocation are 11.13.23.01.01 or later.

Note: People with these time entry profiles are prompted to grant Location access when they use Web Clock on mobile devices or in browsers on any supported device.

Geofencing

When you enable geofencing, you set the validation mode.

• Record and report: Shows the worker a message letting them know that their manager was notified that they reported time outside their geofence. It also records the clock event with an exception.
• Restrict: Won't allow the worker to record web clock events outside the primary assignment work location.