--- 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 --- # Standard ticket page # Standard ticket page {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 Standard ticket page The Standard Ticket Page in ServiceNow provides a consistent layout for viewing submitted requests across different request types. It enables users to see request-specific information while maintaining a uniform experience. This page is available by default in new instances, but upgraded instances require activation of the Standard Ticket Route page route map to enable this feature. Show full answer Show less ## Key Features * **Header Section:** Displays key information such as identification number, creation and update dates, and state. The state field can be customized to represent other ticket status fields. * **Info Section:** Configurable to show regions including: * Ticket Description: Shows short description and optionally the detailed description, which can be mapped to a different field if needed. * Fields Region: Displays associated fields that have values and are accessible to the user. Workflow type fields are generally unsupported except for the Requested Item \[screqitem\] table (e.g., Stage field). * Actions Region: Contains action elements as configured. * **Tabs Section:** Supports tabs such as Activity, Attachments, Variable Editor, Variable Summarizer, and Associated Requests. The Associated Requests tab shows related child requests depending on whether the current ticket is a universal request or not. * **Custom Tabs:** Activity and Attachments tabs are provided by default and can be customized as needed. * **Cross-Scope Application Configurations:** Require restricted caller access privileges for key widgets and the Description field to ensure proper access to application tables. Also requires configuring page route maps to route requests appropriately. * **Domain Separation:** Tab configurations are not domain-separated, but ticket configurations are process domain-separated. The system checks configurations in a specific order across domains and parent hierarchies to determine the active configuration. ## Practical Usage for ServiceNow Customers ServiceNow customers can leverage the Standard Ticket Page to provide end users with a streamlined, consistent interface for viewing requests in Service Portal. Configuration allows tailoring the display to the needs of different request types, showing relevant fields, descriptions, and related requests without compromising the uniform experience. For upgraded instances, activating the Standard Ticket Route page route map is essential to enable this functionality. Adjustments to access privileges and route maps may be necessary for cross-scope applications to ensure all components display correctly. This setup improves user experience by consolidating request information in one place, facilitating easier tracking and management of submitted tickets. Configure individual request types to display the request-specific information, while still having a consistent layout that is similar to other request types. This configuration verifies a consistent experience when viewing submitted requests. For new instances, the standard ticket page is available by default. For upgraded instances, you must activate the Standard Ticket Route page route map. For information about activating this page route map, see [Activate the page route map for the standard ticket page](https://www.servicenow.com/docs/seuJGMBGkEEufxg5okR0Uw "If you have upgraded your instance, redirect the ticket page to standard_ticket page in Service Portal and view requests on the standard ticket page."). The information displayed in each section of a standard ticket page depends on the individual request type. If a configurable section has no specified values or if a user doesn't have access to the information, it isn't visible. Figure 1. Standard ticket page for an incident ## Header section {#standard-ticket-page__section_sj1_hgg_wlb} By default, this section displays the following information for a submitted request: * Identification number * Created and updated dates * State. Instead of the State field, you can also configure any other field that represents the state of the ticket. {#standard-ticket-page__ul_nsf_lhr_xlb} ## Info section {#standard-ticket-page__section_aly_fgg_wlb} If configured, this section displays the following regions for a submitted request: * Ticket description region with the short description, and optionally the description. Note: You can map the Description field to any other field on the record. * Fields region where the associated fields are configured. A configured field isn't visible when it has no value or when a user doesn't have access to the field. Note: A field of the workflow type isn't supported for any table. Only for the Requested Item \[sc_req_item\] table, the workflow type field is supported, for example, the Stage field. This field is displayed at the last irrespective of the field position in the configuration. * Actions region {#standard-ticket-page__ul_ccw_zhr_xlb} ## Tabs section {#standard-ticket-page__section_hml_hgg_wlb} If configured, this section displays the following types of tabs for a submitted request: * Activity * Attachments * Variable editor * Variable summarizer * Associated Requests. Displays all associated requests (visible in the My Requests widget in Service Portal) for which the current ticket is the parent. It's applicable in any of the following scenarios: * If the current ticket is a universal request, then all requests associated (through the Parent field on the task table) with child tickets of the universal request are displayed. * If the current ticket isn't a universal request, then all requests associated (through the Parent field on the task table) with the current ticket are displayed. {#standard-ticket-page__ul_mnc_vlr_jpb} For information on defining filters for the My Requests widget, see [Define filters for My Requests](https://www.servicenow.com/docs/access?context=configure-my-requests&version=brazil&pubname=brazil-servicenow-platform&ft:locale=en-US). * Custom tab {#standard-ticket-page__ul_utc_jkr_xlb} By default, the Activity and Attachments tabs are available. ## Configurations for a cross-scope application {#standard-ticket-page__section_ung_2dw_3mb} For each request type of a cross-scope application, the following configurations are required: * Restricted caller access privileges for the following standard ticket page widgets so that these widgets can access the application tables. For information about these privileges, see [Application access settings](https://www.servicenow.com/docs/access?context=c_ApplicationAccessSettings&version=brazil&pubname=brazil-application-development&ft:locale=en-US). * Widget: Standard Ticket Header * Widget: Standard Ticket Attachments * Widget: Standard Ticket Tab {#standard-ticket-page__ul_bdv_bbw_3mb} * Restricted caller access privileges for the Description field in the application. This field is displayed on the standard ticket page header. * Page route map to route all the requests of that application to the standard ticket page {#standard-ticket-page__ul_nsq_fcw_3mb} ## Domain separation for a standard ticket page {#standard-ticket-page__section_rnj_vky_2mb} Tab configurations aren't domain-separated. Ticket configurations are process domain-separated. For any request type record, when a user opens the standard ticket page, it checks for ticket configurations in the following order irrespective of the user's domain: 1. In the record's domain 1. Ticket configurations for the record table 2. Ticket configurations for the parent table of the record table {#standard-ticket-page__ol_lvh_q5c_fmb} 2. In the record domain's parent hierarchy 1. Ticket configurations for the record table 2. Ticket configurations for the parent table of the record table {#standard-ticket-page__ol_hms_s5c_fmb} {#standard-ticket-page__ol_ohl_45c_fmb} Note: For a table, only one active configuration is enabled per domain. * **[Configure the standard ticket page](https://www.servicenow.com/docs/30n75ktXuhWLT_lceNRCog)** Give Service Portal users a consistent way to view their submitted requests. You can configure the standard ticket page for different request types. * **[Activate the page route map for the standard ticket page](https://www.servicenow.com/docs/seuJGMBGkEEufxg5okR0Uw)** If you have upgraded your instance, redirect the ticket page to standard_ticket page in Service Portal and view requests on the standard ticket page. **Related tasks** * [Configure the standard ticket page](https://www.servicenow.com/docs/30n75ktXuhWLT_lceNRCog "Give Service Portal users a consistent way to view their submitted requests. You can configure the standard ticket page for different request types.") **Related topics** * [Standard ticket page for a requested item](https://www.servicenow.com/docs/access?context=stpage-req-item&version=brazil&pubname=brazil-servicenow-platform&ft:locale=en-US) * [Incident standard ticket page](https://www.servicenow.com/docs/access?context=incident-stnd-ticket-page&version=brazil&pubname=brazil-it-service-management&ft:locale=en-US)