{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":35221,"path":"mobile/universal-linking-web-banner.md","title":"Create path segment records and supported URL records for universal linking","bundle":null,"doc_type":null,"release":"australia","body":"\n# Create path segment records and supported URL records for universal linking\n\nCreate path segment records and supported URLs records for universal linking to display a mobile banner. Users see this banner when they land on specific platform web pages. Within each supported URL, you define the page where the banner appears, the mobile app and the screen type the user views, and the data displayed within the screen.\n\n## Before you begin\n\nRole required: admin\n\n## Procedure\n\n1.  Create a path segment record.\n\n    1.  In the web-based UI, navigate to **System Mobile** &gt; **Mobile Universal Linking** &gt; **Path Segments**.\n\n    2.  Select **New** to create a universal link path segment.\n\n    3.  On the form, fill in the fields.\n\n<table id=\"table_uy4_1xw_spb\"><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\nTitle for the universal link path segment.\n\n</td></tr><tr><td>\n\nPath segment regex\n\n</td><td>\n\nRegular expression of the string that defines the category path of the URL.The system evaluates the regular expression string and then performs the matching process on the supported URLs.\n\n</td></tr></tbody>\n</table>    4.  Select **Submit**.\n\n2.  Create a universal link supported URL.\n\n    1.  In the web-based UI, navigate to **System Mobile** &gt; **Mobile Universal Liking** &gt; **Supported URLs**.\n\n    2.  Select **New** to create a universal link supported URL.\n\n    3.  On the form, fill in the fields.\n\n<table id=\"table_ywm_k1n_wpb\"><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\nTitle for the universal link supported URL.\n\n</td></tr><tr><td>\n\nMobile app\n\n</td><td>\n\nServiceNow mobile app the link opens in. Options are `Agent`, `Onboarding`, or `Request` \\(Now Mobile\\).\n\n**Note:** The selection here overrides the selection made in the **Mobile app** field listed in the topic [Mapping specific mobile screens for universal linking](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/mobile/universal-linking-screen-mapping.md).\n\n</td></tr><tr><td>\n\nActive\n\n</td><td>\n\nOption for enabling the activation of this record.\n\n</td></tr><tr><td>\n\nOrder\n\n</td><td>\n\nOption to determine in which order the instance matches a record. The lower the number, the higher the priority for matching the URL.**Note:** The system matches each record one by one. When a record matches a supported URL the instance generates a banner. The order is a way to put the more general supported URLs lower down on the list to prevent the usurping of specific links you want to match.\n\n</td></tr><tr><td>\n\nPath segment\n\n</td><td>\n\nUse the reference lookup icon to select the path segment you created earlier. The system begins to search for matches by first checking the referenced path segment. If there is no match, the instance does not display a banner.\n\n</td></tr><tr><td>\n\nHas query keys\n\n</td><td>\n\nComma-separated string field for query keys. Each query key added into this string field must exist in the URL for there to be a match. An example entry is `id,table,sys_id`\n\n</td></tr><tr><td>\n\nHas query values\n\n</td><td>\n\nOption to add a name a value for each query key you added. An example is **Name** = `id` and **Value** = `ticket`\n\n</td></tr><tr><td>\n\nMobile screen builder\n\n</td><td>\n\nUse the mobile screen builder script block to define the screen type to build and the data the screen uses. Using one of the provided methods in the script block it creates a list screen, record screen, or browser screen. Each method has its own parameter requirements. You can find specific parameters in the script block comments. For more information, see [GlideRecord](https://developer.servicenow.com/dev.do#!/reference/api/orlando/server/no-namespace/c_GlideRecordScopedAPI).\n\n</td></tr></tbody>\n</table>    4.  Select **Submit**.\n\n\n## What to do next\n\nAfter defining when banners appear and the screen and content the user views, consider enhancing the experience by associating the screen to a preconfigured table. See, [Mapping specific mobile screens for universal linking](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/mobile/universal-linking-screen-mapping.md).\n\n**Parent Topic:**[Mobile universal linking for supported URLs](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/mobile/universal-linking-support-urls.md)\n\n"}}