Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Navigation menus and content links

Navigation menus and content links

The methods for choosing a link target (Open in: current window, iframe, or new window) and referencing the item linked (Redirect to: page reference, attachment reference, or URL reference) are similar, so learning how to link within any of these elements is useful.

Menu sections

Menu sections define groups of links and how the links behave. For example, link behavior determines which page opens when the link is clicked and how it opens (such as in a new page or a new frame). Use the following procedure to view a sample menu section.

In the majority of the default CMS menus, the menu section serves as the menu title followed by secondary text, a separation line, and whatever links you define as menu items. The two menus primarily illustrate CMS menus. Although the design is versatile and flows well between pages, there could be questions about linking and scalability to large catalogs. This may only be a good practice for a small catalog with limited items. Look at the request catalog list / grid view demo in the code example demos menu on the ESS Portal:

Menu items and content links

Menu items can be seen as featured links from each section. There are many choices in URL definitions and link options. Links within the ESS Portal all link to content pages within the site. In turn, each page has an iFrame or set of blocks that houses the corresponding data. This method is useful for rapid prototyping, but consider where you need to create dynamic detail pages. Looking across all the menu sections, this discussion explains some of the linking options available to records within the system.
Before proceeding to the links themselves, it is important to mention content links in the CMS. Menu items are similar to content links except they are called by the list block, not as part of a navigation menu block. Menu items and content links function the same as far as how they are defined and the options available for linking to items within the ServiceNow system. Content links are meant to be called through a list block that calls the Content Link [content_link] table. Content links do not have the Logged in field or the Roles option that can be very useful for controlling the UI experience for various roles defined in the system.

Linking to catalog items, reports, and business services

Business Services links to a content page (CMS page referenced: Business Service Portfolio, URL: that pulls the system service catalog homepage into a frame within the content area. Each link within this section leverages the browse by category page, where you pass in the name of the category to return results.
Featured Services links to to a content page which pulls a small subset of services into an iFrame.
Reporting links to a content page that pulls the reports page into an iFrame. All links within this menu leverage homepages in the system, which creates an issue with the URL. Notice in the links below that ../ is used to create a relative URL outside of the CMS site definition. Without this, the site homepage would render within the iFrame.