Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.
Versions
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store
Close

Installed with geolocation

Log in to subscribe to topics and get notified when content changes.

Installed with geolocation

Several component types are installed with Geolocation.

Modified by Geolocation

The Geolocation plugin adds a field called Geolocation tracked to the User [sys_user] table. This field allows the system to track individual users by their geographical coordinates.

Business rules installed with geolocation

Business rules are added with activation of Geolocation.

Name Table Description
GeoLocation Data updated User

[sys_user]

Populates the Latitude and Longitude fields on the Geolocation History [geo_history] table when the Latitude and Longitude fields are updated on the User [sys_user] table.

Client scripts installed with geolocation

Client scripts are added with activation of Geolocation.

Name Table Description
Update Geolocation on Task Task

[task]

Populates the Latitude and Longitude fields on a user record with GPS coordinates when that user loads any record on the Task table or a table that extends Task. This occurs only when geolocation tracking is enabled for the user.

Properties installed with geolocation

Geolocation provides the following configurable properties in Geolocation > Administration > Geolocation Properties.

The Google Maps plugin provides additional map properties that are used to implement and control specific geolocation features. You must have a private key for Google Maps API for Business to take advantage of the properties listed here.
Table 1. Properties
Name Description
glide.geolocation.allow.toll.roads Allow toll roads to be used. Allows the system to use toll roads when auto-routing or optimizing task routes for agents.
  • Type: True/false
  • Default value: True
glide.geolocation.default.start.time Default start time for all agents when no schedule is set. This value sets the start time for a day other than the current day, when no scheduled task exists or is continued from the previous day. This property uses a 24 hour clock.
  • Type: String
  • Default value: 08:00
glide.geolocation.evening.rush.hours Evening rush hour span, formatted as 14:30-16:00. All times are expressed as a range, separated by a dash with no spaces. Times not using this format are ignored. This property must be used with the work.management.morning.rush.hours and work.management.rush.travel.buffer properties and uses a 24 hour clock.
  • Type: String
  • Default: 0
glide.geolocation.history.cleanup Number of days to keep history data. ServiceNow keeps agent geolocation history records for the number of days specified by this value.
  • Type: Integer
  • Default value: 30
glide.geolocation.morning.rush.hours Morning rush hour span, formatted as 06:30-08:00. This property uses a 24 hour clock. All times are expressed as a range, separated by a dash with no spaces. Times not using this format are ignored. This property must be used with the work.management.evening.rush.hours and work.management.rush.travel.buffer properties.
  • Type: String
  • Default: 0
glide.geolocation.proximity Minimum distance an agent must move to be considered in a new location (in meters). This setting establishes a geolocation perimeter that prevents ServiceNow from creating unnecessary history records when an agent has multiple tasks in the same vicinity. An example of this might be when an agent has several tasks in one building. The system assumes that all task activity within the specified radius is part of a single record and does not create additional records when the agent moves from task to task around the building.
  • Type: Integer
  • Default value: 500
glide.geolocation.proximity.location Maximum distance an agent can be from a specific location and still be placed at that location (in meters). This setting defines the maximum distance that an agent can be from a specified location and still be placed at that location by the system.
  • Type: Integer
  • Default value: 200
glide.geolocation.rush.travel.buffer Percentage to add to all rush hour travel times. The system uses this percentage to calculate schedules when auto-routing an agent. Use this property when both morning and evening rush hour times are defined. An example of a valid time buffer percentage is 15.
  • Type: Integer
  • Default value: 0
glide.geolocation.tracking.frequency Sets the length of the recurring interval, in seconds, that the system waits between attempts to update a user's geographic coordinates. The system updates geographic coordinates only for users who have geolocation tracking enabled.
Minimum amount of time between updating the user's location (in seconds). This setting defines how long the system waits before updating an agent's location, regardless of task activity or travel. This prevents ServiceNow from creating unnecessary history records if an agent in one location views a task multiple times.
  • Type: Integer
  • Default value: 300
glide.geolocation.travel.buffer Percentage to add to all travel times. An example of a valid percentage value is 15.
  • Type: Integer
  • Default value: 0
glide.geolocation.work.spacing Amount of time (in minutes) to add between the end of a task and the travel start of the next. An example of a valid time value is 10.
  • Type: Integer
  • Default value: 0

Script includes installed with geolocation

Script includes are added with activation of Geolocation.

Name Description
GeolocationAJAX Utilities the system uses when making geolocation AJAX calls.
GeolocationUtils Core utilities for geolocation functionality.
Feedback