Including URLs (Smart URLs)

When you receive a notification, it is often helpful to have a link to the item that requires attention. Notifications can be configured in the body of a notification to include the Web address (URL) for the following entities:

  • Packages

  • Requests

  • Request Types

  • Projects

  • Tasks

  • Workflows

  • Validations

  • Object Types

  • Environments

If you are viewing your email with a Web-based mail reader (such as Microsoft� Outlook), you can click the URL in the notification and be taken directly to the referenced entity.

For workflows, request types, validations, object types and environments, the notification can use the entity ID or the entity name as the parameter in the URL. This will bring you to the correct window in the Workbench and open the detail window for the specified entity.

Table 3-3. Smart URL tokens lists the most commonly-used smart URL tokens for packages and requests.

Table 3-3. Smart URL tokens

Smart URL Token

Description

PACKAGE_URL

Provides a URL that loads the package details page in the standard interface.

WORKBENCH_PACKAGE_URL

Provides a URL that loads the package window in the Workbench.

REQUEST_URL

Provides a URL that loads the request details page in the standard interface.

If you use an HTML-formatted message, you must use an alternate token to provide a link to requests. (You can also use this token in plain-text formatted notifications.) The smart URL token (for HTML format) for requests is REQUEST_ID_LINK.

The REQUEST_ID_LINK token provides a link that loads the request detail page in the standard interface. This token resolves to the following format:

<a href="http://URL">Request Name</a>

In the notification, the link is displayed as a linked entry.