--- sourceDocument: Australia ServiceNow AI Platform user interface sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/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 --- # Configure the standard ticket page # Configure the standard ticket page {#ariaid-title1} * Release version: Australia * * Updated April 22, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Give Service Portal users a consistent way to view their submitted requests. You can configure the standard ticket page for different request types. ## Before you begin Role required: admin or sp_admin ## About this task You can add a standard ticket configuration only for a task-extended table. Widgets containing Date/Time values display the date and time only in the Time Ago (for example, 11 minutes ago) format, and user preferences for such widgets aren't considered. For example, the Created date and the Updated date values are displayed in the Time Ago format. ## Procedure 1. Navigate to AllStandard TicketStandard Ticket Configuration. 2. Select New. 3. On the form, fill in the fields. {#configure-st-page__table_nsc_wyx_2mb__entry__2} | Field | Description | |-|-| | Table | Task-extended table for which you want to configure the standard ticket page. | | Active | Whether the ticket configuration is active. | | Application | Application associated with the ticket configuration. | | State field | Any field of the task-extended table. By default, this field maps to the State field of the task-extended table. You have to configure the form to add this field. Note: You can't add fields for any of the following information: * Number * Short description * Created date * Updated date * Watch list * Any user input such as comments and work notes {#configure-st-page__ul_axr_5jc_fmb} | | Info Region || | Show 'Description' | Scenario when the request description should be displayed. Possible options are: * None * Always * When no variables {#configure-st-page__ul_zgp_fzx_2mb} Note: When displayed, you can expand and collapse the description. | | Description field | Field that the sp_admin can select from the fields of the ticket record (for example, sc_req_item, incident), which is displayed as description on the Standard Ticket Page. | | Advanced | Whether a widget is displayed in the info region. | | Info widget | Widget displayed in the info region. This field appears only when the Advanced check box is selected. | | Info widget parameters | Name value pair for the widget parameters. This field appears only when the Advanced check box is selected. | | Info fields | Fields displayed in the info region. This field disappears when you select the Advanced check box. Note: * You can't add fields for any of the following information: * Number * Short description * Created date * Updated date * Watch list * State * Any user input such as comments and work notes {#configure-st-page__ul_rxz_nkc_fmb} * A field of the workflow type is not 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. {#configure-st-page__ul_tzp_3b2_kpb} | | Action Region || | Action widget | Widget for the actions available in the Action region. Note: If the field is configured, it takes precedence over the standard ticket actions. | | Action widget parameters | Name value pair of action widget parameters. | | Summarization || | Summary fields | Standard ticket page fields that are included in the summary generated by Now Assist. Note: The summary fields in the Summarization tab can't be modified, and new fields can't be added. However, previously configured values are honored and remain visible to requesters. If no fields are configured, this section is hidden entirely. To configure summary fields, use the Standard Ticket Summary Fields related list. Note that at least one summary field must be configured and the ServiceNow Otto® in Standard Ticket Page skill must be active for the Summarize button to appear on the standard ticket page. | [Table 1. Ticket Configuration form] {#configure-st-page__table_nsc_wyx_2mb} 4. Select and hold (or right-click) the header menu and select Save. 5. After you make all the required changes, select Submit. * **[Enable instance options for the Activity tab](https://servicenow-prod.fluidtopics.net/XSyI5KyV2mqWXtatuAtN0w)** Format the work notes and add @mentions in the Activity tab on a standard ticket page. * **[Configure tabs for standard ticket page](https://servicenow-prod.fluidtopics.net/fgJhbzT7ACj_VF8WH9JoSw)** You can configure the tabs for the standard ticket page. * **[Configure actions for standard ticket page](https://servicenow-prod.fluidtopics.net/7PcByLiU4~MSA5r8Q7SFTA)** You can configure specific actions to be directly available on the standard ticket page. Requesters are able to initiate these actions. Scriptable APIs can also trigger these actions. * **[Configure summary fields for standard ticket page](https://servicenow-prod.fluidtopics.net/Xg0ALNEzJPiqtKoIxTHggQ)** Configure summary fields on the standard ticket page such that the page displays the Summarize button, enabling requesters to view ServiceNow Otto®-generated overviews of recent ticket activity and details. **Related tasks** * [Enable instance options for the Activity tab](https://servicenow-prod.fluidtopics.net/XSyI5KyV2mqWXtatuAtN0w "Format the work notes and add @mentions in the Activity tab on a standard ticket page.") * [Configure tabs for standard ticket page](https://servicenow-prod.fluidtopics.net/fgJhbzT7ACj_VF8WH9JoSw "You can configure the tabs for the standard ticket page.") * [Configure actions for standard ticket page](https://servicenow-prod.fluidtopics.net/7PcByLiU4~MSA5r8Q7SFTA "You can configure specific actions to be directly available on the standard ticket page. Requesters are able to initiate these actions. Scriptable APIs can also trigger these actions.") **Related topics** * [Standard Ticket Page](https://www.servicenow.com/docs/access?context=now-assist-in-standard-ticket-page&version=australia&pubname=australia-intelligent-experiences&ft:locale=en-US) *[\>]: and then