Defining and using geolocations

You can use geolocations to prevent users of mobile devices from clocking if they are outside of a virtual perimeter called a geofence. For example, you can define a geofence with a 50 meter radius centered around a store location.

In Workforce Management, geolocations are defined at the team level. Each geolocation consists of a pair of GPS coordinates, representing the center of the geofence, and a radius. A team can have one or more geolocations defined for it. For example, truck drivers might have to clock at multiple locations, so you can added geofencing coordinates for each one.

To use geofencing for clock punches, the mobile device's location services must be turned on.

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

Geofencing depends on the GPS coordinates that are received from the device. Workforce Management does not include any GIS services of its own, so the Geolocation API is used to access location data. The Geolocation API works with both browsers and Infor Go.

For more information about the Geolocation API, see the W3C recommendation.

Geolocation inheritance

If a team does not have its own geolocation, it can inherit the geolocation of its parent or another team in the hierarchy. For example, if the team's immediate parent has no geolocation, but the team above that does, then the child team inherits the geolocation of the parent's parent.

Geolocations that are explicitly defined for a team override inherited geolocations. A team that has inherited a geolocation can also opt out of geofencing.