--- sourceDocument: yokohama Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/delta-washingtondc-yokohama Release : - yokohama ft:locale : - en-US ft:publication_title : - yokohama Combined Product Files ft:clusterId : - delta3yw bundleId : - delta3yw --- # Combined Service Portal release notes for upgrades from Washington DC to Yokohama # Combined Service Portal release notes for upgrades from Washington DC to Yokohama {#ariaid-title1} * Release version: Yokohama * * Updated July 9, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 7 minutes to read Consolidated page of all release notes for Service Portal from Washington DC to Yokohama. ## How to use this page To help you prepare for your upgrade, we have combined the cross-family Service Portal release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Washington DC to Yokohama. Tip: If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says "No updates for this release." ## Important information for upgrading Service Portal to Yokohama Before you upgrade to Yokohama, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-serviceportal-summary__entry__2} | Release | Release notes | |-|-| | Washington DC | After upgrading, you must specify the tables from which guest users can access data for any public widgets that accept the table input parameter. By default in the Washington DC release, public widgets that accept the table input parameter can't access and return data from any tables for guest users. If you added the glide.service_portal.widget.table_allow_list or glide.service_portal.widget.allow_list system properties before upgrading, the values of these properties will be migrated to the Public Table Allow List for widgets after upgrading. For more information, see [Configure widget security](https://www.servicenow.com/docs/access?context=configure-widget-security&family=washingtondc&ft:locale=en-US). Additionally, field-level read ACLs are enforced for filter conditions in Simple List widget instances by default. A new system property, glide.service_portal.enable_acls_for_encoded_query_in_list, enforces these ACLs regardless of whether the Enforce field-level Read ACLs on Filter query terms option is selected for Simple List widget instances. To use the Enforce field-level Read ACLs on Filter query terms option, change the value of glide.service_portal.enable_acls_for_encoded_query_in_list to false. For more information, see [Simple List widget](https://www.servicenow.com/docs/access?context=simple-list-widget&family=washingtondc&ft:locale=en-US). If a user previously selected a user consent preference for user experience analytics for portals different from the rest of the platform, the preference selected for the platform is also used for portals in the Washington DC release. For example, if users opted out of tracking for portals but opted in to tracking for the rest of the platform in the Vancouver release, user experience analytics for portals are tracked for them in the Washington DC release. Users can update their selection from the user profile page in portals at any time. | | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | [ ] ## New features Between your current release family and Yokohama, new features were introduced for Service Portal. {#dfrn3-serviceportal-summary__entry__10} | Release | Release notes | |-|-| | Washington DC | [Secure public widgets accessed by guest users](https://www.servicenow.com/docs/access?context=configure-widget-security&family=washingtondc&ft:locale=en-US) : Secure public widgets that accept the table input parameter by specifying the tables from which the widget can access and return data for guest users. [Close all portal notifications at once](https://www.servicenow.com/docs/access?context=properties-service-portal&family=washingtondc&ft:locale=en-US) : Close all notifications at once instead of having to close them individually by selecting Clear All. Portal administrators can use the glide.service-portal.notification.threshold system property to configure the number of notifications that must appear before displaying the Clear All option. The default value is five. | | Xanadu | [Deactivate portals](https://www.servicenow.com/docs/access?context=deactivate-portal&family=xanadu&ft:locale=en-US) : Turn off access to a portal that you don't want users to visit and redirect them to another portal. | | Yokohama | [Analyze the performance of portal pages and their widgets](https://www.servicenow.com/docs/access?context=analyze-page-performance&family=yokohama&ft:locale=en-US) : Set benchmarks against which to analyze the performance of a portal page. Identify widgets on the page that don't meet the performance benchmarks and view details about their performance. [Compare a cloned widget with its base widget](https://www.servicenow.com/docs/access?context=compare-with-base-system&family=yokohama&ft:locale=en-US) : Compare cloned widgets with the base widget from which they were cloned. View differences between the code of the cloned widget and the base widget highlighted in the code comparator. | [ ] ## Changes Between your current release family and Yokohama, some changes were made to existing Service Portal features. {#dfrn3-serviceportal-summary__entry__18} | Release | Release notes | |-|-| | Washington DC | [Critical notifications aren't automatically dismissed](https://www.servicenow.com/docs/access?context=properties-service-portal&family=washingtondc&ft:locale=en-US) : Show critical notifications tagged with the `sn-sticky-notification` HTML class attribute until you specifically dismiss them even when automatic dismissal is enabled for non-critical notifications with the glide.service-portal.notification_timeout.seconds system property. [Unified user consent for tracking user experience analytics](https://www.servicenow.com/docs/access?context=sp-analytics&family=washingtondc&ft:locale=en-US) : Opt in to or out of tracking user experience analytics once for all platform interfaces. Previously, changes to your user consent selection to track user experience analytics in other platform interfaces weren't honored in portals and vice versa. This choice is now stored centrally with the user consent management (UCM) capability used by the rest of the platform so a change for one interface is honored for all interfaces. For more information about user consent management, see [User privacy, tracking, and consent](https://www.servicenow.com/docs/access?context=user-exp-analytics-track-options&family=washingtondc&ft:locale=en-US) in the Usage Insights documentation. | | Xanadu | [Show the current user in the team members list of the User Profile widget](https://www.servicenow.com/docs/access?context=user-profile-widget&family=xanadu&ft:locale=en-US) : Indicate whether to include the logged-in user in the team members list when viewing another team member's user profile from the User Profile widget. [Additional multi-factor authentication options](https://www.servicenow.com/docs/access?context=mfa-use&family=xanadu&ft:locale=en-US) : Log in to portals using a biometric authenticator or hardware security key with multi-factor authentication (MFA). | | Yokohama | [Use ECMAScript 2021 (ES12) JavaScript mode in server scripts for widgets](https://www.servicenow.com/docs/access?context=widget-dev-guide&family=yokohama&ft:locale=en-US) : Use features supported in the ECMAScript 2021 (ES12) JavaScript mode in server-side scripts for widgets by selecting Turn on ECMAScript 2021 (ES12) mode from the widget record or Widget Editor. For information about features supported in the ECMAScript 2021 (ES12) JavaScript mode, see [JavaScript engine feature support](https://www.servicenow.com/docs/access?context=javascript-engine-feature-support&family=yokohama&ft:locale=en-US). [Define roles for page route maps](https://www.servicenow.com/docs/access?context=reroute-page&family=yokohama&ft:locale=en-US) : Control which users are redirected to a new page based on a page route map. Specify the user roles to apply in the Page Route Map form. [Improved redirection for single sign-on (SSO) authentication](https://www.servicenow.com/docs/access?context=c_SPSSOLoginAndRedirects&family=yokohama&ft:locale=en-US) : Improved the experience of logging in to portals that use single sign-on (SSO) authentication by redirecting to the SSO Identify Provider (IdP) login page without trying to load the portal page first. [Enforce providing comments when rejecting requests](https://www.servicenow.com/docs/access?context=approvals-widget&family=yokohama&ft:locale=en-US) : Require approvers to provide comments when rejecting a request from the Approvals widget. Administrators can enable requiring comments from the widget instance options. [Check cross-scope privileges to a table with the Form widget](https://www.servicenow.com/docs/access?context=form-widget&family=yokohama&ft:locale=en-US) : Validate access to tables from which the Form widget fetches data. The Form widget checks for the necessary cross-scope privileges to a table by default. | [ ] ## Removed Between your current release family and Yokohama, some Service Portal features or functionality were removed. {#dfrn3-serviceportal-summary__entry__26} | Release | Release notes | |-|-| | Washington DC | No updates for this release. | | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | [ ] ## Deprecations Between your current release family and Yokohama, some Service Portal features or functionality were deprecated. {#dfrn3-serviceportal-summary__entry__34} | Release | Release notes | |-|-| | Washington DC | No updates for this release. | | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | [ ] ## Activation information Review information on how to activate Service Portal. {#dfrn3-serviceportal-summary__entry__42} | Release | Release notes | |-|-| | Washington DC | Service Portal is a ServiceNow AI Platform feature that is active by default. | | Xanadu | Service Portal is a ServiceNow AI Platform feature that is active by default. | | Yokohama | Service Portal is a ServiceNow AI Platform feature that is active by default. | [ ] ## Additional requirements If any additional requirements were introduced or changed for Service Portal we have noted them here. {#dfrn3-serviceportal-summary__entry__50} | Release | Release notes | |-|-| | Washington DC | No updates for this release. | | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | [ ] ## Browser requirements If any specific browser requirements were introduced or changed for Service Portal we have noted them here. {#dfrn3-serviceportal-summary__entry__58} | Release | Release notes | |-|-| | Washington DC | The Washington DC release doesn't support Internet Explorer 11. The iOS version of Firefox doesn't support Service Portal pages. | | Xanadu | The Xanadu release doesn't support Internet Explorer 11. The iOS version of Firefox doesn't support Service Portal pages. For more information about Service Portal browser support, see [Browser support](https://www.servicenow.com/docs/access?context=browser-support&family=xanadu&ft:locale=en-US). | | Yokohama | The Yokohama release doesn't support Internet Explorer 11. The iOS version of Firefox doesn't support Service Portal pages. For more information about Service Portal browser support, see [Browser support](https://www.servicenow.com/docs/access?context=browser-support&family=yokohama&ft:locale=en-US). | [ ] ## Accessibility information Review details on accessibility information for Service Portal, such as specific requirements or compliance levels. {#dfrn3-serviceportal-summary__entry__66} | Release | Release notes | |-|-| | Washington DC | No updates for this release. | | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | [ ] ## Localization information If there are specific localization considerations for Service Portal we have noted them here. {#dfrn3-serviceportal-summary__entry__74} | Release | Release notes | |-|-| | Washington DC | No updates for this release. | | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | [ ] ## Highlight information If there are specific highlight considerations for Service Portal we have noted them here. {#dfrn3-serviceportal-summary__entry__82} | Release | Release notes | |-|-| | Washington DC | * Secure public widgets that accept the table input parameter. * Show critical notifications until you dismiss them. * Opt in to or out of user experience analytics tracking once for all platform interfaces. * Clear all portal notifications at once. See [Service Portal](https://www.servicenow.com/docs/access?context=c_ServicePortal&family=washingtondc&ft:locale=en-US) for more information. | | Xanadu | Deactivate a portal and optionally redirect users to an alternate portal. See [Service Portal](https://www.servicenow.com/docs/access?context=c_ServicePortal&family=xanadu&ft:locale=en-US) for more information. | | Yokohama | * Analyze the performance of portal pages and their widgets. * Compare cloned widgets with the base widget from which they were cloned. * Use ECMAScript 2021 (ES12) JavaScript mode in widget server scripts. * Enable early single sign-on (SSO) redirection. * Specify the user roles that apply to a page route map. See [Service Portal](https://www.servicenow.com/docs/access?context=c_ServicePortal&family=yokohama&ft:locale=en-US) for more information. | [ ]