---
sourceDocument: Yokohama Release Notes
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/release-notes
Release :
- yokohama
ft:locale :
- en-US
ft:publication_title :
- Yokohama Release Notes
ft:clusterId :
- rn
bundleId :
- rn
---
# Changes to Yokohama features and products
# Changes to Yokohama features and
products {#ariaid-title1}
Release version: Yokohama
Updated September 10, 2026
 166 minutes to read
Cumulative release notes summary on changes to Yokohama features and
products.
Existing products were updated and changed in Yokohama. This includes the renaming of certain buttons or features. {#rn-summary-changes__rn-summary-changes-table__entry__2}
| Application or feature | Details |
|-|-|
| AI Analytics | Overall health : The Overall health dashboard page has been renamed to Usage and Adoption. The new page includes more indicators on usage and adoption of Now Assist. |
| AI Control Tower | [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Configure ACLs for AI agents and agentic workflows](https://www.servicenow.com/docs/access?context=aia-security-implementation&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all authenticated users or publicly available. [Yokohama Patch 3](https://www.servicenow.com/docs/jXrkPnnmOuaGleV7JYQPtA "The Yokohama Patch 3 release contains important problem fixes.") : Enhancements to landing page dashboards for AI steward. |
| AI Search | [Now Assist Multi-Content Response Genius Results](https://www.servicenow.com/docs/access?context=now-assist-multi-content-qna-genius-results&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : If you have Now Assist in AI Search installed, Now Assist Multi-Content Response Genius Results are supported in global and workspace search. Activating Now Assist Multi-Content Response Genius Results in global or workspace search profiles overrides all other Genius Result configurations, so that global and workspace searches only display Genius Result answers from Now Assist Multi-Content Response Genius Results. Virtual Agent topic citations from Now Assist Multi-Content Response Genius Result answers in global or workspace search open the selected topic in the Now Assist panel so the user can continue their conversation on that topic. [Search Suggestions](https://www.servicenow.com/docs/access?context=search-suggestions-overview&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Search administrators with the ais_admin granular admin role can access all Search Suggestions tables. Assign search administrators this role to eliminate needless propagation of full admin access. [Gain insights into search behavior with a refreshed and updated Search Preview UI.](https://www.servicenow.com/docs/access?context=search-preview-ui-new&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Preview search query results using settings from a search application configuration or a search profile. Choose between keyword and hybrid search modes. Display search results as individual EVAM cards or as a JSON-format search query response object, with search and syntax highlighting. Review search query behavior and results and specify search query settings with the new Summary, Genius Results, Details, and Profile admin tools. [Consumer-grade search experience for search portals](https://www.servicenow.com/docs/access?context=viewing-search-results-ais&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : The search results page for search portals has been revised to offer a more intuitive and consistent experience. Navigation tabs have been replaced with source facet buckets. All search results now open in a new browser tab, preserving your search in the existing browser tab. Facet buckets now show minimum search result counts, reflecting results removed by late binding content security. Search terms are no longer highlighted in search results. [Consumer-grade search experience for global search and workspace search](https://www.servicenow.com/docs/access?context=using-ais-next-experience-app&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : The search results page for global search and workspace search has been revised to offer a more intuitive and consistent experience. Navigation tabs have been replaced with source facet buckets. All search results now open in a new browser tab, preserving your search in the existing browser tab. Facet buckets now show minimum search result counts, reflecting results removed by late binding content security. A new glide.ui.ais.show_all_facets system property enables you to display facets from all sources when no source is selected. (The default behavior is to hide facets until a source is selected.) Search terms are no longer highlighted in search results. [Sort facet buckets alphabetically](https://www.servicenow.com/docs/access?context=create-facet-ais&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Override the default sorting of facet buckets by their search result counts and display them sorted alphabetically by their labels. [Improved display for grouped attachment search results](https://www.servicenow.com/docs/access?context=grouping-attachment-srch-results-ais&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : When grouped with their parent search results, attachment search results now appear in collapsed form to save space. If a parent search result includes more than three grouped attachments, you can use the new Show more and Show less links to control how many attachments are visible. |
| AI Skill Kit | [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Configure ACLs for AI agents and agentic workflows](https://www.servicenow.com/docs/access?context=aia-security-implementation&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all authenticated users or publicly available. [Now Assist Skill Kit add tools function moved to Tool editor tab.](https://www.servicenow.com/docs/access?context=add-a-tool&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The ability to add and edit tools for Now Assist Skill Kit previously appeared on the Prompt editor tab. It now appears on the Tool editor tab. |
| AIOps LEAP | [Pin automation opportunities](https://www.servicenow.com/docs/access?context=aiops-leap-features&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US) : You can pin the automation opportunities required for ease of access and research. [Automation feedback and tracking](https://www.servicenow.com/docs/access?context=aiops-leap-features&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US) : You can provide your feedback on the available resolution steps and playbooks. Each activity on the automation activity is tracked and recorded. [Filters for automation opportunities and playbooks](https://www.servicenow.com/docs/access?context=aiops-leap-features&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US) : You can customize filters on the automation opportunity dashboard to filter them according your requirement for analysis. These filters are retained even when the page is refreshed. |
| API | {#rn-summary-changes__table_x1g_1mc_tcc__entry__2} | Class | Methods | |-|-| | [PDFGenerationAPI - Scoped, Global](https://www.servicenow.com/docs/access?context=PDFGenerationAPIBothAPI&version=yokohama&pubname=yokohama-api-reference&ft:locale=en-US) | * convertToPDF() * convertToPDFWithHeaderFooter() {#rn-summary-changes__ul_wcy_wvq_12c} New properties, glide.pdf.url.whitelisting.enabled and com.snc.pdf.whitelisted_urls, have been added to ensure whether external URLs provided should be rendered in the PDF output. A new property, accessibilityEnabled, has been added for PDF accessibility support. | [Table 1. Changed scoped classes in Yokohama] {#rn-summary-changes__table_x1g_1mc_tcc} {#rn-summary-changes__table_omt_fmc_tcc__entry__2} | Class | Methods | |-|-| | [PDFGenerationAPI - Scoped, Global](https://www.servicenow.com/docs/access?context=PDFGenerationAPIBothAPI&version=yokohama&pubname=yokohama-api-reference&ft:locale=en-US) | * convertToPDF() * convertToPDFWithHeaderFooter() {#rn-summary-changes__ul_t1n_zvq_12c} New properties, glide.pdf.url.whitelisting.enabled and com.snc.pdf.whitelisted_urls, have been added to ensure whether external URLs provided should be rendered in the PDF output. A new property, accessibilityEnabled, has been added for PDF accessibility support. | [Table 2. Changed global classes in Yokohama] {#rn-summary-changes__table_omt_fmc_tcc} {#rn-summary-changes__table_lcz_gmc_tcc__entry__2} | API | Endpoints | |-|-| | [Attachment API](https://www.servicenow.com/docs/access?context=c_AttachmentAPI&version=yokohama&pubname=yokohama-api-reference&ft:locale=en-US) | POST /now/attachment/file: A new parameter, creation_time, can be used to capture attachment creation times when the Now Mobile app is offline and the attachment is uploaded to a record at a later time. | [Table 3. Changed REST APIs in Yokohama] {#rn-summary-changes__table_lcz_gmc_tcc} |
| Accounts Payable Operations | [Work with invoices](https://www.servicenow.com/docs/access?context=work-with-invoices&version=yokohama&pubname=yokohama-source-to-pay-operations&ft:locale=en-US) : * Invoice line statuses are updated as: * PO matching error to Mapping error * PO matching completed to Mapping complete * Matching error to Mapping error * Review mapping {#rn-summary-changes__ul_zzg_wcl_y2c} {#rn-summary-changes__ul_uqd_b41_tdc} |
| Adoption Services | [Guided Setup](https://www.servicenow.com/docs/access?context=guided-setup&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) : Choose from the playbook player and Next Experience and explore improved navigation across Guided Setup activities. [Guided Setup](https://www.servicenow.com/docs/access?context=guided-setup&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) : Assign and transfer Guided Setup tasks to relevant users, for execution. This capability requires admin roles.Set Guided Setup steps as mandatory by disabling the skip action.You can now run the Guided Setup player or builder multiple times.Select the multi-run feature while you're configuring and executing the tasks multiple times. [Help Center](https://www.servicenow.com/docs/access?context=help-center&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) : The Help Center panel is now attachable and detachable from the header. You can also drag and resize it after you detach it. This feature is available with a keyboard, for accessibility support. [Guided Tours](https://www.servicenow.com/docs/access?context=guided-tours&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) : Guided Tours is now accessible in dark and light themes. This capability now inherits any theme-based color and scheme that you select. [Help Center](https://www.servicenow.com/docs/access?context=help-center&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US){#rn-summary-changes__adoption-services-rn-rn-workspace} : Navigate to What's New within the Help Center panel across all experiences, including Core UI. Starting in the Yokohama release, configuration support for this new feature is available in classic and custom pages.This feature isn't supported for non-Polaris users. |
| Advanced AI Search Management Tools | [AI Search analytics dashboard](https://www.servicenow.com/docs/access?context=ai-search-analytics-dashboard&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : The performance metrics, trends, and charts for this dashboard have been refreshed to offer a cleaner visual experience. [AI Search analytics dashboard](https://www.servicenow.com/docs/access?context=ai-search-analytics-dashboard&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : The Date range interactive filter now enables you to access data from the last 180 days, rather than the last 90 days. |
| Advanced Risk | [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). |
| Agent Client Collector | : Starting in version 1.1.0, ACC for Visibility has been renamed as Kubernetes Visibility Agent and consists only of what is currently CNO for Visibility. The term CNO for Visibility has been deprecated and replaced with Kubernetes Visibility Agent. All other ACC for Visibility functions are now part of Agent Client Collector for Visibility Content. [Explore metrics with Metric Explorer independent of Agent Client Collector Monitoring](https://www.servicenow.com/docs/access?context=agent-workspace-ops-intelligence&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US) : Starting in version 4.1.0, view and monitor metric data with Metric Explorer, even if you have not installed Agent Client Collector Monitoring. |
| Agent experience for CSM | [Customer Activity Guided Setup now accessible from a new location](https://www.servicenow.com/docs/access?context=configure-customer-activity&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US) : Use the following updates in Guided Setup to enhance navigation and access customer history configurations: * Access the Customer Activity Guided Setup from AllCustomer CentralCustomer ActivityGuided Setup. * View Activity Contexts, Activity Types, Activity Groups, and Activity Type Templates within Guided Setup. You can also access them in the menu by navigating to AllCustomer CentralCustomer ActivityGuided Setup. * Customer Activity has been renamed to Customer History, maintaining the same functionality. * Access the Business Rule in the Activity Feed where it is now listed independently alongside Activity Types, Activity Groups, and Activity Type Templates for improved accessibility. Previously, it was nested under Activity Types. {#rn-summary-changes__ul_xmt_xff_w2c} [Front-line case page lookup component](https://www.servicenow.com/docs/access?context=csm-front-line-case-page&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US#section_dnl_3f4_s1c) : The Front-line case page includes the following enhancements: * Includes the Consumer lookup component. * Uses advanced search to look up contacts and consumers. * Contact and consumer record cards can be collapsed to display more record space. {#rn-summary-changes__ul_rnx_b3v_w2c} [Action bar layout](https://www.servicenow.com/docs/access?context=csm-front-line-case-page&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US#section_imv_qhs_mbc) : The following interaction record pages include an action bar with a single action layout: * CSM Interaction record page * CSM voice interaction record page {#rn-summary-changes__ul_gjc_p3v_w2c} [Comment and Work note modeless dialogs](https://www.servicenow.com/docs/access?context=csm-front-line-case-page-modeless-dialogs&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US#section_gzj_wlb_s2c) : Create and use form templates that add content to the Additional comments and Work notes fields on a case record. Automatically display a modeless dialog that includes the content from the form template and then post that content to the activity stream. [Customer History component features](https://www.servicenow.com/docs/access?context=customer-history-component-features&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US) : Use the following features to provide agents real-time updates and customer history details: * Automatically refresh the Customer History component when account, contact, or consumer details change. * Prompt agents to add missing account or contact details instead of leaving fields empty. * Display an empty component until an agent links a contact using the lookup component, then show the contact's details. * Enables agent to view updated customer information directly in Customer History on the Front-line Case page. {#rn-summary-changes__ul_zqj_vfp_w2c} [Front-line case page integration with knowledge guidance](https://www.servicenow.com/docs/access?context=csm-front-line-case-page&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US) : Enable agents to attach and add links to knowledge articles in comments, work notes, or emails by using modeless dialogs. [Resurface special handling notes](https://www.servicenow.com/docs/access?context=c_OnScreenAlerts&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US) : Display the special handling notes for a case at any time by selecting Special handling notes from the More actions menu on the case record action bar. [Customer Central application moved from family to store release](https://www.servicenow.com/docs/access?context=customer-central&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US) : Starting with the Yokohama release, the Customer Central application (com.sn_csm_customer_central) has moved to the ServiceNow Store. Any new enhancements to this application are delivered through the Customer Central store app. [Recommended Actions AI search replaces Agent Assist](https://www.servicenow.com/docs/access?context=csm-front-line-case-page&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US#section_trg_ypr_m1c) : Recommended Actions AI search replaces Agent Assist in the contextual side panel for the following record pages included with the CSM Configurable Workspace: * CSM default record page * Front-line case page * CSM Interaction record page (for type = Chat, Video, Walkup, Email) {#rn-summary-changes__ul_c52_wjv_w2c} [Form template enhancements](https://www.servicenow.com/docs/access?context=csm-workspace-form-templates&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US){#rn-summary-changes__customer-service-config-ws-rn-rn-workspace} : Use the following form template enhancements to create or edit templates as needed: * The Templates tab in the configurable side panel displays larger template cards with the template name and an expanded description. Users can view different lists of templates, mark their favorites, and sort templates either alphabetically or by last used. * The template form displays template fields in a clearly labeled form section and displays the line numbers and headings for each template line to improve readability * The template tab header displays "Edit template" when a user opens a template in edit mode. {#rn-summary-changes__ul_cpt_s4f_3dc} [Front-line case page contextual side panel](https://www.servicenow.com/docs/access?context=csm-front-line-case-page&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US#section_trg_ypr_m1c) : The Record Information tab in the contextual side panel includes the Overview and Active SLA cards. The contact card and timeline card have been removed to improve the page load time. |
| Application Manager | [Unlicensed application information](https://www.servicenow.com/docs/access?context=available-for-you-app-mgr&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : In addition to details about applications that are already licensed, the "Available for you" tab of the Application Manager now includes information about applications that haven't been procured from the ServiceNow Store yet. |
| Audit Management | [Reflow for Configurable Workspace](https://www.servicenow.com/docs/access?context=auto-reflow&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) : The Audit Management configurable workspace supports reflow, which enables pages and content to be zoomed up to 400% through your browser settings without loss of content or functionality. |
| Authentication | [Multi-factor Authentication enforcement](https://www.servicenow.com/docs/access?context=mfa-enforcement&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US) : MFA is mandated and is enforced to all the non-SSO login users accessing ServiceNow®. |
| Business Continuity Management | [Using latest assessment template for conducting BIAs](https://www.servicenow.com/docs/access?context=using-smart-asmt-template&version=yokohama&pubname=yokohama-governance-risk-compliance&ft:locale=en-US) : * The BIA form displays the assessment questionnaire that is based on the latest assessment template. The Assessments tab in the BIA record page has been enhanced to eliminate repetitive UI actions and reduce large empty spaces. The latest assessment template includes additional question types such as drop-down, references, text, attachments, check boxes, date, time, and number value inputs. * The PDF template for the BIA has been updated to include the questions and answers that are based on the latest assessment template. {#rn-summary-changes__ul_dps_mhj_tdc} [Adopting UIB page for improved performance](https://www.servicenow.com/docs/access?context=crisis-map-migration&version=yokohama&pubname=yokohama-governance-risk-compliance&ft:locale=en-US) : The enhancements to the Crisis map user interface are: * Alerts are displayed in the side panel of the Crisis map application. * The alert details page includes the Open alert and Dismiss alert UI actions, which enable you to either open or dismiss alerts. * The active alerts can be sorted by using the Severity, Created, Updated fields, and can also be toggled from top-to-bottom or bottom-to-top by using the Toggle option. * The alerts display can be updated with the Refresh icon ![Refresh icon.](). * The active and dismissed alerts are now displayed on the Alerts page. {#rn-summary-changes__ul_sbc_plx_mdc} [Using nested plans](https://www.servicenow.com/docs/access?context=creating-nested-plan-in-event&version=yokohama&pubname=yokohama-governance-risk-compliance&ft:locale=en-US) : The enhancements to the nested plans user interface are: * The hierarchical view shows the nested event tasks. * The progress bar displays the progress of the creation of related plans, event assets, or event tasks. {#rn-summary-changes__ul_qx4_hkn_tdc} [Using latest assessment template for conducting BIAs](https://www.servicenow.com/docs/access?context=using-smart-asmt-template&version=yokohama&pubname=yokohama-governance-risk-compliance&ft:locale=en-US){#rn-summary-changes__grc-business-continuity-management-rn-rn-workspace} : You can use the latest assessment template to conduct the Business Impact Analysis (BIA). |
| Case management for CSM | [Case lines and workflows](https://www.servicenow.com/docs/access?context=case-line-form&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US) : The Case Line table (sn_case_line) includes the Install base and Asset reference fields. These fields display information based on the selected account and product. [Process mining](https://www.servicenow.com/docs/access?context=process-config-builder&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US){#rn-summary-changes__customer-service-management-rn-rn-workspace} : Use the process mining enhancements to improve processes as needed: * Removed the viewer role from all records in the Process Mining Content Pack for Customer Service Management (CSM). * Set process configurations as read-only templates, deletable only by a process mining administrator. You can enable customers to copy the template or import specific parts into their custom configuration. {#rn-summary-changes__ul_j13_x3q_sdc} |
| Code Signing | [Enhancements to the guardrails check](https://www.servicenow.com/docs/access?context=cse-ppi-config&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US) : The Code Signing Guardrails check has been improved to enhance signature verification, resulting in more secure workflows. In addition, multiple optimizations have been implemented to improve the performance benchmarks of the Guardrails scan, and log files now feature a more intuitive naming convention, which simplifies file identification within your system. |
| Collaborative Work Management | [Improved navigation in the workspace](https://www.servicenow.com/docs/access?context=cwm-spaces&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US) : The improved navigation panel provides a simpler and cleaner user interface. At a given time, the navigation panel shows the contents of just one Space to provide a distraction-free experience while you work.Use the Spaces menu to choose a different Space or use the Search option to quickly find and open any Space, Board or Doc.Additionally, you can also choose to resize the navigation panel or collapse it altogether to increase the working area for your Boards or Docs. [Verify content through browser spell checks](https://www.servicenow.com/docs/access?context=cwm-docs&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US) : Identify and manage incorrect spellings in typed or pasted content in a Doc. The incorrect spellings are highlighted automatically, and you can correct them using the right-click menu options on the highlighted word. [Improved user experience for adding hyperlinks in Docs](https://www.servicenow.com/docs/access?context=cwm-docs&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US) : Insert hyperlinks in a Doc easily and quickly through the formatting toolbar, inline commands, or by pasting a copied link. The pasted URL can be converted into a hyperlink by pressing the Space or Enter key and edited using the inline edit modal. [Numbering on automation cards](https://www.servicenow.com/docs/access?context=manage-or-delete-automations-in-cwm&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US) : Instead of record numbers, Board automation cards show a sequential list numbering of 1, 2, 3, and so on. Error messages use these list numbers so you can easily identify an existing automation from the list of available automations for the Board. [Improved user experience for copying links of Boards](https://www.servicenow.com/docs/access?context=board-views-in-cwm&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US) : Ensure that your team sees the same data as you while sharing links of your Boards through the Copy link action, which now accesses the linked workspace showing the view in which the Board is displayed to you regardless of the user's view settings. [Redirection to the CWM task from notification emails](https://www.servicenow.com/docs/access?context=cwm-boards&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US) : Access task details when you open a task from an assignment email from CWM in a new browser tab in the context of its Board rather than being directed to the workspace home page. [Redirection to the specific doc pages from notification emails](https://www.servicenow.com/docs/access?context=cwm-docs&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US) : Access the specific Doc page that you are @-mentioned in by selecting View Doc in the notification email, eliminating the need to look through multiple pages in the Doc. [Reflow for Configurable Workspace](https://www.servicenow.com/docs/access?context=auto-reflow&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) : The CWM workspace supports reflow, which enables pages and content to be zoomed up to 400% through your browser settings without loss of content or functionality. |
| Common Core | [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Create data relationships](https://www.servicenow.com/docs/access?context=create-data-relationships&version=yokohama&pubname=yokohama-governance-risk-compliance&ft:locale=en-US) : The Data Relationship tab has been added to the template configuration record as part of the configuration process for the Document designer Microsoft Word add-in. [Column Organization](https://www.servicenow.com/docs/access?context=create-an-audit-report-template&version=yokohama&pubname=yokohama-governance-risk-compliance&ft:locale=en-US) : You can select and reorder columns when adding a table into your template by using the Document designer Microsoft Word add-in. You can now organize your content better to meet your reporting needs. [Create content configurations](https://www.servicenow.com/docs/access?context=create-content-configurations&version=yokohama&pubname=yokohama-governance-risk-compliance&ft:locale=en-US) : You can add up to 20 columns in a table and content block by using the Document designer application. You now have more flexibility with customizing your table and content block to meet your reporting needs. |
| Compliance Case Management | [Roles updated for smart assessment](https://www.servicenow.com/docs/access?context=roles-compliance-case-management&version=yokohama&pubname=yokohama-governance-risk-compliance&ft:locale=en-US) : The following roles in Compliance Case Management have been updated with respect to smart assessments. * sn_comp_case.compliance_case_admin * sn_comp_case.compliance_case_analyst * sn_comp_case.compliance_case_business_user * sn_comp_case.compliance_case_manager {#rn-summary-changes__ul_mcl_svk_sdc} [Reflow for Configurable Workspace](https://www.servicenow.com/docs/access?context=auto-reflow&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) : The Compliance Management configurable workspace supports reflow, which enables pages and content to be zoomed up to 400% through your browser settings without loss of content or functionality. |
| Configuration Management Database (CMDB) | [Access changes for the sn_cmdb_editor and sn_cmdb_admin user roles](https://www.servicenow.com/docs/access?context=installed-with-cmdb-workspace&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) : * Starting with Yokohama Patch 4 (zbooted or upgraded), access has been reduced for the sn_cmdb_editor (CMDB Editor) and the sn_cmdb_admin (CMDB Admin) user roles which are used in [CMDB Workspace](https://www.servicenow.com/docs/access?context=cmdb-workspace&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US). The sn_cmdb_editor and sn_cmdb_admin user roles no longer have create, update, or delete access to records in the Configuration Item \[cmdb_ci\] class. * Starting with Yokohama Patch 6 (zbooted or upgraded), you must manually run the scheduled job 'Remove CMDB Roles from ITIL roles and Add CUD access to sn_cmdb_admin/sn_cmdb_editor roles to configure the sn_cmdb_admin and the sn_cmdb_editor user roles with the permissions that are necessary for performing some CMDB Workspace tasks. This scheduled job modifies user roles as follows: * Updates the itil user role to no longer contain the sn_cmdb_editor user role, and updates the itil_admin user role to no longer contain the sn_cmdb_admin user role. * If those permissions don't exist, updates the sn_cmdb_admin and the sn_cmdb_editor user roles with create, update, and delete access to the Configuration Item \[cmdb_ci\] class. For more information about the 'Remove CMDB Roles from ITIL roles and Add CUD access to sn_cmdb_admin/sn_cmdb_editor roles' scheduled job, see [Remove sn_cmdb_admin from itil_admin and sn_cmdb_editor from itil, and then add create/update/delete access to cmdb_ci table for sn_cmdb_admin / sn_cmdb_editor \[KB2290506\]](https://support.servicenow.com/kb_view_customer.do?sysparm_article=KB2290506). {#rn-summary-changes__ul_ztk_mbz_vfc}{#rn-summary-changes__patch-rn-yp6-2} {#rn-summary-changes__ul_ytk_mbz_vfc} [CMDB Workspace v7.5](https://www.servicenow.com/docs/access?context=cmdb-workspace&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) : In the CMDB Workspace version 7.5, you can now do the following tasks: * Delete CMDB Data Manager retirement definitions in CMDB Workspace (other than the cmdb_ci retirement definition). For more information, see [Delete a CMDB Data Manager retirement definition](https://www.servicenow.com/docs/access?context=data-manager-manage-ret-def-wrkspc&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US). * Configure a CMDB Data Manager certification policy to disallow reviewers, to update fields' value while reviewing CIs in a certification task. Administrators can clear the Allow updates to field values option to prevent reviewers from updating non-compliant field values into compliance, resulting in rejecting those CIs. For more information, see [Create a CMDB Data Manager policy in CMDB Workspace](https://www.servicenow.com/docs/access?context=data-manager-create-policy-wrkspc&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US). * Schedule a de-duplication template for daily, weekly, monthly, or periodic runs for continuous remediation of duplicate CIs. For more information, see [Schedule a de-duplication template](https://www.servicenow.com/docs/access?context=workspc-dedup-schedule-template&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US). * Receive notifications from CMDB Data Manager about certification and attestation tasks, that are incomplete or overdue. For more information, see [Components related to CMDB Data Manager](https://www.servicenow.com/docs/access?context=components-cmdb-data-manager&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US). * Review and process tasks of your direct reports and of members of any user group that you manage. For more information about accessing these tasks in CMDB Data Manager, see [My Work view in CMDB Workspace](https://www.servicenow.com/docs/access?context=cmdb-workspace-govern-view&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US). * Reject a CMDB Data Manager life-cycle task in CMDB Workspace. For more information, see [Review CMDB Data Manager tasks in CMDB Workspace](https://www.servicenow.com/docs/access?context=data-manager-review-task-wrkspc&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US). * Use the Create CI experience with a preset class when drilling down a class in the CI Summary chart on the Home view of CMDB Workspace. For more information about creating CIs manually while applying IRE processes, see [Create a CI manually in CMDB Workspace](https://www.servicenow.com/docs/access?context=create-ci-manual-cmdb-workspace&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US). {#rn-summary-changes__ul_etr_1vb_q2c} [CMDB Workspace v6.4](https://www.servicenow.com/docs/access?context=cmdb-workspace&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) : You can now use dot-walking when setting assignments for the User Field or User Group Field options for CMDB Data Manager policies (such as Certification). Also, when converting legacy certification schedules into Data Manager Certification policies, existing dot-walking settings are preserved. For more information, see [Create a CMDB Data Manager policy in CMDB Workspace](https://www.servicenow.com/docs/access?context=data-manager-create-policy-wrkspc&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US). [CMDB Workspace v7.4](https://www.servicenow.com/docs/access?context=cmdb-workspace&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) : In the CMDB Workspace version 7.4, you can now do the following tasks: * Manually create a CI in CMDB Workspace that complies with its class identification rule and other class requirements, and is tested for uniqueness in CMDB, to help ensure that the CI is valid and maintains the integrity of CMDB. For more information, see [Create a CI manually in CMDB Workspace](https://www.servicenow.com/docs/access?context=create-ci-manual-cmdb-workspace&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US). * Set the CMDB Health dashboard to use the legacy methods to calculate the completeness, correctness, and compliance KPIs. That legacy calculation method relies on settings of proportional weights of metrics within the aggregated score of KPIs and was used up until the Washington DC release. By default, those weights aren't used in the calculations of KPI scores. Also, the CMDB Health dashboard now shows the overall score, which by default, is a simple average of the aggregated scores of the completeness, correctness, and compliance KPIs. {#rn-summary-changes__ul_w5c_cpw_sdc} [CMDB Workspace v6.3](https://www.servicenow.com/docs/access?context=cmdb-workspace&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) : * Apply the filters that were previously available only to the coverage charts to all charts in the Discovery sources tile in the CMDB 360 dashboard. For example, you can filter out non-CMDB tables or include records only from principal classes. For more information, see [CMDB 360 experience in CMDB Workspace](https://www.servicenow.com/docs/access?context=cmdb360-exp-cmdb-workspace&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US). * Use a condition builder or a custom script to narrow down the list of de-duplication tasks that are assigned to a template. For more information, see [Create a de-duplication template](https://www.servicenow.com/docs/access?context=workspc-dedup-create-template&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US). * Use the new Allow empty field values option to allow or disallow certification of empty value fields when creating a certification policy type in CMDB Data Manager. For more information, see [Create a CMDB Data Manager policy in CMDB Workspace](https://www.servicenow.com/docs/access?context=data-manager-create-policy-wrkspc&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US). {#rn-summary-changes__ul_xmh_t3w_xcc} [Update to the Walk stage reports on the CSDM Data Foundations dashboard](https://www.servicenow.com/docs/access?context=csdm-datafdn-dash-walk-tab&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) : The Technical Service Offerings with Support Group or Change Group report now includes data that meets the sys_class _name = offering parameter. [Table label changes](https://www.servicenow.com/docs/access?context=cmdb-tables-details&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) : The following table labels have changed: * The label for the cmdb_ci_service_auto table is now Service Instance instead of Application Service. * The label for the cmdb_ci_service_technical table is now Technology management service instead of Technical service. {#rn-summary-changes__ul_mds_vqw_sdc} [Class descriptions showing in the user interface](https://www.servicenow.com/docs/access?context=cmdb-tables-details&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) : The descriptions for the base system classes are now integrated into CI Class Manager and appear in the Description field, on the Basic Info page for a class. [Reflow for configurable workspace](https://www.servicenow.com/docs/access?context=auto-reflow&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) : The CMDB configurable workspace supports reflow, which enables pages and content to be zoomed up to 400% through your browser settings without loss of content or functionality. |
| Continuous Authorization and Monitoring | [Generate the OSCAL SSP model of an authorization package](https://www.servicenow.com/docs/access?context=generate-oscal-models&version=yokohama&pubname=yokohama-governance-risk-compliance&ft:locale=en-US) : Export the SSP model of an authorization package in the OSCAL format. The exported report contains only the control objectives linked to the authorization package and their additional information, such as inherited controls and the hierarchy of the control objectives. [Generate ATO artifacts in Microsoft Word and HTML templates](https://www.servicenow.com/docs/access?context=generate-ato-artifacts-cam-ws&version=yokohama&pubname=yokohama-governance-risk-compliance&ft:locale=en-US) : Use the Document designer plugin (com.sn_grc_doc_design) to create report templates in Microsoft Word. A new property module has been introduced to select the template type as a Microsoft Word template in addition to an HTML template. |
| Creator Studio | [Navigation moved from header to sidebar](https://www.servicenow.com/docs/access?context=creator-studio-add-form&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US) : As of Creator Studio version 27.2.2, the navigation has moved from the application header to a navigation panel so you can more easily see what's in your application. The following changes have been made: * The Forms in your app section of the navigation panel enables you to easily access forms. If an app has multiple forms, each of them appears separately in the navigation panel. * Automations appear in the navigation panel under the form they're associated with. The link to Add automation now appears under each form. * The form submissions section has been renamed List configurations and now appears in the Manage your submission configurations section of the navigation panel. * The submitted record configuration is now available in the Record details in the Manage your submission configurations section of the navigation panel. * A search box in the new navigation panel enables you to search all forms and automations in an app. * A bookmark icon (![bookmark icon]()) in the navigation panel enables you to bookmark an app for faster access. {#rn-summary-changes__ul_zhc_x5y_v2c} [Streamlined app creation](https://www.servicenow.com/docs/access?context=create-app-creator-studio&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US) : As of Creator Studio version 27.2.2, the following changes have been made when you create an app: * A new page appears asking you what type of app you want to build, such as a Service Desk app. Note that admins can choose not to display this page. * Choosing a template, adding a form, and previewing it is now a separate process rather than being done during the app creation process. {#rn-summary-changes__ul_yff_rrh_s2c} [Form preview change](https://www.servicenow.com/docs/access?context=creator-studio-edit-form&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US) : As of Creator Studio version 27.2.2, the way you preview forms has changed in the following ways: * The option to select between Portal, Now Mobile, and Virtual Agent experiences has moved to the top of the preview. * You can preview only the form you're currently viewing rather than being able to switch between forms in the preview. * The preview no longer shows the record details and workspace configuration. Those items have moved to the new navigation panel. {#rn-summary-changes__ul_mhj_r5h_s2c} [Request App Workspace more intuitive to use](https://www.servicenow.com/docs/access?context=creator-studio-request-app-workspace&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US) : As of Creator Studio version 27.2.2, the Request App Workspace has been streamlined to help fulfillers find and analyze requests more easily. The following changes have been made: * The Home view has been removed, so the Lists view now appears by default. * The Analytics view has been renamed Dashboard overview, and the analytics Home, Data Visualizations, and KPIs tabs have been removed. * A link to the Request App Workspace now appears in AllApp EngineWorkspaces. {#rn-summary-changes__ul_dnb_2bz_m2c} [Playbooks use only published forms](https://www.servicenow.com/docs/access?context=creator-studio-add-automation&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US) : As of Creator Studio version 27.2.2, forms must now be published (marked as ready) before you can use them to create an automated playbook. [Hide the App Engine Studio template with a new system property](https://www.servicenow.com/docs/access?context=creator-studio-components-installed&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US) : As of Creator Studio version 27.2.2, Creator Studio users who have both App Engine Studio (AES) and Creator Studio installed will no longer see the AES template when they create an app. Admins can choose to show the AES template using the new com.glide.creator_studio.template_deny_list system property. [Form location removed from form creation](https://www.servicenow.com/docs/access?context=creator-studio-edit-form-settings&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US) : Defining the catalogs and topics for a form is now accomplished by modifying the form settings rather than being done during the form creation process. If you haven't defined a location for a form, you are prompted to do so before you can mark it as ready. [Search for apps on the home page](https://www.servicenow.com/docs/access?context=view-apps-creator-studio-home-page&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US) : Quickly find the app that you're looking for using the new search bar on the Creator Studio home page. [Save and quickly find apps with bookmarks](https://www.servicenow.com/docs/access?context=crs-work-with-bookmarked-apps&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US) : Bookmark apps to find them faster using the new Bookmarks pill on the home page. |
| Customer Success Management | [Success portfolio](https://www.servicenow.com/docs/access?context=account-lifecycle-success-landing&version=yokohama&pubname=yokohama-acct-lifecycle-events&ft:locale=en-US) : The Success portfolio dashboard provides visibility into the overall health of a customer success manager's portfolio. With this dashboard, you can view the health of an engagement, individual indicators, health and risk trends, and touchpoints. [Engagement page enhancements](https://www.servicenow.com/docs/access?context=account-lifecycle-view-engage&version=yokohama&pubname=yokohama-acct-lifecycle-events&ft:locale=en-US) : Use the engagement home page to see a high-level overview of an engagement. You can also view the current health score, identify issues, and monitor objectives and outcomes. [Data import enhancements](https://www.servicenow.com/docs/access?context=account-lifecycle-import-data&version=yokohama&pubname=yokohama-acct-lifecycle-events&ft:locale=en-US) : Optimize the onboarding process by importing and publishing a large amount of data and resolve any errors or issues quickly. |
| Data Loss Prevention Incident Response | [Data Loss Prevention Incident Response Analyst Workspace](https://www.servicenow.com/docs/access?context=using-dlp-ops-portal&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US) : Introduced a new action in the DLP incident form view that requires users to specify a closure code prior to incident closure. [Create additional incident data fields](https://www.servicenow.com/docs/access?context=create-custom-fields-dlp&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US) : In the DLP incident table, the Custom Fields column has been renamed Additional Incident Data Fields. |
| Data Management | [Data Management Console](https://www.servicenow.com/docs/access?context=viewing-data-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US){#rn-summary-changes__data-management-rn-rn-workspace} : You can now access data usage on your instance by navigating to AllSystem Data ManagementData Management Console. |
| Data management for CSM | [Inbound Request Configuration table](https://www.servicenow.com/docs/access?context=inbound-request-configuration-table&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US) : The Inbound Queue \[sn_tmt_core_inbound_queue\] table is renamed to Inbound Request table. Use the Request Configuration field on the Inbound Request \[sn_tmt_core_inbound_queue\] table to reference the Inbound Request Configuration \[sn_tmt_core_inbound_queue_config\] table while executing synchronous or asynchronous flows. [Specification Class on Product Inventory related list](https://www.servicenow.com/docs/access?context=product_inventory_configurations&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US) : The Specification class field on the Product Inventory related list provides information on whether the selected product inventory record has a product specification or service specification that is associated with it. [Notification for case tasks at business locations](https://www.servicenow.com/docs/access?context=manage-business-location-cases&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US) : View the notifications for the case tasks that are associated with the business locations on the Business Location Service Portal (BLSP). This way, your location members can stay informed about their pending tasks. [Case resolution by location staff at other business locations](https://www.servicenow.com/docs/access?context=ebl-as-a-fulfiller&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US) : Enable your location staff, whether at company-owned or third-party-owned organizations (internal and external business locations), to handle and resolve issues from other eligible business locations. [Product Inventories configurations for Customer Life Cycle Management workflows](https://www.servicenow.com/docs/access?context=product_inventory_configurations&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US){#rn-summary-changes__data-management-for-csm-rn-rn-workspace} : Perform the Modify, Suspend, Resume, and Disconnect operations on product inventory records directly from the Product Inventory related list on the Accounts page. [Grant write access to account relationships](https://www.servicenow.com/docs/access?context=t_CreateAcctRelationshipRecord&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US) : Enable administrators and customer service managers to update account relationship records. [Enable write access to contact relationships](https://www.servicenow.com/docs/access?context=t_CreateAContactRelationship&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US) : Enable administrators and customer service managers to update the contact relationship records. [Populate the Type field in relationship tables using the fix script](https://www.servicenow.com/docs/access?context=migration-of-account-manager-responsibility-access&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US) : Migrate the account manager responsibilities from the account team member relationships to the new responsibility access configurations. The updated framework enables you to manage access settings more efficiently. [Update roles within relationship agent and relationship contributor](https://www.servicenow.com/docs/access?context=features-supp-and-unsupp-by-unified-consumer&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US) : Modify the roles of the relationship agent and relationship contributor to include the new granular roles that can grant access by responsibilities. |
| Decision Builder in Workflow Studio | [Pagination](https://www.servicenow.com/docs/access?context=decision-builder-user-interface&version=yokohama&pubname=yokohama-build-workflows&ft:locale=en-US#section_lyv_v4r_ndc) : Use the pagination feature to switch between pages by selecting the page you'd like to see. |
| DevOps Change Velocity | [Enhanced JFrog integration with DevOps Change Velocity](https://www.servicenow.com/docs/access?context=devops-jfrog-connect-workspace&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : Gather JFrog evidence seamlessly and create change records automatically using the improved JFrog integration with DevOps Change Velocity. [Bearer authentication in JFrog](https://www.servicenow.com/docs/access?context=devops-jfrog-connect-workspace&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : Connect to JFrog using the secure bearer token authentication to comply with JFrog's updated security policies. [HTTP proxy for Docker](https://www.servicenow.com/docs/access?context=servicenow-custom-actions-for-gitlab&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : Connect to DevOps Change Velocity through HTTP proxy settings using environment variables in your Docker deployment for instances that run a proxy server. [Health scan enhancements](https://www.servicenow.com/docs/access?context=run-health-scan-check&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : * Identify any callback processing issues in your instance. * Identify any access control rule (ACL) that is incorrectly associated with a role in your instance. * Verify whether all DevOps tables are present in your instance and confirm whether all metadata in sys_\* tables is present. * Verify whether all DevOps roles in your instance contain all expected roles, including inherited roles. {#rn-summary-changes__ul_nkx_pcj_13c} [Auto close without Change Management - State Model \[Legacy\] plugin](https://www.servicenow.com/docs/access?context=dev-ops-change-acceleration&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : Change requests can now be auto-closed without requiring you to install the Change Management - State Model \[Legacy\] plugin. [Prod deploy commit logic for other step types](https://www.servicenow.com/docs/access?context=dev-ops-commits-release&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : Update the sn_devops.commit_rel_change_step_type property to have other step types, like Test or Deploy, use the same commit logic as Prod Deploy. [Override start and end time of a change request](https://www.servicenow.com/docs/access?context=dev-ops-config-change-details&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : Set the sn_devops.change_request.auto_close_allow_override_start_time and sn_devops.change_request.auto_close_allow_override_end_time properties as false to consider the change request start and end time instead of the pipeline's when the autoCloseChange parameter is enabled in a pipeline. [Node version of DevOps extension](https://www.servicenow.com/docs/access?context=config-dev-ops-extensions-azure&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : The node version of the ServiceNow DevOps extension has been upgraded to version 20.x in Azure DevOps. [Enhanced pipeline governance in GitLab](https://www.servicenow.com/docs/access?context=servicenow-custom-actions-for-gitlab&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : View change request details like status, sys_id, priority in the GitLab console when a change request is created in GitLab using Docker image. [Health scan enhancements](https://www.servicenow.com/docs/access?context=run-health-scan-check&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : * Identify outdated or prolonged discover and import requests using the DevOps -Stale or Long-Running Discover and Import Requests health check. * Verify whether webhooks have been configured correctly for any tracked repository, pipeline, or plan in GitHub, GitLab, Azure DevOps, and Jenkins using the DevOps webhook configuration analysis health check. * Identify OAuth app configuration issues for GitHub tools in the connected state using the DevOps webhook configuration analysis health check. * Verify if any scheduled job has been configured to run as an invalid or non-admin user. * Navigate to the Findings list from the DevOps Change Workspace home page by selecting View all findings in the Health scan findings widget. {#rn-summary-changes__ul_nqc_rwy_3hc} [Support for MID Server cluster](https://www.servicenow.com/docs/access?context=playbook-enter-github-instance-details&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : Improve load balancing and failover protection by selecting a MID Server cluster when connecting to a tool instance associated with a MID Server cluster. This configuration enables multiple MID Servers with relevant capabilities to be grouped. [Improved UX for DevOps Change health scans](https://www.servicenow.com/docs/access?context=run-health-scan-check&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : Run health scans and analyze findings efficiently in the DevOps Change workspace with an intuitive and user-friendly interface. [Pipeline association for GitHub Actions](https://www.servicenow.com/docs/access?context=sc-github&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : When onboarding GitHub Actions pipelines through the App onboarding catalog or the onboarding APIs, now only the selected pipelines are associated with the DevOps app. If no pipeline is selected, all pipelines within the specified repository are associated. [Tool connection check status](https://www.servicenow.com/docs/access?context=devops-reference-error-messages&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : If a tool is marked as Disconnected because of a system-generated failure during an unsuccessful connection check, any subsequent successful check automatically updates the connection status to Connected. If you manually disconnect the tool, the tool status remains Disconnected even if there's a subsequent successful connection check. [New roles for vulnerability integration](https://www.servicenow.com/docs/access?context=installed-with-dev-ops&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : * The sn_vul.app_sec_manager role is added to the DevOps Tool Owner \[sn_devops.tool_owner\] role when the DevOps Vulnerability Integrations plugin (sn_devops_vul_ints) is installed. * The sn_vul_veracode.configure_integration role is added to the DevOps Tool Owner \[sn_devops.tool_owner\] role when the Vulnerability Response Integration with Veracode plugin (sn_vul_veracode) is installed. {#rn-summary-changes__ul_vxg_h1p_rfc} [Additional scans for DevOps Health Scan Content pack](https://www.servicenow.com/docs/access?context=run-health-scan-check&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : Additional set of proactive checks focused on problems that tend to occur before or after an upgrade along with identifying configuration issues like plugin and version incompatibilities, or pipelines that chronically fail, have been added. [Import pull-request records for Bitbucket Server or Bitbucket Data Center](https://www.servicenow.com/docs/access?context=devops-wkspc-bitbucket-tool-conn&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : Import pull-request records for Bitbucket Server or Data Center for improved insights and efficiency. [Change request creation with errors in DevOps data retrieval for Harness pipelines](https://www.servicenow.com/docs/access?context=change-request-creation-with-devops-data-retrieval-errors&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : Enable change request creation even if there is an error in retrieving the DevOps data for a Harness pipeline. [Branch name filter](https://www.servicenow.com/docs/access?context=create-devops-change-request-manual&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : Search for build numbers by the branch name while associating DevOps data to a change request in the Service Operations Workspace (SOW) or Classic UI. [Test summary name in GitHub Actions](https://www.servicenow.com/docs/access?context=servicenow-devops-custom-actions-from-github-marketplace&version=yokohama&pubname=yokohama-it-service-management§ion=servicenow-devops-test-report-custom-action&ft:locale=en-US) : The servicenow-devops-test-report custom action in GitHub now includes an optional test-summary-name parameter to specify the test summary results name. [Token based authentication for Rally](https://www.servicenow.com/docs/access?context=configure-webhooks-for-rally-manually&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : Configure webhooks for Rally using token based authentication instead of using the integration username and password. [Renamed variables for Docker](https://www.servicenow.com/docs/access?context=servicenow-custom-actions-for-gitlab&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : The environmental variables in the Generic Docker actions for DevOps Change Velocity have been renamed by removing the CI prefix for better clarity. [Security scan results](https://www.servicenow.com/docs/access?context=dev-ops-change-acceleration&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : Security scan results on the change record associated to a pipeline execution with a linked package are now displayed in the Security Summaries tab. [Source of commits in SOW](https://www.servicenow.com/docs/access?context=create-change-sow&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : View the source of commits like pipeline execution, branch, repository, and so on for a change request in the DevOps data section of the Service Operations Workspace. [Track file changes](https://www.servicenow.com/docs/access?context=sc-github&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : The Track file changes option is now disabled by default when a repository is configured to prevent any potential security risks. [Close code value for a change request](https://www.servicenow.com/docs/access?context=dev-ops-administration&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : Two new properties have been added in DevOps Change Velocity, so that you can specify a close code value for a change request based on the change request completion state when the autoCloseChange parameter is enabled. [Simplified onboarding of orchestration tools not supported in the base system](https://www.servicenow.com/docs/access?context=devops-user-created-orchestration-tool-integration&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : Integrate orchestration tools that aren't supported in the base system by leveraging a generic framework. [Custom fields for planning tool integration](https://www.servicenow.com/docs/access?context=add-custom-field-for-a-planning-tool-integration&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : Add custom fields into your planning tool integration to improve configurability and access business-specific information, which facilitates more informed decision-making. |
| Digital End-User Experience | [DEX UI enhancements](https://www.servicenow.com/docs/access?context=dex-landing&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : Several user interface improvements have been made to help enhance usability and make navigation more intuitive, leading to a better overall user experience. |
| Dispute Rules Content Pack for Visa | [Visa Resolve Online (VROL) version 25.2 updates](https://www.servicenow.com/docs/access?context=visa-spoke&version=yokohama&pubname=yokohama-integrate-applications&ft:locale=en-US#section_gsl_nw5_vyb){#rn-summary-changes__dispute-rules-content-pack-for-visa-rn-workspace} : Updated the dispute questionnaire provided through Dispute Rules Content Pack for Visa to align with Visa Resolve Online (VROL) release 25.2 revision changes. |
| Document Intelligence | [Document and visual insights AI agent enhancements](https://www.servicenow.com/docs/access?context=document-and-visual-insights-ai-agent&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Generate a summary of document and image attachments with the document and visual insights AI agent. |
| Document Services | Summarize button. : The Summarize button was changed to the Ask Now Assist button. [Subflows for Shared drives for Google Drive](https://www.servicenow.com/docs/access?context=google-drive-spoke-document-services&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US). : Added Spoke subflows for Shared drives in Google Drive. [Pop-up window](https://www.servicenow.com/docs/access?context=pdf-generation-accessibility&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) : Added a pop-up window for list and form export with a check box that enables you to export an individual record or a list of records into a PDF format. The PDF includes accessibility support. [PDF generation and accessibility](https://www.servicenow.com/docs/access?context=pdf-generation-accessibility&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US){#rn-summary-changes__document-services-rn-rn-workspace} : Export a collection of records or a single record into a PDF format. New system property was added for better accessibility. [Workflow migration for Managed Documents](https://www.servicenow.com/docs/access?context=c_ManagedDocuments&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) : Improved usability, low code accessibility, and feature parity due to the newly configured workflows. |
| ERP Semantic Mining | [Faster initialization](https://www.servicenow.com/docs/access?context=how-erp-clean-core-inputs-data&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US) : In addition to daily total application statistics, the SQLM and APPSTATS initial scan now also retrieves all monthly total application statistics up to the current date. |
| Enterprise Architecture (formerly Application Portfolio Management) | [Application Rationalization page enhancements](https://www.servicenow.com/docs/access?context=eaw-rationalize-business-applications&version=yokohama&pubname=yokohama-application-portfolio-management&ft:locale=en-US) : * Added the Score for fiscal period filter drop-down. * Added a filter button. * Removed the previously available filter drop-downs. * Added the export icon. * Added the technical debt column on the list view page. * Added the technical debt indicator in the bubble size list under the settings of the bubble chart page. {#rn-summary-changes__ul_m5j_vps_wgc} [View business capabilities for a business application](https://www.servicenow.com/docs/access?context=eaw-view-business-capabilities-assoc-with-ba&version=yokohama&pubname=yokohama-application-portfolio-management&ft:locale=en-US) : Added the Business Capabilities tab in the business application related list. Add and Remove buttons are added to associate or dissociate a business capability with a business application. [Business application related list enhancements](https://www.servicenow.com/docs/access?context=eaw-app-portfolio&version=yokohama&pubname=yokohama-application-portfolio-management&ft:locale=en-US) : The business application related list is reorganized and the available tabs are: * Business Capabilities * Information Objects * Architectural Artifacts * Digital Interfaces * Digital Integrations * Application Model Lifecycle * CI Scores * Architecture Reviews {#rn-summary-changes__ul_ocv_chl_y2c} [Insights section enhancements](https://www.servicenow.com/docs/access?context=eaw-insights&version=yokohama&pubname=yokohama-application-portfolio-management&ft:locale=en-US) : A new card "Past due certification tasks for business applications" is added in the Application Portfolio tab of the Insights section. The following cards are removed the Application Portfolio tab of the Insights section: * Open quarterly certifications for business applications * Open on demand certifications for business applications {#rn-summary-changes__ul_hmr_rhl_y2c} [Enterprise Modeling and Visualization](https://www.servicenow.com/docs/access?context=eaw-modeling&version=yokohama&pubname=yokohama-application-portfolio-management&ft:locale=en-US) enhancements : * In the Diagrams page, added an option to create a business process map. * Added a field in the shape library element form to show or hide the shape for different diagram types. * The following categories are added for the ArchiMate shapes: * ArchiMate- Application Layer * ArchiMate- Business Layer * ArchiMate- Technology Layer * ArchiMate- Relationships {#rn-summary-changes__ul_bbx_23l_y2c} * Enhanced the Enterprise Architecture shape library with new shapes for Value Stream and Value Stream Stage. {#rn-summary-changes__ul_n4q_13l_y2c} [Architectural Artifacts](https://www.servicenow.com/docs/access?context=eaw-managing-architectural-artifacts&version=yokohama&pubname=yokohama-application-portfolio-management&ft:locale=en-US) enhancements : * In the Architectural Artifacts list of the Portfolio page, selecting the New button displays a modal to create an architectural artifact. * In the architectural artifact details page, the Upload Version button is renamed to New version version. * In the architectural artifact related list, the following tabs are removed: * Role permissions * User Criteria permissions * User permissions * Group permissions {#rn-summary-changes__ul_kvq_rdq_y2c} * Added the Share button in the architectural artifacts Details tab in the Portfolio page to share the architectural artifacts with users and groups. * In the architectural artifact related list, renamed the Architectural Artifact Versions tab to Artifact versions. * In the Artifact versions tab, the New button is removed. * In the Portfolio page, the Architectural Artifact Versions section is removed from the Information Portfolio. Added the New version button at the artifact version details page. * In the architectural artifact Details tab, the Access Setting section is removed. * In the architectural artifact Details tab, the Download artifact button is removed. Added the Download button on the artifact version page. {#rn-summary-changes__ul_wnx_43l_y2c} [Configure certification policies](https://www.servicenow.com/docs/access?context=eaw-config-cert-schedules&version=yokohama&pubname=yokohama-application-portfolio-management&ft:locale=en-US) : In the Setup page, the Certification Schedules section is renamed to Certification Policies. [Create diagram action](https://www.servicenow.com/docs/access?context=eaw-modeling-create-diagram-action&version=yokohama&pubname=yokohama-application-portfolio-management&ft:locale=en-US) : An option to open diagram actions list for the Enterprise Modeling and Visualization in the Setup page. [Create a blank diagram using modeling in the EA Workspace](https://www.servicenow.com/docs/access?context=eaw-modeling-create-diagram&version=yokohama&pubname=yokohama-application-portfolio-management&ft:locale=en-US) : In the Enterprise Modeling and Visualization, an option to create blank diagrams is added. [Restart the TPM Discovered Technologies and Lifecycles job](https://www.servicenow.com/docs/access?context=eaw-restart-tpm-scheduled-job&version=yokohama&pubname=yokohama-application-portfolio-management&ft:locale=en-US) : The Restart button added on the TPM Logs page to restart the Populate TPM Discovered Technologies and Lifecycles scheduled job. [TRM technical debt form](https://www.servicenow.com/docs/access?context=eaw-trm-technical-debt-form&version=yokohama&pubname=yokohama-application-portfolio-management&ft:locale=en-US) : The technical debts table \[sn_apm_trm_standards_technical_debt\] displays the server details for the TRM products along with the associated business applications details, and the reason for the technical debt. [Regenerate indicator scores in Enterprise Architecture Workspace](https://www.servicenow.com/docs/access?context=eaw-regenerate-indicator-score&version=yokohama&pubname=yokohama-application-portfolio-management&ft:locale=en-US) : The following buttons are added to generate scores for indicators and scoring profiles: * The Regenerate indicator score button is added in the Indicator record. * The Generate scores button is added in the Scoring Profile record. {#rn-summary-changes__ul_hq2_dmz_gdc} [Portfolio list view](https://www.servicenow.com/docs/access?context=portfolio-list-view&version=yokohama&pubname=yokohama-application-portfolio-management&ft:locale=en-US) : New modules and features have been added in the Portfolio section. [Add additional category details for TRM products](https://www.servicenow.com/docs/access?context=eaw-request-a-trm-products&version=yokohama&pubname=yokohama-application-portfolio-management&ft:locale=en-US) : The Other Category field is added in the Request TRM Product form and the Create TRM product form. Using this data, you can filter for TRM products using additional categories details. |
| Enterprise Asset Management | [MAC address field on the asset form](https://www.servicenow.com/docs/access?context=asset-fields-eam&version=yokohama&pubname=yokohama-it-asset-management&ft:locale=en-US) : The asset form shows the MAC address field for the following asset classes: * Construction * Facility * Industrial * Medical * Retail * Tactical equipment * Transportation * Wearable * Hardware {#rn-summary-changes__ul_ewq_hj3_cdc} Note: The MAC address field is shown on the asset form in Enterprise Asset Workspace and OT Asset Workspace. [Child assets activity and MAC address field in the asset onboarding playbook](https://www.servicenow.com/docs/access?context=create-asset-onboarding-task-eam&version=yokohama&pubname=yokohama-it-asset-management&ft:locale=en-US) : The child assets activity was added to the asset onboarding playbook for preassembled industrial assets. The Asset details activity in the playbook shows the MAC address field. Note: These UI changes apply to Enterprise Asset Workspace and OT Asset Workspace. [MAC address field in multi-asset onboarding](https://www.servicenow.com/docs/access?context=asset-onboarding-eam&version=yokohama&pubname=yokohama-it-asset-management&ft:locale=en-US) : The MAC address field was added to the Add assets dialog box in multi-asset onboarding through catalog requests and onboarding orders. The Asset details activity in the Multi-asset onboarding playbook shows the MAC address that you provided. Note: This UI change applies to Enterprise Asset Workspace and OT Asset Workspace. [MAC address field in an Advanced Shipment Notification](https://www.servicenow.com/docs/access?context=asn-eam&version=yokohama&pubname=yokohama-it-asset-management&ft:locale=en-US) : The MAC address field was added to the Download template for an Advanced Shipment Notification. After a successful import, the MAC address that you provided in the template is added to the Asset \[alm_asset\] table. The MAC address field is also shown on the asset form for all assets except consumables and pallets. Note: This UI change applies to Enterprise Asset Workspace and OT Asset Workspace. [MAC address field in Bulk import](https://www.servicenow.com/docs/access?context=overview-bulk-import-eam&version=yokohama&pubname=yokohama-it-asset-management&ft:locale=en-US) : The MAC address field was added to the Download template for the following Bulk import modes: * Create assets * Update assets * Create models and assets {#rn-summary-changes__ul_fcb_m53_cdc} After a successful import, the MAC address that you provided in the template is added to the Asset \[alm_asset\] table. The MAC address field is also shown on the asset form for all assets except consumables and pallets. Note: This UI change applies to Enterprise Asset Workspace and OT Asset Workspace. [MAC address field in Receive Purchase Order](https://www.servicenow.com/docs/access?context=t_ReceiveAnAsset&version=yokohama&pubname=yokohama-it-asset-management&ft:locale=en-US) : The Capture asset tags dialog box in the Receive Purchase Order shows the MAC address field in addition to the Serial number and Asset tag. Note: This UI change applies to Enterprise Asset Workspace and OT Asset Workspace. [OT entity flag](https://www.servicenow.com/docs/access?context=ot-asset-ws-otam&version=yokohama&pubname=yokohama-it-asset-management&ft:locale=en-US) : The asset form shows that the OT entity flag set to true for hardware and industrial assets that were created in the OT Asset Workspace. [Refresh flow in OT workspace](https://www.servicenow.com/docs/access?context=request-eam-assetrefresh&version=yokohama&pubname=yokohama-it-asset-management&ft:locale=en-US) : For single and multi-model refresh orders, the OT manager can edit the replacement model even after the refresh order has been created in the OTAM workspace. Additionally, the sourcing location is also editable. [Reflow for Configurable Workspace](https://www.servicenow.com/docs/access?context=auto-reflow&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) : The configurable Enterprise Asset Workspace supports reflow, which enables pages and content to be zoomed up to 400% through your browser settings without loss of content or functionality. |
| Event Management | [Property name changes](https://www.servicenow.com/docs/access?context=enable-alert-grouping&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US) : Enable CMDB Correlation for Alert Aggregation ( CMDB groups) (sa_analytics.agg.query_cmdb_correlation_enabled) has been renamed Enable CMDB correlation.Enable alert aggregation for CI-based Automated groups (sa_analytics.specific_patterns_enabled) has been renamed Enable ML based Automation correlation.Enable alert aggregation for Text-based groups (sa_analytics.text_based_group_enabled) has been renamed Enable Text based correlation.Use all CMDB relations for CMDB group correlation. This property impacts both CMDB group correlation and Alert Similarity on the Alert form (evt_mgmt.related_cis_get_all_relation_types) has been renamed Use all CMDB relations for CMDB group correlation. [Pull connectors](https://www.servicenow.com/docs/access?context=t_EMConfigureConnectorInstance&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US) : Simplifying the setup for Out-of-the-Box (OOTB) event rules that come with the pull connectors that have not yet been activated, deactivated, or modified, the Apply additional matching rules option is now enabled by default. If a rule has been previously applied, you must set this option manually. |
| External Content Connectors | [Connector creation UI](https://www.servicenow.com/docs/access?context=creating-ext-cont-connectors&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : The connector creation UI now includes optional steps for configuring user permission crawls (for connectors that support them) and for linking connector search sources to your search profiles. If you want to change these settings for an existing connector, you can configure these settings from the connector editor. [Analytics for external content connectors](https://www.servicenow.com/docs/access?context=analytics-external-content-connectors&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Analyze connector performance and behavior in a selected time period using the redesigned Analytics page. You can access this page from the connector editor. [Atlassian Jira Cloud connection settings](https://www.servicenow.com/docs/access?context=create-ext-cont-connector-jira&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : The Atlassian Jira Cloud external content connector no longer requires your Atlassian Jira Cloud instance ID as a connection setting. [Microsoft OneDrive connection settings](https://www.servicenow.com/docs/access?context=create-ext-cont-connector-microsoft-onedrive&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : The Microsoft OneDrive external content connector now accepts certificate SHA1 thumbprint hashes in hexadecimal format as well as in base64-encoded format. [Microsoft SharePoint Online connection settings](https://www.servicenow.com/docs/access?context=create-ext-cont-connector-mspo&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : The Microsoft SharePoint Online external content connector now accepts certificate SHA1 thumbprint hashes in hexadecimal format as well as in base64-encoded format. [Microsoft Teams connection settings](https://www.servicenow.com/docs/access?context=create-ext-cont-connector-msteams&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : The Microsoft Teams external content connector now accepts certificate SHA1 thumbprint hashes in hexadecimal format as well as in base64-encoded format. [Connector creation UI](https://www.servicenow.com/docs/access?context=creating-ext-cont-connectors&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : The connector creation UI now includes optional steps for configuring the new connector's crawl settings and creating and scheduling crawls for it. You can still configure these settings from the connector editor, so you can skip these steps during connector creation if you want to configure crawl settings and create crawls later on. [Webcrawler external content connector](https://www.servicenow.com/docs/access?context=webcrawler-external-content-connector&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : The predefined web sources external content connector has been subsumed into the new Webcrawler external content connector, which allows you to specify a custom web source or select a predefined one. [New UI for creating external content connectors](https://www.servicenow.com/docs/access?context=creating-ext-cont-connectors&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : On the External Content Admin Home page, you now select New instead of Create to create a new connector. Next, you select the appropriate source system type on the Choose source page. Finally, you fill in required values on the Connector details page. |
| Financial Services Card Operations | [Visa Resolve Online (VROL) version 25.1 updates](https://www.servicenow.com/docs/access?context=card-operations-reference&version=yokohama&pubname=yokohama-financial-services-operations&ft:locale=en-US) : Updated the following columns to align with release 25.1 revision changes: * The is_parcelado column has been removed from the dispute intake table. * The domain value description for the DisputeResponseReason column has been updated from Copy of ATM Cash Disbursement or Load Transaction to Copy of ATM Cash Disbursement. {#rn-summary-changes__ul_hwq_5wb_v2c} |
| Financial Services Operations Core | [Added fields to Claim Base table](https://www.servicenow.com/docs/access?context=fso-core-insurance-tables&version=yokohama&pubname=yokohama-financial-services-operations&ft:locale=en-US){#rn-summary-changes__financial-services-operations-core-rn-rn-workspace} : Added the following fields to the Claim Base \[sn_bom_claim_base\] table: * SIU review * Claim validation decision * Claim fraud decision {#rn-summary-changes__ul_nnx_5lg_pdc} |
| Financial Services Operations Integration with Visa | [Visa Resolve Online (VROL) version 25.1 updates](https://www.servicenow.com/docs/access?context=components-installed-with-the-financial-services-operations-integration-with-visa&version=yokohama&pubname=yokohama-financial-services-operations&ft:locale=en-US) : Updated the following subflows to align with release 25.1 revision changes: * Submit Dispute questionnaire * Submit fraud report {#rn-summary-changes__ul_ics_mpb_w2c} |
| Flows, subflows, and actions in Workflow Studio | [Display text descriptions of data changes](https://www.servicenow.com/docs/access?context=exploring-flows&version=yokohama&pubname=yokohama-build-workflows&ft:locale=en-US) : See a natural language description of the data each component of a flow uses. Understand what data flow triggers, actions, and flow logic blocks use without having to open their configuration details. |
| Generative AI Controller | [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Configure ACLs for AI agents and agentic workflows](https://www.servicenow.com/docs/access?context=aia-security-implementation&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all authenticated users or publicly available. [Configure Data Privacy and Data Discovery to protect the personally identifying information (PII) of your users.](https://www.servicenow.com/docs/access?context=configure-now-assist-data-privacy&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US) : Generative AI Controller has changed to use the Data Privacy application instead of the Sensitive Data Handler to help anonymize PII. The process for choosing what gets anonymized and how has shifted to different tables and forms that your administrator must configure for your organization. |
| Hardware Asset Management | [My Assets menu and Assets tab on the Employee Center portal](https://www.servicenow.com/docs/access?context=asset-attestation-ham&version=yokohama&pubname=yokohama-it-asset-management&ft:locale=en-US) : The My Assets menu appears on the global header navigation bar of the Employee Center home page. This menu provides employees with quick access to the details of assets assigned to them. The Employee profile widget now includes an Assets tab, which shows the details of the assets assigned to the employee. [Reflow for Configurable Workspace](https://www.servicenow.com/docs/access?context=auto-reflow&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) : The configurable Hardware Asset Workspace supports reflow, which enables pages and content to be zoomed up to 400% through your browser settings without loss of content or functionality. |
| Health Log Analytics | [Component-based alert grouping is deprecated](https://www.servicenow.com/docs/access?context=hla-op-log-analytics-alert-types&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US) : Starting in version 36.0.19, the adoption of a streamlined two-tier alert model, Log Analytics Group to Single Alert, has replaced component-based alert groups, which have been removed. This model aligns alert representation with the service-level anomalies identified by Health Log Analytics, rather than individual host CIs. The update improves alert visibility, simplifies correlation, and enhances overall alert management efficiency. [ServiceNow System Logs data input](https://www.servicenow.com/docs/access?context=hla-data-input-glide-syslog&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US) : The Glide Syslog data input has been renamed ServiceNow System Logs data input. |
| ITOM Optimization | : The following UI changes are applicable for workflow migration: * In the Resource BlockOperationsSteps, within the Add Operations Steps dialog box, the Invoke Workflow option has been removed from the Operation Type field. * In the Resource BlockOperationsSteps, within the Add Operations Steps dialog box, the Workflow check box has been removed from the Add Operations Steps field. * In the Cloud Catalog Items, under the Operation Implementation drop-down list, the Workflow option has been removed. {#rn-summary-changes__ul_xyp_b2z_lbc} {#rn-summary-changes__itom-optimization-rn-rn-workspace} : * Migration of legacy workflows to Workflow Studio flows or subflows. * Policy Rule Actions now supports Workflow Studio subflows instead of legacy workflows. {#rn-summary-changes__ul_hdf_j1v_lbc} |
| ITOM Visibility | [Limits in tag-based Service Mapping](https://www.servicenow.com/docs/access?context=components-installed-with-service-mapping-plus&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US) : Starting with version 1.15.2, experience improved performance in Service Mapping. A new property limits the creation of tag-based service candidates to 200 per service family. [Name suggestions for application service candidates](https://www.servicenow.com/docs/access?context=app-services-name-suggestions&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US) : Experience more accurate name suggestions for application service candidates based on Service Fingerprints in Service Mapping Plus store version 1.15.0. [Limits in Service Mapping](https://www.servicenow.com/docs/access?context=components-installed-with-service-mapping&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US) : Limits in Service Mapping prevent the disabling or deletion of jobs scheduled for the Checkpoint Reaper or the Service Model's Blob Reaper. [Name update in Service Mapping](https://www.servicenow.com/docs/access?context=create-it-services&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) : * Application Services in the navigation menu has been renamed Service Instances. * The label for the \[cmdb_ci_service_auto\] table has been changed from Application Service to Service Instance. {#rn-summary-changes__ul_nwm_51f_sdc} [Discovery status monitoring](https://www.servicenow.com/docs/access?context=c_DiscoveryStatus&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US) : Discovery schedules that have no status updates for over a defined number of minutes are analyzed automatically by the Discovery Status Monitor job. By default, this job applies to Discovery schedules that discover configuration items. |
| Identity | [Access Analyzer](https://www.servicenow.com/docs/access?context=access-analyzer&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US) : Assign the access_analyzer_admin role to the users to access and administer the Access Analyzer. |
| Impact | [Impact Workspace name change](https://www.servicenow.com/docs/access?context=impact-in-platform-home&version=yokohama&pubname=yokohama-impact&ft:locale=en-US) : Impact Workspace has been renamed as Impact. [Impact Store App user experience](https://www.servicenow.com/docs/access?context=impact-store-app&version=yokohama&pubname=yokohama-impact&ft:locale=en-US) : Impact users who have migrated from the Impact Delivery Instance may access Quicklinks to access features that haven't been migrated to Impact Store Application yet. [Custom payload in Instance Observer alerts integration](https://www.servicenow.com/docs/access?context=custom-payload-help-guide-impact&version=yokohama&pubname=yokohama-impact&ft:locale=en-US) : Define and manage a custom JSON request payload for ServiceNow and third-party integrations with the Instance Observer enhancements. New [Impact Store Application](https://www.servicenow.com/docs/access?context=impact-store-app&version=yokohama&pubname=yokohama-impact&ft:locale=en-US) experience{#rn-summary-changes__impact-rn-rn-workspace} : The new Impact Store Application provides a more efficient, streamlined way for you to work. For information about how to upgrade, see [Configuring the Impact Store Application](https://www.servicenow.com/docs/access?context=configuring-impact-platform&version=yokohama&pubname=yokohama-impact&ft:locale=en-US). Note that [Impact Delivery Instance (formerly Impact Digital Experience)](https://www.servicenow.com/docs/access?context=impact-digital-experience&version=yokohama&pubname=yokohama-impact&ft:locale=en-US) is still supported in this release. [Accelerator catalog](https://www.servicenow.com/docs/access?context=accelerator-catalog&version=yokohama&pubname=yokohama-impact&ft:locale=en-US) : Minor updates have been incorporated into the following accelerators: * [Jumpstart Your GenAI](https://www.servicenow.com/docs/access?context=jumpstart-gen-ai&version=yokohama&pubname=yokohama-impact&ft:locale=en-US) * [Jumpstart Your Now Assist Skill Kit](https://www.servicenow.com/docs/access?context=jumpstart-now-assist-skill-kit&version=yokohama&pubname=yokohama-impact&ft:locale=en-US) * [Jumpstart Your Document Intelligence](https://www.servicenow.com/docs/access?context=jumpstart-document-intelligence&version=yokohama&pubname=yokohama-impact&ft:locale=en-US) * [On-Demand Value Report](https://www.servicenow.com/docs/access?context=on-demand-value-report&version=yokohama&pubname=yokohama-impact&ft:locale=en-US) * [LSD Maturity Assessment](https://www.servicenow.com/docs/access?context=lsd-maturity-assessment&version=yokohama&pubname=yokohama-impact&ft:locale=en-US) {#rn-summary-changes__ul_wvf_ll1_1fc} The following Accelerators are renamed: * Jumpstart Your Now Assist for ITSM is now [Jumpstart Your AI Agents for ITSM](https://www.servicenow.com/docs/access?context=jumpstart-your-ai-agents-for-itsm&version=yokohama&pubname=yokohama-impact&ft:locale=en-US) * Jumpstart Your Now Assist for CSM is now [Jumpstart Your AI Agents for CSM](https://www.servicenow.com/docs/access?context=jumpstart-ai-agents-csm&version=yokohama&pubname=yokohama-impact&ft:locale=en-US) {#rn-summary-changes__ul_zbh_qs1_1fc} [Data Collection Toolkit](https://www.servicenow.com/docs/access?context=data-collection-toolkit&version=yokohama&pubname=yokohama-impact&ft:locale=en-US) : * Download the content packs for both regulated (GCC/NSC) and non-regulated customers. * Automatically transfer Impact Value Metrics to the centralized Impact instance to manage the value journey, including setting value baselines and targets, outcome performance reviews, and the value report with the enhanced toolkit. {#rn-summary-changes__ul_s2g_35v_2fc} [Impact Delivery Instance (formerly Impact Digital Experience)](https://www.servicenow.com/docs/access?context=impact-digital-experience&version=yokohama&pubname=yokohama-impact&ft:locale=en-US) : With the Yokohama release, Impact Digital Experience (IDE) has been renamed as Impact Delivery Instance (IDI). [Impact Store Application](https://www.servicenow.com/docs/access?context=impact-store-app&version=yokohama&pubname=yokohama-impact&ft:locale=en-US) : Impact is accessible in both the Impact Delivery Instance, formerly the Impact Digital Experience, and as the ServiceNow Impact Store Application. [Value Management](https://www.servicenow.com/docs/access?context=impact-value-journey&version=yokohama&pubname=yokohama-impact&ft:locale=en-US) name changes: : * Impact Value Journey is renamed to Impact Value * Value Blueprint is renamed to Objectives and Outcomes. * Outcomes Performance is renamed to Outcomes Insights. * Business Objectives is renamed to Objectives. * Operational Outcomes is renamed to Outcomes. * Business Value Report is renamed to Value Report. {#rn-summary-changes__ul_kgm_ry5_dfc} [Impact packages](https://www.servicenow.com/docs/access?context=impact-packages&version=yokohama&pubname=yokohama-impact&ft:locale=en-US) : * Add-on SKUs have been updated to provide additional flexibility for Impact customers and are available in all environments where Impact is available. * Updates to the Impact Advanced package, offered pursuant to the applicable Impact Accelerator Description available at . {#rn-summary-changes__ul_y3m_c5v_2fc} |
| Incident Management | [Email redirection behavior for major incident email notification links](https://www.servicenow.com/docs/access?context=email-notif-redirt-inci-major-inci&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : In major incident email notifications, you can now decide where the links to a major incident record are redirected. Instead of a major incident record automatically opening in the classic UI16 interface in Major Incident Management, the record can be opened in SOW. The major incident record link in an email notification opens in SOW only if the following conditions are met: * The Redirect SOW Email notification (sow_email_notification_redirect) property is set to true. Setting this property to true enables the email redirection behavior for all tables including major incident. * The Redirect SOW Email notification for Major Incident Management (sn_major_inc_mgmt.sow_email_notification_redirect.mim) property is set to true. * You have the sn_sow_user role. {#rn-summary-changes__ul_v1l_cnz_3bc} The ITSM Notifications Redirection (com.snc.itsm.notifications_redirection) plugin is installed and activated automatically to support this behavior. [Email redirection behavior for incident email notification links](https://www.servicenow.com/docs/access?context=email-notif-redirt-inci-major-inci&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : In incident email notifications, you can now decide where the links to an incident record are redirected. Instead of an incident record automatically opening in the classic UI16 interface in Incident Management, the record can be opened in SOW. The incident record link in an email notification opens in SOW only if you have the sn_sow_user role and any of the following conditions are met: * The Redirect SOW Email notification (sow_email_notification_redirect) property is set to true. Setting this property to true enables the email redirection behavior for all tables including incident. * The Redirect SOW Email notification for Incident Management (sow_email_notification_redirect.incident) property is set to true. You can create this property if you want to enable or restrict the email redirection behavior specifically for the incident table. This property, if created and set, overrides the Redirect SOW Email notification (sow_email_notification_redirect) base system property. {#rn-summary-changes__ul_lxn_fs3_ddc} The ITSM Notifications Redirection (com.snc.itsm.notifications_redirection) plugin is installed and activated automatically to support this behavior. To ensure consistency, the email notification templates for incident tasks are also updated to send the notification from Service Operations Workspace (SOW) in the same format as sent from classic UI16 interface similar to incident. Also, the template theme is updated to match the Next Experience theme. [Incident and problem workflow changes](https://www.servicenow.com/docs/access?context=incident-management-properties&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : When a problem is fixed and the Share fix option is triggered, the event is added to the Work notes (Private) field instead of the Additional comments (Customer visible) field for the incident associated with the problem record. This feature is available in the base system for the new customers. For existing or upgrade customers, admin must set the Communicate problem workaround to incident worknotes (com.snc.incident.communicate_prb_workaround_to_inc_worknotes) system property to true to enable the feature. [Changes in the reopening incident behavior](https://www.servicenow.com/docs/access?context=reopening-incident&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : Enable the agents with incident write access, callers, requesters, or Opened by end users to reopen a resolved incident. Both the caller and the requester can view and use the Reopen option on the incident classic UI16 form and the Portal UIs, such as Service Portal and Employee Service Center (ESC) portal. An agent can view and use the Reopen option on the incident classic UI16 form to reopen any incident that is assigned to them or to other agents. However, on the Portal UI, an agent can only view and use the Reopen option to reopen an incident if it's assigned to them. [Sorting CIs in incident forms](https://www.servicenow.com/docs/access?context=create-an-incident&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : The search performance of the available CIs for the Configuration item field on an incident form is enhanced to promote a clean UI and quick loading and sorting of the CIs. The search results that list the CIs are sorted alphabetically by CI name instead of by CI class and then CI name. The ref_ac_order_by=sys_class_name attribute is removed from the default attributes on the cmdb_ci field of the Task \[task\] table, which increases the performance of the field. This change is applicable to new and existing users using the default attributes. You can use the Override attributes option to restrict this change for any required child tables that extend to the cmdb_ci field of the Task \[task\] table. |
| Industrial Process Manager | [Not in use value for the Operational Status field](https://www.servicenow.com/docs/access?context=equipment-model-workspace&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The Not in use value was added as an Operational Status field option in an equipment model entity site record in the Industrial Workspace. [All OT Devices by Managed Network list](https://www.servicenow.com/docs/access?context=view-ot-devices-managed-by-network&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The All OT Devices by Managed Network list was added to the Industrial Process Manager module on the ServiceNow AI Platform. [Favorite icon in the Equipment Model Manager of the Industrial Workspace](https://www.servicenow.com/docs/access?context=favorite-child-equipment-model-entity&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : In the Equipment Model Manager on the Industrial Workspace, the Favorite icon (![]()) was added to add child equipment model entities as a favorite in your system. [Show Favorites toggle in the in the Equipment Model Manager of the Industrial Workspace](https://www.servicenow.com/docs/access?context=favorite-child-equipment-model-entity&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : In the Equipment Model Manager on the Industrial Workspace, you can switch on the Show Favorites toggle to view only your favorite equipment model entities. The Show Favorites toggle focuses your UI view on specific equipment model entities to help you stay on track while making changes in the Equipment Model Manager. [List expansion during equipment model entity search in the Equipment Model Manager of the Industrial Workspace](https://www.servicenow.com/docs/access?context=search-equipment-model-entities&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : When you use the search function to find an equipment model entity, the list expands to show and highlight the search entity. [Mapped equipment model entity column](https://www.servicenow.com/docs/access?context=view-all-mapped-ot-devices&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The Mapped equipment model entity column was added to the Industrial Workspace list views for OT devices. [Mapped OT Devices list](https://www.servicenow.com/docs/access?context=view-all-mapped-ot-devices&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The Mapped OT Devices list is now available in the Industrial Workspace list view so you can view the mapping between an equipment model entity and an OT device. [ISA Hierarchy search bar](https://www.servicenow.com/docs/access?context=search-equipment-model-entities&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : A search bar was added to the ISA Hierarchy in the Industrial Workspace so you can search for equipment model entity names. [View OT Unified Map button](https://www.servicenow.com/docs/access?context=view-ot-unified-map&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The View OT Unified Map button was added to the equipment model entity record in the Industrial Workspace to access the Unified Map. [View OT Unified Map button](https://www.servicenow.com/docs/access?context=view-ot-unified-map&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The View OT Unified Map button was added to OT incident records, OT change request records, and remediation task records to access the Unified Map associated with the opened record. [Industrial Process Health icon](https://www.servicenow.com/docs/access?context=view-ot-unified-map&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The Industrial Process Health icon (![Industrial Process Health icon]()) was added to OT incident records, OT change request records, and remediation task records to access the Unified Map in the record side panel. [Viewing multiple records at once in the Equipment Model Manager](https://www.servicenow.com/docs/access?context=managing-equipment-models-after-data-import&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : In the Equipment Model Manager of the Industrial Workspace, view multiple records and keep the record context available instead of only viewing one record at a time. When creating or opening multiple records, the records open in single row of tabs at the same level so you can navigate back to other opened records. |
| Instance Data Replication | [Seeding request improvements](https://www.servicenow.com/docs/access?context=exploring-instance-data-replication&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) : In V2 replication sets, the number of records in a seeding request is now unlimited. [Data comparison improvements](https://www.servicenow.com/docs/access?context=comparing-replicated-data&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) : In V2 replication sets, the number of records in comparison or reseeding counts is now unlimited. [Reseed missing attachments](https://www.servicenow.com/docs/access?context=comparing-replicated-data&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) : Attachments are now included in data comparison requests. [Seeding performance improvements](https://www.servicenow.com/docs/access?context=seed-consumer-instance&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) : Seeding throughput and message queue efficiency has been optimized in IDR. |
| Insurance Claims Core | [Added fields to Claim Incident table](https://www.servicenow.com/docs/access?context=insurance-claims-core-tables&version=yokohama&pubname=yokohama-financial-services-operations&ft:locale=en-US){#rn-summary-changes__insurance-claims-core-rn-workspace} : Added the following fields to the Claim Incident \[sn_ins_claim_property\] table: * Injured * Insured property {#rn-summary-changes__d2742e76} |
| Integration Hub | [Create an HTTP(s) connection](https://www.servicenow.com/docs/access?context=create-https-connection&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US) Options to specify the MID Server capabilities and MID application in a connection record : The Configure Connection form, that you use to configure a connection between your ServiceNow instance, and a third-party application now provides the following fields when you select Auto-Select MID Server from the MID Selection list. * Capabilities: The capabilities that the MID Server must support to be eligible for selection. * MID Application: The application that the MID Server must support to be eligible for selection. {#rn-summary-changes__ul_zsc_h5m_hdc} |
| Knowledge Center | [Knowledge Center Home Page](https://www.servicenow.com/docs/access?context=kc-home-page&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) : The Knowledge Center home page comes equipped with dashboards. New features like article optimization, identify knowledge gaps and, manage duplicate articles improve productivity. The enhanced article editor is integrated with article optimization support to generate high quality content effortlessly. |
| Knowledge Graph | [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Configure ACLs for AI agents and agentic workflows](https://www.servicenow.com/docs/access?context=aia-security-implementation&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all authenticated users or publicly available. |
| Knowledge Management | [Editing functions for knowledge articles in the HTML editor](https://www.servicenow.com/docs/access?context=knowledge-html-editor&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) : Identify and resolve accessibility related issues during Knowledge article generation through a new accessibility checker button in the TinyMCE toolbar. |
| MID Server | [MID Server supports and requires a minimum JRE version 17](https://www.servicenow.com/docs/access?context=r_MIDServerSystemRequirements&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) : The MID Server is compiled using Java 17 and is incompatible with any Java version below 17 for runtime execution. The MID Server is bundled with version 17.0.12 and the minimum JRE version supported is 17.0.10. See the [MID Server JRE Minimum Version Requirement Update to JRE 17 Starting from Yokohama Release \[KB1704368\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1704368) article in the Now Support Knowledge Base for information about required procedures before upgrading the instance. [Improvements when manually installing a MID Server on Windows](https://www.servicenow.com/docs/access?context=mid-server-install-prereqs&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) : The MID Server can now be installed on Windows hosts directly as a LocalSystem or non-admin user with Start and Stop permissions. |
| Mentoring | [Share mentor names and key dates with my manager check box](https://www.servicenow.com/docs/access?context=edit-mentee-preferences&version=yokohama&pubname=yokohama-employee-service-management&ft:locale=en-US) : A new Share mentor names and key dates with my manager check box is introduced in the mentee preferences form. Selecting this check box shares information with your manager and helps them validate your skill levels. |
| Mobile Platform | [Mobile App Builder](https://www.servicenow.com/docs/access?context=mab-concept&version=yokohama&pubname=yokohama-mobile&ft:locale=en-US) : Use the following enhancements added to Mobile App Builder: * Live component preview enables admins to view their mobile app changes in real-time. * Use Mobile App Builder to transform your web forms into native mobile experiences with the guided flow when you create a new mobile record screen. * The right-hand panel is now visible when a record is opened in a preview browser tab. * Component recommendations available for additional record types. * The card selection and preview screens in the Web to Mobile flow have been consolidated to create a more streamlined user experience. This allows for the ability to generate previews using the different card options and jump back and forth between them to review. {#rn-summary-changes__ul_vtq_frc_ycc} [Input form screen enhancement and changes](https://www.servicenow.com/docs/access?context=parameter-input-screen&version=yokohama&pubname=yokohama-mobile&ft:locale=en-US) : Use the following enhancements added to the input form screen: * Selecting input values directly within the input form screen, either from a list or from a group of chips. Now users don't need to navigate to a separate dedicated screen for value selection, when using the inline choice chips layout. You can also define the number of input values to display on an input form screen section. * Ability to add images, plain text, and rich text within specific inputs. These added descriptive elements provide more context to your users and give a clearer idea of what is required for certain inputs. For example, an image can accompany a checklist to ensure that a piece of hardware is wired correctly. * Provide users with the ability to perform actions in relation to the displayed input parameter, while working directly on an input form screen. The available actions are: navigate to another screen, add an attachment from the gallery or camera, and add a comment to a field. Users submit these added actions either when saving their progress or completing the input form screen. * Save input form screen data before it's submitted. Users with access to the same record can see each other's changes either when saving their progress or completing the input form screen. * Interact and switch between other navigation tabs while also working on the input form screen. * Sections are no longer displayed if they don't contain any input fields. {#rn-summary-changes__ul_g5j_qqq_ycc} [Additional number attributes for input form screens](https://www.servicenow.com/docs/access?context=parameter-screen-var-attr&version=yokohama&pubname=yokohama-mobile&ft:locale=en-US) : Use the following number attributes in your input form screens: * Use the CustomErrorMessage attribute to specify an error message when a UI rule condition is met. * Use the SkipValidationWhenHidden attribute to skip validation on hidden inputs. {#rn-summary-changes__ul_osh_h4k_hdc} [Enable barcode scanning with an external scanner](https://www.servicenow.com/docs/access?context=enable-external-barcode-scanner&version=yokohama&pubname=yokohama-mobile&ft:locale=en-US) : Configure barcode scanning with an external scanner without denying access to the camera for the entire mobile app. [Mobile Publishing enhancements and changes](https://www.servicenow.com/docs/access?context=mobile-publishing&version=yokohama&pubname=yokohama-mobile&ft:locale=en-US) : * Enabled Android deep links for multiple instances. * Enhanced validation for transparent images used in branded apps. * Support for public-facing screens in branded mobile apps. Admins can configure URLs that link to public-facing web pages. These web pages are displayed to end users without needing to log in to the mobile app. {#rn-summary-changes__ul_sgb_4py_hdc} [Turn off Zero Trust Access banners in mobile app screens](https://www.servicenow.com/docs/access?context=turn-off-zta-banner&version=yokohama&pubname=yokohama-mobile&ft:locale=en-US) : In mobile client versions 19.4 and later, you can turn off Zero Trust Access banners on mobile screens. Turning off these banners can enhance usability of your mobile apps because the banner does not display each time the connection state changes so end users are not interrupted by the banner display. You can configure this behavior by setting the disableZTABanner mobile property on your ServiceNow instance. |
| Next Experience | [Enable keyboard focus on truncated text user preference](https://www.servicenow.com/docs/access?context=next-experience-accessibility-preferences&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) : The "Enable keyboard focus on truncated text" user preference has been updated to "Enable keyboard focus on text that displays a tooltip." [Improved keyboard shortcut modal](https://www.servicenow.com/docs/access?context=using-the-next-experience-global-header&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) : The keyboard shortcut menu has improved usability in the following ways: * The modal now includes two columns that include the keyboard shortcut and a description with a scrollable list of available shortcuts on the viewed page. * A search field enables you to search for shortcuts that are relevant to the page you're viewing. * A Close button enables you to easily close the modal. {#rn-summary-changes__ul_z4v_q52_ycc} [Next Experience preferences](https://www.servicenow.com/docs/access?context=set-up-preferences-next-experience&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US){#rn-summary-changes__next-experience-rn-rn-workspace} : The new user preference panel provides a more efficient, streamlined way for you to work. Use the new search bar to locate your preferences. A wider modal displays all preference groups and when you select a group, all the individual preferences that are related to it appear in the same window. |
| Next Experience Components | {#rn-summary-changes__table_qvp_xdg_zcd__entry__2} | Component | Enhancement | |-|-| | Appointment calendar | * Select multiple slots * Add customizable categories for appointment slots * Hide past and unavailable slots * Add contextual tags in appointment slots * Configure number of rows displayed in each slot in the Day and DAYMOBILE views * Configure container height adjustment {#rn-summary-changes__ul_sfn_sn5_4dc} | | Attachments | * Option to download all attachments * Revised delete attachment confirmation popup message {#rn-summary-changes__ul_j13_jfg_pdc} | | Avatar | Configure avatar to behave as a button or a link. | | Calendar | * DST support with multiple time zones in the Calendar and Timeline views * Hide header * Multiple time zones in the Timeline view * Scroll control for the Calendar and Timeline views {#rn-summary-changes__ul_p22_4yl_qdc} | | Email composer | Now Assist generative AI suggestions for all email scenarios, email templates, response templates, and quick messages. | | Email composer (mini) | Now Assist generative AI suggestions for all email scenarios, email templates, response templates, and quick messages. | | Form | * Configuration panel updates * Form controller configuration panel updates {#rn-summary-changes__ul_nh4_rfg_pdc} | | Form templates | * Sort templates alphabetically and by last used. * New tab for Favorites for you to add and remove templates. * Larger cards that don't truncate template name and description, and show Last used timestamp. {#rn-summary-changes__ul_bzp_vfg_pdc} | | Highlighted value | * Medium size variant. * Custom tooltip property. {#rn-summary-changes__ul_owp_lyg_ldc} | | iFrame | Send messages to iframed document. | | Kanban Board | * Multi-select in cards * Configure selecting dependency lines * Add secondary header {#rn-summary-changes__ul_xkx_b3m_qdc} | | Modeless dialog | Make the dialog dynamic and automatically resize to fit the content. | | Node Map | * Force layout for representing graphs without structure or hierarchy * Custom popover configuration in Hierarchical, Layered, and Force layouts * Customizable nodes in non-unified layouts * Self-referencing nodes denoted with edges looping back to the node * Export maps in JPG and PNG * Aggregate or segregate multiple connections between the same nodes {#rn-summary-changes__ul_ibn_f45_4dc} | | Pill | Display the selected pill state which doesn't display by default. | | Quick filter | * Configure section headers in typeahead dropdown * Configure footer action button * Configure placeholder text value for input field {#rn-summary-changes__ul_vtf_cgg_pdc} | | Record lookup | * Search for contacts by name, phone, or email * Preview shortlisted results in a paginated form * Quickly link or unlink a shortlisted contact to a case * Edit details for a record without accessing the parent record * Hide record header * Configure search results * Render highlighted values in the linked card * Qualify search results using specific conditions (reference qualifiers) * Hide fields with empty values * Hide link button * Expand or collapse card {#rn-summary-changes__ul_gwg_lgg_pdc} | | Stepper | * Standardized font size (small or medium) for all steps * By default, pagination adjusts to display the current selected step {#rn-summary-changes__ul_ehz_tdb_pdc} | [Table 4. Components] {#rn-summary-changes__table_qvp_xdg_zcd} {#rn-summary-changes__table_eqq_1fg_zch__entry__2} | Chart | Enhancement | |-|-| | Bar | Percent (%) information added to chart tooltips and data table below chart. | | Bubble | Percent (%) information added to chart tooltips. | | Geomap | Percent (%) information added to chart tooltips and data table below chart. | | Heatmap | * Percent (%) information added to chart tooltips and data table below chart. * When the metric value is set to "Count," show a zero (0) when no data is available. {#rn-summary-changes__ul_t5k_gzv_ldc} | | Pivot table | * When there's no value in the selected dataset or for the configuration, choose the display format. * Data sources limit increased from 10 to 15. {#rn-summary-changes__ul_dby_gsg_pdc} | | Time series | * Percent (%) information added to chart tooltips and data table below chart. * Support for business calendars such as Gregorian, fiscal, and any manually added calendar. * For all chart formats, except "column:" * When there's no value in the selected dataset or for the configuration, choose the display format. * For table data sources, when there's no data for a specific time on the chart, show a continuous line without gaps. {#rn-summary-changes__ul_vlr_gcw_ldc} * Show a chart and graph data table for easier screen reader access. * For line, spline, area, and step charts, have a marker show at each data point on the chart including where values are zero (0) or missing. * For a chart with up to 3 metrics, you can add alternative Group by's for each metric for the user to select from. * Sorting when data is grouped. * New Date range option to set the period end date to update automatically to the current date. {#rn-summary-changes__ul_l52_4wv_ldc} | [Table 5. Data visualizations] {#rn-summary-changes__table_eqq_1fg_zch} {#rn-summary-changes__table_y2f_x1z_4dc__entry__2} | Template | Description | |-|-| | Dashboards | * Pills at the top of the page display any categories assigned to the dashboard * User avatars at the top of the page indicate real-time editing {#rn-summary-changes__ul_wh3_lyk_ydc} | [Table 6. Templates] {#rn-summary-changes__table_y2f_x1z_4dc} {#rn-summary-changes__table_cr1_bfg_zce__entry__2} | Bundle | Enhancement | |-|-| | Record list | * Condition builder available in the list header * If live list is enabled, infinite scrolling is enabled by default {#rn-summary-changes__ul_azt_jdz_4dc} | [Table 7. Bundles] {#rn-summary-changes__table_cr1_bfg_zce} |
| Next Experience Developer (NED) Tools | Component visualization : Highlighted components feature a tooltip that displays the element tag name and element ID. Time filters for events : Icons were added to each event to enable you to select a timeframe when filtering events. Subtree filters for events : Scroll and search through a selected portion of the component tree. |
| Notifications | [Advanced filters options for notification preferences](https://www.servicenow.com/docs/access?context=advanced-notification-prefrences&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Added categories, delivery channels, active or inactive notifications, subscriptions, and digest-enabled filter options for notification preferences. [Standard forms](https://www.servicenow.com/docs/access?context=advanced-notification-prefrences&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Enabled standardized forms across custom notification preferences and delivery channels. [Assignment group field](https://www.servicenow.com/docs/access?context=create-add-assignment-group&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Extended the provider framework to add support for assignment groups. [Advanced condition field](https://www.servicenow.com/docs/access?context=noti-new-update-notification&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Extended the provider framework to add an advanced condition. [Advanced filters in notification preferences](https://www.servicenow.com/docs/access?context=advanced-notification-prefrences&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US){#rn-summary-changes__notifications-rn-rn-workspace} : Use notifications filters for categories, delivery channels, active or inactive notifications, subscriptions, and digest enabled notifications. [Support for assignment group](https://www.servicenow.com/docs/access?context=create-add-assignment-group&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Send provider notifications for assignment groups and to users that are part of groups stored in sys_user_group table. [Advanced condition for provider framework](https://www.servicenow.com/docs/access?context=noti-new-update-notification&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Use an advanced condition to send a notification that is based on the current email record, changing field values, or system properties. [Mandatory notifications for provider framework](https://www.servicenow.com/docs/access?context=make-notification-mandatory-provider&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Make critical notifications mandatory for the provider framework. [Email bounce](https://www.servicenow.com/docs/access?context=email-bounce&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Prevent resending bounced emails to the addresses that are known to generate bounces. |
| Now Assist | [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Configure ACLs for AI agents and agentic workflows](https://www.servicenow.com/docs/access?context=aia-security-implementation&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all authenticated users or publicly available. [Edit a Now Assist skill](https://www.servicenow.com/docs/access?context=edit-a-now-assist-skill&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : You can now view the Helpful resources and Frequently asked questions (FAQ) tabs on the list view of the Now Assist skills page. [Email reply recommendation](https://www.servicenow.com/docs/access?context=now-assist-skills&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The email response creation skill offers guidance in choosing the most appropriate template based on the user's specific context. Additionally, it identifies the potential errors when a response isn't generated as intended. [Default email client for email recommendation skill](https://www.servicenow.com/docs/access?context=now-assist-skills&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The Seismic email client is enabled by default on Core UI with the activation of email recommendation. This client provides the Generative AI application features for creating email responses, draft management, and template management. [Now Assist panel response](https://www.servicenow.com/docs/access?context=now-assist-panel-overview&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US)Now Assist panel response : With the carousel experience removed, the Now Assist panel now generates a synthesized response for any user inquiry. This response includes content from Knowledge articles, flows \& actions, skills, and links to those articles, instead of only the Now Assist panel skills. [Now Assist data sharing opt-out moved to Data sharing and processing tab.](https://www.servicenow.com/docs/access?context=opt-out-of-data-sharing-for-now-assist&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The opt-out button in the data sharing card from the AI Admin Hub Account page has moved to the Settings page on the Data sharing and processing tab. [Now Assist context menu](https://www.servicenow.com/docs/access?context=now-assist-write-overview&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : You can now open the Now Assist context menu by selecting the Now Assist context menu icon (![Now Assist Context menu icon.]()) for effortless access.The Now Assist context menu enables users to automatically select a sentence, paragraph, or the entire content even if they initially make a partial selection. Administrators can configure the selection to be a sentence, paragraph, or the entire content.The dynamic header label next to the Now Assist context menu icon can be customized to display the query status.The new Now Assist context menu icon (![Context menu icon .]()) was updated with an enhanced animation. [Configure multilingual service for Now Assist applications](https://www.servicenow.com/docs/access?context=enable-dynamic-translation-for-now-assist-applications&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Enable translation settings is now Multilingual service in Now Assist admin console. |
| Now Assist AI agents | [Create an AI agent](https://www.servicenow.com/docs/access?context=configure-next-best-action-agent&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The guided setups for creating an AI agent and agentic workflow have been updated. [Define security controls for an agentic workflow](https://www.servicenow.com/docs/access?context=define-sec-controls-aw&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) and [Define security controls for an AI agent](https://www.servicenow.com/docs/access?context=define-sec-controls-aia&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : New security configuration UI pages have been added in the AI Agent Studio application to configure security controls for agentic workflows and AI agents for role masking. [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Configure ACLs for AI agents and agentic workflows](https://www.servicenow.com/docs/access?context=aia-security-implementation&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all authenticated users or publicly available. [Platform Request status AI agent](https://www.servicenow.com/docs/access?context=ticket-status-aia&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The request status AI agent provides an AI-generated summary of the most recent comments from the AI agent or other people working on a ticket. You can add attachments to an open ticket or incident to support a request action. To find more information about an open ticket, you can ask the request status AI agent follow-up questions based on previous answers from the agent. [Configuring Now Assist AI agents](https://www.servicenow.com/docs/access?context=configuring-ai-agents&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Run AI agents and agentic workflows concurrently in AI Agent Background Channel and in Non-interactive mode. [Add a Knowledge Graph to an AI agent](https://www.servicenow.com/docs/access?context=add-knowledge-graph&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The Global Graph resource for creating a Knowledge Graph tool has been renamed to Enterprise Graph. [Confirm your web search tool provider data policies](https://www.servicenow.com/docs/access?context=add-web-search-ai-agent&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : If you select Google as your web search provider for web search AI agent tools, Google will use [Grounding with Google Search](https://cloud.google.com/vertex-ai/generative-ai/docs/grounding/grounding-with-google-search), offered under a Global Standard deployment, and data may be routed to places outside of regions specified on your ServiceNow instance as a result. Consult your organization's data policies before enabling AI agents with web search tools that use Google as the provider. [Follow new guided setups for agentic workflows and AI agents](https://www.servicenow.com/docs/access?context=configure-use-case-ai-agents&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new steps for the guided setups for AI voice agents and agentic workflows includes additional help text and guidance for writing LLM instructions to help improve outcome and task completion. [Manually test the execution of an AI agent](https://www.servicenow.com/docs/access?context=test-ai-agent&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The tab names on the AI Agent Studio testing page have been renamed. The Test scenario tab is renamed to Test AI reasoning tab and the Output tab to Chat responses tab. [Add version control to instructions sent to the LLM](https://www.servicenow.com/docs/access?context=version-control&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : You can review multiple versions of instructions sent to the LLM when designing your AI agents or agentic workflows. You can choose which version is active to help with testing or evaluating the success of an AI agent or agentic workflow to compare against other versions. Versions are named and ordered by time created for organizational purposes. [Duplicate and edit existing tools when creating new AI agents](https://www.servicenow.com/docs/access?context=add-tool-aia&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : When adding a tool to an AI agent, you can select an existing tool instead of creating a new tool from scratch. After an existing tool is added, you can make changes to suit the specific AI agent's needs. [Now Assist AI agents reference](https://www.servicenow.com/docs/access?context=na-aia-reference&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The sn_aia.enable_agent_tool_input_value_overrides system property is migrated to the \[sn_aia_property\] agent system property. [Monitor more AI agent analytics in the AI Agent Analytics dashboard](https://www.servicenow.com/docs/access?context=ai-agent-dashboard&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Two new pages have been added to the AI Agent Analytics dashboard, giving administrators more indicators, visualizations, and breakdowns to track AI agent performance and usage. [Exploring Now Assist AI agents](https://www.servicenow.com/docs/access?context=exploring-ai-agents&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Impersonation in Now Assist records transactions done by an AI agent in the name of the AI agent who executes the agentic workflow. [Now Assist AI agents](https://www.servicenow.com/docs/access?context=na-ai-agents&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) - The phrase "use case" has been updated to "agentic workflow". : In AI Agent Studio, the phrase "use case" in the UI has been replaced with the phrase "agentic workflow" on all screens. [Tools visible when testing AI agents](https://www.servicenow.com/docs/access?context=test-ai-agent&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : When testing an AI agent, individual tool processes are now visible in the testing window, enabling you to track tool use, successes, or failures when trying out new AI agents. [Use data picker for value overrides in AI agent tools](https://www.servicenow.com/docs/access?context=configure-next-best-action-agent&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : When creating or modifying tools for AI agents, you can now use a data picker in value override fields. This helps ensure that information in records fields is transferred between tools. |
| Now Assist for IT Operations Management (ITOM) | [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Configure ACLs for AI agents and agentic workflows](https://www.servicenow.com/docs/access?context=aia-security-implementation&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all authenticated users or publicly available. [AIOps AI agents removed from the analyze alert impact agentic workflow](https://www.servicenow.com/docs/access?context=now-assist-itom-agentic-aia&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US) : Four AIOps AI agents have been removed from the analyze alert impact agentic workflow as they're now available in the manage alerts autonomously agentic workflow. AI agents for Dynatrace, Kentik, and New Relic remain in the analyze alert impact agentic workflow to help you learn about and respond to alerts. |
| Now Assist for Source-to-Pay Operations | [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Configure ACLs for AI agents and agentic workflows](https://www.servicenow.com/docs/access?context=aia-security-implementation&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all authenticated users or publicly available. [Use the ServiceNow Otto for Sourcing and Procurement Operations (SPO) skills in a Virtual Agent chat](https://www.servicenow.com/docs/access?context=now-assist-spo-va-using&version=yokohama&pubname=yokohama-source-to-pay-operations&ft:locale=en-US) : Requesters can leverage contextual generative AI by using ServiceNow Otto for SPO in a Virtual Agent chat to complete self-service tasks, such as purchasing products. |
| Now Assist in AI Search | [Now Assist in Virtual Agent conversational prompt auto-complete suggestions](https://www.servicenow.com/docs/access?context=auto-complete-suggestion-types-na-ais&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Auto-complete suggestions for Now Assist in Virtual Agent conversational prompts are only returned from the search user's domain. Suggestions are disabled if they match any exclusion rule entry from the Search Suggestion Exclusion List \[sys_search_suggestion_blacklist\] table. The system scores suggestions based on how search users interact with and rate their Genius Result responses, and preferentially displays higher-scored suggestions. [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Configure ACLs for AI agents and agentic workflows](https://www.servicenow.com/docs/access?context=aia-security-implementation&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all authenticated users or publicly available. [Semantic vector search indexing includes Catalog Item short descriptions](https://www.servicenow.com/docs/access?context=semantic-search-ais&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Semantic indexing now indexes short descriptions from Catalog Item source records to improve search recall and make field indexing more consistent between legacy (keyword) and semantic indexing. |
| Now Assist in Contract Management | [Automated obligation extraction](https://www.servicenow.com/docs/access?context=cmpro-na-reminder-agentic-wf&version=yokohama&pubname=yokohama-employee-service-management&ft:locale=en-US#section_tgm_mt3_dhc) : Use the manage contract repository agentic workflow to automatically identify and capture key contractual obligations from signed contracts and create obligation records in the contract repository. The AI agent in the manage contract repository agentic workflow uses the Now Assist Contract obligation extraction skill to extract key contractual obligations from contracts. [Using contract playbook to review AI-extracted obligations](https://www.servicenow.com/docs/access?context=cmpro-na-review-obligations&version=yokohama&pubname=yokohama-employee-service-management&ft:locale=en-US) : Review extracted obligations in the contract playbook, with options to edit, approve, or reject each obligation. Approved obligations are added as obligation records in the contract repository while rejected obligations are deactivated. [Contract obligation extraction skill in Now Assist in Contract Management](https://www.servicenow.com/docs/access?context=cncore-conf-obligation-extraction&version=yokohama&pubname=yokohama-employee-service-management&ft:locale=en-US) : Configure and map use cases for obligation extraction skill in the AI Admin Hub console to automatically extract key contractual obligations from signed contracts. The AI agent in the manage contract repository agentic workflow uses the Now Assist Contract obligation extraction skill to extract key contractual obligations from contracts. [Conversational contract search and insights Workflow](https://www.servicenow.com/docs/access?context=cmpro-agentic-use-conv-search&version=yokohama&pubname=yokohama-employee-service-management&ft:locale=en-US) : Contract documents are often complex and stored across multiple formats and repositories, making keyword-based search inefficient and error-prone. The new Now Assist powered conversational search feature enables you to search contract documents using natural language and dialogue-driven queries. The conversational search feature does not support searching within contract documents that are scanned PDFs. [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Now LLM LTS support for Contract Management Pro](https://www.servicenow.com/docs/access?context=now-llm-model-updates&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Long term stable (LTS) models are part of Now LLM Service and provide longer model stability windows for regulated industries. These models can integrate with tools to provide governance, monitoring, and compliance controls. [Extract metadata from signed contracts automatically](https://www.servicenow.com/docs/access?context=cmpro-na-reminder-agentic-wf&version=yokohama&pubname=yokohama-employee-service-management&ft:locale=en-US) : Use the AI agents in the Manage contract repository agentic workflow to automatically extract metadata from signed contracts and calculate the contract reminder dates for contract renewal or termination. You can review the AI results in the contract playbook and update it if necessary before saving it. [Contract metadata extraction use cases](https://www.servicenow.com/docs/access?context=metadata-extraction-use-case&version=yokohama&pubname=yokohama-employee-service-management&ft:locale=en-US) : Support for 14 additional metadata fields in the CM Pro - Contract Metadata Extraction use case available in the base system. [Configuring contract metadata extraction](https://www.servicenow.com/docs/access?context=cncore-conf-metadata-extraction&version=yokohama&pubname=yokohama-employee-service-management&ft:locale=en-US) : Create a use case and its associated fields for contract metadata extraction in the AI Admin Hub console to define the information that you want Now Assist to detect in a signed contract.Create a use case mapping in the AI Admin Hub console to map a use case to specific tables and define conditions to apply the use case for metadata extraction. [Configuring contract analysis](https://www.servicenow.com/docs/access?context=cmpro-conf-contract-analysis&version=yokohama&pubname=yokohama-employee-service-management&ft:locale=en-US) : Create a use case and its associated question groups for contract analysis in the AI Admin Hub console to identify the non-standard and missing clauses in a contract.Create a clause mapping AI Admin Hub console to map question groups of a use case to active clauses in the clause library to display suggestions for non-standard clauses in a contract.Create an expected response mapping in the AI Admin Hub console to map questions of a use case to an expected response to identify the non-standard clause in a contract.Create a use case mapping in the AI Admin Hub console to map a use case to specific tables and define conditions to apply the use case for contract analysis. |
| Now Assist in Document Intelligence | [Document and visual insights AI agent enhancements](https://www.servicenow.com/docs/access?context=document-and-visual-insights-ai-agent&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Tools used by the document and visual insights AI agent are consolidated to improve performance. [Now Assist in Document Intelligence skills are now turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading: Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. {#rn-summary-changes__ul_inq_nsg_m3c} [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Configure ACLs for AI agents and agentic workflows](https://www.servicenow.com/docs/access?context=aia-security-implementation&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all authenticated users or publicly available. [Document and visual insights AI agent enhancements](https://www.servicenow.com/docs/access?context=document-and-visual-insights-ai-agent&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Generate a summary of document and image attachments with the document and visual insights AI agent. [Usability enhancements to use case setup features](https://www.servicenow.com/docs/access?context=set-up-use-case-for-now-assist-document-intelligence&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Various features for the use case setup are updated to create a more effective user experience: * Field is changed to question in the field form for Q\&A use case setup. * Single field is changed to Field in the field form for the document extraction use case setup. * An Additional Details field is added to the table form for the document extraction use case setup as a way to help the large language model (LLM) extract the relevant information from the document. {#rn-summary-changes__ul_cw3_jyq_52c} |
| Now Assist in Platform Analytics | [View recommended actions](https://www.servicenow.com/docs/access?context=expl-view-recommended-actions&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : AI Data Explorer can suggest actions based on the insights that it generates in an exploration. [Ask questions about FX currency data](https://www.servicenow.com/docs/access?context=qg-supported-query-operations&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : Query Generation now supports the FXCurrency (Currency 2) data type. This means that you can use AI Data Explorer to explore financial operations data, including those within Source-to-Pay Operations. [Benefit from improvements to segments](https://www.servicenow.com/docs/access?context=querygen-segments&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : Segments are reusable definitions in Query Generation that provide non-obvious context to assist the semantic layer or LLM to select the correct dimension and values. Users can create manual segments via a new form. A scheduled job synchronizes manual and autogenerated segments. This job also cleans up segments to help surface the correct segments and reduce noise. Domain separation is also now supported, with a Domain field on the Segments table. Segments based on reports and filters inherit the source domain. Manual segments have domains that are passed up to the Segments table on synchronization. Segments are not supported for indicator sources or modules on domain-separated instances. [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Configure ACLs for AI agents and agentic workflows](https://www.servicenow.com/docs/access?context=aia-security-implementation&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all authenticated users or publicly available. [Query Generation skills are active by default](https://www.servicenow.com/docs/access?context=enable-query-generation&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : If the Generative AI Controller plugin is activated, the skills for Query Generation are activated by default. [Greater visibility into the Query Generation process](https://www.servicenow.com/docs/access?context=ask-expl-questions&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : When you call Query Generation from AI Data Explorer or another application, you see each state that the query and response goes through before completing. [Multi-table source support](https://www.servicenow.com/docs/access?context=ask-expl-questions&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : Query Generation supports related table conditions and dot-walking in queries. [Get insights and visualizations for Workflow Data Fabric tables](https://www.servicenow.com/docs/access?context=create-integrations-applications&version=yokohama&pubname=yokohama-integrate-applications&ft:locale=en-US) : Ask AI Data Explorer information about Workflow Data Fabric data and get insightful responses. You must first add the Workflow Data Fabric tables to the Query Generation Semantic Table Configuration table. [Use database views in queries](https://www.servicenow.com/docs/access?context=add-table-semantic-layer&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : Generate visualizations or ask AI Data Explorer about data kept in database views, like SLA data. You have to add the database views to the Semantic Table Configuration table. [Add tables to the semantic data layer](https://www.servicenow.com/docs/access?context=add-table-semantic-layer&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : Choose which tables your users can query with generative AI for data analysis. [Monitor the health of the Query Generation back end](https://www.servicenow.com/docs/access?context=querygen-health-page&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : View the state of Now Assist for Platform Analytics LLM, plugins, system properties, components, and dependent products. |
| Now Assist in Virtual Agent | [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Conversational Platform Now Assist skills are active by default](https://www.servicenow.com/docs/access?context=now-assist-skills&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The following Platform Now Assist skills are active by default and no longer visible in AI Admin Hub console: * Now Assist Multi-Turn Catalog Ordering * Now Assist Q\&A Genius Results * Now Assist Topics * Subflows and actions * Custom skills * AI agents {#rn-summary-changes__ul_i34_r1j_nhc} [UI Virtual Agent Designer updates](https://www.servicenow.com/docs/access?context=vad-topics-page&version=yokohama&pubname=yokohama-conversational-interfaces&ft:locale=en-US) : * Use a new option in the Actions on row icon to remove an LLM assistant from a given asset. * View a tooltip if you try to promote more than six topics for a given LLM assistant. * View a list of available asset types and their descriptions when you select Create asset in the Asset library tab. {#rn-summary-changes__ul_etc_s1l_hhc} [UI chat assistant updates](https://www.servicenow.com/docs/access?context=assistant-designer&version=yokohama&pubname=yokohama-conversational-interfaces&ft:locale=en-US) : * Configuring a chat or voice assistant is done in AllAssistant DesignerAssistants tab. AllConversational InterfacesAssistants contains a Manage assistants button that directs you to Assistant Designer. * Chat and voice assistants are shown in both card and map views. * Pages within the chat assistant setup have been removed, added, or moved to a different spot within the create or edit flow. * The Overview page has been replaced by the Basic details page. * Assign Now Assist skills page has been removed. Admins no longer need to turn on/off Now Assist skill types at the assistant level in Now Assist Admin console and no longer need to assign Now Assist skill types at the assistant level. * When adding search sources, an External Content Connectors link directs you to create or configure external sources. (This replaces the External Content Connectors card.) The following sections have been removed from the search sources page: Now Assist topics, Custom skills, AI agents, and Conversational subflows and actions. They are now within the Assets page. * Knowledge Graph was moved from the Information sources page to its own page. * Assets such as topics, subflows and actions, custom skills, and AI agents are added on the Assets page. In the display experience for Now Assist panel assistants, a ServiceNow platforms header is shown. * Minor enhancements to the standard chat preview pane when branding an assistant. * Promoted assets tab within the Chat experience page has been moved to the Information sources (sub-tab)Asset visibilityPromoted while in edit mode. * Web search mode, response streaming, document uploads, and closed chats have been moved to its own Chat features page. * Testing a chat assistant is no longer part of the Review page. Access it from the Assistant DesignerAssistants tab, or on each page while in edit mode. * Editing a chat assistant is done from the Assistant DesignerAssistants tab. {#rn-summary-changes__ul_lz3_hht_fhc} {#rn-summary-changes__ul_vjr_xcs_fhc} [UI enhanced chat updates](https://www.servicenow.com/docs/access?context=nava-enhanced-chat&version=yokohama&pubname=yokohama-conversational-interfaces&ft:locale=en-US) : * Dynamic processing messages for agentic conversations are now consolidated under one View AI Steps header rather than under several View AI Steps headers. * The View all options link shows below the suggested or promoted topics cards on the greeting topic in Now Assist in Virtual Agent and Now Assist panel's enhanced chat. At least one suggested or promoted asset has to be enabled for this link to show. * The auto-complete suggestion type in the Ask Now Assist header appears at the top of the portal search bar's drop-down list. The results in the Ask Now Assist header can now show more targeted search results from AI Search rather than the GlideRecord. The entered search term can appear highlighted in bold after you have configured AI Search as the source for Ask Now Assist suggestions. For more information about this configuration, see [Configure AI Search as the source for Ask Now Assist suggestions](https://www.servicenow.com/docs/access?context=configure-ai-search-source-ask-now-assist-suggestions&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US). * The static and dynamic choice nodes now appear differently in standard and enhanced chat depending on the number of choices for single-select options. For example: * 2-5 choices appear as pills * 6 or more choices appear as a choice list with a scroll bar {#rn-summary-changes__ul_rbr_nyy_chc} * The input bar for enhanced chat has moved all icons below any inputted text. Uploaded documents appear above any inputted text. * The float, pinned, and 90% screen views of enhanced chat now have a gradient border around them. * The enhanced chat full-page experience was updated so that the Now Assist and Search button tabs that were originally center-aligned buttons are now left-aligned tabs that no longer look like buttons. {#rn-summary-changes__ul_dn3_yqq_chc} [Agentic conversation processing messages for Now Assist panel and Now Assist in Virtual Agent](https://www.servicenow.com/docs/access?context=nava-enhanced-chat&version=yokohama&pubname=yokohama-conversational-interfaces&ft:locale=en-US) : Before receiving a response, you receive acknowledgment messages from the Virtual Agent and on-screen processing messages to let you know where the agent is at in the agentic processing flow. The on-screen processing messages appear in present tense until the processing flow is complete. After the processing flow is complete, then the on-screen messages change to past tense and a View AI Steps section header appears above the processed messages. You can expand the collapsed View AI Steps section header to view the processed messages. [UI chat updates](https://www.servicenow.com/docs/access?context=nava-enhanced-chat&version=yokohama&pubname=yokohama-conversational-interfaces&ft:locale=en-US) : * The enhanced chat navigation area was updated. The New Chat, Chats, Support, and Settings icons were reworked into a simplified subheader. Additionally, each chat title now appears in the simplified subheader. * The enhanced chat's subheader reflects conversational modes in a banner whenever you enter into a specific mode, such as web search, live agent, or document upload. * In the enhanced chat's ChatsClosed chats section, hover over a chat to view the delete option and complete the delete confirmation prompts. * Minor animations occur in the following five enhanced chat transitions: * Hovering over the chat icon. * Minimizing and opening the chat icon. * Transitioning from a floating chat window to a pinned chat window and vice versa. * Transitioning from a floating chat window to a 90% modal and vice versa. * Transitioning from a pinned chat window to a 90% modal and vice versa. {#rn-summary-changes__ul_fcy_cxj_tfc} Note: Transition animation doesn't apply to custom icons. {#rn-summary-changes__ul_rkp_1tj_tfc} [UI admin guided setup updates](https://www.servicenow.com/docs/access?context=configure-now-assist-va&version=yokohama&pubname=yokohama-conversational-interfaces&ft:locale=en-US) : * Manage search profile button replaces the search profile text link. * Add external search sources drop-down list has been replaced with Add search sources drop-down list to include internal and external search sources. * The simple and advanced views within the Chat experience page are consolidated into a single view. * Copy existing configuration button is featured more prominently, and it's shown with information about its use. {#rn-summary-changes__ul_ghf_xl1_5fc} [Additional fallback options](https://www.servicenow.com/docs/access?context=using-now-assist-in-va&version=yokohama&pubname=yokohama-conversational-interfaces&ft:locale=en-US) : There are up to five fallback options that can be presented to end users: * Search the web: Triggers web search mode and uses the internet to search for the results. Note: Only the last query entered into the conversation is considered when entering web search mode via the fallback option. * Request a live chat: Triggers live agent mode and routes you to a human support representative. * Create a generic ticket: Creates a record. * End this chat: Ends the chat. Note: This option is only available to standard chat conversations. * Custom fallback option: Presents a fallback Virtual Agent topic. {#rn-summary-changes__ul_fdz_sbq_4fc} [Web search mode enhancements](https://www.servicenow.com/docs/access?context=web-search-requestor&version=yokohama&pubname=yokohama-conversational-interfaces&ft:locale=en-US) : Manually enter into web search mode via the input bar for standard and enhanced chat conversations. Web search mode includes in-line citations and the associated sources. A web search mode banner appears in enhanced chat conversations that end users can use to end the mode. [Profanity recognition response](https://www.servicenow.com/docs/access?context=nava-enhanced-chat&version=yokohama&pubname=yokohama-conversational-interfaces&ft:locale=en-US) : If AI Guardian is enabled and the end user's request contains profane content, the Virtual Agent responds with a message prompt to re-enter an appropriate request without profanity or offensive content. [UI chat updates](https://www.servicenow.com/docs/access?context=using-now-assist-in-va&version=yokohama&pubname=yokohama-conversational-interfaces&ft:locale=en-US) : * The summary card in a Now Assist in Virtual Agent conversation was updated to a more modern look and feel. * The default chat widget button for enhanced chat and standard chat now differs on the portal. * An Ask Now Assist header now appears with suggested searches in a drop-down on the portal's search bar. * The Boolean choice, static choice, and dynamic choice controls were updated to a more modern look and feel for requesters. {#rn-summary-changes__ul_nlk_sf2_y2c} [Standard chat](https://www.servicenow.com/docs/access?context=nava-standard-chat&version=yokohama&pubname=yokohama-conversational-interfaces&ft:locale=en-US) : The existing Now Assist in Virtual Agent LLM conversational behavior received a terminology update and is now referred to as standard chat. [UI chat updates](https://www.servicenow.com/docs/access?context=using-now-assist-in-va&version=yokohama&pubname=yokohama-conversational-interfaces&ft:locale=en-US) : * The New messages below button in Virtual Agent was replaced with a simplified down-arrow indicator. * The New messages above button was deprecated because Virtual Agent now auto-scrolls to the top of the oldest new message. * The Input text bar was updated to a more modern look and feel. * The start a new conversation icon was updated. {#rn-summary-changes__ul_d4s_35t_52c} [Dynamic Translation calls](https://www.servicenow.com/docs/access?context=translation-for-now-assist&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : If native translation is enabled, a Dynamic Translation call is only made if an unsupported language for native translation is used. |
| On-Call Scheduling | [Email redirection behavior for links in major on-call schedule email notification](https://www.servicenow.com/docs/access?context=create-update-schedule-oncall&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US){#rn-summary-changes__on-call-scheduling-rn-rn-workspace} : In all major on-call schedule or shift email notifications, you can now decide where the links to an on-call schedule or shift record are redirected. Instead of an on-call schedule or shift record automatically opening in the classic UI16 interface in On-Call Scheduling, the record can be opened in SOW. The on-call schedule or shift record link in an email notification opens in SOW only if the following conditions are met: * The Redirect SOW Email notification (sow_email_notification_redirect) property is set to true. * The Redirect SOW Email notification for On-call scheduling (sow_email_notification_redirect.on_call) property is set to true. * You have the sn_sow_user role. {#rn-summary-changes__d2756e82} The ITSM Notifications Redirection (com.snc.itsm.notifications_redirection) plugin is installed and activated automatically to support this behavior. |
| Operational Resilience | [Business services dashboard](https://www.servicenow.com/docs/access?context=opres-ws-homepage-overview&version=yokohama&pubname=yokohama-governance-risk-compliance&ft:locale=en-US) : The Business services dashboard has been added to display business services data. [New modules for services and processes](https://www.servicenow.com/docs/access?context=using-csdm-v5&version=yokohama&pubname=yokohama-governance-risk-compliance&ft:locale=en-US) : The Services, Business Services, Service Offerings, and Business Processes modules have been added to the Operational Resilience Workspace. Operational Resilience managers use these modules to manage the services, business services, service offerings, and business processes used in Operational Resilience reporting. [Entity Types and Pillars modules](https://www.servicenow.com/docs/access?context=manage-entity-types-pillars-from-ws&version=yokohama&pubname=yokohama-governance-risk-compliance&ft:locale=en-US) : The Entity Types and Pillars modules have been added to the Operational Resilience Workspace. These modules enable Operational Resilience managers to update the entity types and pillars directly from the Workspace. [Primary origin tab](https://www.servicenow.com/docs/access?context=add-impacted-area-to-vul&version=yokohama&pubname=yokohama-governance-risk-compliance&ft:locale=en-US) : The Primary origin tab has been added to the Operational vulnerability record to identify the main source and report the upstream entities of the vulnerability. [Addition of classes to the assessment form](https://www.servicenow.com/docs/access?context=submit-an-assessment-in-ws&version=yokohama&pubname=yokohama-governance-risk-compliance&ft:locale=en-US) : The Business Service and Offering classes have been added to the Scope tab of the assessment form, enabling you to assess the business services and service offerings alongside services. Once the assessment is complete, the importance and impact tolerance of these items are displayed in the Importance and Impact Tolerance columns on the Scope tab. [Addition of classes to the scenario analysis form](https://www.servicenow.com/docs/access?context=scenario-analysis-in-ws&version=yokohama&pubname=yokohama-governance-risk-compliance&ft:locale=en-US) : The Business Service and Offering classes have been added to the Scope tab of the scenario analysis form, enabling you to analyze the business services and service offerings alongside services. [Addition of classes to the self-attestation form](https://www.servicenow.com/docs/access?context=self-attestation-in-ws&version=yokohama&pubname=yokohama-governance-risk-compliance&ft:locale=en-US) : The Business Service and Offering classes have been added to the Scope tab of the self-attestation form, enabling you to self-attest the business services and service offerings alongside services. [Digital resilience incident reporting module](https://www.servicenow.com/docs/access?context=drir-module&version=yokohama&pubname=yokohama-governance-risk-compliance&ft:locale=en-US) : The Digital resilience incident reporting module is used to report the Information and Communication Technology (ICT) related incidents to the regulators. |
| Operational Sustainability Management | [Forecast planning and analysis](https://www.servicenow.com/docs/access?context=scenario-analysis-forecast&version=yokohama&pubname=yokohama-environmental-social-governance&ft:locale=en-US) : The forecast planning analysis module is now included in the List view of the Operational Sustainability Workspace. [Result types](https://www.servicenow.com/docs/access?context=create-manual-metric-definition&version=yokohama&pubname=yokohama-environmental-social-governance&ft:locale=en-US){#rn-summary-changes__esg-management-rn-workspace} : If you have the ESG manager \[sn_esg.metric_manager\] role, you can now configure either text, choice, or HTML format options for responses to qualitative metric data tasks that are related to manual metric definitions, including both initial and overridden responses. These options help you achieve more precision and detail in your data collection process. [Metric data table filters and side panel enhancements](https://www.servicenow.com/docs/access?context=metric-data-table&version=yokohama&pubname=yokohama-environmental-social-governance&ft:locale=en-US) : If you have the ESG data owner \[sn_esg.data_owner\] role, you can now apply filters by using the filter menu and reject or approve tasks from the metric data table side panel. Data owners can now multi-submit and assign approvers to multi-approve or reject tasks, with the option to use choice and HTML response formats. [Data owner assignment types](https://www.servicenow.com/docs/access?context=create-manual-metric-definition&version=yokohama&pubname=yokohama-environmental-social-governance&ft:locale=en-US) : If you have the ESG Manager \[sn_esg.metric_manager\] role, you can now configure the Data Owner Assignment type to be either simple or advanced for manual metric definitions. When you select the Simple option, the system assigns the specified Data Owner or Data Owner Group to the Metric Data Task. If you choose the Advanced assignment option, which is available with the GRC: Approver Configurator application, you can set custom configuration conditions, tables, or data owners to dynamically assign data owners. Table added to the GRC: Metrics application : The following tables were added to the GRC: Metrics application: * sn_grc_metric_import_job * sn_grc_metric_data_import * sn_grc_metric_st_import_log * sn_grc_metric_st_transform_history * sn_grc_metric_import_template {#rn-summary-changes__ul_n2b_gxq_tdc} Table added to the ESG content accelerator application : The sn_esg_content_issb_citation table was added to the ESG content accelerator application. Table added to the Forecast planning analysis application : The following tables were added to the Forecast planning analysis application: * sn_grc_forecast_analysis * sn_grc_forecast_context * sn_grc_forecast_data * sn_grc_forecast_parameter_data {#rn-summary-changes__ul_f5z_hyq_tdc} Database view added to the Scope 3 emissions management application : The sn_esg_scope3_asset_emissions database view was added to the Scope 3 emissions management application. Changes made to the sn_grc_metric_data_task table : In the sn_grc_metric_data_task table, the job_submitted, job_errors, choice, overridden_choice, html, and overridden_html columns were added. The type="string" attribute was added to the state column. Changes made to the sn_grc_metric_metric table : In the sn_grc_metric_metric table, the period_date, data_owner_type, data_owner, and data_owner_group columns were added. The type="string" attribute was added to the domain_area column. Changes made to the sn_grc_metric_parent_data table : In the sn_grc_metric_parent_data table, the formula_operands columns, and html columns were added. Changes made to the sn_grc_metric_base_definiton table : In the sn_grc_metric_base_definiton table, the formula_tree, result_type, choice_table, choice_field, choice_condition, data_owner_assignment_type, source columns were added. The type="string" attribute was added to the frequency column. Changes made to the sn_grc_metric_data_by_entity table : In the sn_grc_metric_data_by_entity table, the html column was added. Attributes modified in the sn_grc_metric_collector_data table : In the sn_grc_metric_collector_data table, the display="true" attribute was removed from the collector_definition column. Attributes modified in the sn_grc_metric_data_process_queue table : In the sn_grc_metric_data_process_queue table, the reference_cascade_rule="delete" attribute was added to the metric_definition column. Attributes modified in the sn_grc_metric_definition table : In the sn_grc_metric_definition table, the type="string" attribute was added to the type, method_type columns. Changes made to the sn_esg_msoff_intg_o365_reporting_configuration_filter table : In the sn_esg_msoff_intg_o365_reporting_configuration_filter table, the related_fields column was added. The display="true" attribute was added to the field_name column in the sn_esg_msoff_intg_o365_reporting_configuration_filter table. System properties are added to the GRC: Metrics application : The following properties were added to the GRC: Metrics application: * com.glide.event_manager.grc_metrics_queue.even.load.distribution.enabled * com.glide.event_manager.grc_metrics_queue.claim_limit {#rn-summary-changes__ul_mpx_tyq_tdc} |
| Operational Technology (OT) Manager Foundation | [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills, agents, and agentic workflows are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The skills are automatically available to appropriate role users for the application, such as ITIL roles on incident forms or change forms. This change simply activates the skill and does not touch the roles that may be needed to use the skill. The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills and agentic workflows are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill, agent, or agentic workflow is turned on automatically (the AI asset was never configured and turned on, then turned off again). Previously configured skills and agentic workflows that were turned on, then off, remain inactive. [Role masking](https://www.servicenow.com/docs/access?context=aia-role-masking&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : [Role masking](https://www.servicenow.com/docs/access?context=aia-role-masking&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) enables users to limit the roles and privileges of agentic workflows during tool execution. Agentic workflows and their AI agents that get installed with Now Assist applications are assigned pre-defined roles. If you select Users with specific roles for user access, you must configure the security controls to include these roles. Data access settings must also include these roles. For the instructions to change the security controls, see [Define security controls for an agentic workflow](https://www.servicenow.com/docs/access?context=define-sec-controls-aw&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US). |
| Operational Technology Change Management | [Incidents Fixed by Change related list](https://www.servicenow.com/docs/access?context=create-ot-incident-from-ot-change&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The Incidents Fixed by Change related list was added to the OT change request record in the Industrial Workspace. You can use this related list to create an OT incident or link an existing OT incident that has been fixed by the OT change request. [Incidents Caused by Change related list](https://www.servicenow.com/docs/access?context=create-ot-incident-from-ot-change&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The Incidents Caused by Change related list was added to the OT change request record in the Industrial Workspace. You can use this related list to create an OT incident or link an existing OT incident that is needed because of the OT change request. |
| Operational Technology Manager | [OT device related items and related lists](https://www.servicenow.com/docs/access?context=ot-assets-related-links-and-lists&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The Key Value \[cmdb_key_value\], Software Instance \[cmdb_software_instance\], and Firmware Install \[cmdb_firmware_install\] related lists were added to the OT view on IT and OT classes to view the following information: * Information related to the OT device populated through the integrations and captured as Key Value pairs. * Software installed on the OT device if Software Asset Management isn't available. * Firmware associated with the OT device. {#rn-summary-changes__ul_nt3_fq3_xfc} You can view these related lists on the ServiceNow AI Platform® and in the Industrial Workspace Admin. [OT Excel SGC - Import Task list module in the Industrial Workspace](https://www.servicenow.com/docs/access?context=create-import-task-excel-sgc&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The OT Excel SGC - Import Task list module has been added to the Industrial Workspace list view. From the available lists, you can access the import task functionality for the Service Graph Connector for Microsoft Excel. [OT Excel SGC - Remediation Task list module in the Industrial Workspace](https://www.servicenow.com/docs/access?context=create-remediation-task-for-validation-errors&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The OT Excel SGC - Remediation Task list module has been added to the Industrial Workspace list view. From the available lists, you can access the remediation task records created from an import task. [View and edit device to device connections](https://www.servicenow.com/docs/access?context=view-device-to-device-connections&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The Device to Device Connections list has been added to the OT Network menu available in the Industrial Workspace List view. You can view the device connections in detail using this list. Also, the Device to Device Connections related list was added to the Related Records tab on the OT device record in the ServiceNow AI Platform. [Is Virtual field for OT devices](https://www.servicenow.com/docs/access?context=ot-assets-form&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : Identify whether an OT device is virtual through the Is Virtual field added to the OT device form in the Industrial Workspace. [OT Subnet Mappings related list](https://www.servicenow.com/docs/access?context=ot-assets-related-links-and-lists&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The OT Subnets related list has been renamed OT Subnet Mappings in both the Industrial Workspace and the ServiceNow AI Platform when viewing an OT device record. [Manufacturer and Model Number fields](https://www.servicenow.com/docs/access?context=ot-assets-form&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The Manufacturer and Model Number fields have been removed from the OT device list and form views on both the ServiceNow AI Platform® and in the Industrial Workspace. [Request chart in the OT Action-Oriented Landing Page](https://www.servicenow.com/docs/access?context=oper-tech-task-oriented-landing-page&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : A chart for OT requests was added to the OT Action-Oriented Landing Page so you can track your requests in the Industrial Workspace. [Sort items field in the OT Action-Oriented Landing Page](https://www.servicenow.com/docs/access?context=oper-tech-task-oriented-landing-page&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The Sort items field was added to the OT Action-Oriented Landing Page under the Important Actions section. [Mapped Equipment Model Entity column](https://www.servicenow.com/docs/access?context=view-all-mapped-ot-devices&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The Mapped Equipment Model Entity column was added to the Industrial Workspace and ServiceNow AI Platform list views for OT devices. Use this column to identify the equipment model entity an OT device is mapped to. [Dashboard Library icon](https://www.servicenow.com/docs/access?context=exploring-industrial-workspace&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The Dashboard Library icon (![Dashboard Library icon]()) was added to the Industrial Workspace and contains the available dashboards for Operational Technology, including the Operational Technology Visibility dashboard. [Site filter on the Operational Technology Visibility dashboard](https://www.servicenow.com/docs/access?context=ot-devices-dashboard-filters-vr&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : A site filter was added to the Operational Technology Visibility in the Industrial Workspace so you can filter the displayed data by a chosen site. [OT device related items and related lists](https://www.servicenow.com/docs/access?context=ot-assets-related-links-and-lists&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The Key Value \[cmdb_key_value\], Software Instance \[cmdb_software_instance\], and Firmware Install \[cmdb_firmware_install\] related lists were added to the OT view on IT and OT classes to view the following information: * Information related to the OT device populated through the integrations and captured as Key Value pairs. * Software installed on the OT device if Software Asset Management isn't available. * Firmware associated with the OT device. {#rn-summary-changes__ul_nt3_fq3_cys} You can view these related lists on the ServiceNow AI Platform® and in the Industrial Workspace Admin. [OT Excel SGC - Import Task list module in the Industrial Workspace](https://www.servicenow.com/docs/access?context=create-import-task-excel-sgc&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The OT Excel SGC - Import Task list module has been added to the Industrial Workspace list view. From the available lists, you can access the import task functionality for the Service Graph Connector for Microsoft Excel. [OT Excel SGC - Remediation Task list module in the Industrial Workspace](https://www.servicenow.com/docs/access?context=create-remediation-task-for-validation-errors&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The OT Excel SGC - Remediation Task list module has been added to the Industrial Workspace list view. From the available lists, you can access the remediation task records created from an import task. [View and edit device to device connections](https://www.servicenow.com/docs/access?context=view-device-to-device-connections&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The Device to Device Connections list has been added to the OT Network menu available in the Industrial Workspace List view. You can view the device connections in detail using this list. Also, the Device to Device Connections related list was added to the Related Records tab on the OT device record in the ServiceNow AI Platform. [Is Virtual field for OT devices](https://www.servicenow.com/docs/access?context=ot-assets-form&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : Identify whether an OT device is virtual through the Is Virtual field added to the OT device form in the Industrial Workspace. [OT Subnet Mappings related list](https://www.servicenow.com/docs/access?context=ot-assets-related-links-and-lists&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The OT Subnets related list has been renamed OT Subnet Mappings in both the Industrial Workspace and the ServiceNow AI Platform when viewing an OT device record. [Manufacturer and Model Number fields](https://www.servicenow.com/docs/access?context=ot-assets-form&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The Manufacturer and Model Number fields have been removed from the OT device list and form views on both the ServiceNow AI Platform® and in the Industrial Workspace. [OT Devices tab data](https://www.servicenow.com/docs/access?context=ot-manager-dashboard&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The following data available in the OT Devices tab of the OT Manager dashboard has been moved to the Operational Technology Visibility dashboard. * New OT devices discovered * Inactive OT devices * OT Devices overview * Total CMDB OT devices * Unclassed OT devices * Unassigned OT devices * Unmapped OT devices {#rn-summary-changes__ul_qxw_qmf_rdc} * OT devices by category * Supervisory systems * Control systems * Field devices * Computers and servers * Network Gear * Industrial IoT {#rn-summary-changes__ul_uqt_xmf_rdc} * OT devices by Purdue level * OT devices by type (Top Level) * OT devices by manufacturer (Top Level) * OT devices by criticality {#rn-summary-changes__ul_fjb_wlf_rdc} |
| Operational Technology Vulnerability Response | [OT Vulnerable items list in the Industrial Workspace](https://www.servicenow.com/docs/access?context=view-solutions-of-vit-in-industrial-workspace&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The All list was added in the OT Vulnerable Items list available in the Industrial Workspace list menu. You can use this section to view all the vulnerable items (VITs) that have been created for your OT environment. You must be assigned the user_role to view all VITs. [OT Remediation Tasks list in the Industrial Workspace](https://www.servicenow.com/docs/access?context=view-otvr-remediation-tasks-in-industrial-workspace&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The All list was added in the OT Remediation Tasks list available in the Industrial Workspace list menu. You can use this section to view all the remediation tasks that have been created for the respective VITs in your OT environment. You must be assigned the user_role to view the remediation tasks. [OT Vulnerability Exception Approvals list in the Industrial Workspace](https://www.servicenow.com/docs/access?context=view-vulnerability-exceptions-in-industrial-workspace&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : Use this menu to view all vulnerability exceptions that have been approved by you or assigned to you. This menu enables you to view any change of state for approvals and details of requested approvals for a given exception triggered from the Industrial Workspace. [Dashboard Library icon](https://www.servicenow.com/docs/access?context=ot-manager-dashboard&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The Dashboard Library icon (![dashboard library icon]()) was added to the Industrial Workspace and contains the available dashboards for Operational Technology, including the OTVR (PA) dashboard. [Site filter on the OTVR (PA) dashboard and the Risk Management dashboard](https://www.servicenow.com/docs/access?context=operational-technology-vulnerability-response-dashboard&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : A site filter was added to both the OTVR (PA) dashboard and the OT Risk Management dashboard in the Industrial Workspace so you can filter the displayed data by a chosen site. [Vulnerability Solutions section in the List menu of Industrial Workspace](https://www.servicenow.com/docs/access?context=view-solutions-of-vit-in-industrial-workspace&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : A new Vulnerability Solutions section was added in the List menu (![List icon]()) of the Industrial Workspace. In the Solutions section, you can view the solutions for the enlisted VITs. [Overview tab for a vulnerable item](https://www.servicenow.com/docs/access?context=ot-vulnerable-item-fields&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The Overview tab in a VIT provides important information about the VIT, such as State, Risk Rating, Risk Score, Associated Vulnerability, and more. [OT Vulnerabilities tab data](https://www.servicenow.com/docs/access?context=operational-technology-vulnerability-response-dashboard&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The following data that was available in the OT Vulnerabilities tab of the OT Manager dashboard has been moved to the OTVR (PA) dashboard: * Total OT Vulnerable Items * New OT Vulnerable Items * OT Unassigned Vulnerable Items * OT Vulnerable Items by State * OT Vulnerable Items by Risk Rating {#rn-summary-changes__d2311e296} |
| Opportunity Marketplace | [A new step is added in the task for creating opportunities.](https://www.servicenow.com/docs/access?context=egd-create-other-opportunities&version=yokohama&pubname=yokohama-employee-service-management&ft:locale=en-US) : You must select how you want to get started with creating an opportunity. * Create using an existing project enables opportunity owners with the correct assigned roles to import details from Project Workspace projects. Note: This option is only visible when both Project Workspace and Opportunity Marketplace are installed. * Create on your own enables Opportunity Marketplace opportunity owners to create opportunities of type Gig, Project, or Volunteer. [Enable selection of multiple user goups to manage which groups of users can view an opportunity.](https://www.servicenow.com/docs/access?context=egd-create-other-opportunities&version=yokohama&pubname=yokohama-employee-service-management&ft:locale=en-US) : Select multiple user criteria groups from the Who can view this opportunity? field on the Opportunity details widget page. [Import Project Workspace project information to create an opportunity](https://www.servicenow.com/docs/access?context=egd-create-other-opportunities&version=yokohama&pubname=yokohama-employee-service-management&ft:locale=en-US){#rn-summary-changes__opportunity-marketplace-rn-rn-workspace} : Opportunity Marketplace opportunity owners can create Project Opportunity types by importing projects from the ServiceNow® Project Workspace. Note: Creating a project opportunity type by importing a project file is only available to users with both ServiceNow Project Workspace and Opportunity Marketplace installed. An opportunity owner must have the following roles assigned to them to create a Project type opportunity by importing project details from Project Workspace. reource_user [Resource management process](https://www.servicenow.com/docs/access?context=r_ResourceManagementProcess&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US) : If you're assigned the resource_user role, you can be a resource requester. [sn_ppm_read](https://www.servicenow.com/docs/access?context=business-stakeholder-role-ppm&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US) : The sn_ppm_read role provides read-only access to the Portfolio, Program, and Timecard dashboards along with the Resources report to the assigned users. [Select multiple user criteria groups](https://www.servicenow.com/docs/access?context=egd-create-other-opportunities&version=yokohama&pubname=yokohama-employee-service-management&ft:locale=en-US) : Opportunity owners can select multiple user criteria groups from the Who can views this opportunity? field on the Opportunity details page. For more information, see [Create opportunities in Opportunity Marketplace](https://www.servicenow.com/docs/access?context=egd-create-other-opportunities&version=yokohama&pubname=yokohama-employee-service-management&ft:locale=en-US). |
| Platform Analytics experience | [Migration center flow UX improved](https://www.servicenow.com/docs/access?context=data-migration-perform&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : * A confirmation modal is displayed when Start moving or Activate is selected. * Bulk migration can be retriggered after source artifacts are changed. * The creation of new analytics artifacts can be blocked when bulk migration starts. {#rn-summary-changes__ul_eqx_nvh_tcc} Percent information added to tooltips : Tooltips in geomap, vertical and horizontal bar, heatmap, and bubble visualizations now include percentages when applicable. [Migrate more features to Platform Analytics from the Core UI](https://www.servicenow.com/docs/access?context=data-migration&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : Migration scripts are improved to support more features. All migration script improvements are applied automatically on upgrade to content that was previously migrated in compatibility mode. * Data table configurations are migrated from the Core UI to Platform Analytics data visualizations. * Dashboard groups are migrated to dashboard categories. * Pareto charts are migrated. * List component border changes are migrated. * Follow/unfollow filter settings are migrated for Lists. {#rn-summary-changes__ul_ksw_y5h_tcc} [Use more Core UI features in Platform Analytics](https://www.servicenow.com/docs/access?context=data-mig-unmigrated-content&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : Several data visualizations have been enhanced to match the capacities in Core UI reports and widgets. The migration script supports these enhancements. Each of these enhancements has an entry in the release notes with links to the product documentation. * Use the new Box plot data visualization. * Configure Follow filters per metric on bar or time series visualizations with multiple metrics. * Sort values by name, report range, and element order on time series visualizations of table data. * Choose an aggregate or separate view of breakdown elements on time series visualizations of indicator data. * Select dates from business calendars on time series visualizations. {#rn-summary-changes__ul_f53_hdk_fdc} [Trend by Business calendars in time series data visualizations](https://www.servicenow.com/docs/access?context=config-dv-time-series-table-data&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : Business calendars are a Trend by option for table data sources on time series visualizations. (Core UI feature gap) [Use a Fiscal calendar in date filters](https://www.servicenow.com/docs/access?context=create-date-filter-workspace&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : If your instance has Fiscal calendars installed, you can choose relative data ranges from that calendar. Export [dashboards](https://www.servicenow.com/docs/access?context=export-pae-dashboard-ppt&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) and [data visualizations](https://www.servicenow.com/docs/access?context=export-visualization-vd&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) to PDF and PPT : Export dashboards and data visualizations to PDF or Microsoft PowerPoint files at will or in [scheduled emails](https://www.servicenow.com/docs/access?context=schedule-export-dboards-data-viz&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US). [Show breakdown elements separately on time series visualizations of indicators](https://www.servicenow.com/docs/access?context=config-dv-time-series-ind-data&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : Show multiple elements in the chart separately rather than as an aggregate value by turning on the Show filter as separate series option. (Core UI feature gap) [Lock editing on dashboards](https://www.servicenow.com/docs/access?context=edit-db-in-ac&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : Ensure that only one person can have a dashboard open for editing at one time through the edit lock on dashboards. If you are locked out of editing a dashboard, you see who the current editor is. [Access indicator record or scoresheet from KPI Details](https://www.servicenow.com/docs/access?context=access-indicator-record-scoresheet&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : Navigate either to the record of the indicator you are exploring or its scoresheet through KPI Details. Appropriate roles are required. [Export records that underlie an indicator from KPI Details](https://www.servicenow.com/docs/access?context=show-compare-edit-records&version=yokohama&pubname=yokohama-now-intelligence§ion=kpid-record-list-actions&ft:locale=en-US) : With Show records activated in KPI Details, you can export the list of records in one of several formats, either as a local download or as an email attachment. [Hide axes for bar visualizations](https://www.servicenow.com/docs/access?context=create-dv-bar-ac&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : Control the display of axes on bar charts. On horizontal bar charts, you can hide the y-axis. On vertical bar charts, you can hide the x-axis. [Cache indicator scorecard data](https://www.servicenow.com/docs/access?context=data-caching-pa&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : Indicator scorecards now support data caching. [Group by elements more efficiently in data visualizations](https://www.servicenow.com/docs/access?context=select-group-runtime&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : Specify the maximum number of elements in a Group By you want to retrieve through the Max number of groups option. Previously, all elements from the database were retrieved and then sorted. [Prefetch dashboard layout](https://www.servicenow.com/docs/access?context=configure-dashboard-data-broker&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : If you have a dashboard component on a page in your own workspace, improve performance by using a preset to configure a data broker that pre-fetches static JavaScript, such as layout. [Call multiple visualizations together](https://www.servicenow.com/docs/access?context=local-data-instance-multi-viz&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : For a technical dashboard, if you have multiple data visualizations of the same type calling the same data source, configure a data resource to make a single call for all of them. [Improvements to time-series visualizations](https://www.servicenow.com/docs/access?context=config-dv-time-series-table-data&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : * Simplify identifying specific values on line, spline, area, or step charts through the Show markers option, which displays a symbol at each data point. * Sort by name, report range, group bucket, and element order. (Core UI feature gap) {#rn-summary-changes__ul_jmg_2xs_bdc} [Improvements for visualizations that show multiple metrics](https://www.servicenow.com/docs/access?context=chart-options-multi-metrics&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : * In time series visualizations, provide viewers an alternative group by, where the viewer chooses the group-by value at runtime, for up to 3 data sources. (Core UI feature gap) * Set whether individual metrics follow filter components on the page or dashboard in both bar and time series visualizations. (Core UI feature gap) {#rn-summary-changes__ul_i1b_cv3_fdc} |
| Playbooks in Workflow Studio | Trigger label updated : The trigger is now labeled "Start" in Workflow Studio. Change triggers in any playbook : Edit triggers when you duplicate a playbook, in a variant, etc. |
| Policy and Compliance Management | [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). |
| Portfolio Planning | [Capacity Planning tab name change](https://www.servicenow.com/docs/access?context=using-cap-plan-pp&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US) : The name of the Capacity Planning tab in the planning view is changed to Capacity. [Financials UI changes](https://www.servicenow.com/docs/access?context=using-portfolio-financials-ppw&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US) : * New Financials tab in the Planning page. * The name of the ETC field is changed to Remaining Estimates. * The name of the EAC field is changed to Forecast. * The name of the Actuals to date field is changed to Actuals. * New Financials view in scenario planning. * New financial widgets in the compare scenario page. {#rn-summary-changes__ul_a3y_tzq_tdc} |
| Privacy Management | [Tagging of information object tags](https://www.servicenow.com/docs/access?context=tag-io-with-pi&version=yokohama&pubname=yokohama-governance-risk-compliance&ft:locale=en-US) : Use the Data classification field to tag information objects instead of using the tag icon. [Initiating privacy assessment](https://www.servicenow.com/docs/access?context=send-privacy-asmt-from-pa&version=yokohama&pubname=yokohama-governance-risk-compliance&ft:locale=en-US) : When you initiate a privacy assessment from either an entity or a processing activity, you're no longer redirected to the Create new privacy assessment form, instead, a new pop-up window appears where you can specify all the assessment details. |
| Process Mining | [Usability improvements introduced](https://www.servicenow.com/docs/access?context=explore-process-mining&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : A few improvements are introduced for ease of usability. * View the improvement opportunities on the Summary and Insights page as a card view or list view. * Rename the scheduled tasks that help to identify and view a specific result. {#rn-summary-changes__ul_jln_rtk_bdc} |
| Product Catalog Management and Pricing Management | [Multiple configurations](https://www.servicenow.com/docs/access?context=multiple-child-offering-configurations&version=yokohama&pubname=yokohama-order-management&ft:locale=en-US) : Define child product offerings that can have multiple configurations in configurable opportunities, quotes, and orders. Agents can clone or split a child product offering to create multiple product offering instances. Each quantity for an offering instance can then have its own unique configuration. [Transient product offerings](https://www.servicenow.com/docs/access?context=configuring-transient-products&version=yokohama&pubname=yokohama-order-management&ft:locale=en-US) : Define single-use product offerings, such as installation services or consulting services, as transient products that are fulfilled in ServiceNow Order Management. After orders for transient products are fulfilled, sold product or product inventory records are created but have an Inactive status. Move, Add, Change, Delete (MACD) actions aren't supported for the sold product or product inventory records of transient products. [Needs analysis in CRM Workspace](https://www.servicenow.com/docs/access?context=configuring-needs-analysis&version=yokohama&pubname=yokohama-order-management&ft:locale=en-US) : Starting with the Yokohama release, the options for configuring a needs analysis are available in the List view of the CRM Workspace and can be found by navigating to Needs. [Volume-based pricing](https://www.servicenow.com/docs/access?context=configure-volume-pricing&version=yokohama&pubname=yokohama-order-management&ft:locale=en-US) : Set volume discounts for product offerings based on the product quantity. |
| Project Portfolio Management | [Demand Management UI changes](https://www.servicenow.com/docs/access?context=identify-similar-demands&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US) : * The Identify similar demands button has been added to the demand form to identify and view any similar demands with the identify similar demands skill. * The Similar Demands related list has been added, which displays the list of similar demand records identified by Now Assist. {#rn-summary-changes__ul_nw2_mp1_fhc} |
| Project Workspace | [Skill name updates](https://www.servicenow.com/docs/access?context=project-workspace-landing-page&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US) : Renamed the Project Gen AI Docs skill to the Project doc summarization skill in Project Workspace. [Resource assignment UI enhancements](https://www.servicenow.com/docs/access?context=resource-assignments-pw&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US) : Added the Extend option and the Extend Assignment modal to request a resource assignment extension. * Updated the create resource assignment form to include these fields: * The Name field to captures a unique or descriptive name for the resource assignment. * The Ready for review list to confirm if a resource assignment is ready for the allocation review. * The Notes field to add additional context when creating a resource assignment. {#rn-summary-changes__ul_zjb_c3p_y2c} * Time span fields are changed to weekly and monthly. * Included the following information in the heatmap modal: * The Utilization column to display the total effort across approved or pending tasks. * The Resource status column to display the approved or pending assignments. * The Remaining capacity column to indicate available or exceeded effort limits. {#rn-summary-changes__ul_fjc_ynq_y2c} {#rn-summary-changes__ul_bq2_bgp_y2c} [Financials UI changes](https://www.servicenow.com/docs/access?context=using-financials-spw&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US) : * New Financials tab in the planning view. * The name of the ETC field is changed to Remaining Estimates. * The name of the EAC field is changed to Forecast. * The name of the Actuals to date is changed to Actuals. {#rn-summary-changes__d2335e164} [Heatmap enhancements](https://www.servicenow.com/docs/access?context=use-resource-mgmt-prj-wksp&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US){#rn-summary-changes__resource-management-workspace-rn_0-rn-workspace} : The resource allocation heatmap displays the resource status, capacity, and utilization, enabling efficient planning and allocation based on availability and workload. |
| Public Sector Digital Services | [Constituent Service Dashboard Migration to Platform Analytics](https://www.servicenow.com/docs/access?context=constituent-services-dashboard&version=yokohama&pubname=yokohama-government-industry&ft:locale=en-US) : The Constituent Service Dashboard has been migrated to Next Experience Platform Analytics. Next Experience is a ServiceNow AI Platform® feature that is active by default when the user loads or upgrades to the Yokohama release. The dashboard migration to Next Experience enables you to visualize historical and real-time process statistics in role-based dashboards, which enable individual stakeholders to make informed decisions. The new dashboard can be accessed by navigating to AllPlatform AnalyticsLibraryDashboards. |
| RPA Hub | [Build with Now Assist wizard](https://www.servicenow.com/docs/access?context=create-automation-now-assist&version=yokohama&pubname=yokohama-integrate-applications&ft:locale=en-US) : In the RPA Desktop Design Studio, create an automation with Now Assist by selecting the Create automation button and follow the next set of steps in the Build with Now Assist wizard. [Create an activity with Now Assist](https://www.servicenow.com/docs/access?context=create-activity-now-assist&version=yokohama&pubname=yokohama-integrate-applications&ft:locale=en-US) : In the RPA Desktop Design Studio, create an activity using Now Assist by selecting and holding (or right-clicking) Activities in the Project Explorer. Then, select the New activity using Now Assist option. [Build an automation with Now Assist](https://www.servicenow.com/docs/access?context=build-automation-now-assist&version=yokohama&pubname=yokohama-integrate-applications&ft:locale=en-US) : In the RPA Desktop Design Studio, extend the automation logic using the Build automation with Now Assist option. On the design canvas, select a component and hover over the AI icon (![]()). Select the AI icon (![]()) to open the Build automation with Now Assist window, you can describe the automation logic based on the selected components. [High density robots](https://www.servicenow.com/docs/access?context=high-density-robots-rpa-hub&version=yokohama&pubname=yokohama-integrate-applications&ft:locale=en-US) : In the Robot form of RPA Hub, the High Density Robot and Screen Resolution fields are added to support the high-density robot feature. [Enhanced user experience on the Sample Automation home page](https://www.servicenow.com/docs/access?context=rpa-studio-ui&version=yokohama&pubname=yokohama-integrate-applications&ft:locale=en-US) : The following options have been added to enhance user experience on the Sample Automation home page in RPA Desktop Design Studio: * Pagination: Scroll through different pages containing sample automations using the pagination option. * Search bar: Filter and display only the automations that contain the search keyword in their title or description using the search bar option. The search is case-insensitive and dynamically updates the list of displayed automations based on the search query. {#rn-summary-changes__ul_uf5_r33_rdc} [Changed fields for the Unattended Robot application](https://www.servicenow.com/docs/access?context=set-up-rpa-runtime&version=yokohama&pubname=yokohama-integrate-applications&ft:locale=en-US){#rn-summary-changes__rpa-rn-changed-fields-unattended} : In the Unattended Robot dialog box, the RPA Hub field name has been changed to Instance URL. [Embedded Task Automation in RPA Hub](https://www.servicenow.com/docs/access?context=embedded-task-auto-rpa&version=yokohama&pubname=yokohama-integrate-applications&ft:locale=en-US) : Trigger attended bot processes (attended automations) from the ServiceNow forms in the Workspace experience apart from initiating them from a classic UI or the Attended Robot application. [Microsoft Software Installer (MSI) compatibility](https://www.servicenow.com/docs/access?context=download-installer-rpa&version=yokohama&pubname=yokohama-integrate-applications&ft:locale=en-US) : Older MSIs that are related to Attended Robot and RPA Desktop Design Studio from the RPA Hub store release versions 7.0.3 and 9.0.0 are compatible and can be used with the current store release version (12.0.X) of RPA Hub. For Unattended Robot, the latest MSI must be installed, as it is not backward compatible.However, there are some limitations: * Any new automation components available in the latest version aren't available in the older versions. For example, the SSH connector in version 12.0 doesn't work in older versions. * Components of the same name with different parameters aren't backward compatible. {#rn-summary-changes__ul_uj3_5fr_zbc}If robot machines use older MSIs than the current instance version, they won't have the new features from later versions. For example, features released after version 10.0 won't work in version 10.0 MSIs. Only features from version 10.0 are available in that version. [TerminateByName component behavior change](https://www.servicenow.com/docs/access?context=use-sysprocess-terminatename&version=yokohama&pubname=yokohama-integrate-applications&ft:locale=en-US) : The TerminateByName component stops processes or applications only within the current user session. |
| Recommended Actions for Operational Technology Service Management (OTSM) | [Recommended actions button](https://www.servicenow.com/docs/access?context=use-recommended-actions-ot-incidents&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The Recommended actions ![]() button was added to the Industrial Workspace to access the Recommended Actions panel for an OT incident. |
| Regulatory Change Management | [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Changes on the action task form](https://www.servicenow.com/docs/access?context=create-action-task-using-ws&version=yokohama&pubname=yokohama-governance-risk-compliance&ft:locale=en-US) : The Category: Compliance section and the Category: Risk section on an action task form have been removed. They're replaced by the Impacted area table field and the Impacted area field. [Assess impact](https://www.servicenow.com/docs/access?context=assess-impact-of-reg-change-using-ws&version=yokohama&pubname=yokohama-governance-risk-compliance&ft:locale=en-US) : The Initiate Impact Assessment button is now called the Assess impact button. [Overview page of regulatory alerts](https://www.servicenow.com/docs/access?context=list-view-of-reg-alerts&version=yokohama&pubname=yokohama-governance-risk-compliance&ft:locale=en-US) : The Overview page for regulatory alerts includes a drop-down menu that enables you to track the progress of a regulatory assessment. Additionally, you can view the counts of completed, open, and overdue regulatory assessments. [Home page updates for Regulatory Change Management](https://www.servicenow.com/docs/access?context=rcm-workspace-for-managers&version=yokohama&pubname=yokohama-governance-risk-compliance&ft:locale=en-US) : On the Regulatory Change Management home page, within the Tracking section, a new drop-down menu has the Regulatory Assessments or Risk Assessments options. With these options, regulatory change managers can see the number of open and overdue assessments to help them efficiently monitor the status of their assessments. [Regulatory assessments in the Tasks pane](https://www.servicenow.com/docs/access?context=regulatory-assessment-in-rcm&version=yokohama&pubname=yokohama-governance-risk-compliance&ft:locale=en-US) : The Tasks pane in the Compliance Workspace now displays all the Regulatory assessments. |
| Request Management | [Sorting configuration items in requested item forms](https://www.servicenow.com/docs/access?context=create-request-workspace&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US){#rn-summary-changes__request-management-rn-rn-workspace} : The list of configuration items (CIs) displayed for the Configuration item field in the Requested item form is now displayed and sorted based on the CI names in alphabetical order instead of sorting by CI class and then presenting the CI names in alphabetical order within a class. This change means you can determine whether a particular CI is available more quickly. |
| Resource Management Workspace | [New navigation menu](https://www.servicenow.com/docs/access?context=using-rmw&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US#section_v4k_rtg_1fc) : * New Reporting dashboard landing page in Resource Management Workspace to view and access the resource allocation details. * Interactive widgets in Reporting dashboard to access the custom resource boards. {#rn-summary-changes__ul_bjy_ndc_dfc} [Using Resource Management Workspace](https://www.servicenow.com/docs/access?context=using-rmw&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US#section_fmx_yrl_b1c) : Added the following details in the resource allocation heatmap view. * The Resource status column to view Approved and Pending assignments. * The Remaining capacity column to view the remaining or over-allocated efforts. * The Utilization column to view the total efforts of approved and pending tasks. {#rn-summary-changes__ul_bcv_t2g_tdc} [Create resource assignments in Resource Management Workspace](https://www.servicenow.com/docs/access?context=create-ra-rmw&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US) : * Added the following fields to create resource assignment form. * The Name field provides a custom or identifiable name for resource assignment. * The Ready for review list to confirm if a resource assignment is ready for a Resource manager's review for allocation. * The Notes field to add any additional notes while creating a resource assignment. {#rn-summary-changes__ul_iyc_ysp_tdc} * Added the following fields in the row context menu of resource assignments in the top tray. * The Open Resource Assignment field to view and edit a specific assigned assignment. * The Open Parent Resource Assignment field to view and edit the parent assignment. * The Extend menu item and Extend Assignment modal to request an extension to a resource assignment. {#rn-summary-changes__ul_exf_ctp_tdc} {#rn-summary-changes__ul_a4l_xsp_tdc} [New resource heatmap view](https://www.servicenow.com/docs/access?context=using-rmw&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US#section_fmx_yrl_b1c){#rn-summary-changes__d2349e199} : The resource allocation heatmap view provides more relevant information such as resource status, remaining capacity, and utilization of resources which helps resource managers to plan efficiently and allocate the resources based on their availability, bandwidth, and work requirements. |
| Security Incident Response | [Start a Sidebar chat in Security Incident Response](https://www.servicenow.com/docs/access?context=initiate-chat-sidebar-sir&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US) : The Discuss option has been renamed Start Chat and moved under the Collaborate option. [Security Operations](https://www.servicenow.com/docs/access?context=security-operations-landing-page&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US) : {#rn-summary-changes__table_h5p_xyl_sdc__entry__2} | Integration name | Integration changes | |-|-| | Microsoft Teams Chat | Simplified the setup of Microsoft Teams Chat integration with Major Security Incident Management Workspace. For more information, see [Integrate Major Security Incident Management with Microsoft SharePoint](https://www.servicenow.com/docs/access?context=integrate-msim-sharepoint&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US). | | Microsoft SharePoint | Simplified the setup of Microsoft SharePoint integration with Major Security Incident Management Workspace. For more information, see [Integrate Major Security Incident Management with Microsoft Teams](https://www.servicenow.com/docs/access?context=integrate-teams-msim&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US). | | Security Incident Response Integrations | Workflow was migrated to Workflow Studio. For more information, see the following: * [Get Log Data Flow](https://www.servicenow.com/docs/access?context=get-threat-log-data&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US) * [Get WildFire Data Enrichment Flow](https://www.servicenow.com/docs/access?context=enrich-wildfire-data&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US) * [Get started with the Microsoft Exchange On-Premises integration](https://www.servicenow.com/docs/access?context=activate-configure-ms-exch-on-prem-integ&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US) * [Microsoft Exchange - Perform Email Search and Deletion flow](https://www.servicenow.com/docs/access?context=ms-exch-perform-email-search-deletion-wf&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US) * [Get AutoFocus Session Info Enrichment Flow](https://www.servicenow.com/docs/access?context=search-for-malicious-content&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US) {#rn-summary-changes__ul_lkt_2rh_c2c} | | Security Incident Response Orchestration | Workflow was migrated to Workflow Studio in the section [Run procdump flow](https://www.servicenow.com/docs/access?context=invoke_procdump&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US). | | Security Operations common functionality | Workflow was migrated to Workflow Studio. For more information, see the following: * [Integration capabilities](https://www.servicenow.com/docs/access?context=integration-capabilities&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US) * [Security Operations Integration- Block Request capability](https://www.servicenow.com/docs/access?context=block-request-capability&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US) * [Security Operations Integration- Email Search and Delete capability](https://www.servicenow.com/docs/access?context=email-search-capability&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US) * [Security Operations Integration- Enrich CI capability](https://www.servicenow.com/docs/access?context=enrich-ci-capability&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US) * [Security Operations Integration- Enrich Observable capability](https://www.servicenow.com/docs/access?context=enrich-observable-capability&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US) * [Security Operations Integration- Get Network Statistics capability](https://www.servicenow.com/docs/access?context=get-network-statistics-capability&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US) * [Security Operations Integration- Get Running Processes capability](https://www.servicenow.com/docs/access?context=get-running-processes-capability&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US) * [Security Operations Integration- Isolate Host capability](https://www.servicenow.com/docs/access?context=isolate-host-capability&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US) * [Security Operations Integration- Publish to Watchlist capability](https://www.servicenow.com/docs/access?context=pubish-to-watchlist-capability&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US) * [Security Operations Integration- Sightings Search capability](https://www.servicenow.com/docs/access?context=sightings-search-capability&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US) * [Security Operations Integration - Threat Lookup capability](https://www.servicenow.com/docs/access?context=sec-ops-threat-lookups-capability&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US) * [Change the order of flow execution](https://www.servicenow.com/docs/access?context=change-wf-execution-order&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US) {#rn-summary-changes__ul_eql_j5h_c2c} | [ ] {#rn-summary-changes__table_h5p_xyl_sdc} [Other additional Security Incident Response setup tasks](https://www.servicenow.com/docs/access?context=t_ConfigureSIM&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US) : View security incidents with read access and update security incidents with write access without any defined security role. |
| Self-service and omnichannel engagement for CSM | [Using the email interaction page](https://www.servicenow.com/docs/access?context=using-email-interaction-page&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US) : The following UI elements have been added to the Email Interaction page: * A Contact card to simplify the process of adding and viewing customer information. * A Customer History tab that displays the details of previous conversations between the customer and the agent. {#rn-summary-changes__ul_hdz_xdd_s2c} [Using the email interaction page](https://www.servicenow.com/docs/access?context=using-email-interaction-page&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US){#rn-summary-changes__customer-self-service-omnichannel-engagement-rn-rn-workspace} : Manage and view customer-related information and past conversations while interacting with customers via email. [Now Assist conversational experience in self-service portals](https://www.servicenow.com/docs/access?context=nass-portal&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US) : Receive comprehensive and detailed answers with intelligent search and conversational experiences using Now Assist in Virtual Agent. The search results are synthesized from Knowledge Base articles, Virtual Agent articles, and catalog items with links to the sources. The agent retains conversation context across multi-turn questions, promoting continuity and relevance in responses. |
| Service Catalog | [Accessibility checker in the toolbar](https://www.servicenow.com/docs/access?context=t_DefineACatalogItem&version=yokohama&pubname=yokohama-servicenow-platform§ion=service-catalog-accessibility-checker&ft:locale=en-US) : Identify and resolve accessibility related issues during catalog item generation through a new accessibility checker button in the TinyMCE toolbar in Service Catalog. |
| Service Observability | [New Overview tab in the SOW](https://www.servicenow.com/docs/access?context=view-overall-service-health&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US) : After services are activated for the Overview tab in Service Observability, the Service Details page in SOW now shows reliability metrics from Service Reliability Management (SRM) as well as metrics from Service Observability. [New Observability tab in the SOW](https://www.servicenow.com/docs/access?context=view-service-health-metrics&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US) : The Observability tab on the Service Details page in SOW shows related metrics from connected APM vendors. [Admin Center support for activating services and data sources](https://www.servicenow.com/docs/access?context=activate-teams-and-services&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US) : You can activate services to use in Service Observability and then connect and map APM data sources to those services. Starting in version 1.6.4, you no longer need to activate services. Any of the supported service types in the CMDB can be used Starting in version 1.6.4, the Service Observability admin role can configure Service Observability in the Admin Center without involving an administrator. |
| Service Operations Workspace for ITSM | [GenAI email templates for communication](https://www.servicenow.com/docs/access?context=compose-communication-mim-sow&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : Use the GenAI capabilities for composing email with GenAI email templates in all major incident communications. The GenAI email templates are visible in a separate section when the email templates field is selected and the following conditions are met: * Any GenAI variable is available in the email templates. * ServiceNow Otto for ITSM is installed and activated. * GenAI skills are enabled. * User have the required roles to execute the GenAI skills. {#rn-summary-changes__ul_l3m_1r3_y2c} [Close resolved incident](https://www.servicenow.com/docs/access?context=close-resolved-incident-sow&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : Close an incident in Resolved state using the itil_admin user role. [Resize modals on the SRP and list pages](https://www.servicenow.com/docs/access?context=srp-service-operations-workspace&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : Ensure flexibility and efficiency by enabling users to resize the modals on the SOW SRP and list pages. This helps in adjusting screen space allocation, enabling multi-tasking, and optimizing content visibility for different tasks and screen sizes. [Incident record page changes](https://www.servicenow.com/docs/access?context=view-inc-record-info-contextual-sidepanel&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US){#rn-summary-changes__service-operations-workspace-itsm-rn-rn-workspace} : The Incident record page has the following changes: * The caller card is placed first on the Record information side panel for tier 1 agents. * The origin card itself is no longer clickable to reduce usability issues with the card and its clickable elements. {#rn-summary-changes__ul_v4n_ghp_qdc} [Reference field behavior changes in SOW](https://www.servicenow.com/docs/access?context=view-update-inc-overview-tab&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : Selecting any reference field in SOW now displays only the recent selection values instead of automatic searching and displaying the results of the field values available in the system. This change increases the overall performance of the reference fields. By default, this change is enabled. To revert this change, set the Reference search on click (ref_search_on_click) UX page property to set to true. [Viewing Assign to me option](https://www.servicenow.com/docs/access?context=users-sow-itsm&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : Users with the incident_read role can no longer view the Assign to me option for an incident record. Email component issues on SOW Incident : Email components are now accurately displayed for SOW Incident when the email is selected from the activity stream, stacked view, or email template is applied. Resetting filter conditions : Filter conditions are now reset when switched from one related list to another related list. Saving interaction record loads recent tasks : When a new interaction record is created and saved, the sidebar now loads record Information instead of recent Tasks. [Problem Management state transitions](https://www.servicenow.com/docs/access?context=understanding-state-mgmt-transitions&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : Sections that are configured to be expanded now automatically expand when you transition to a new state, without requiring a page reload. |
| Service Portal | [Use ECMAScript 2021 (ES12) JavaScript mode in server scripts for widgets](https://www.servicenow.com/docs/access?context=widget-dev-guide&version=yokohama&pubname=yokohama-platform-user-interface&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&version=yokohama&pubname=yokohama-api-reference&ft:locale=en-US). [Define roles for page route maps](https://www.servicenow.com/docs/access?context=reroute-page&version=yokohama&pubname=yokohama-platform-user-interface&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&version=yokohama&pubname=yokohama-platform-user-interface&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&version=yokohama&pubname=yokohama-platform-user-interface&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&version=yokohama&pubname=yokohama-platform-user-interface&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. |
| Service Reliability Management | [New banner for configuring SLIs](https://www.servicenow.com/docs/access?context=sr-create-slo-sli&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US) : Starting in version 6.3, when you set up an SLI, a new information banner shows how many configuration items are associated with your service. To set up an effective SLI for your system, select View CIs in service map to see how the service and configuration items relate. [Service import improvements](https://www.servicenow.com/docs/access?context=sr-add-service&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US) : Starting in version 6.3, the service import flow includes the following updates: * Services owned by others are selectable options in the UI. * Service suggestions appear in the search box, reducing the need to remember exact service names. {#rn-summary-changes__ul_cwr_z15_w2c} [Express List](https://www.servicenow.com/docs/access?context=express-list&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US) : The Express List icon (![Express List icon)]() is now in the navigation pane. [Integrations Launchpad](https://www.servicenow.com/docs/access?context=integrations-launchpad&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US) : The Integrations Launchpad icon (![Integrations Launchpad icon]()) is now in the navigation pane. Note: Starting in version 6.3, the custom Integrations Launchpad in SRM was replaced with the official Service Operations Workspace version. This change promotes consistency across applications and gives you immediate access to the latest SOW updates. |
| ServiceNow AI Lens | [Changes in the scanner window UI](https://www.servicenow.com/docs/access?context=create-record-sn-lens&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The UI of the scanner window has been changed. See the following image. When you open the scanner window, the toolbar is displayed outside of it. However, when you maximize the window, the toolbar moves inside. [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. |
| ServiceNow AI Platform core feature | [Updated Access Control Lists (ACLs) for Transaction tables and Session Management tables](https://www.servicenow.com/docs/access?context=exploring-access-control-list&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US) : The ACLs for a number of Transaction Management tables and Session Management tables have been updated to enhance security using a combination of Deny and Allow ACLs. All new ACLs have a security attribute. You must have the security attribute to add to the role list of an ACL. For more information, see [Configure an ACL rule](https://www.servicenow.com/docs/access?context=t_CreateAnACLRule&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US), [Deny-Unless ACL](https://www.servicenow.com/docs/access?context=acl-denial-behavior&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US), and . The updated Transaction Management tables include: * syslog * syslog_ajax * syslog_email * syslog_transaction * syslog_script {#rn-summary-changes__ul_vm4_s4z_4dc} The updated Session Management tables include: * sys_audit * sys_security_acl * sys_user_auth * sys_user_session {#rn-summary-changes__ul_u1h_x4z_4dc} [Configuring plugins for the TinyMCE HTML editor](https://www.servicenow.com/docs/access?context=configuring-the-html-plugins-for-tinymce&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : The Accessibility Checker (a11ychecker) plugin is now available in the TinyMCE HTML editor. The plugin identifies WCAG and Section 508 accessibility violations and provides an auto-repair feature where applicable. To configure the plugin, see [Change the TinyMCE HTML editor plugins](https://www.servicenow.com/docs/access?context=configuring-the-html-plugins-for-tinymce&version=yokohama&pubname=yokohama-platform-administration§ion=change-the-tinymce-html-editor-plugins&ft:locale=en-US). Additional configurations to the accessibility rules, like changing the WCAG level and HTML versions can also be done via TinyMCEconfigscript script. [Field types supported in a configurable workspace](https://www.servicenow.com/docs/access?context=r_FieldTypes&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : The following field types are now supported for use in a configurable workspace: * Documentation_field * Domain_path * HTML_Script * Long * Longint * multi_small * Order index * Radio {#rn-summary-changes__ul_hh5_pjz_4dc}For more information, see [Field types reference](https://www.servicenow.com/docs/access?context=r_FieldTypes&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US). [Specify the tables that a REST API access policy restricts](https://www.servicenow.com/docs/access?context=create-api-access-policy&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US) : Specify the tables that a Table REST API access policy applies to on the API Access Policy form. [Use ISO currency codes with the FX Currency field type](https://www.servicenow.com/docs/access?context=fx-currency&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Use three-digit ISO 4217 currency codes from the Numeric code field on the Currency \[fx_currency\] table with fields of the FX Currency field type. [Sorting according to the session language](https://www.servicenow.com/docs/access?context=sorting-session-language&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Configure whether string values in columns are sorted according to the user's session language or English. [Columnstore index type](https://www.servicenow.com/docs/access?context=t_CreateCustomIndex&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Optimize data storage and retrieval by creating a columnstore index. This index type is available with RaptorDB Professional. |
| ServiceNow Otto for App Engine | [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Configure ACLs for AI agents and agentic workflows](https://www.servicenow.com/docs/access?context=aia-security-implementation&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all authenticated users or publicly available. |
| ServiceNow Otto for Collaborative Work Management (CWM) | [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Configure ACLs for AI agents and agentic workflows](https://www.servicenow.com/docs/access?context=aia-security-implementation&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all authenticated users or publicly available. |
| ServiceNow Otto for Configuration Management Database (CMDB) | [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Configure ACLs for AI agents and agentic workflows](https://www.servicenow.com/docs/access?context=aia-security-implementation&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all authenticated users or publicly available. |
| ServiceNow Otto for Creator | [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills, agents, and agentic workflows are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The skills are automatically available to appropriate role users for the application, such as ITIL roles on incident forms or change forms. This change simply activates the skill and does not touch the roles that may be needed to use the skill. The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills and agentic workflows are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill, agent, or agentic workflow is turned on automatically (the AI asset was never configured and turned on, then turned off again). Previously configured skills and agentic workflows that were turned on, then off, remain inactive. [Configure ACLs for AI agents and agentic workflows](https://www.servicenow.com/docs/access?context=aia-security-implementation&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all authenticated users or publicly available. [Improved query engine for Analytics Generation](https://www.servicenow.com/docs/access?context=analytics-assist-landing-page&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : Starting in Yokohama Patch 1, analytics generation supports GPT-4o for generating queries, to provide better accuracy in responses. These improvements include support for up to two levels of dot-walking based on user utterances. [Find files faster when previewing an application in the Now Assist for app generation skill](https://www.servicenow.com/docs/access?context=sns-app-gen-using-landing&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US) : Filter the app files list and narrow the search when previewing an application that is created with the Now Assist for app generation skill. [Enhanced visibility of apps created by the Now Assist for app generation skill](https://www.servicenow.com/docs/access?context=sns-app-gen-review-apps&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US) : On the ServiceNow Studio home page, apps that are generated by AI display the AI indicator. [More easily identify changes when previewing and updating applications](https://www.servicenow.com/docs/access?context=sns-app-gen-using-landing&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US) : When previewing an application, any requested changes made by the Now Assist for app generation skill are listed when the preview pane loads. [Edit applications without having to change the scope manually](https://www.servicenow.com/docs/access?context=sns-app-gen-review-apps&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US) : When editing applications, the Now Assist for app generation skill now changes the scope that you're working in to the scope of the application automatically. [More easily query Analytics Generation](https://www.servicenow.com/docs/access?context=analytics-assist-landing-page&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : Analytics Generation now uses a semantic filter instead of Natural Language Query (NLQ), resulting in less rigid requirements for queries. |
| ServiceNow Otto for Customer Service Management (CSM) | [Triage cases agentic workflows enhancements](https://www.servicenow.com/docs/access?context=case-resolving-use-case&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US) : Added new standalone AI agents to check duplicate cases and split some existing standalone AI agents to focus on more specific tasks. The AI agents available are the Triage cases planner AI agent, Context validator and analyzer agent, Duplicate identifier AI agent, Informational queries AI agent, Transactional queries AI agent, Case creation AI agent, Entity extraction AI agent, Document verification AI agent, and Email response AI agent. [Now Assist in Portal case form enhancement](https://www.servicenow.com/docs/access?context=using-ai-search-with-q-a-within-the-portal-form&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US) : Added the new Ask Now Assist button that opens a contextual chat window so that a requester can carry the conversation forward. If no results are found or if the requester isn't satisfied with the result, they can get further assistance by selecting the button to chat and get an answer, which helps to avoid case creation. [Email reply recommendations enhancements](https://www.servicenow.com/docs/access?context=generate-email-reply-recommendations&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US){#rn-summary-changes__now-assist-for-csm-rn-rn-workspace} : Refined the AI-generated reply recommendation to create the best response for users by applying tone changes in the Now Assist context menu. Additional tone options, including casual, formal, and sympathetic, are available. [Chat reply recommendation enhancements](https://www.servicenow.com/docs/access?context=generate-chat-reply-recommendations&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US) : Added the chat reply recommendation enhancements to respond in a conversational tone and get feature parity in the AI Admin Hub console: * Refined the AI-generated reply recommendation to create the best answer for your users by applying tone changes in the Now Assist context menu. Additional tone options, including casual, formal, and sympathetic, are available. * Added parity with the chat summarization AI Admin Hub console capabilities. The AI Admin Hub console can specify the portal and channels for chat reply recommendations and assign additional support roles. {#rn-summary-changes__ul_hyr_kgp_sdc} [Case summarization enhancement](https://www.servicenow.com/docs/access?context=summarize-a-call-by-using-now-assist-for-customer-service-management-csm&version=yokohama&pubname=yokohama-customer-service-management&ft:locale=en-US) : Detailed feedback option is now available for negative feedback in the generated case summary.Xanadu Patch 7: Extended the capabilities of the case summarization feature so it can now be used on custom tables. |
| ServiceNow Otto for Enterprise Architecture (EA) | [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Configure ACLs for AI agents and agentic workflows](https://www.servicenow.com/docs/access?context=aia-security-implementation&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all authenticated users or publicly available. Yokohama Patch 3 [Agentic workflow name update](https://www.servicenow.com/docs/access?context=using-na-ea-ai-agents&version=yokohama&pubname=yokohama-application-portfolio-management&ft:locale=en-US) : Renamed the Enterprise Architecture Diagrammer AI agent to Enterprise architecture diagrams AI agent. [UI name updates](https://www.servicenow.com/docs/access?context=configure-now-assist-ea&version=yokohama&pubname=yokohama-application-portfolio-management&ft:locale=en-US) : * In the All menu, renamed the Features option under Now Assist Admin to Skills. * On the Now Assist Admin page, renamed the Now Assist Features tab to Now Assist Skills. {#rn-summary-changes__ul_y4f_v2q_1fc} |
| ServiceNow Otto for Field Service Management (FSM) | [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Configure ACLs for AI agents and agentic workflows](https://www.servicenow.com/docs/access?context=aia-security-implementation&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all authenticated users or publicly available. [Removed prompt headers](https://www.servicenow.com/docs/access?context=cust-now-assist-fsm-wot-summarization-skill&version=yokohama&pubname=yokohama-field-service-management&ft:locale=en-US) : The prompt headers have been removed from the work order summarization skill to support third-party Large Language Models (LLMs). You can now customize prompts via a hyperlink to the Now Assist skill. |
| ServiceNow Otto for Financial Services Operations (FSO) | [Role configuration required for agentic workflows and AI agents](https://www.servicenow.com/docs/access?context=aia-role-masking&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Agentic workflows and AI agents included with Now Assist applications require additional security configuration. If you select Users with selected roles for your user access security controls for an agentic workflow or AI agent, you must add the installed roles, or they will not execute. Data access settings must also include these roles. See the documentation for the agentic workflow or AI agent for the specific roles you must add. [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). |
| ServiceNow Otto for HR Service Delivery (HRSD) | [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Configure ACLs for AI agents and agentic workflows](https://www.servicenow.com/docs/access?context=aia-security-implementation&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all authenticated users or publicly available. Flow name : The Resolve noncritical HR cases flow has been renamed to Resolve HR cases flow. |
| ServiceNow Otto for Hardware Asset Management (HAM) | [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Configure ACLs for AI agents and agentic workflows](https://www.servicenow.com/docs/access?context=aia-security-implementation&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all authenticated users or publicly available. |
| ServiceNow Otto for IT Service Management (ITSM) | [Yokohama Patch 11](https://www.servicenow.com/docs/o~Ty6nl6ETxZAE_DIVoJJw "The Yokohama Patch 11 release contains important problem fixes.")[Changing the password reset topic to an AI agent](https://www.servicenow.com/docs/access?context=itsm-va-ai-agents&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : The Virtual Agent Password reset topic has been changed to a Virtual Agent AI agent. The agent guides the users with instructions to reset passwords using KB articles in their self-service portal. Yokohama Patch 6 [Removing the prompt headers from the Customize prompt screen](https://www.servicenow.com/docs/access?context=cust-now-assist-itsm-skill&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : The prompt headers have been removed from the Customize prompt screen in the Incident summarization and Change summarization skill to support third-party Large Language Models (LLMs). Yokohama Patch 3[Terminology change](https://www.servicenow.com/docs/access?context=now-assist-itsm-ai-agents-use-cases&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : * The term use case is replaced with the term agentic workflow. For example, the Notify users with Twilio use case is now referred to as the Notify users with Twilio agentic workflow. * The naming of the AI agents has changed. For example, Twilio SMS texter has been renamed to Twilio SMS texter AI agent. {#rn-summary-changes__ul_cf2_jgg_y2c} Yokohama Patch 3 [IT Service Management AI agent collection Triage and categorize ITSM incidents agentic workflow](https://www.servicenow.com/docs/access?context=now-assist-itsm-aiagents-catincidents-usecase&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : The Categorize incidents use case has been renamed to the Triage and categorize ITSM incidents agentic workflow. The following AI agents have been added to the workflow: * Link major incident AI agent * Link incident to problem AI agent {#rn-summary-changes__ul_jjp_y45_w2c}The Incident categorize AI agent has been renamed to Categorize incident AI agent. Yokohama Early Availability [New look and feel for the display of incident and change request summarizations](https://www.servicenow.com/docs/access?context=summarize-incident-now-assist&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : Get the summary of an incident or a change request by using the new and more intuitive summarization user interface. The new interface is available in Service Operations Workspace and in the Core UI. [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Role configuration required for agentic workflows and AI agents](https://www.servicenow.com/docs/access?context=aia-role-masking&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Agentic workflows and AI agents included with Now Assist applications require additional security configuration. If you select Users with selected roles for your user access security controls for an agentic workflow or AI agent, you must add the installed roles, or they will not execute. Data access settings must also include these roles. See the documentation for the agentic workflow or AI agent for the specific roles you must add. [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Skills activated by default in Now Assist for ITSM](https://www.servicenow.com/docs/access?context=using-now-assist-for-itsm&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : For new ServiceNow Otto for IT Service Management (ITSM) users, the following skills are activated by default: * Incident summarization * Change request summarization * Chat summarization {#rn-summary-changes__ul_z4x_2vm_khc} Yokohama Early Availability[System property to display knowledge article templates](https://www.servicenow.com/docs/access?context=Now-Assist-generate-article-SOW-itsm&version=yokohama&pubname=yokohama-it-service-management&ft:locale=en-US) : Display Knowledge article templates that you can use to create articles by using a system property. In earlier releases, the templates were displayed by default. |
| ServiceNow Otto for Legal Service Delivery (LSD) | [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Role configuration required for agentic workflows and AI agents](https://www.servicenow.com/docs/access?context=aia-role-masking&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Agentic workflows and AI agents included with Now Assist applications require additional security configuration. If you select Users with selected roles for your user access security controls for an agentic workflow or AI agent, you must add the installed roles, or they will not execute. Data access settings must also include these roles. See the documentation for the agentic workflow or AI agent for the specific roles you must add. |
| ServiceNow Otto for Order Management | [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Configure ACLs for AI agents and agentic workflows](https://www.servicenow.com/docs/access?context=aia-security-implementation&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all authenticated users or publicly available. |
| ServiceNow Otto for Sales Automation | [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Configure ACLs for AI agents and agentic workflows](https://www.servicenow.com/docs/access?context=aia-security-implementation&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all authenticated users or publicly available. |
| ServiceNow Otto for Security Incident Response (SIR) | [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills are now turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The following Now Assist skills for ServiceNow Otto for Security Incident Response (SIR) and ServiceNow Otto for Unified Security Exposure Management are activated by default. * Security incident summarization (SIR) * Resolution notes generation (SIR) * Post incident analysis (SIR) * Security incident recommended actions (SIR) * Correlation insights generation (SIR) * Security incident quality assessment (SIR) {#rn-summary-changes__ul_wkk_fb1_nhc} The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. {#rn-summary-changes__ul_cvh_rph_nhc} [Configure ACLs for AI agents and agentic workflows](https://www.servicenow.com/docs/access?context=aia-security-implementation&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all authenticated users or publicly available. [Generate recommended actions for a security incident with ServiceNow Otto for Security Incident Response (SIR)](https://www.servicenow.com/docs/access?context=generate-recommended-actions-now-assist-for-security&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US) : Introduced a new UI card Show More to enhance the visibility of recommended actions. As a security analyst, you can now access additional context along with further recommended steps to assist in the analysis and investigation of security incidents. [Now Assist for Security Incident Response application name change](https://www.servicenow.com/docs/access?context=activate-skills-for-now-assist-security-incident&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US) : Starting with version 2.0.1, the Now Assist for Security Operations application in the ServiceNow® Store and in your ServiceNow AI Platform® instance has changed to the ServiceNow Otto for Security Incident Response (SIR) application. |
| ServiceNow Otto for Software Asset Management (SAM) | [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills, agents, and agentic workflows are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The skills are automatically available to appropriate role users for the application, such as ITIL roles on incident forms or change forms. This change simply activates the skill and does not touch the roles that may be needed to use the skill. The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills and agentic workflows are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill, agent, or agentic workflow is turned on automatically (the AI asset was never configured and turned on, then turned off again). Previously configured skills and agentic workflows that were turned on, then off, remain inactive. [Role configuration required for agentic workflows and AI agents](https://www.servicenow.com/docs/access?context=aia-role-masking&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Agentic workflows and AI agents included with Now Assist applications require additional security configuration. If you select Users with selected roles for your user access security controls for an agentic workflow or AI agent, you must add the installed roles, or they will not execute. Data access settings must also include these roles. See the documentation for the agentic workflow or AI agent for the specific roles you must add. |
| ServiceNow Otto for Strategic Portfolio Management | [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Configure ACLs for AI agents and agentic workflows](https://www.servicenow.com/docs/access?context=aia-security-implementation&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all authenticated users or publicly available. [More actions context menu UI enhancements](https://www.servicenow.com/docs/access?context=email-project-summary-skill-pw&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US) : * Email project summary option has been renamed to Configure project insights. * Enable critical task alerts option has been added. * Disable critical task alerts option has been added. {#rn-summary-changes__ul_glg_j3c_fhc} [Configure project insights modal UI enhancements](https://www.servicenow.com/docs/access?context=email-project-summary-skill-pw&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US) : * Email project summary modal has been renamed to Configure project insights modal. * Disable email summary check box has been renamed to Pause cadence check box. * Choose topics, personalize content, and set frequency setup have been added. * Project tasks, Milestones, and Resources check boxes have been added. * Include critical path task changes check box has been removed. * Schedule and send button has been renamed to Schedule button. * Send preview button has been added to send an email instantly. {#rn-summary-changes__ul_wfb_qjc_fhc} [Skill name updates](https://www.servicenow.com/docs/access?context=email-project-summary-skill-pw&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US) : The email project summary skill has been renamed to the project insights generation skill. [Demand Management UI changes](https://www.servicenow.com/docs/access?context=identify-similar-demand-records&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US) : * The Identify similar demands button has been added to the demand form to identify and view any similar demands with the identify similar demands skill. * The Similar Demands related list has been added, which displays the list of similar demand records identified by Now Assist. {#rn-summary-changes__d2427e240} [Skill name updates](https://www.servicenow.com/docs/access?context=now-assist-spm&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US) : * Renamed the Project Gen AI Docs skill to the Project doc summarization (Project Workspace) skill. * Renamed the Planning item Gen AI Docs skill to the Planning item doc summarization (Strategic Planning) skill. * Renamed the EAP Teams Gen AI Docs skill to the EAP doc summarization (Enterprise Agile Planning) skill. * Renamed the Story generation skill to Agile story generation (Enterprise Agile Planning). * Added the Write planning items skill in Strategic Planning. {#rn-summary-changes__ul_eyh_yv5_x2c} [Animation support for Now assist buttons and icons](https://www.servicenow.com/docs/access?context=now-assist-spm&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US) : * Added hover animation in the Now Assist (![summarize-button.]()) icon for the Summarize button on the feedback list and Docs. * Added the Now Assist (![email-project-summary-button.]()) icon in the Email project summary button. * Added hover animation in the Now Assist (![summarize-button-on-docs-page.]()) icon for the Now Assist button in the Docs page. {#rn-summary-changes__ul_l5c_zw5_x2c} [UI enhancements](https://www.servicenow.com/docs/access?context=now-assist-spm&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US) : The following UI enhancements were made: * Added hover animation for the Now Assist (![now-assist-icon.]()) icon. * Added a loader for the Now Assist side panel for a more engaging loading experience. {#rn-summary-changes__ul_c5f_1wz_sdc} |
| ServiceNow Otto for Telecommunications, Media, and Technology (TMT) | [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Configure ACLs for AI agents and agentic workflows](https://www.servicenow.com/docs/access?context=aia-security-implementation&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all authenticated users or publicly available. |
| ServiceNow Otto for Unified Security Exposure Management | [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills are now turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The following Now Assist skills for ServiceNow Otto for Unified Security Exposure Management are activated by default. * Recommend preferred solution for VIT (VR) * Vulnerable item de-duplication (VR) * Approval Recommendation (VR)(USEM) * Security Exposure Management (SEM) Insights (VR)(USEM) * SPC Setup Connector (Security Posture Control) {#rn-summary-changes__ul_s4c_zzg_d3c} The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. {#rn-summary-changes__d1859e102} [Configure ACLs for AI agents and agentic workflows](https://www.servicenow.com/docs/access?context=aia-security-implementation&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all authenticated users or publicly available. |
| ServiceNow Otto for Workplace Service Delivery (WSD) | [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Starting with Yokohama Patch 5, Now Assist usage measurement is transitioning from a 365-day look-back model to a 365-day burn-down model, with usage resetting at the contract anniversary date. For more information, refer to [KB KB2704710: Now Assist Usage - Overview \& New Measurement Logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Some Now Assist skills are turned on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : The new default behavior works as follows: * New customers: When you install a Now Assist product, designated skills are turned on automatically. * Existing customers who are upgrading (starting with Yokohama Patch 11): Any previously unconfigured skill is turned on automatically (the skill was never configured and turned on, then turned off again). Previously configured skills that were turned on, then off, remain inactive. [Configure ACLs for AI agents and agentic workflows](https://www.servicenow.com/docs/access?context=aia-security-implementation&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : Configure the access control lists for who can discover and trigger AI agents and agentic workflows in their guided setups in AI Agent Studio. You can determine whether an AI agent or agentic workflow behaves as a dynamic user or as an AI user. You can also specify if an AI agent or agentic workflow can be available to all authenticated users or publicly available. |
| ServiceNow SDK | [Subcommands replaced with parameters on the auth command](https://www.servicenow.com/docs/access?context=servicenow-sdk-cli-commands&version=yokohama&pubname=yokohama-application-development§ion=now-sdk-auth-command&ft:locale=en-US) : Configure authentication credentials with the `--add`, `--delete`, `--list`, and `--use` parameters of the `now-sdk auth` command. [Dependencies command installs type definitions](https://www.servicenow.com/docs/access?context=servicenow-sdk-cli-commands&version=yokohama&pubname=yokohama-application-development§ion=now-sdk-dependencies-command&ft:locale=en-US) : Download TypeScript type definitions for Glide APIs and script includes from a ServiceNow instance based on the scripts in your application. [Build command includes --frozenKeys parameter](https://www.servicenow.com/docs/access?context=servicenow-sdk-cli-commands&version=yokohama&pubname=yokohama-application-development§ion=now-sdk-build-command&ft:locale=en-US) : Validate that the auto-generated keys.ts file is up to date for continuous integration (CI) builds by setting the `--frozenKeys` parameter to true with the `now-sdk build` command. [Deploy command renamed install](https://www.servicenow.com/docs/access?context=servicenow-sdk-cli-commands&version=yokohama&pubname=yokohama-application-development§ion=now-sdk-deploy-command&ft:locale=en-US) : Install or update an application on a ServiceNow instance using the `now-sdk install` command. [Automated Test Framework Test API supports two-way synchronization](https://www.servicenow.com/docs/access?context=atf-test-now-ts&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US) : Synchronize changes to Automated Test Framework tests made outside of source code into source code definitions and back to metadata. [Table API supports licensing configurations](https://www.servicenow.com/docs/access?context=table-api-now-ts&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US) : Create a licensing configuration \[ua_table_licensing_config\] to track subscription counts for a table with the licensing_config object in the Table API. [Table API supports remote tables](https://www.servicenow.com/docs/access?context=table-api-now-ts&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US) : Create a remote table with the scriptable_table property in a Table object. |
| ServiceNow Studio | [Create an application in ServiceNow Studio](https://www.servicenow.com/docs/access?context=create-an-application-in-servicenow-studio&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US) : As of version 27.2.4, the available options at the success page for creating an application changed from Go to app dashboard to View App Details and Create File. [Modify an app's settings in ServiceNow Studio](https://www.servicenow.com/docs/access?context=modify-an-apps-settings-in-servicenow-studio&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US) : The App settings icon in ServiceNow Studio used to open a small modal where only a few settings could be updated and the app could be deleted. In this release, the icon opens a Core UI view of all the app settings and related links for the app. |
| Software Asset Management | [Reflow for Configurable Workspace](https://www.servicenow.com/docs/access?context=auto-reflow&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) : The Software Asset configurable workspace supports reflow, which enables pages and content to be zoomed up to 400% through your browser settings without loss of content or functionality. [Publisher optimizations dashboard for Microsoft](https://www.servicenow.com/docs/access?context=pub-opt-microsoft&version=yokohama&pubname=yokohama-it-asset-management&ft:locale=en-US) : The Publisher Optimizations dashboard for Microsoft has been updated to support additional subscriptions. |
| Strategic Planning | [Skill name updates](https://www.servicenow.com/docs/access?context=alignment-planner-workspace-landing-page&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US) : * Renamed the Planning item Gen AI Docs to the Planning item doc summarization skill in Strategic Planning. * Renamed the EAP Teams Gen AI Docs to the EAP doc summarization skill in Enterprise Agile Planning. * Added the Write planning items skill in Strategic Planning. {#rn-summary-changes__d2450e263} [Capacity Planning name updates](https://www.servicenow.com/docs/access?context=using-cap-plan-spw&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US) : Change in the name of the Capacity Planning tab to Capacity in the planning view. [Financials UI changes](https://www.servicenow.com/docs/access?context=using-portfolio-financials-spw&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US) : * New Financials tab in the Planning page. * The name of the ETC field is changed to Remaining Estimates. * The name of the EAC field is changed to Forecast. * The name of the Actuals to date field is changed to Actuals. * New Financials view in scenario planning. * New financial widgets in the compare scenario page. {#rn-summary-changes__d2451e153} [Changes in planning item forms](https://www.servicenow.com/docs/access?context=epic-form&version=yokohama&pubname=yokohama-it-business-management&ft:locale=en-US) : The dates in the Planned start date and Planned end date fields are editable for all planning item types other than Demand and Project planning item types. Also, the State field is editable for EAP planning items and its child items. |
| Subscription Management | [Hidden user-based subscription allocations](https://www.servicenow.com/docs/access?context=subscriptions-overview-v2&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : To help prevent inaccuracy when allocations aren't complete, allocation details for user-based subscriptions are now hidden from the Subscription Management overview. Contact your account executive for user-based subscription allocation details. [Changes to Now Assist usage measurement](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Now Assist usage measurement is evolving. If your instances are below Yokohama Patch 12, update Subscription Management to version 6.0.2 or later on all instances to avoid mixed measurement types. For more information, see [Now Assist Usage - Overview \& New Measurement Logic \[KB2704710\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2704710). [Allocation charts reflect only active users](https://www.servicenow.com/docs/access?context=subscription-details-v2&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US){#rn-summary-changes__subscription-management-rn-rn-workspace} : The Allocation summary and Allocation history charts on the subscription details page reflect only the subscriptions allocated to active users for each month following the upgrade. [Auditing App Engine V1 usage](https://www.servicenow.com/docs/access?context=allocating-custom-tables-subscr-apps-v2&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : The App Engine Usage dashboard has been restored. For details on auditing App Engine V1 usage, see the [Auditing App Engine v1 \[KB0999383\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0999383) article in the Now Support Knowledge Base. |
| Synthetic monitoring | Overview and detail pages in SOW. : Create view and manage your synthetic monitors on the overview and detail pages. As of version 1.2, the following UI enhancements are available: * Improved filtering for finding your endpoints. * Bulk editing of monitors. * Charts on the Overview page now display failures instead of successes. {#rn-summary-changes__ul_znt_x2x_z2c} |
| System Update Sets | Application installations : You can add specific applications or versions as an app installation and configure to track them in an update set. |
| Table Builder | Transition to NOW Design Systems (NDS) : Shift from the previous custom table builder icons to the NOW Design System (NDS) icons in the user interface. |
| Talent Development Core | [Credly Badges](https://www.servicenow.com/docs/access?context=achievements-lxp&version=yokohama&pubname=yokohama-employee-service-management&ft:locale=en-US) : As an employee, view your achievement badges on your employee profile. (Available across multiple applications within Talent Development Core). [Create a growth plan with the help of Now Assist](https://www.servicenow.com/docs/access?context=egd-create-growth-plan-with-nowassist&version=yokohama&pubname=yokohama-employee-service-management&ft:locale=en-US) : You can create growth plans with the help of Now Assist. Employees can select the Build with Now Assist button to access help from Now Assist. |
| Theme Builder | [New Image styles tab added to Editor page](https://www.servicenow.com/docs/access?context=working-with-image-styles&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) : As of Theme Builder version 5.1, the Editor page has the following additional options: * The general styles panel, which includes Global and Component styles, now features Image styles. The Image styles tab displays all illustrations available for editing. * When you select an empty state illustration for editing from the Image styles tab, the property panel opens with two additional tabs: Images and Colors. The Images tab displays which image files are applied to an empty state illustration. The Colors tab displays which theme colors are applied to an illustration. {#rn-summary-changes__ul_xqd_f43_q2c} [Navigation updated](https://www.servicenow.com/docs/access?context=tb-edit-components&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) : The Return to component overview link within the Component Editor is replaced with breadcrumb-style navigation for a more contextual navigation experience. [Component Editor button replaced](https://www.servicenow.com/docs/access?context=tb-edit-components&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) : The Go to Component Editor button is now labeled either Style variants, Style subcomponents, or Style interactions depending on the selected component. The Component Editor behaves in the same way despite this UI change. [Component Editor Interactions States panel updated](https://www.servicenow.com/docs/access?context=tb-edit-components&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) : The Interaction States panel within the Component Editor now refers to either Interactions or Subcomponents. |
| Threat Intelligence Security Center | [Courses of Action](https://www.servicenow.com/docs/access?context=course-of-action&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US) : Renamed Course of Actions to Courses of Action. [Create Inbound Data Exclusion Rules](https://www.servicenow.com/docs/access?context=define-filtering-rules&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US) : Renamed Inbound Filtering Rules to Inbound Data Exclusion Rules. |
| Upgrade Center | [Upgrade Plan enhancements](https://www.servicenow.com/docs/access?context=uc-upgrade-plan&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) : Experience a seamless upgrade on your instance with the Upgrade Plan, offering the option to either include or bypass skipped records and customizations during its building. |
| Usage Insights | [Primary User Experience Analytics navigation has moved under the All menu.](https://www.servicenow.com/docs/access?context=user-exp-analytics-dashboard&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : * User Experience Analytics experience moved under Platform Analytics module. * User Experience Analytics administrative functions moved under the Platform Analytics AdministrationUX Analytics settings module. {#rn-summary-changes__ul_alb_rfb_hdc} [Updated navigation within User Experience Analytics](https://www.servicenow.com/docs/access?context=exploring-user-exp-analytics&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : Navigation to Analytics pages simplified to Analytics and Data Foundation sections for each application. [New layout](https://www.servicenow.com/docs/access?context=exploring-user-exp-analytics&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : The previous navigation has been replaced with a more unified, cleaner look and feel which enables you to understand the usage, user experience, and user satisfaction with your application. [Improved Funnels UI](https://www.servicenow.com/docs/access?context=funnel-reports-uxa&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : The UI has improved readability and navigation. [New custom user property configuration](https://www.servicenow.com/docs/access?context=uxa-add-filters-uxa-pages&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : An easy way to configure which user-related fields are available to use as filters and in user details. Configured user properties are available for all applications. Previously created custom user properties are no longer supported and must be recreated in the new UI. [Country consent policies are set by default to No Consent Required](https://www.servicenow.com/docs/access?context=uxa-tracking-types&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : Default country consent policies are now set to No Consent Required. If you have previously updated your country consent policies, they will retain the custom setting. Existing users who have set their tracking preferences will retain their settings. New users will not require consent for tracking unless you update your country consent policies. [Longer user history](https://www.servicenow.com/docs/access?context=configuring-user-exp-analytics&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : Detailed data for users and sessions extended to two years. [Optimized the way metrics are calculated](https://www.servicenow.com/docs/access?context=uxa-duration-calculations&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : Percent time on app and Average duration per page calculations changed compared to the application view in Xanadu or prior releases. Percentage time on app was Percentage time on site in Xanadu or prior releases. [Client page load and Full page load aggregated in the same visualization](https://www.servicenow.com/docs/access?context=view-pages&version=yokohama&pubname=yokohama-now-intelligence&ft:locale=en-US) : All performance metrics associated with Client, Network, Page Load, and Server time are aggregated together. |
| Virtual Agent | Changes to Virtual Agent Designer list view : * Tabs have replaced pills in the Virtual Agent Designer list view. * Hover over the tooltip icon () to see information about the assistant you have selected from the drop-down menu. * Use the new AI agents and Agentic workflows tabs to select from the types of topics on the home page, along with Topics, Subflows, Actions, and Custom skills. * When a promoted asset has a conditional property that determines the context in which appears for an assistant, it's marked as Condition applied under Show more. {#rn-summary-changes__ul_kvt_mqm_rfc} [Test assistant options](https://www.servicenow.com/docs/access?context=test-llm-topics&version=yokohama&pubname=yokohama-conversational-interfaces&ft:locale=en-US) : The Test button in the Virtual Agent Designer canvas directly opens up the chat widget. [UI chat updates](https://www.servicenow.com/docs/access?context=using-now-assist-in-va&version=yokohama&pubname=yokohama-conversational-interfaces&ft:locale=en-US) : * The New messages below button in Virtual Agent was replaced with a simplified down-arrow indicator. * The New messages above button was deprecated because Virtual Agent now auto-scrolls to the top of the oldest new message. * Input text bar was updated to a more modern look and feel. * The start a new conversation icon was updated. {#rn-summary-changes__d2472e99} [Dynamic Translation calls](https://www.servicenow.com/docs/access?context=translation-for-now-assist&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US) : For Now Assist, if native translation is enabled, a Dynamic Translation call is only made if an unsupported language for native translation is used. [Table bot response control](https://www.servicenow.com/docs/access?context=table-bot-response&version=yokohama&pubname=yokohama-conversational-interfaces&ft:locale=en-US) : Use the new Show links for each record toggle switch to activate links for each record in the output in your Virtual Agent conversation.{#rn-summary-changes__patch-4n-yp7-1} [Topic Properties tab](https://www.servicenow.com/docs/access?context=vad-topic-properties-tab&version=yokohama&pubname=yokohama-conversational-interfaces&ft:locale=en-US) : * [Create a topic form](https://www.servicenow.com/docs/access?context=vad-topic-creation-form&version=yokohama&pubname=yokohama-conversational-interfaces&ft:locale=en-US): Read improved topic description field helper text and tooltip. * [Change the application scope for Virtual Agent Designer topics](https://www.servicenow.com/docs/access?context=change-application-scope-vad&version=yokohama&pubname=yokohama-conversational-interfaces&ft:locale=en-US): View the current scope setting on the Virtual Agent Designer topic properties tab. {#rn-summary-changes__ul_d1m_fbq_qdc} [Topic Flow tab](https://www.servicenow.com/docs/access?context=vad-topic-flow-tab&version=yokohama&pubname=yokohama-conversational-interfaces&ft:locale=en-US) : * View an updated Unpublished changes message on the header bar. * Hover over the Unpublished changes message to get info on which changes are not yet published. * Recover unsaved changes using the Recover changes button that appears on the header bar if you close a topic without saving. * Both message and button appear on the header bar if you add a node to the canvas before closing without saving. {#rn-summary-changes__ul_avr_q5b_q2c} [Testing LLM topics](https://www.servicenow.com/docs/access?context=test-llm-topics&version=yokohama&pubname=yokohama-conversational-interfaces&ft:locale=en-US) : View a Matching badge next to the skill activated during testing. [Custom skills in Virtual Agent Designer](https://www.servicenow.com/docs/access?context=managing-custom-skills&version=yokohama&pubname=yokohama-conversational-interfaces&ft:locale=en-US) : Use an updated Virtual Agent Designer list-based home page that includes custom skills. |
| Visa Spoke | [Visa Resolve Online (VROL) version 25.2 updates](https://www.servicenow.com/docs/access?context=visa-spoke&version=yokohama&pubname=yokohama-integrate-applications&ft:locale=en-US#section_gsl_nw5_vyb) : Updated the following Visa Spoke actions to align with Visa Resolve Online (VROL) release 25.2 revision changes: * Submit Dispute Questionnaire * Hypersearch Request Builder * Hypersearch Response Parser * Create Dispute Pre-Arbitration Request Builder * Create Dispute Pre-Arbitration Response Parser * Look up Dispute Response Details Request Builder * Look up Dispute Response Details Response Parser * Look up Dispute Pre-Arbitration Response Details Request Builder * Look up Dispute Pre-Arbitration Response Details Response Parser * Look up Dispute Pre-Arbitration Details Request Builder * Look up Dispute Pre-Arbitration Details Response Parser * Look up Dispute Details Request Builder * Look up Dispute Details Response Parser {#rn-summary-changes__ul_qbv_2ms_pgc} [Visa Resolve Online (VROL) version 25.1 updates](https://www.servicenow.com/docs/access?context=visa-spoke&version=yokohama&pubname=yokohama-integrate-applications&ft:locale=en-US#section_gsl_nw5_vyb) : Updated the following Visa Spoke actions to align with Visa Resolve Online (VROL) release 25.1 revision changes: * Submit Fraud Report Request Builder * Look up Fraud Report Details Response Parser * Look up Dispute Response Details Response Parser * Look up Dispute Details Response Parser * Submit Dispute Questionnaire {#rn-summary-changes__ul_rcv_gyb_v2c} |
| Vulnerability Response Integration with Claroty CTD | [Updates made for Claroty CTD v5.1](https://www.servicenow.com/docs/access?context=connect-to-claroty-ctd-vr-integration&version=yokohama&pubname=yokohama-operational-technology&ft:locale=en-US) : The following updates were made to support Claroty CTD v5.1: * There's no limit now on the number of Common Vulnerabilities and Exposures (CVEs) that you can import. * The Minimum CVSS Score field was replaced with the CVSS V3 Score field. {#rn-summary-changes__ul_hdq_ttj_y2c} |
| Workspace | [AI filter assist](https://www.servicenow.com/docs/access?context=use-ai-filter-assist&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) : Convert everyday language into an encoded query with AI filter assist. Favorite form templates : See your favorite form templates that you use most often in the Templates list. Larger form template cards : Larger form template cards provide you with the entire labels for form templates in the Templates list without selecting them. Sorting preferences for form templates : Sort form templates in the Templates list by the last used templates or in alphabetical order. [Preview the relevant templates in the email composer](https://www.servicenow.com/docs/access?context=use-email-templates-in-the-compose-email-page&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) : Preview relevant email templates, response templates, and quick messages that are listed in the email composer's Apply templates modal. [View a total count of drafts in the email composer](https://www.servicenow.com/docs/access?context=review-draft-emails&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) : A badge on the View drafts icon displays the total count of your drafts that are available in the email composer. [Preview all drafts available in the email composer](https://www.servicenow.com/docs/access?context=review-draft-emails&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) : Preview all drafts that are available in the email composer's View drafts modal instead of your three most recent drafts. Time elapsed in the Activity stream : Timestamps in the Activity stream provide more clarity on the amount of time that has elapsed by reflecting the format for timestamps in the Core UI. Compose text area expands with changes : The Compose text area expands dynamically to fit the parent container in the side-by-side view and modeless dialog. [Customize the multi-record associator](https://www.servicenow.com/docs/access?context=set-up-resizing-for-select-modals-in-configurable-workspace&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) : Resize the multi-record associator and adjust the number of rows that are shown per page in the multi-record associator. Download all attachments : Create a zip file and download all attachments in the Attachments list. Download multiple attachments at once : Select multiple attachments to download from the Attachments list at once. Reopen special handling notes : Reopen special handling notes after they have been dismissed without refreshing the page or closing and reopening the record. Indicator for personalized lists : A dot was added to the Update Personalized List icon as an indicator that the current list shows the personalized columns instead of the column defaults. Progress bar for Percent complete list field : When you add a Percent complete field to a list, a progress bar displays next to the percentage. Condition builder integrated into list : Condition builder opens above the list as an integrated part of the list experience instead of opening as a modal. Open column search row with icon : The Show column search row icon enables you to display a row to search columns in a list instead of using the Column options menu. [Context-based suggestions with @mentions](https://www.servicenow.com/docs/access?context=set-up-at-mentions&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) : Receive suggestions for users with access to the record when using @ mentions. [Expand all tiles in the Activity stream](https://www.servicenow.com/docs/access?context=activity-stream-expand-tiles&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) : Set a user preference to keep all tiles in the Activity stream expanded across cases and user sessions. Access control security model for the Activity stream : Data filters and access rules provide role-based access control for viewing and editing tables in the Activity stream. [Multiple records added from the multi-record associator load in the background](https://www.servicenow.com/docs/access?context=set-up-asynchronous-record-addition&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) : Work on a record while the multiple records that were selected from the multi-record associator are added in the background. Attach display text to knowledge base links in the email composer : Manage your email's appearance by attaching display text to knowledge base links. Infinite scroll for lists : Use the Record List bundle to scroll through lists infinitely without pagination. Live updates for lists : Use the Record List bundle to view live updates on lists without refreshing the page. Temporary lists available in the list menu : Temporarily access personalized lists that are sent to you as links within the My Lists menu. Filter for hierarchy in condition builder : The is within hierarchy field in the condition builder enables you to filter your list within a hierarchy instead of only direct reports. |
| Zero Copy Connector for ERP | [View ERP Canvas software information](https://www.servicenow.com/docs/access?context=view-erp-system-information&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US) : From the ERP Canvas system form, view detailed system information including machine type, node name, supported database, and Unicode status. [Preview model entities before adding to a model](https://www.servicenow.com/docs/access?context=erp-canvas-preview-entity&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US) : In the Model Manager, confirm you are adding the correct entity by examining and verifying read table entities before adding the entity to a model. |
[ ]
{#rn-summary-changes__rn-summary-changes-table}
*[\>]: and then