Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Embedded help

Log in to subscribe to topics and get notified when content changes.

Embedded help

Embedded help provides targeted help content to a user in a UI page, based on their role. Some embedded help content comes with the base instance. Your organization can add or replace embedded help content.

Note: Embedded help is only available in UI16. It is not compatible with UI15. For more information, see Activate UI16.

The Embedded Help plugin (com.glide.embedded_help) is active by default for all new and upgraded instances. Embedded help content appears in the right sidebar when the user clicks the help icon. If embedded help exists for the current UI page, the help icon has an indicator (Embedded help indicator on help icon).

Figure 1. Embedded help for the Catalog Task page
Catalog task page with embedded help

If there is no embedded help for a list or form, the sidebar displays links to the User Guide and the documentation site search. Click Search Documentation to search for documentation about that feature.

Users with the embedded_help_admin or admin role can add help to the page. They can also edit custom content that appears for a page. The following image shows what the admin sees when there is no help article, and how to open an existing article. If you want to edit base system help content, follow the steps in Add custom embedded help from a copy.

Figure 2. Embedded help administrator features in the help pane
Add content or edit existing content

Embedded help is displayed based on the user's role. If the content has no associated role, all users see it. If the role is different than admin, users with the specified role and above see the content. For example, content with the itil role appears for itil, itil_admin, and admin.

Working with embedded help content

You can add new embedded help content or replace content. Replacing content involves inactivating the existing topic and adding a topic.

Following are some of the reasons for your organization to add or replace embedded help content.
  • To provide help for custom applications.
  • To provide more specific instructions or embedded videos to describe your business process.
  • To provide embedded help content where none exists for a page.
  • To provide embedded help content in languages other than English (default).
  • To provide different content for different roles.

The UI page name identifies embedded help content. To find the page name, look for the table name in the URL for that view. For example, the page name for the list view of Assessment Metric Types is asmt_metric_type_list and is found in this address: The page name for the form view is asmt_metric_type.

You cannot edit the content in a base system topic. In base system topics, the read-only ServiceNow Help check box is selected. If you edit the content and try to save changes, you see an error message. To change the information that appears in a base system topic, make a copy of the topic, which clears the ServiceNow Help check box. Modify the topic with your content and save it. Customized content takes precedent over ServiceNow help content and is displayed when a user opens help for that UI page.

Embedded help and domain separation

If your organization uses domain separation, you can create custom embedded help for each domain. To associate help content with a domain, the administrator configures the Help Content form to include the Domain field. When custom content is created, the author selects the domain to which the content applies.

Considerations include the following list:
  • Content with no specified domain is in the global domain.
  • If domain-specific content does not exist for a user in a domain, the user sees the global help content.
  • Users in the global domain only see global help content. An administrator who wants to test domain-specific help must impersonate a user in that domain.

Embedded help process

The ServiceNow datacenter contains the Content Delivery Network (CDN) where embedded help content is stored. Topics in the local (instance) Embedded Help Content [sys_embedded_help_content] table are populated from the CDN. Help content in the CDN is refreshed every 30 days.

When a user accesses a UI page, the embedded help process displays a custom topic if one exists for the user's role. If there is no custom topic, the following steps are performed.
  1. Checks the browser cache first, and displays the content if found in the cache. It then checks the Embedded Help Content [sys_embedded_help_content] table for the corresponding embedded help topic with the role and qualifier, if applicable.
    • If a topic is found, it checks the date in the Last sync field. If the date is 15 or more days old, it places a request in the Embedded Help Queue [sys_embedded_help_queue] table with the last sync date and the resource ID.
    • If a topic is not found, it places a request in the Embedded Help Queue [sys_embedded_help_queue] table with the current date and the resource ID.
  2. Within a minute of the page being viewed, the system processes the request and checks the CDN. In the first case, it checks whether the topic was updated since the Last sync date. In either case, after a minute, refresh the page to see the content.
    • If the topic was updated, it pulls the updated topic into the table and updates the Last sync date.
    • If the topic was not updated, it displays the local cached or database topic, and updates the Last sync date.
  3. If the topic was not in the local database, it pulls the topic into the table if it exists on the CDN. If it does not exist, there is no action.

The administrator can modify the default 15-day synchronization duration in system properties