Links to records in email notifications

  • Rversion finale: Australia
  • Mis à jour 12 mars 2026
  • 1 minute de lecture

    • Adding the ${URI} parameter to an outbound email body or template creates a link to a specific record.

    When a user clicks the word LINK, the instance prompts the user to log in if not already logged in, and then redirects the user to the record specified in the URI.
    Figure 1. Link displayed by ${URI} parameter
    The ${URI} parameter has an extension called the ${URI+} format to specify additional arguments in the email link, such as sysparm terms, in addition to the automatically created URI. For example (whitespace added for improved readability):
    ${URI+&sysparm_scriptlet=current.assigned_to=gs.getUserID()
&sysparm_scriptlet_condition=current.assigned_to.nil()
&sysparm_view=incident_active}
    This example executes the JavaScript:
    current.assigned_to=gs.getUserID()
    when the condition of
    current.assigned_to.nil()

    is satisfied. Additionally, the script sets the view to incident_active.

    Linking to a record in Workspace

    The ${URI} and ${URI_REF} variables don't apply to records in Workspace. To link to a record in Workspace, create a mail script and reference it in your notification. For more information on using mail scripts, see JavaScript in emails.

    The mail script that you create should print a URL to the notification. The URL must have the following format:
    https://<instance_name>/now/workspace/<workspace_name>/record/<table_name>/<sys_id>
    The following example script shows the logic that a mail script must include to create a link to a record in Workspace.
    // Dynamically construct an Agent Workspace URL and insert a link in the notification
  var agentURL = '<a href="' + gs.getProperty('glide.servlet.uri') + '/now/workspace/agent/record/'+ current.getTableName() + '/' + current.sys_id + '">' + current.number + '</a>';
  template.print(agentURL + "<br />");