Create path segment records and supported URL records for universal linking
Create 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.
Before you begin
Role required: admin
Procedure
Create a path segment record.
In the web-based UI, navigate to System Mobile > Mobile Universal Linking > Path Segments.
Select New to create a universal link path segment.
On the form, fill in the fields.
| Field | Description |
|---|---|
| Name | Title for the universal link path segment. |
| Path segment regex | Regular 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. |
4. Select **Submit**.
Create a universal link supported URL.
In the web-based UI, navigate to System Mobile > Mobile Universal Liking > Supported URLs.
Select New to create a universal link supported URL.
On the form, fill in the fields.
| Field | Description |
|---|---|
| Name | Title for the universal link supported URL. |
| Mobile app | ServiceNow mobile app the link opens in. Options are Note: The selection here overrides the selection made in the Mobile app field listed in the topic Mapping specific mobile screens for universal linking. |
| Active | Option for enabling the activation of this record. |
| Order | Option 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. |
| Path segment | Use 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. |
| Has query keys | Comma-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` |
| Has query values | Option to add a name a value for each query key you added. An example is Name = id and Value = ticket |
| Mobile screen builder | Use 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. |
4. Select **Submit**.
What to do next
After 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.
Parent Topic:Mobile universal linking for supported URLs