---
sourceDocument: Australia ServiceNow AI Platform user interface
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/platform-user-interface

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia ServiceNow AI Platform user interface

ft:clusterId :

    - platux

bundleId :

    - platux

workflow :

    - Platform


---

# Content Management integration points

# Content Management integration points {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

Integration points use content blocks in CMS to link different applications together
using static and dynamic methods.

By using integration points, users can connect to different systems from a single page. The
power of the CMS is that it can display any data within the ServiceNow platform. The ESS portal, for
example, connects users to a service catalog, a knowledge base, and a help and incident reporting
site. Each section contains a set of links to additional content. List blocks offer the easiest
way to display data dynamically. Content types define how lists link to the detailed data they
reference.

Generating lists from the ServiceNow
platform is straightforward, especially if you use filtering. When the CMS was first introduced,
lists were the only method available to create navigational systems for sites. Content types
define system record links using specific templates to define the list and the details.  
* Summary template: defines the list
* Detail template: defines the detail as it is rendered in a page.
{#c_CMSIntegrationPoints__ul_u22_lq2_zt}

The templates work together to pass data attributes or [Unique record identifier (sys_id)](https://www.servicenow.com/docs/access?context=c_UniqueRecordIdentifier&version=australia&pubname=australia-platform-administration&ft:locale=en-US) (sysid) into a single detail page that manages the data. Any
attribute variations use the URL sent to the page.

Understanding how content types work can mean the difference between a site with 20 pages
versus a site with 200 pages. There is a time for both types of data calls. Depending on the
task, there are appropriate times to use static content and times for dynamic methods.
* **[View links between system elements and URLs](https://servicenow-prod.fluidtopics.net/wMYfxJCJEWl2UKBAk63W6g)**   
  You can view the links between your system elements and their URLs to render more specific content within your site.
* **[Static methods](https://servicenow-prod.fluidtopics.net/LFsLUDGz9ERN_IIj4OB8mA)**   
  Static methods in the CMS application were created for ease of use.
* **[Dynamic methods](https://servicenow-prod.fluidtopics.net/XQcUK8bb706QPiHOLV865w)**   
  While static methods are a powerful navigational tool, you have more control over data rendering using the dynamic methods.
* **[Example integration points](https://servicenow-prod.fluidtopics.net/wDuPbaxVENB0YvbSPTKQIg)**   
  Each element on the page links to a specific URL point.

**Conceitos relacionados**   

* [Content Management design](https://servicenow-prod.fluidtopics.net/i6oppkRa1l796A3pjIK9aQ "Before building a website in the CMS, it is important to have a good understanding of what to build and who the audience is.")
* [Domain separation and the Content Management System](https://servicenow-prod.fluidtopics.net/hK3mi0GCP_SZ4vXBJIDqgw "Domain separation is supported in the Content Management System. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.")
* [Content Management testing](https://servicenow-prod.fluidtopics.net/I~Pjp5Be5Pw8CV9NXKrlcQ "Test your site to ensure that all pages display correctly, links go to the specified address, and images are not broken. It is important to test the site as you build it. Do not wait until just before launch to begin testing.")
* [Global search in Content Management](https://servicenow-prod.fluidtopics.net/rI3u5NbPeEr2KtYs_l5f9Q "When you add global search to a CMS site, two different search result blocks can display, depending on the user role: global or no global.")
* [CMS translation](https://servicenow-prod.fluidtopics.net/7_FLWXOJK5ST7t_DPdjjpw#c_CMSTranslation "You can translate CMS sites by activating internationalization plugins and manually translating custom interface strings.")  
**Tarefas relacionadas**   

* [Configure Content Management sites](https://servicenow-prod.fluidtopics.net/2539aImALq0okddWqAtxkw "Planning a CMS site involves obtaining resources, communicating with others about design, and gathering content.")