{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":42064,"path":"platform-user-interface/c_MapPages.md","title":"Map pages","bundle":null,"doc_type":null,"release":"australia","body":"\n# Map pages\n\nMap pages display ServiceNow data graphically on a Google map page based on location data that you provide.\n\nYou can create as many map pages as required to define the types of data to display, the links to show, and the appearance of the map. After creating the map pages, you can create modules to display the map pages.\n\n**Note:** Map pages are subject to the non-production access limitations. See [Set up Google Maps API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-user-interface/set-up-google-maps-api.md) for details.\n\n## Map locations\n\nLocations are used by various applications to locate users, facilities, or configuration items \\(CI\\) and are stored in the Location \\[cmn\\_location\\] table. You can configure different levels of location in a parent-child hierarchy. For example, an email server might be associated with a location of Second Floor, whereas the email business service might be associated with New York City.\n\nEach level of this hierarchy contains a separate location record, with the next higher level specified as a parent.\n\nThe location is also used to generate a full identifier in the **Full name** field, which is available by configuring the form. For more information, see .\n\n\\[Omitted image \"LocationFullName.png\"\\] Alt text: The Full name field on the Location form\n\n## How locations are defined\n\nTo create a location, navigate to **User Administration** &gt; **Locations** and select **New**.\n\n<table id=\"table_xqf_tdw_dp\"><thead><tr><th>\n\nField\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nName\n\n</td><td>\n\nThe name of the location. This name is the display value that the system uses when referencing this location on a form.\n\n</td></tr><tr><td>\n\nStreet\n\n</td><td>\n\nThe street address of the location.\n\n</td></tr><tr><td>\n\nCity\n\n</td><td>\n\nThe city of the location.\n\n</td></tr><tr><td>\n\nState / Province\n\n</td><td>\n\nState or province of the location.\n\n</td></tr><tr><td>\n\nZip / Postal Code\n\n</td><td>\n\nThe zip or postal code of the location.\n\n</td></tr><tr><td>\n\nCountry\n\n</td><td>\n\nThe country of the location.\n\n</td></tr><tr><td>\n\nContact\n\n</td><td>\n\nName of a user who is the contact for this location.\n\n</td></tr><tr><td>\n\nPhone\n\n</td><td>\n\nThe phone number for the location.\n\n</td></tr><tr><td>\n\nFax phone\n\n</td><td>\n\nThe fax number for the location.\n\n</td></tr><tr><td>\n\nParent\n\n</td><td>\n\nName of the parent location for this location. Location hierarchies are described earlier.\n\n</td></tr><tr><td>\n\nLatitude\n\n</td><td>\n\nThe latitude of the location.The **get\\_lat\\_long** business rule automatically populates this field and the **Longitude** field described below when the form contains enough information, such as an address or city name and a postal code.\n\n Deactivate this business rule to avoid the system overwriting any values entered manually into these fields.\n\n</td></tr><tr><td>\n\nLongitude\n\n</td><td>\n\nThe longitude of the location.\n\n</td></tr><tr><td class=\"sub-head\" colspan=\"2\">\n\nFields that can be added by configuring the form:\n\n</td></tr><tr><td>\n\nCompany\n\n</td><td>\n\nA reference field to the **Company** `[core_company]` table.\n\n</td></tr><tr><td>\n\nFull name\n\n</td><td>\n\nA read-only, calculated field that assembles the parent hierarchy of the location into a full name.\n\n</td></tr><tr><td>\n\nStock room\n\n</td><td>\n\nA Boolean field that identifies whether the location is being used as a stock room.\n\n</td></tr><tr><td>\n\nTime zone\n\n</td><td>\n\nThe time zone of the location. By default, the location uses the system time zone.\n\n</td></tr></tbody>\n</table>## Latitude and longitude\n\nWhen a **Company** or **Location** record is created, or has one of its address fields changed `[street, city, state, zip or country]`, the **get\\_lat\\_long** business rule is triggered. This business rule uses the **GoogleMapsHelper** script include to create `sys_geocoding_request` records.\n\nThe scheduled job **Process Geocoding Request** must be enabled to process `sys_geocoding_request` records. **Process Geocoding Request** uses the Google Map service to populate the latitude and longitude fields of the changed or created **Company** and **Location** records.\n\nAfter the latitude and longitude are populated, Map Pages can be defined that display locations in an interactive map.\n\n**Note:** Latitude and longitude are expressed as a floating point data type. Previous releases expressed this information as a string. During an upgrade, the system converts the data where possible.\n\n-   **[Set up Google Maps API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-user-interface/set-up-google-maps-api.md)**  \nYou enable the geolocation feature using the appropriate entries from a Google Maps API for Business license, or a Google Maps JavaScript API Key.\n-   **[Create a map page](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-user-interface/t_CreateAMapPage.md)**  \nYour ServiceNow instance provides several default map pages. You can also create custom map pages with the script examples described in this page.\n-   **[Create a map page module](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-user-interface/create-map-page-module.md)**  \nYou can create a new application module for desktop or smartphone users to display a Google map page.\n-   **[Create an advanced Map Page](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-user-interface/create-advanced-map-page.md)**  \nUse advanced configuration to set up Map Pages without scripting.\n-   **[Set map application scope](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-user-interface/set-map-application-scope.md)**  \nEnable map application scope to specify which application can modify your Map Page configuration.\n-   **[Create a smartphone map page module](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-user-interface/t_CreateASmartphoneMapPageModule.md)**  \nYou can create a custom smartphone module that links directly to a map page.\n-   **[Scripting for map pages](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-user-interface/scripting-for-map-pages.md)**  \nThe Script field on the Map Page form allows the use of attributes or custom code to define map characteristics, such as marker appearance, display information, and more.\n\n**Parent Topic:**[User interface configuration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-user-interface/p_NavigationAndUIConfiguration.md)\n\n"}}