Configure iFrames

An iFrame embeds a URL on a page within a frame. It can embed external pages or render ServiceNow content.

Before you begin

Role required: content_admin or admin

About this task

Configure an iFrame with forms you create in the instance and link to the page in which the iFrame resides.

Note: Do not add any type of report, such as a calendar, to iFrames. For more information on adding a report directly onto a page without using iFrames, see Embedding reports in Jelly.

Procedure

  1. Navigate to Content Management > Specialty Content > iFrames.
  2. Click New.
  3. Complete the iFrame form fields.
    Table 1. iFrame form fields
    Field Input value
    Name Type a unique name for the iFrame block.
    Frame name Type a name for the frame on the page.

    When you use iFrames to present ServiceNow content such as forms or lists, the frame name must be gsft_main. This name allows links within the iFrame to open within the iFrame.

    URL

    Enter the URL to display in the iFrame. If you use the iFrame to display ServiceNow content, start with the page name and do not include the base instance part of the URL. For example, to show the list of requested items, the URL is:

    sc_req_item_list.do

    Queries can be applied to the URL. For instance, to display a list of open requested items, the URL is:

    sc_req_item_list.do?sysparm_query=active=true

    For more information, see URL schema.

    Sizing Select an option for iFrame block size.
    Note: The Expand to fit content choice only works with ServiceNow content. If Fixed Size is selected, height and width fields are displayed for you to enter the size in pixels.
    Note: Some browsers suppress iFrames because they use an X-Frame-Options header value of SAMEORIGIN. The X–Frame-Options header was introduced in Internet Explorer 8 RC1, to help detect and prevent frame-based redressing. The SAMEORIGIN value causes the browser to render a blank page instead of the target page of the <frame> or <iframe> when the frame target is not on the same origin as the page itself. Support for this header has been implemented in Safari 4.0, Chrome 4.1.249.1042, and Firefox 3.6.9 and above.