--- sourceDocument: Brazil ServiceNow AI Platform user interface sourceDocumentLink: https://www.servicenow.com/docs/r/platform-user-interface Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil ServiceNow AI Platform user interface ft:clusterId : - platux bundleId : - platux workflow : - Platform --- # Content Management and Service Portal # Content Management and Service Portal {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Content Management and Service Portal Service Portal is a modern alternative to the traditional Content Management System (CMS) within ServiceNow, offering a refined user experience and optimized mobile support. While CMS continues to be supported and existing CMS sites remain functional after activating Service Portal, Service Portal uses different underlying technologies and design principles requiring consideration before transitioning, especially for complex or highly customized CMS implementations. Show full answer Show less ## Key Features * **Technology:** Service Portal is built on AngularJS, server-side JavaScript, HTML, and CSS, unlike CMS which relies on Jelly scripting and iFrames. This enables better styling control and responsive design. * **Mobile Optimization:** Service Portal is designed mobile-first, supporting APIs appropriate for mobile environments and a maximum two-column layout for forms, which may necessitate simplifying complex Service Catalog forms. * **Component Differences:** Key CMS components map differently in Service Portal: * Content sites become Portals * Content pages remain pages without requiring content types * Content blocks are replaced by reusable widgets * Layout uses containers, rows, and columns instead of dropzones * Service Catalog pages render via the SC Catalog Item widget, sharing forms between CMS and Service Portal * Themes use CSS similarly in both ## Transition Considerations * **Customization Compatibility:** Complex CMS customizations, particularly in Service Catalog forms and client scripts, may not function correctly in Service Portal and typically require refactoring. * **Script Refactoring:** Client scripts must use mobile-supported APIs. UI Macros should be replaced with widgets or alternative solutions compatible with Service Portal. * **Form Simplification:** Service Catalog items and record producers should be simplified to fit the two-column layout supported by Service Portal. * **Upgrade Planning:** Customers should verify their ServiceNow release supports required Service Portal features before transitioning. ## Practical Outcomes for ServiceNow Customers Customers adopting Service Portal can expect a more responsive, mobile-friendly interface and improved styling flexibility. However, transitioning from CMS involves careful review and modification of existing customizations to ensure compatibility. Service Portal's widget-based architecture and updated scripting requirements provide a modern framework but may require development effort to refactor or rebuild complex forms and scripts. Service Portal and CMS coexist independently, allowing gradual transition without disrupting existing CMS sites. This flexibility helps customers plan migration to leverage Service Portal's benefits while maintaining current CMS functionality as needed. Service Portal is a compelling alternative to the Content Management System (CMS) with a refined user experience. It does not duplicate CMS or platform UI functionality. Users who have sophisticated experiences delivered through CMS may need to invest time into transitioning to Service Portal, especially if the CMS implementation includes complex and customized Service Catalog forms. ## Service Portal compatibility with existing CMS sites ServiceNow continues to support CMS in current and upcoming releases. If you have existing CMS sites and activate Service Portal on your instance, your CMS sites will continue to work, as CMS and Service Portal are separate applications. ## Differences between Service Portal and CMS Service Portal is an alternative to CMS based on more modern technologies. Major differences include: Underlying technology : CMS uses Jelly, which is not a widely used technology. Service Portal instead uses [AngularJS](https://docs.angularjs.org/guide/introduction), server-side JavaScript, HTML, and CSS. Any scripts that use Jelly do not work in Service Portal. Building widgets in Service Portal requires knowledge of AngularJS. Visual layer : CMS uses iFrames which can be difficult to work with, limited in terms of styling, and susceptible to upgrade issues. Alternatively, Service Portal is a self-contained application that accesses data from other tables on the platform. This enables fine-tuned control over style and responsive design. Mobile first : Unlike CMS, Service Portal is optimized for a mobile environment. For this reason, the following apply to the Service Portal environment: * Any scripts used in Service Portal can only use APIs supported in a mobile environment. For example, some APIs used in your Service Catalog client scripts may not be supported. For a list of supported APIs, see [Service Portal and client scripts](https://www.servicenow.com/docs/xlVPEeVFkQRMjzIiSmnX2g "You can use client scripts and catalog client scripts in the Service Portal if the UI Type is set to Mobile / Service Portal or All. Client scripts and catalog client scripts are used with the Form widget and SC Catalog Item widget, as opposed to a widget client controller."). * Service Portal forms support a maximum of two-columns. As a result, any highly customized Service Catalog forms, such as catalog items and record producers that use containers and variable sets, must be simplified to work in a two-column layout. {#c_CMSAndSP__ul_ayt_jfm_mbb} If transitioning to Service Portal, review the following resource: [Mobile client GlideForm (g form) scripting and migration](https://www.servicenow.com/docs/access?context=r_MobilePlatformMigrationImpacts&version=brazil&pubname=brazil-api-reference&ft:locale=en-US). To understand how core CMS components are configured in Service Portal, refer to the following table. {#c_CMSAndSP__table_oys_yth_cbb__entry__2} | CMS component | Service Portal equivalent | |-|-| | Content site | [Portal](https://www.servicenow.com/docs/ON0cEQLWBttElINiJndn6Q "Create a portal for users to browse company resources, discover articles, and get help.") | | Content page | [Page](https://www.servicenow.com/docs/toFajOCT1DdxbQY5LNhBvQ "Use pages to organize content, ensure responsive mobile optimization, and design meaningful portal user experiences for your customers. A page houses containers and rows, which then contain widgets. By manipulating the layout of the page, and the widgets within it, you can construct your desired user experience.") | | Content types | Content types link a table to a content page. In Service Portal, content types are no longer required. Record data is queried and displayed using base system widgets. You can add widgets to any number of Service Portal pages. Learn more: [Using portal widgets](https://www.servicenow.com/docs/kjFBnrDg7lVbAAVnbgc80g "Widgets are what define the content of your portal pages. You can use the base system widgets provided with Service Portal, clone and modify widgets, or develop custom widgets to fit your own needs."). | | Layout and dropzones | In Service Portal, pages are made up of containers, rows, and columns. Learn more: [Pages](https://www.servicenow.com/docs/toFajOCT1DdxbQY5LNhBvQ "Use pages to organize content, ensure responsive mobile optimization, and design meaningful portal user experiences for your customers. A page houses containers and rows, which then contain widgets. By manipulating the layout of the page, and the widgets within it, you can construct your desired user experience."). | | Content block | A content block is a reusable piece of content. In Service Portal, content blocks are replaced by widgets. Learn more: [Using portal widgets](https://www.servicenow.com/docs/kjFBnrDg7lVbAAVnbgc80g "Widgets are what define the content of your portal pages. You can use the base system widgets provided with Service Portal, clone and modify widgets, or develop custom widgets to fit your own needs."). | | Service Catalog | Service Catalog pages are rendered using the SC Catalog Item widget in Service Portal. For this reason, Service Catalog forms such as catalog items and record producers are shared between your CMS implementation and Service Portal. If you have a highly customized Service Catalog, you may need to invest time in simplifying your Service Catalog items and client scripts so that they render as expected in Service Portal. Learn more: [Service Catalog forms in Service Portal](https://www.servicenow.com/docs/KoPnzKeTJX8kVxGYtwNkAg "Service Catalog forms are rendered within Service Portal widgets in a two-column layout. Complex forms may not display as expected."). | | Theme | [Theme](https://www.servicenow.com/docs/BAoyrAgyiElDA2wYIctIBw "If you need more customizations than the Branding Editor can provide, you can create your own custom theme.") | | CSS | [CSS](https://www.servicenow.com/docs/uhCDDffF5VKB01RKvWd0dw "Pages are made up of containers, columns, rows, widgets, and widget instances. You can configure the CSS of each component, or use the CSS defined in theme and branding as global definitions for the portal. If you do not define CSS in theme or branding, Bootstrap defaults are used.") | [Table 1. CMS and Service Portal components] {#c_CMSAndSP__table_oys_yth_cbb} ## CMS and Service Catalog customizations Service Portal comes with base system widgets to address common use cases and to display record data. Even though there is no direct migration path from CMS to Service Portal, there may be some items, such as catalog items or knowledge articles, that render as expected in Service Portal without any effort. However, because Service Portal is supported in a mobile environment, you may need to modify any customized forms and scripts. This approach ensures that the items display well on a mobile device and present a better user experience. Before transitioning to Service Portal, you may need to: * Refactor client scripts used in your CMS/Service Catalog to use supported mobile APIs and global objects. For a list of supported APIs, see [Service Portal and client scripts](https://www.servicenow.com/docs/xlVPEeVFkQRMjzIiSmnX2g "You can use client scripts and catalog client scripts in the Service Portal if the UI Type is set to Mobile / Service Portal or All. Client scripts and catalog client scripts are used with the Form widget and SC Catalog Item widget, as opposed to a widget client controller."). * Build widgets to replace UI Macros and other unsupported scripts. If using a UI Macro in a catalog item form and referencing values on the form, you can use the following workaround instead: [Replace a Service Catalog form script with a widget](https://www.servicenow.com/docs/Zuu2Hewx4dq~3UaV_GtqoA "You can use widgets in Service Portal to replace UI Macros. If your Service Catalog form includes a UI Macro that references other fields or variables on the form, you can create a widget to hold reusable code and embed it within the Service Catalog form. Use special syntax to access any variable fields on the form."). * Simplify any complex forms used in your Service Catalog to fit the Service Portal two-column form layout. * Consider which release supports the required functionality. You may want to upgrade your instance before transitioning to ensure that you have the required base system features. {#c_CMSAndSP__ul_t2j_njb_cbb} * **[CMS to Service Portal transition](https://www.servicenow.com/docs/h632rrOGnFqgMW3IBctm8g)** Your CMS may include complex forms and customizations that do not render as expected in Service Portal. Use this guide to understand how best to modify your CMS and Service Catalog implementation for Service Portal adoption, and to understand how a conversion may affect your users.