Mobile deep link structure

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 3 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Mobile Deep Link Structure Considerations Before Implementation

    This guide provides essential information on constructing and utilizing mobile deep links within ServiceNow mobile applications. Mobile deep links consist of three primary components: a variable name, a reference to a mobile app, and a public method for generating the link.

    Show full answer Show less

    Key Features

    • Variable Name: Choose a descriptive name for easy identification in future references.
    • Mobile App Call: Specify the target mobile app, either 'Request' for the Now Mobile app or 'Agent' for the Mobile Agent app.
    • Public Methods: Use various public methods to create deep links, each suited for specific screen types. Key methods include:
      • getButtonLink: Links to input form screens using button ID and optional table name and record ID.
      • getFormScreenLink: Links to non-parameterized form screens with required parameters.
      • getLauncherScreenLink: Links to launcher screens using the screen ID.
      • getPrefillLink: Pre-fills login details for first-time users; requires a boolean for local login.
      • getScreenLink: Links to list screens and can accept UI parameters.
      • getSSOPrefillLink: Generates links for single sign-on, requires activation of the Multi-Provider SSO plugin.
      • getUniversalLink: Creates a link to any resource based on the provided URL.

    Key Outcomes

    By implementing mobile deep links appropriately, ServiceNow customers can enhance user navigation within mobile applications, streamline access to specific screens, and improve the overall user experience. Understanding the structure and methods allows for effective integration of deep linking capabilities, catering to both first-time and returning users while supporting various authentication methods.

    Familiarize yourself with how to construct and use mobile deep links in any screen type within a mobile app.

    Mobile deep links essentially consist of three components. The name of the variable, a reference to a mobile app, and the public method used to pull the mobile deep link. The following mobile deep link has a variable with the name deepLinkGen, where a specified screen opens in the Mobile Agent.

    var deepLinkGen= new global.MobileDeepLinkGenerator('Agent');
 return deepLinkGen.getScreenLink('73f3d135532033002d96ddeeff7b1212');
    Variable name
    You can give any variable name for the mobile deep link, although it should be identifiable for future reference.
    Mobile app call
    Enter one of the mobile apps that the mobile deep link points to. You can enter either Request for the Now Mobile app or Agent for the Mobile Agent app. For example, to generate a link using the mobile deep link generator that points to the Now Mobile app, use the following code: new global.MobileDeepLinkGenerator('Request');
    Public method
    Use one of the public methods that can be used to create a mobile deep link. Reference the table for an explanation of each method, and the reason for its use.
    Method Reason for use Method parameters
    getButtonLink(buttonId, tableName, recordSysId) getButtonLink is used to link into any input form screen. buttonId (required): sys_id of the button you want to launch the input form screen

    tableName (optional): name of the table for the current context

    recordSysId (optional): sys_id of the current context record
    getFormScreenLink(formScreenId, tableName, recordSysId) getFormScreenLink is used to link into any non-parameterized form screen. formScreenId (required): sys_id of required form screen

    tableName (required): table name of required form screen

    recordSysId (required): sys_id of record from tableName
    getLauncherScreenLink(launcherScreenId) getLauncherScreenLink is used to link into any launcher screen. launcherScreenId (required): sys_id of the required launcher screen.
    getPrefillLink(forceLocalLogin) getPrefillLink is useful for first-time ServiceNow mobile users. This link format pre-fills the instance link for users who have not yet added an instance to their mobile app. This method is the default authentication experience.

    This method does not generate a link to a specific screen.

    		 forceLocalLogin (required):

    Enter true for the system to pre-fill the instance login details of the user.

    Enter false, for the user to manually enter login details.
    getScreenLink(documentId, uiParams) getScreenLink is used to link into any list screens, including both parameterized and non-parameterized types. Can also be used for any non-parameterized screen type. An optional UI parameter can be passed into this method. documentId (required): sys_id of desired screen

    uiParams (optional): Parameter of a data item
    getSSOPrefillLink(sys_id) getSSOPrefillLink generates a link that uses the identity provider (IdP) that is identified by the sys_id parameter. This link can be used to authenticate end users that use different IdPs. For example, pre-hires might use Microsoft Azure as their IdP, and on-boarded employees might use Okta as their IdP. A common use of these SSO (single sign-on) pre-filled links is to embed them in emails sent to employees. These emails contain a link that can be used to log in securely to a ServiceNow instance using their mobile apps.
    Important:
    You must activate the Multi-Provider SSO plugin and have an active IdP to use this method. For more information, see Activate Multi-Provider SSO plugin
    		 sys_id (required): Enter the sys_id of the IdP you want to use from the Identity Providers [sso_properties] table.
    To get the sys_id of the IdP:
    1. Navigate to All > Multi-Provider SSO > Identity Providers.
    2. Right-click an identity provider record and select Copy sys_id.
    getUniversalLink(url) getUniversalLink generates a link into either a list, form, or browser. A screen is generated based on the content of this URL. See Universal linking for mobile. url (required): a link to a resource on an instance