--- sourceDocument: Australia ServiceNow AI Platform user interface sourceDocumentLink: https://www.servicenow.com/docs/r/australia/platform-user-interface Release : - australia ft:locale : - en-US ft:publication_title : - Australia ServiceNow AI Platform user interface ft:clusterId : - platux bundleId : - platux workflow : - Platform --- # Standard ticket page # Standard ticket page {#ariaid-title1} Release version: Australia Updated March 12, 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 Australia release provides a consistent and configurable interface for viewing submitted requests across various request types. It enhances user experience by displaying request-specific information while maintaining a uniform layout for all tickets. This page is enabled by default in new instances; however, upgraded instances require activation of the Standard Ticket Route page route map to use this feature. Show full answer Show less ## Key Features * **Header Section:** Displays essential request details such as identification number, creation and update dates, and state. The state field can be customized to represent any relevant ticket status. * **Info Section:** Shows three configurable regions: * Ticket description with short and optionally full description fields, which can be mapped to alternative fields. * Fields region displaying configured fields that have values and are accessible to the user; workflow type fields are generally unsupported except for specific cases like the Stage field on Requested Item \[screqitem\]. * Actions region for user interactions. * **Tabs Section:** Customizable tabs include Activity, Attachments, Variable editor, Variable summarizer, and Associated Requests. The Associated Requests tab shows all related requests based on parent-child relationships, supporting both universal and non-universal tickets. * **Cross-Scope Application Configuration:** Requires restricted caller access privileges for specific widgets and description fields, plus a page route map to ensure all requests for the application route to the standard ticket page. * **Domain Separation:** Tab configurations are not domain-separated, but ticket configurations are process domain-separated. The system resolves configurations by checking the record's domain, its table, and parent tables in the domain hierarchy, ensuring only one active configuration per domain. ## Practical Use for ServiceNow Customers By configuring the Standard Ticket Page, you provide Service Portal users with a streamlined and uniform way to view their requests, improving usability and consistency. For upgraded instances, activating the page route map is essential to redirect existing ticket views to this new standard page. Configuring individual sections and tabs allows tailoring the interface to specific request types and business needs, while domain separation handling ensures multi-domain setups operate correctly. Ensuring proper access privileges and route mappings for cross-scope applications allows seamless integration of custom or third-party apps with the standard ticket page framework. 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/90CUkD8uapH_J~49pr2xPw "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=australia&pubname=australia-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=australia&pubname=australia-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/xNaKiVA4aHGjTUtF3TF1hg)** 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/90CUkD8uapH_J~49pr2xPw)** 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/xNaKiVA4aHGjTUtF3TF1hg "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=australia&pubname=australia-servicenow-platform&ft:locale=en-US) * [Incident standard ticket page](https://www.servicenow.com/docs/access?context=incident-stnd-ticket-page&version=australia&pubname=australia-it-service-management&ft:locale=en-US)