Defining and using geolocations

Geofencing can be used to validate clocks based on the location of a mobile device. A geofence is a virtual perimeter that represents a geographic area. Using geofencing, you can prevent users of mobile devices from clocking if they are outside of the virtual perimeter. You can also track whether specific activities occurred inside or outside this virtual area.

For example, you can define a 50 meter geofence for a team centered around a store location. Alternatively, you can use pay rules to automatically unauthorize an employee's timesheet if the clock transaction occurs outside of the geofence.

In Workforce Management, geolocations are defined at the team level. Each geolocation consists of a pair of GPS coordinates, representing the physical location of the team, and a radius. Together, they define a circular geofence around the location for this team.

Note: Workforce Management does not include any GIS services its own. Geofencing uses the GPS coordinates that are received from the mobile device.

Capturing GPS coordinates during an attempted clocking transaction requires a mobile device's location services to be turned on.

Note: To disable the capture of GPS coordinates by Workforce Management entirely, the GEO_LOCATION_CAPTURE registry parameter can be set to OFF. See "GEO_LOCATION_CAPTURE" in the Infor Workforce Management Registry Parameter Reference Guide.

Geolocation inheritance

If a team does not have a geolocation of its own defined, it inherits the geolocation of its parent. If the team's immediate parent has no defined geolocation, the system continues up the hierarchy until it finds a defined geolocation or reaches the top.

Geolocations explicitly defined for a team override the inherited geolocations. Only a single geolocation applies to each team at any one time.

A sub-team can opt out of geofencing. When a team opts out, no location-based clock validation is performed.