---
sourceDocument: Xanadu Release Notes
sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/release-notes

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Release Notes

ft:clusterId :

    - rn

bundleId :

    - rn


---

# Xanadu Patch 7

# Xanadu Patch 7 {#ariaid-title1}

* Release version: Xanadu
* 
* Updated March 12, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 48 minutes to read

The Xanadu Patch 7 release contains important problem fixes.

Xanadu Patch 7 was released on March 12, 2025.
:

    * Build date: 03-06-2025_0935
    * Build tag: glide-xanadu-07-02-2024__patch7-02-27-2025

Important:  
For more information about how to upgrade an instance, see [ServiceNow Upgrades](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0547244).

For more information about the release cycle, see the [ServiceNow Release Cycle](https://support.servicenow.com/kb_view.do?sysparm_article=KB0547244).{#xanadu-patch-7__p_download-version}  
Note:  
This ServiceNow AI Platform major family release is now available in ServiceNow's Regulated Market environments. For more information about services available in isolated environments, see [KB0743854](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0743854&_ga=2.238511747.200430442.1684856845-2052949275.1611611591). For a downloadable, sortable version of the fixed problems in this release, click [here](https://downloads.docs.servicenow.com/enus/xanadu/rn/patches/PRBs-X07.00.xlsx).

## Overview {#xanadu-patch-7__overview}

Xanadu Patch 7 includes 164 problem fixes in various categories. The chart below shows the top 10 problem categories included in this patch.  
Figure 1. Top 10 problem categories

## Security-related fixes {#xanadu-patch-7__security-related-fixes}

Xanadu Patch 7 includes fixes for security-related problems that affected certain ServiceNow® applications and the ServiceNow AI Platform®. We recommend that customers upgrade to this release for the most secure and up-to-date features. For more details on security problems fixed in Xanadu Patch 7, refer to [KB1925102](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1925102).

## Notable fixes {#xanadu-patch-7__section-notable-fixes}

The following problems and their fixes are ordered by potential impact to customers, starting with the most significant fixes.
{#xanadu-patch-7__notable-fixes__entry__4}

| Problem | Short description | Description | Steps to reproduce |
|-|-|-|-|
| Approvals PRB1845668 [KB1810362](https://hi.service-now.com/kb_view.do?sysparm_article=KB1810362) | Multi-Level approval skips steps due to race conditions | Overlapping transactions on the sc_req_item table cause race conditions, allowing approval steps to be skipped. | Refer to the listed KB article for details. |
| List Administration PRB1688076 [KB1585842](https://hi.service-now.com/kb_view.do?sysparm_article=KB1585842) | In Vancouver, changing the rows per page in UI Builder results in security restraints messages | When a user changes the rows per page on Tokyo or Utah and refreshes, it resets to 20 per page and this error doesn't appear. | Refer to the listed KB article for details. |
| List Administration PRB1804211 [KB1710147](https://hi.service-now.com/kb_view.do?sysparm_article=KB1710147) | A list is failing to load due to Access Control List (ACL) failures | Lists do not load, and a response is returned in the call for the record list composite data broker. | Refer to the listed KB article for details. |
[ ]

{#xanadu-patch-7__notable-fixes}

## All other fixes {#xanadu-patch-7__other-fixes}

{#xanadu-patch-7__all-other-fixes__entry__4}

| Problem | Short description | Description | Steps to reproduce |
|-|-|-|-|
| Access Control PRB1850716 | There should be a check for customization before the removal of the snc_internal ACL role from a set of ACLs | If a snc_internal acl role record has an entry in the sys_update_xml table, then the record shouldn't be deleted. |   |
| Activity Stream PRB1843408 | If a user deletes drafts after sending mail, the last sent email disappears in the filtered 'Activity Stream' section |   | 1. Open an email page record. 2. Select the 'Email' tab. 3. Compose an email with valid recipients. 4. Select the Send button. 5. Once the email history is updated, select the 'Email drafts' icon and delete all drafts. 6. Close the dialog/modal. {#xanadu-patch-7__ol_klr_rrb_42c} Expected behavior: Sent email logs should be displayed on the email's history. Actual behavior: The last sent email has disappeared from the email's history. |
| Activity Stream PRB1858894 | Application Programming Interface (API), ServiceNow AI Platform, and GraphQL is slow due to the Table Cleaner being throttled, causing heavy replication lag | API, ServiceNow AI Platform, and GraphQL calls are slow specifically because of the Table Cleaner on sys_activity shards. ​Using Instant Alter added an index, and as a result, all records were replicated with the load causing replication lag. When replication lag is detected, Table Cleaners are throttled, which can exacerbate the amount of data that is being replicated and cause timeouts. Timeouts are caused by the Table Cleaner running synchronously in the Activity Stream load request. |   |
| Advanced Work Assignment PRB1857820 | Agent Outside Workspaces that use OpenFrame soft phone are set to an 'Offline' presence state within a minute after the agent moves to an available state | If an agent isn't also on a workspace, the presence reverts to 'Offline' within about a minute. Since the agent is using OpenFrame to manage capacity, it shouldn't automatically revert to 'Offline'. The issue occurs after an Xanadu upgrade. |   |
| Agent Chat PRB1846351 | Audio notifications don't play intermittently when the browser has 'Allow All Auto-Play' configured | On a Safari browser, when the user doesn't allow the Auto-Play for the ServiceNow site, audio notifications intermittently don't play for an agent. This is applicable for inbox and conversation notifications. For example, if an agent doesn't hear an audio notification for an incoming inbox notification, it's possible the following conversation's audio alert to play or not play. Once audio notifications begin to play, proceeding audio notifications usually play. The audio state can be 'interrupted'. | 1. In a Safari browser, as an agent, open Service Operations Workspace. 2. Change the status to 'Available'. 3. Using a Chrome browser, impersonate a requester. 4. Turn off audio notifications in the web client. 5. Initiate a chat and attempt to connect to a live agent. 6. In the Safari browser, as an agent, accept the incoming work item.The audio notification plays. 7. From the Chrome browser, as a requester, send a message to ensure an audio notification plays on the agent's side. 8. In the same Safari browser, as an agent, open a new tab with a random URL. Keep this as the active tab and workspace tab in the background. 9. In Chrome, as the requester, wait for the timeout reminder and observe if the audio notification plays. 10. In Chrome, as the requester, send a message.Observe at this time, the audio notification stopped working, even though the console log says it successfully played audio. {#xanadu-patch-7__ol_vlr_rrb_42c} |
| Agile Development PRB1845010 | Add the spm_agile_common_user role to the plannedtask.\* ACL to view a rm_story form | A spm_agile_common_user should be able to have CURD access on the rm_story table. |   |
| AI Search PRB1827624 | A search doesn't return any results | After configuring the search profiles and the user, the search results don't appear, but if the location.state field is changed for the user, search results appear. | 1. Download and import the search profiles. 2. Ensure the search profiles were uploaded. 3. Find the 'Location boost' risk intelligence report. 4. Select the 'Location boost' risk intelligence report. 5. Navigate to positive. 6. Change the match field from 'location.city' to 'location.state'. 7. Publish the profile. 8. Set up a user. 9. Assign the user the knowledge_admin and ITIL roles. 10. Ensure the values in the company field are empty. 11. Change the location field to 'California'. 12. Select Save. 13. Select the value California. 14. Ensure that the column 'state' is 'California'. 15. Ensure that the 'name' is 'California'. 16. Run this query 'Employee benefits?' on Global, Service Portal, and Now Assist Virtual Agent. 17. Navigate to 'sys_generative_ai_log.list'. 18. Check the response. {#xanadu-patch-7__ol_pmr_rrb_42c} Expected behavior: The Knowledge Base article, 'Employee Benefit - US' should be at the top. Actual behavior: The search results don't appear, but if the user changes the location.state field, the Knowledge Base article appears. |
| AI Search PRB1838451 | AisJournalFieldPeekAhead throws a NullPointerException (NPE) | Leaving the value empty when adding a journal value column to kb_knowledge throws an NPE. | 1. Add a journal value column to kb_knowledge. 2. Leave the value empty. 3. Attempt to ingest the document. {#xanadu-patch-7__ol_jnr_rrb_42c} Observe the NPE. |
| AI Search PRB1852129 | Selecting a search result in the Portal adds the parameter 'SearchTerm', leading to a 404 error | With AI Search enabled, searches in the Portal lead to a '404 page not found' error. This occurs when search results that are external links are presented in the search results. When a search result is selected, an additional parameter is added to the URL '\&searchTerm=', which causes the 404 error. | 1. Navigate to a Xanadu instance. 2. Add an external link to the AI Search source. 3. Navigate to the Employee Portal. 4. Search for the external link. 5. Select the top search result. 6. Observe that 'searchTerm=' is added to the URL. {#xanadu-patch-7__ol_vnr_rrb_42c} Expected behavior: The user lands on the external link after selecting the search result. Actual behavior: The user lands on an page with the error message '404 Page not found'. |
| AI Search PRB1852402 [KB1909618](https://hi.service-now.com/kb_view.do?sysparm_article=KB1909618) | SearchAnalyticsService. pruneSearchSignalEvents occasionally purges events with the wrong application ID | The sysauto_script scheduled job, 'Prune Search Signal Events', may cause sys_search_events and its related tables to be incorrectly pruned. | Refer to the listed KB article for details. |
| AI Search PRB1857237 | Images aren't returned for Now Assist actions on Service Portal |   | 1. On a Yokohama instance with Now Assist for Search 10.0.14, navigate to Service Portal. 2. Search for 'Apple' or 'Laptop'. {#xanadu-patch-7__ol_d4r_rrb_42c} Expected behavior: Images should be returned for the Now Assist actions Genius Results. Actual behavior: Notice that the images aren't coming back for Genius Results. |
| Application Install Engine PRB1836818 | A parent application installs successfully despite missing dependencies | A parent application (for example, Generative AI Controller 9.0.1-Snapshot) is installed successfully even though its dependencies (for example, Microsoft Azure AI Speech Spoke) were not installed during the process | 1. Attempt to install a parent application with known dependencies. 2. Simulate a scenario where the dependency (for example, Microsoft Azure AI Speech Spoke) fails to install. {#xanadu-patch-7__ol_td4_b1q_42c} Observe that the parent application still installs, creating a record in the sys_store_app table, but dependencies remain missing. |
| Attachments to Records PRB1849752 [KB1885864](https://hi.service-now.com/kb_view.do?sysparm_article=KB1885864) | There's an issue with archive table clean-up using the 'PurgeOrphanAttachments' job | There's an issue that may result in the unintentional removal of records from the sys_attachment table under specific conditions. The issue may impact instances on Washington DC and later releases. | Refer to the listed KB article for details. |
| Case and Knowledge Management for HR Service Delivery PRB1827858 | Ship RCA for a KB search in the target scope |   | 1. Set up Now Assist for HR. 2. Enter a query in Virtual Agent: 'Tell me about parental leave policy' or any other KB related query. {#xanadu-patch-7__ol_u4r_rrb_42c} Expected behavior: The numbers should be visible and clickable. Actual behavior: The numbers aren't displayed in the KB result. |
| Case and Knowledge Management for HR Service Delivery PRB1850236 | RCA issues with tuition reimbursement AI agents | There are RCA records that are needed in app-hr to let tuition reimbursement request AI agents to function. |   |
| Case Card Component for HRSD Agent Workspace PRB1828093 | Tooltips aren't working | After upgrading to Xanadu, the tooltips stopped working on all the workspaces. | 1. Access any Xanadu instance that was upgraded from Utah or Washington DC. 2. Navigate to sys_ux_lib_asset_list. 3. Observe if the instance has the file sys_ux_lib_asset_ 4eca5b08258a2192915e9d083b0bf32e.xml. 4. Open any workspace. 5. Observe that there's no tooltip. 6. Remove the file mentioned on step 3. {#xanadu-patch-7__ol_apr_rrb_42c} Observe that the tooltips are working. |
| Client Scripts PRB1794520 | Newly populated on_hold_reason field data doesn't display for a duplicate tab | The behavior is different from the native view and the Service Operations Workspace view. | 1. Log on to any instance. 2. Navigate to 'change_request.do' and populate the assignment_group field. 3. Save the form. 4. Select the Request Approval UI action. 5. Duplicate the tabs so users have the change request open on two tabs - Tab A and Tab B. 6. In Tab A, select the 'on_hold' checkbox.Observe that the on_hold_reason field appears. 7. Enter '123' in the on_hold_reason field. 8. Save the form. 9. Move to Tab B.Observe that the 'on_hold' checkbox is now ticked, but the on_hold_reason field doesn't have '123' populated. 10. Refresh Tab B.Observe that '123' is now populated. {#xanadu-patch-7__ol_ipr_rrb_42c} |
| CMDB Query Builder PRB1830100 | The 'Dynamic CI' group is missing a few CIs | The QueryBuilderOutput. getCISysIdsFromQBResults() loop has an issue. | 1. Create a QB query (can use only one node) to qualify a few thousand CIs. 2. Run the query entirely by selecting the Load All Results button. 3. Note the count of CIs. 4. Create a CMDB Group and use the QB query from step 1 into this group. 5. Create a Dynamic CI Group and use the CMDB Group from step 4 to populate it.Give it a minute or so to associate CIs with this DCG before going to the next step. 6. On the 'Form' page of this Dynamic CI Group, select View Service CIs. 7. Note the count of CIs. {#xanadu-patch-7__ol_xpr_rrb_42c} Expected behavior: The count of CIs from step 7 should match the count of CIs from step 3. Actual behavior: The count of CIs from step 7 doesn't match the count of CIs from step 3. |
| Code Signing PRB1857413 | Signatures created by 'Signing' jobs have the update_name field empty |   | Run the 'Signing' job to generate a signature for records. Excepted behavior: Generated signatures should populate the update_name field Actual behavior: The update_name field is empty for a generated signature. This prevents records from Git check-in and the 'Publish to App' repo. |
| COE Legacy Family Component PRB1850825 | Moving the resizable panes handle quickly doesn't work on a configurable page with an iFrame component | If users add an iFrame component in the tab sidebar, then it causes an issue when trying to adjust the size of the panes in the workspace. |   |
| Conversational Interfaces PRB1810492 | A module key isn't present in the ms_teams_crypto_module, but the key is present in oauth_entity, which is causing migration issues |   | Create a data migration from security jobs. The migration fails because a record from the oauth_entity table is skipped. The oauth_entity had a key but the respective crypto_module module key doesn't exist. |
| Customer Service Management PRB1855041 | Unable to create an email draft in an application scope | The sys_email_draft table has table-level access limitation. Only 'Can Read' is allowed in the application scope. | 1. AI AgentTesting. 2. Select the AI agent 'CSM Response Handler'. 3. Enter the task detail as: 1. record_table = 'sn_customerservice_case' 2. record_sysid = '5078cc9a2be71210f980f0aef291bf0b' 3. email_reply_content = 'We can't complete this case until missing fields and missing documents are added' {#xanadu-patch-7__ol_yqr_rrb_42c} {#xanadu-patch-7__ol_xqr_rrb_42c} Observe the email response tool 'Draft Email' returns an error message 'Email draft is failed created'. |
| Database Persistence - Data Management PRB1808866 | Inefficient chunk production for a document ID type reference | For a document ID type reference, the 'Unreferenced Record Cleaner' producer first computes the list of unique table names and then produces the chunks. The SQL query to compute the list of unique table names can timeout leading to no chunks being produced. | 1. Create a large table with a document ID type reference. 2. Have a large number of unique table names in the table name field. 3. Set the SQL timeout (sysrule_quota) to a small value. {#xanadu-patch-7__ol_hrr_rrb_42c} Observe that 'Unreferenced Record Cleaner' producer times out computing the list of unique table names, thus producing no chunks. |
| Database Persistence - Data Management PRB1820795 | The DMJob allows the restarting of timed out DM runs | This issue was seen in an unreferenced record cleaner cleanup. Runs are left in a 'processing' state. |   |
| Database Persistence - Data Management PRB1840970 | Monthly/Yearly scheduled jobs named 'Physical Table Stats Aggregator/Gatherer' causes slow CPU and instance responses | This problem manifested primarily on demo instances that have more than 300 DBIs, but it isn't necessarily isolated to demo hosts. |   |
| Database Persistence - Data Scale PRB1777198 | When upgrading, the fix script does not update records |   | Run an upgrade. Notice that records in sys_query_rewrite have the Engine field, but no value in it. |
| Database Persistence - Data Scale PRB1807483 | Track the number of total/dropped messages per SqlType | Currently, the number of dropped messages is already being tracked and the stats are exposed in xmlstats. When a capture is run, one can hit the xmlstats to get the state/health of the capture, which includes the number of dropped messages. However, the dropped messages are not tracked per SqlType, which makes it impossible to know the percentage of the dropped messages. |   |
| Database Persistence - Data Scale PRB1834412 | Make JDBC driver properties load dynamically from the DB so nodes don't need to be bounced | This property currently requires updating file properties and bouncing of nodes, which is hard on instances. | Update the sys_properties table with glide.db.postgresql. jdbc.largeResult SetProtectionMethod = disk. Observe JDBC driver still uses stream mode. |
| Database Persistence - Data Scale PRB1834816 | Send txn-level SQL execution time in micros | Currently, TransactionMessage.sql_time is being sent to indicate the total SQL time for the transaction. The value comes from Transaction#getSQLTime and the unit is in milliseconds. The total transaction-level SQL time should be measured and sent in microseconds. |   |
| Database Persistence PRB1763563 | SNCVARCHAR fields are created as an unbounded length, but should be set to 16 MB |   | 1. Create a payload larger than 16MB. 2. Insert into a text field set to more than string 255. {#xanadu-patch-7__ol_srr_rrb_42c} |
| Developer Sandboxes PRB1788330 | Standby nodes are incorrectly elected as controller/sandbox nodes over primary nodes | The available sandbox count should only count primary nodes (seen from sys_cluster_state). Only primary nodes should be assigned DSB nodes. If there are no more primary nodes left to assign sandboxes, then the available sandbox count should be 0 and a sandbox shouldn't be able to be created. | 1. Create a sandbox instance with many nodes, some as standby and others as primary. 2. Increase the sandbox controller count. 3. Check the expected behavior below, and repeat increasing the count as needed. {#xanadu-patch-7__ol_wrr_rrb_42c} Expected behavior: Each time the count is increased, an available primary node is chosen as the controller node. Actual behavior: Sometimes a standby node is chosen as the controller node over an available primary node. |
| Discovery PRB1804025 | During Shazzam, updates should be batched to discovery_status.started | A lot of updates in a short time causes a performance issue. In this case, batch means to change the started count only once for all probes that are to be launched. | 1. Run a discovery using RaptorDB. 2. Observe the performance. {#xanadu-patch-7__ol_esr_rrb_42c} |
| Discovery PRB1824650 | Smart content for the November release should be true upped |   |   |
| Discovery PRB1843022 | Simple Network Management Protocol (SNMP) GetTable commands during pattern execution no longer exit the pattern when errors occur that exceed the limit | SNMP GetTable commands no longer exit pattern when errors occur that exceed the limit, and the failure count continues to increase. | 1. Setup a Discovery. 2. Run a Discovery against an SNMP device that returns errors running 'getTable' requests.Ensure that this sets the MID properties 'mid.sa.snmp.allowable_failures_before_success' and 'mid.sa.snmp.allowable_failures_after_success' to 0. 3. Check the logs after the Discovery. 4. Observe messages such as, 'SNMP command failure count is 1 and allowable failures before success is 0. Exiting pattern execution'. {#xanadu-patch-7__ol_hsr_rrb_42c} Expected behavior: The pattern should exit after the first failure. Actual behavior: The pattern doesn't exit, and the failure count continues to increase on subsequent errors. |
| Discovery PRB1860779 | True-up licensing app |   |   |
| Dynamic Translation for Virtual Agent PRB1853153 | Virtual Agent responses are in English when Dynamic Translations are on | This impacts Brazilian Portuguese, French, German, Italian, Japanese, and Spanish. | 1. Ensure Dynamic Translation is enabled and Native LLM is turned off. 2. Set the language session to Japanese. 3. Navigate to 'https://\<instance name\>.service-now.com/sp'. 4. Open the Virtual Agent chatbot. 5. Request for '社内在庫管理' and, once the item is found, start the request. 6. Begin entering Serial ID item inputs. 7. Continue responding to any additional questions prompted by the chatbot. 8. Observe the language of the chatbot's responses. {#xanadu-patch-7__ol_tsr_rrb_42c} Expected behavior: All chatbot responses, including those for Serial ID item inputs and other user-provided answers, should be entirely in Japanese. Actual behavior: The chatbot responds in English for every input provided by the user, including Serial ID item inputs and any other follow-up responses in the process. |
| Dynamic Translation PRB1847469 | A Spanish user runs skills and gets a response in English |   | 1. Set up Dynamic Translation. 2. Impersonate an agent. 3. Change the language to Spanish. 4. Type or select a skill pill. {#xanadu-patch-7__ol_htr_rrb_42c} Expected behavior: The user gets the entire response in Spanish Actual behavior: The user gets a response in English and Spanish. |
| Edge Encryption PRB1844471 | After a Vancouver upgrade, a scheduled upgrade is blocked from appearing on a Washington DC or Xanadu's instance for a Vancouver proxy | The Schedule button doesn't appear on the edge proxy page, so users are unable to schedule an upgrade. |   |
| Employee Center PRB1734350 | Portal Utils prediction methods should respect missing or inactive HR AI configuration records | HR_MLPortalUtilsSNC has two methods, 'getSimilarProfiles' and 'getRecommendedArticles' that retrieve HR AI configurations before trying to predict matches. getRecommendedArticles doesn't check for an HR AI configuration. It could be useful for a user to be able to turn off this functionality if they don't wish to train AI data and don't want to see the 'Solution GlideRecord does not exist, please train the solution definition' repeated in the system error logs. | 1. Log in to the instance. 2. Check system logs for the message 'Solution GlideRecord does not exist, please train the solution definition' from the sn_hr_sp source. {#xanadu-patch-7__ol_mtr_rrb_42c} |
| Employee Center PRB1792636 | Rich text content isn't translated on the ESC portal 'Get Support' widget | It still displays English content inside for rich text content. |   |
| Employee Center PRB1817222 | Level 2 subcategories don't follow a tree form in the 'Categories' widget | The 'SC Categories' widget doesn't display the proper indentation for the Level 2 categories. The tree structure of the second level is the same as the parent and this creates confusion of where the categories end. | 1. Navigate to any Washington DC instance. 2. Navigate to esc?id=sc_category. 3. Select the second level catalogs. {#xanadu-patch-7__ol_rtr_rrb_42c} Expected behavior: The second level content under the tree should get aligned similarly to the first level. Actual behavior: The content under the first level is properly aligned below the tree. The second level content isn't aligned properly under the tree. |
| Employee Taxonomy Framework PRB1766037 | The 'Search within Topic' page doesn't return results in the Employee Center when the topic name has special characters | The value of the _kb_knowledge.topic _level_2_s field on documents under the 'Compensation (Base/Incentive/Stock)' topic is actually 'Compensation Base Incentive Stock'. The special characters were removed at indexing. The facetFilters added by the 'Topic Content' sp_widget don't get the same treatment. The query has a filter looking for documents where the field's value is 'Compensation (Base/Incentive/Stock)' when the actual value is 'Compensation Base Incentive Stock'. |   |
| External Triggers PRB1848664 | Change the spoke sys_id to the spoke ID in the definition for external triggers telemetry |   |   |
| Field Service Management PRB1827771 | Sm_config records are updated randomly with new versions | . |   |
| Flow Engine PRB1825217 [KB1709497](https://hi.service-now.com/kb_view.do?sysparm_article=KB1709497) | When applying inline scripting to pass the value in an input of a dynamic template, it's not working, and the field appears empty | When users create a new action from scratch with one input of a dynamic template and apply inline scripting to pass the value to this input in the flow, it doesn't work. | Refer to the listed KB article for details. |
| Flow Engine PRB1843277 | Users get an error when creating a flow from Table Builder or from logic and automation on a partially upgraded instance | An error is thrown: 'java.lang.NullPointerException: Cannot invoke "com.glide.db. PrimaryKey.addQuery (com.glide.db. meta.Query, String)...' | 1. Provision an instance having Washington DC installed. 2. Partially upgrade it to Yokohama. 3. Navigate to AES. 4. Create an app or use existing an app. 5. Create a table in it. 6. Edit the table. 7. Create a flow in it. {#xanadu-patch-7__ol_ytr_rrb_42c} Expected behavior: The user must be able to create the flow in it. Actual behavior: The user is getting an error. |
| Flows (Family Channel) PRB1844406 | The IntermediateFlow. processIntermediateFlow() API doesn't work properly with the trigger type 'sla_task' |   |   |
| Flows (Family Channel) PRB1850367 | Enable a generation_source value other than 'text2flow' in Flow Generation |   |   |
| GRC Platform Plugins PRB1789050 | When importing policy text, images don't render and there's misalignment | In Compliance Workspace with O365 Integration enabled, 'Import Policy Text - Images' don't render and there's misalignment. | 1. Impersonate a user. 2. Open a policy in the Compliance Workspace. 3. Create a policy in 'Draft'. 4. Navigate to 'Policy text'. 5. Select Import Policy text. 6. Add a file in attachment. 7. Select Import. 8. Navigate back to the 'Policy text' tab. {#xanadu-patch-7__ol_f5r_rrb_42c} Observe the misalignment. |
| GRC Platform Plugins PRB1842928 | The Revised by field is empty when a policy is re-published in Policy and Compliance | Re-publishing a policy after moving it into a 'Draft' state displays an empty Revised by field. | 1. Navigate to an instance. 2. Create a policy. 3. Publish the policy. 4. Move the policy into the 'Draft' state. 5. Re-publish the policy. {#xanadu-patch-7__ol_n5r_rrb_42c} |
| Hermes (Family) PRB1789573 | The GCF metrics collector for certain internal topics is broken | Certain topic name patterns break GCF metrics' name parsing and selects the wrong value for the app ID. |   |
| Hermes (Family) PRB1845208 | Hermes tables aren't being audited |   | Modify hermes_topics_state or hermes_app_services. Notice that it's not being audited. |
| Hermes (Family) PRB1845224 | There's no warning that deleting sys_kafka_topic deletes the topic in a cluster | Deleting a topic in sys_kafka_topic deletes it in the cluster. Users should be warned about that. | Delete a sys_kafka_topic record in Xanadu or later. Notice that it's deleted in a cluster and no warning was given. |
| Horizontal Portal Capabilities for Customer Service PRB1827623 | '\[Add to Wishlist\]' isn't displayed in the CSM portal after upgrading to Xanadu | It can be added in Service Portal, but in the CSM portal, the 'CSM SC Cat item' widget doesn't have \[Show Add/Update Wish List buttons\] as an instance option. | 1. Provision an instance with the Customer Service Management plugin to have a CSM portal. 2. Find one sc_cat_item with 'Catalogs' and 'Category' defined and 'Catalog' enabled with Wishlist=true. 3. Confirm it in the CSM portal. {#xanadu-patch-7__ol_s5r_rrb_42c} Expected behavior: It should be with the \[Add to Wishlist\] option, same as Vancouver. Actual behavior: \[Add to Wishlist\] isn't displayed in Washington and Xanadu. |
| HR Service Delivery PRB1819942 | HTML tags are seen in the Description(description) field of an HR case |   |   |
| HTML Field Type Editor PRB1841733 [KB1813433](https://hi.service-now.com/kb_view.do?sysparm_article=KB1813433) | There's warnings seen in syslogs on visiting a classic form with an html-editor on it | 'com.glide.script.RhinoEcmaError: null is not a function. : Line(1) column(0) ==\> 1: null()' warnings are displayed in sys logs after upgrading to Xanadu. | Refer to the listed KB article for details. |
| HTML Field Type Editor PRB1853234 | The 274 records related to TinyMCE 27.0.0 in the \[sys_ux_lib_asset\] table shouldn't be presented | For example, when it comes to search, starting with 'sn-tinymce/27.0.0' in the 'Name' column. |   |
| Instance Data Replication (IDR) PRB1838458 | Selected fields in 'Outbound Entry' aren't replicated to 'Inbound Entry' when a transformation is enabled (specifically sys_fields) | When a user creates a 'Replication Entry' with transformation enabled, this freezes the selected/deselected sys_ fields. Specifically, it freezes the ones that are gated by the 'Preserved Modified By' checkbox. | 1. On a 'Producer Replication' set, have sys_ fields included and enable transformation on any table. 2. Establish a 'Consumer' set. 3. Ensure replication works. 4. Remove/add a sys_ field on a 'Producer Entry' set. 5. Synchronize on the consumer side. {#xanadu-patch-7__ol_bvr_rrb_42c} Observe that the removal/addition isn't present on the 'Consumer Inbound Entry'. |
| Instance Data Replication (IDR) PRB1846711 | If the legacy cluster is offline, the 'IDR Producer' job is in a 'doNothing' state | This prevents processing for Hermes sets too, even if the Hermes cluster is online. | Have the legacy cluster offline. Notice errors in the log and observe that the Hermes replication sets are also not processed. |
| Integration Hub PRB1836492 | After upgrading to Xanadu, a 'No valid MID server' error is outputted by OAuthTokenRefreshJob | The error 'No valid MID server with REST capability available to obtain new access token' is outputted. The use_mid field doesn't exist on the discovery_credentials table until the 'com.snc.mid. enhanced_security.oaut' plugin is installed. | 1. Prepare an instance which doesn't install the 'com.snc.mid. enhanced_security.oauth' plugin. 2. Allow OAuthTokenRefreshJob to run. 3. Check the syslog to see if the error message is outputted. {#xanadu-patch-7__ol_jvr_rrb_42c} |
| Key Management Framework (KMF) PRB1819713 | A node is stuck in deadlock due to a LegacyPropertyEncrypter DB call in GlidePropertiesController.snapshot() | This is a highly intermittent issue. This may take a significant number of node restarts to get this to occur due to the underlying race condition. | 1. Open a one node instance. 2. Fire a full cache flush messages in a loop. 3. Add 100 repeat jobs running every 1 second. 4. Reduce the DB connection pool size as small as possible. {#xanadu-patch-7__ol_pvr_rrb_42c} |
| Key Management Framework (KMF) PRB1839570 | Upgrading to Xanadu causes module keys that are wrapped with a deactivated IKEK to be rekeyed with the active IKEK and then deactivated | This is an issue in KMF that causes module keys that are wrapped with a deactivated IKEK to be rekeyed with the active IKEK and then deactivated. The user is using a specific filter to find the correct module key to use for CLE, based on the sys_id. However, because that key was deactivated, CLE failed. |   |
| Knowledge Management PRB1768407 | The Request Translation UI action can be used multiple times for the same language on any knowledge article that has a version higher than 1 | . | 1. Open a 'Knowledge Article' list. 2. Find an article which has a version \> 1. 3. Select the knowledge article in the list. 4. Select the Request Translation action. 5. Select a language to translate. 6. Complete the process until a draft knowledge article version is created.Notice that the draft knowledge article has a 'Parent' set to v1 of the knowledge article instead of the selected version. 7. Select the Request Translation UI action. 8. Select the same language as per the above step. 9. Submit the request. {#xanadu-patch-7__ol_vvr_rrb_42c} See the translation request is still being created. |
| Language and Translations PRB1835314 | Search is not working in the sc_cat_item table when a catalog item is created in a non-English language, and is then updated to an English language in an Oracle DB instance | When the user creates a catalog item in a non-English language, it can be searched by its name in the sc_cat_item table. However, when the name of the catalog item is updated to an English language, it cannot be searched in the sc_cat_item table in a non-English language. |   |
| Lifecycle Events PRB1847452 | The 'Check Activity closure - Flow' business rule (BR) may run and query more often than necessary | Notice that the 'Check Activity closure - Flow' business rule runs and queries for all sys_flow_context updates where 'state=COMPLETE'. This can lead to performance issues with an excessive number of sys_trigger records created and unnecessary queries run by this BR. |   |
| List Administration PRB1809729 | When opening the database view record from a list, the view isn't the same as the list |   |   |
| List Administration PRB1821700 | On an extensible list, users are unable to create an incident | The error message 'The page you are looking for could not be found' is displayed. | 1. Log in to the instance. 2. Navigate to Service Operations Workspace. 3. Navigate to the 'Incident' list. 4. Refresh the page. 5. Select the New button to create an incident. {#xanadu-patch-7__ol_zqk_yq3_42c} Users are unable to create an incident. |
| MID Server PRB1760614 | SudoProcessor doesn't properly support commands with file paths | When configuring certain commands used by 'Parse File', they fail with 'Permission Denied' errors if configured in Sudo with a filepath specified, such as: /bin/cat /path/to/file. |   |
| MID Server PRB1808137 | Migrate 3DES ssh_private_key data to the new format of KMF encrypted data | Any ssh_private_key data must be encrypted in the password2 new KMF format. Any old_format data must be migrated to the new format. |   |
| MID Server PRB1840424 [KB1772428](https://hi.service-now.com/kb_view.do?sysparm_article=KB1772428) | MID Server ECCSender thread gives an 'Invalid byte 2 of 4-byte UTF-8 sequence' error, blocking sending of valid ecc_queue inputs to an instance | This is most likely to be seen in LDAP user imports, or Import Set JDBC Data Sources, where large data is involved. Large data is likely to include extended unicode characters such as emojis. For LDAP probes, emojis have been seen in OU/CN group names and user details data. For REST integrations synching incidents, emojis have been seen in comments of cases. They could potentially appear anywhere, for any feature's probe result data. | Refer to the listed KB article for details. |
| Mobile Experience for Field Service Management PRB1840564 | A map doesn't load when users tap 'set location' | Users see a blank screen. |   |
| Mobile Platform PRB1843738 | Field parameters for the URL button type that are used for the URL template are always encoded even when it's not needed | When selecting the options below on the Now Mobile app, the page doesn't navigate as expected. Instead, it is taken to a 'The page you are looking for could not be found' search screen. After selecting Go, the page is redirected correctly. Options: 'Open my Reservation \>\> mesp?id=wsd_reservations' and 'Create a new general reservation \>\>mesp?id=wsd_search'. | 1. Access the instance via Now Mobile. 2. Open my Reservation \>\> mesp?id=wsd_reservations. 3. Create a new general reservation \>\>mesp?id=wsd_search. 4. Select Go. {#xanadu-patch-7__ol_rwr_rrb_42c} Notice that the page redirects correctly after selecting Go. |
| Mobile Platform PRB1844740 | If a dot-walk field references a column in the parent table, document data isn't saved | Document data isn't displayed offline because it isn't saved in SQLite DB. | 1. Create a Table A extending task. 2. Add a reference column. 3. Create a child Table B extending from Table B. 4. Add a few columns. 5. Add a form screen to display the Table B record to show the reference field defined in Table A. 6. Verify that the form screen is displayed correctly in the mobile app. 7. Go offline. {#xanadu-patch-7__ol_ywr_rrb_42c} Notice that the form screen can't be displayed offline because the document data for Table B isn't saved in an SQLite database. |
| Next Experience Unified Navigation PRB1792732 | Next Experience's impersonate is much slower than UI16's impersonate | When users have a large number of sys_user, the impersonate dialog can take a long time to open in Next Experience. | 1. Open an instance with at least 200k sys_user records. 2. Enable Next Experience. 3. Connect as a user with admin rights in Next Experience. 4. Notice the time it takes to open the impersonate dialog. 5. Set the user preference to not use Next Experience. 6. Reconnect and open the impersonate dialog. {#xanadu-patch-7__ol_jxr_rrb_42c} Observe that it takes a long time to open. |
| Next Experience Unified Navigation PRB1814384 | Adding a parent application and child module to the configurable menu breaks the menu API |   | 1. Create a configurable menu. 2. Add the application 'Benchmark' to the configured items of the menu. 3. Add a child module of 'Benchmark' to the configured menu. {#xanadu-patch-7__ol_uxr_rrb_42c} Expected behavior: The API should return the menu items' response. Actual behavior: The API returns 500. |
| Next Experience Unified Navigation PRB1836091 | There's a 'Session Expired 401' modal on public pages | The 'sn-banner-announcement-list' component emits an HTTP_ERROR_OCCURRED event causing a CANVAS_GLOVAL_ERROR event to open the 401 alert dialog. | 1. Create a page in UI Builder. 2. Make it public. 3. Log out. 4. Open that public page. {#xanadu-patch-7__ol_cyr_rrb_42c} Notice a 'Session Expired (401)' dialog displays. |
| Now Assist Panel PRB1852531 | The latency feedback messages are cut at the bottom | The problem likely stems from a height issue for the container. | 1. Navigate to NAP. 2. Type 'summarize a record'. 3. Check the latency feedback messages. {#xanadu-patch-7__ol_gyr_rrb_42c} Expected behavior: The message text is displayed whole in the container. Actual behavior: The bottom part of the messages are cut. |
| On-Call Scheduling PRB1814433 | The 'Reminder Report' displays in an incorrect format |   |   |
| Platform Analytics Dashboard API PRB1760775 | There's an issue with reports on a workspace dashboard | Legends display duplicate values when translated into non-English language. | 1. Provision an instance with the 'Install Platform Analytics workspace' plugin installed. 2. Create a Platform Analytics dashboard with a column report with 2 data sources. 3. Change the language to Brazilian Portuguese. {#xanadu-patch-7__ol_myr_rrb_42c} |
| Playbooks (Family Channel) PRB1842669 | Data definition synchronization slows down Playbook activation even when Playbook has no questionnaire activities | Activating Playbook can take over 1 hour to complete on a Xanadu instance. After setting a system property to turn off flow data variable sync, the activation time decreased to 40 minutes. When running a background script to activate, the process took 19 minutes. Previously, activation time took between 8 and 10 minutes. | 1. Create a Playbook with 100 activities but without any questionnaire activities, adding a trigger and filling all required fields. 2. Activate the Playbook. {#xanadu-patch-7__ol_syr_rrb_42c} |
| Playbooks (Family Channel) PRB1847073 | Questionnaire data definition and flow data variable (questions) are missing after duplicating a playbook |   | 1. Create a playbook. 2. Add a lane and a questionnaire activity. 3. Open the configuration panel and add a questionnaire (data definition). 4. Add a question (flow data var). 5. Save and close the configuration panel. 6. Duplicate the playbook. {#xanadu-patch-7__ol_yyr_rrb_42c} Expected behavior: The questionnaire is duplicated. Actual behavior: The questionnaire isn't duplicated. |
| Playbooks (Family Channel) PRB1848445 | A PD update set generation takes a long time and/or timeouts for large playbooks with many conditions to run | This can happen with large processes. In extreme cases, update set generation takes 60+ minutes, where the entire process errors out. | 1. Create a large process (e.g. 200 activities), where all activities have a condition to run. 2. Activate. {#xanadu-patch-7__ol_fzr_rrb_42c} Notice how long it takes to generate the update set, and if it fails. |
| Predictive Intelligence Similarity Solution PRB1826156 | Untranslated annotations with the i18n language plugin | The annotation, 'STEP 1: Please select the table \& field(s) you want to use to retrieve your similarity results, and the table and fields you want compared' is left untranslated and in English. | 1. Set up a Xanadu testing environment. 2. Install an i18n language plugin for French. 3. Navigate to now/nav/ui/classic/params/target /ml_capability_definition_similarity.do. {#xanadu-patch-7__ol_kzr_rrb_42c} Observe the hardcoded string, 'STEP 1: Please select the table \& field(s) you want to use to retrieve your similarity results, and the table and fields you want compared'. |
| Process Mining Workspace PRB1830418 | Edit transitions aren't working |   | 1. Apply a transition. 2. Select Edit from applied filters. {#xanadu-patch-7__ol_szr_rrb_42c} Expected behavior: The transitions pop-up should be filled. Actual behavior: The transitions pop-up is empty. |
| Process Mining Workspace PRB1834704 | When applying a transition filter and then an RCA, there's issues with flickering, the transitions, and filters | When applying a transition filter and then an RCA, after selecting any leading influencers and selecting 'Apply', there's multiple issues. Transitions aren't displayed properly. The screen flickers. Pop-ups are displayed multiple times. Applied filters and buttons aren't seen. |   |
| Process Mining Workspace PRB1839094 | Full mining is enabled for a freemium project on the 'Project list' page | No users should be able to edit the evaluation project. No users should be able to delete the evaluation project(s). Users with a Process Mining role (analyst, power or admin) role can copy any project, including an evaluation project(s). The copied project is handled as a regular project and follows regular license check validation. No users should be able to do a full mine on evaluation project(s). The option shouldn't be available on UI16 and project card drop down menu. |   |
| Process Mining Workspace PRB1848238 | Transitions freeze when max constrains are set to 0 | The max duration in the constraints set is automatically handled as 0 when not filled in. This results in 0 matched records. Second, the UI freezes when the transition as 0 records, making it impossible to set a max duration field manually. This can also happen when a filter set has a transition with an activity from a previous version, which isn't present in the current version. | 1. Create a project with any AD. 2. In the analyst workbench, open the Transition field. 3. Configure 2 conditions/activity. 4. Configure a constraint with: * Start = step 1 * End = step 2 * Min duration = 1 min * max duration: Keep empty {#xanadu-patch-7__ul_xzr_rrb_42c} {#xanadu-patch-7__ol_wzr_rrb_42c} Expected behavior: When the max duration is left empty, the max duration should be set to infinite (so all records longer than the min duration should match). Also, the user should be able to use the transition UI to add/remove fields and constraints. Actual behavior: When applying the transition, zero records match despite some matches. The max duration fields are set to 0 rather than kept empty. Also, when zero records match the condition, the user isn't able to change anything in the transition. |
| Project Management PRB1829307 | A project actual isn't populated in the resource aggregated monthly for October, though it's populated for September and November | A category project actual isn't populated in table resource_aggregate_monthly for October. It does populate for September and November. There is one record for a project actual in October. If looking in resource_aggregate_weekly, all project actual records are there. | 1. Open the resource aggregate monthly \[resource_aggregate_monthly\] table.Only 1 record displays under the monthly table and it excludes the month of October. 2. Check in resource aggregate weekly \[resource_aggregate_weekly\].Records are displayed as expected including the month of October. {#xanadu-patch-7__ol_j1s_rrb_42c} |
| Project Management PRB1829721 | For a group-based ORA, if users update allocation dailies, it's rolling up to only immediate user-based allocation but not rolling up to group allocation without a user |   |   |
| Related Lists PRB1780317 | Inline cell edit options appear off-screen for related lists | The inline edit box should be right-justified when on the right side of the screen and should show all inline edit icons. Instead, the inline edit box is left justified when on the right side of the screen and disappears off the right edge of the screen. |   |
| Resource Management PRB1841076 | After an Xanadu upgrade, there's a resource reports issue | Resource reports are broken after an Xanadu upgrade when the glide.sys.date_format is dd-MM-yyyy. | 1. On Xanadu, set the date format to dd-MM-yyyy or dd/MM/yyyy. 2. Navigate to AllResourceResource ReportsResource Reports. 1. Start date auto populates = today's date. 2. End date auto populates = 1 year from today's date - 1 day. {#xanadu-patch-7__ol_t1s_rrb_42c} 3. Update the start date to 10/12/2024 and end date to 11/11/2025. 4. Select Run. {#xanadu-patch-7__ol_s1s_rrb_42c} Observe the error message 'Report duration can't be more than 12 months'. The system considers the start date as being the 12th of October and not the 10th of December. |
| Rollback Contexts PRB1844400 [KB1803428](https://hi.service-now.com/kb_view.do?sysparm_article=KB1803428) | The 'Clean Expired Rollback Contexts' job causes memory issues and node restarts | The job is streaming through large rowblocks of data and causing node restarts. The heap dump shows 1.2GB of memory taken by this job. | Refer to the listed KB article for details. |
| SaaS integration with Adobe Cloud (Glide) PRB1843443 [KB1913878](https://hi.service-now.com/kb_view.do?sysparm_article=KB1913878) | sn_samp. UpdateReclamationCandidates \> getUserSubscriptionCost code issue | The potential_savings field is only present on the samp_sw_ reclamation_candidate table, and not in samp_sw_rc _m2m_subscription. This is causing the 'SAM - Updating Existing Reclamation Candidates' job to fail when updating the hybrid subscription cost. | Refer to the listed KB article for details. |
| Schedules PRB1831078 | The 'Timeline' page isn't displaying properly with sub items after an Xanadu upgrade | When there is a \[cmn_timeline_sub_item\] record attached, 'View Timeline' doesn't seem to work. The issue is only there when there's a timeline sub item in the 'Timeline' page. If there's no timeline, there's no issue. | 1. Navigate to AllTimeline Pages. 2. Select ServiceNow Roadmap. 3. Select the View Timeline button. {#xanadu-patch-7__ol_ebs_rrb_42c} |
| Server-side scripts PRB1842183 | Accessing ex.message throws an error in the 'try - catch' block when there's a RhinoException in the script | If there a RhinoException, there is an error: 'Allowing access to org.mozilla.javascript. RhinoException: getMessage:() Ljava/lang/String;...' | 1. Write a server side script. 2. Try to access ex.message in try-catch block. {#xanadu-patch-7__ol_jbs_rrb_42c} |
| Service Catalog PRB1835283 | A UI policy script is running in Virtual Agent though the UI type is set to 'Desktop' |   | In Virtual Agent chat, request the item 'Seating Arrangement for Onboarding.' This has an onLoad UI Policy to make will_this_employee _be_seated_flex_or_remote' read only. Expected behavior: The first question should be about a desk request. Actual behavior: The question 'Will this employee have a reserved desk, flexible desk, or work remotely?' is asked. This indicated that this isn't a read only question, and the onLoad UI Policy did run. |
| Service Mapping PRB1816637 | In TB service connection, 2 CIs that are already part of a service and belong to the same CI type aren't added even if they match the traversal rule | When calculating a TB service, it starts from the tagged CIs, and then goes rule by rule to bring the next level according to the rule. When a rule is defined on the same class, if 2 CIs of that class have a connection that matches the rule between them, but those CIs are already part of a service, this connection isn't added to service. |   |
| Service Mapping PRB1836767 | When deleting a solution in the ml_solution table, a cascade delete is triggered on ml_cluster_detail, but the records are not deleted | When deleting a solution in the ml_solution table, a cascade delete is triggered on ml_cluster_detail, and it times out and does not delete all of the records because there are too many records in the table to handle a cascade delete. |   |
| Service Mapping PRB1851972 | Updating the same last_mark in blob table during recomputation | During recomputation, the blob tables (svc_model_obj_relation for example) are updated with today's date in the last_mark field. The code is using 'date time' instead of the date to update the field. | 1. Open the SQL debug. 2. Change a CI that connects to a service.Users see an update to the last_mark field with 'date time' instead of just the date. 3. Repeat the process. {#xanadu-patch-7__ol_nbs_rrb_42c} Observe the same record updating with the same date. |
| ServiceNow Security Center (Family Release) PRB1843476 | At an upgrade time with updated content, the completed steps of a customer action keeps the action status as 'ready', which turns off the action's Complete button |   |   |
| Service Portal PRB1840878 | The display of the Genius Results card using Now Assist and Knowledge Base articles are not aligned properly after resizing the browser | This issue also impacts the display in mobile devices. | 1. Navigate to a Xanadu instance with Now Assist configured. 2. Ensure that the Portal has AI search enabled. 3. Set the Genius search results limit to ten in the Search Application Configuration of the Portal Record. 4. Ensure that the Search Profile has the Genius Results configuration 'Now Assist Q\&A' set in 'Related List'. 5. Navigate to the Portal. 6. Search for any keyword.Notice that catalog items populate in Genius Results. 7. Resize the browser.Notice that the alignment of the Genius Results are not correct. 8. Navigate to the Knowledge tab in the search results.Notice that the alignment of the Knowledge Base results are also not properly aligned. {#xanadu-patch-7__ol_pnl_tzp_42c} |
| Session Validation PRB1846625 [KB1812394](https://hi.service-now.com/kb_view.do?sysparm_article=KB1812394) | Deeplinks redirection failed with a node switch from an unauthenticated session to an authenticated session | On opening a deeplink URL, the user should authenticate and redirect to a specific resource. | Refer to the listed KB article for details. |
| Software Asset Management Licensing and Compliance PRB1807335 | Daily subscription counts intermittently get zero counts | The 'SAM/CI populate data' job clears out resources counts but takes 7 minutes to repopulate. Since 'Usage Analytics definition' queries that for the daily count, if the definition query happens during the 7 minute window when the 'SAM/CI populate data job' is running, definition query doesn't get an accurate count. | 1. Run the 'SAM/CI populate data' job at 4AM. 2. Run 'Usage Analytics for definition' counts at 4AM. {#xanadu-patch-7__ol_ubs_rrb_42c} Observe daily subscription counts gets zero counts. |
| Software Asset Management PRB1787960 [KB1826337](https://hi.service-now.com/kb_view.do?sysparm_article=KB1826337) | There's a slow query caused by updateMultipleEntity in Suite Engine | The query causes a reconciliation performance issue, with slow updates due to chunking. There's significant performance degradation. | Refer to the listed KB article for details. |
| Software Asset Management PRB1790386 | There's a replication lag caused by 'untagSoftwareModel ForUnlicensedInstall' in AutomaticSMRCreation |   |   |
| Software Asset Management PRB1853225 | Remediation options buttons aren't triggering a scheduled job immediately if date_format is different | A scheduled job should be scheduled to run immediately. |   |
| Software Asset Normalization PRB1808233 | The 'SAM - Normalize discovery models using content library rules' scheduled job is not robust because a single corrupted samp_package_map record can make the job fail | The code should be robust to not fail the job because one record threw an exception. Also, this job triggers another job, 'SAM - Normalize discovery models using ML', which should be checked for being active before adding in a trigger. | 1. Create a discovery model. 2. Create a matching version hash record in samp_package_map where the package reference is corrupted. 3. Run the job. {#xanadu-patch-7__ol_ybs_rrb_42c} Observe that it fails. |
| Software Asset Reconciliation PRB1791385 | ignoreNonBYOLInstalls shouldn't insert a reason for 'Missing Cloud License Type' |   |   |
| Special Handling Notes PRB1836082 | Simplify 'Refresh SHN' conditionals for readability and backportability | In Xanadu, if users set the Special Handling Notes (SHN) property 'Display special handling notes only once per session' to false, then the SHN pop-up window isn't displayed at all each time a user accesses a record. However, in Xanadu, once the property is set to false, the SHN pop-up window isn't displayed at all each time a user accesses a record. According to the documentation, the SHN pop-up window should be displayed each time a user accesses a record. | 1. Ensure that the plugin 'Special Handling Notes' (com.sn_shn) is activated. 2. Ensure to upgrade the Store apps to the latest versions. 3. Create 'Special Handling Notes' (sn_shn_notes) for the 'Incident' table. 4. Specify a condition, such as 'Short description', that contains something. 5. Open the SHN 'Properties' page and set the property 'Display special handling notes only once per session' to false. 6. Open an 'Incident' record which matches the condition in Service Operations Workspace or CSM Workspace. {#xanadu-patch-7__ol_ecs_rrb_42c} Notice that the 'Special Handling Notes' pop-up window isn't displayed at all each time a user accesses the record in either workspace. |
| Survey Management PRB1847800 | Inactive metrics aren't displayed on the user response form |   | 1. Open any instance on or after Xanadu. 2. Create a survey. 3. Assign the survey to a user. 4. Take the survey. 5. Submit it.After submitting, when users view a user response form, users are able to see all the questions along with their response. 6. Mark a few questions as inactive. 7. Open the view user response form. {#xanadu-patch-7__ol_scs_rrb_42c} Expected behavior: Inactive metrics should also be shown in the response form. Actual behavior: Inactive metrics aren't displayed now even though the responses were there. |
| Syntax Editor PRB1533082 | The fonts defined on the system property 'glide.ui.html.editor .v4.font.collection' aren't displayed on the font list of the HTML editor on Agent Workspace | The list should show only the fonts defined in the value of system property 'glide.ui.html.editor .v4.font.collection, but it shows all the fonts mentioned on the system property 'Description'. On the native UI HTML editor, it's working as expected. |   |
| System Events PRB1818627 | The 'Slow Delete DMLs' from the 'Text index events process' job is contributing towards a replication lag on the Standby DB | 'Slow delete DMLs' originating from the 'Text index events process' job is contributing towards the lag when observed at any point of time during the lag increasing time. It can run past 3 hours. |   |
| System Import Sets PRB1847486 | Multiple concurrent import sets are created for one data source |   | 1. Install an AWS version with parallel loading. 2. Configure AWS. 3. Run import. 4. Check the concurrent import set attached to the imports sets. {#xanadu-patch-7__ol_dds_rrb_42c} |
| Table Administration and Data Management PRB1811830 | Records with no translations for translated fields appear first when sorted a to z |   | 1. Provision an instance with a language plugin installed. 2. Switch the user language from English to another language. 3. Navigate to any table with a translated type field. 4. Order the translated type columns. {#xanadu-patch-7__ol_jds_rrb_42c} Expected behavior: The order should be correct. Actual behavior: The order isn't correct with 'a to z' or 'z to a'. |
| UI Field Administration PRB1696422 | The Toggle Domain Scope UI action doesn't work in a workspace | The Toggle Domain Scope in form UI action isn't working when Next Experience is on. It works fine with Next Experience off on UI16 pages. This issue doesn't impact legacy Agent Workspace. It impacts configurable workspaces only. |   |
| UI Form Administration PRB1820922 | The display business rule causes info messages to not display on quick-edit of records in the Service Operations Workspace (SOW) | An info message doesn't display the message when using the 'i' quick-edit feature in SOW or any other workspace. When selecting the 'i' icon to edit a record in quick edit from the list view in the workspace, the info message is not shown. However, the info message appears correctly when previewing a record using the 'i' icon in the Native UI. | 1. Open any Xanadu or Washington DC instance. 2. Create a business rule for the incident table that executes on 'Display'. 3. Add an info message in the script section of the business rule. 4. Open the incident list in the Native UI. 5. Select on the i preview of a record. Observe that the business rule is executed and displays the info message. 6. Open SOW or any workspace. 7. Select the i icon for the quick view edit of a record in the list view. {#xanadu-patch-7__ol_rds_rrb_42c} Expected behavior: The info message should be displayed upon triggering the business rule in the workspace. Actual behavior: The info message is not displayed in the quick-edit view in the workspace. |
| Upgrade Center PRB1812035 [KB1831586](https://hi.service-now.com/kb_view.do?sysparm_article=KB1831586) | Records with \<sys_es_latest_script action="INSERT_OR_UPDATE"\> in the XML are listed in the plugin update list as 'skipped' during the plugin upgrade | It seems that the entire XML file is diffed here, when users would expect only the contents of the record to matter. | Refer to the listed KB article for details. |
| Upgrade Center PRB1844300 | sys_claims customization protection behaves differently than sys_update_xml during upgrades when the sys_policy of the file changes | The installer has no historic knowledge and can't tell if a record was previously unprotected and just became protected in a subsequent release version. This applies both to sys_claims as well as sys_update_xml as a protection mechanism for changes. | 1. Open a Washington DC instance. 2. Install the sn_hr_agent_ws app. 3. Customize the 'sys_ux_macroponent_ 1d033475eb3011106eb96bf3a252287f' file. 4. Publish to the app repo. 5. Create a customization pack. 6. Open another instance. 7. Install the above app along with the app customization. 8. Ensure the entry for that file is present in the sys_claim table. 9. Upgrade the instance to Xanadu's latest patch. 10. Check the upgrade history log for that file. {#xanadu-patch-7__ol_v2s_rrb_42c} Notice that it should be 'SKIPPED', but instead is 'UPDATED'. |
| Virtual Agent PRB1817023 | A NAVA response is still loading when the conversation is closed |   | 1. On NAVA, start a conversation. 2. Type 'show me some article'. {#xanadu-patch-7__ol_hfs_rrb_42c} Observe that the NAVA response is displaying as 'Looking into your request. |
| Virtual Agent PRB1849035 | Skill discovery is failing because of a missing sn_aia_usecase table |   | 1. Install AI Agent Jan version to an instance with Now Assist. 2. Create sn_aia_usecase. 3. Upgrade the instance on to the latest build. 4. Open NAP. {#xanadu-patch-7__ol_kfs_rrb_42c} Observe that topic discovery is failing. |
| Virtual Agent PRB1851004 | Skill discovery and execution fails with the proxy sys_prop enabled in Yokohama | Discovery and execution fails when the sysprop com.glide.cs.one_extend. auto_proxy_enabled = false. This is enabled by default. | 1. Open a NAVA portal. 2. Execute a topic.The topic executes with error messages in each stage. 3. Try to perform a topic discovery. {#xanadu-patch-7__ol_pfs_rrb_42c} Observe that discovery fails with a 'sorry' message. |
| Virtual Agent PRB1851248 | In sync mode, skill execution involving RAG is failing | For the skill mentioned, the RAG tool is failing in 'sync' mode due to an empty query input. It looks like it's not able to fetch and resolve 'query' from the previous tool output. |   |
| Virtual Agent PRB1854061 | OptimisticLockException when executing dynamic capability | The output refiner response is proper, but it fails to return a response to the dynamic capability node in the topic. |   |
| Virtual Agent PRB1854081 | GAIC Licensing should charge assists instead of trial assists even when the 'Licensing' API returns that a feature isn't configured in pricing | When a GAIC capability is executed, as part of licensing, a call is made to the 'Licensing' API to get the assists configured for that capability. If it is not present in pricing, users get an empty response. In that case, trial assists are configured in GAIC (sys_gen_ai_license _metadata_trial) and set as trial assists. This needs to be changed that the trial assists should still be charged as real assists when inserting into sys_gen_ai_usage_log. |   |
| Virtual Agent PRB1855393 | User KnowledgeGraph data should be applied for search |   |   |
| Virtual Agent PRB1856309 | Create a metadata table for AI agents's skill discovery | This is a product update. |   |
| Virtual Agent PRB1856323 | An NSA admin user is unable to switch LLMs | The issue exists during activating a skill. | 1. Impersonate with an NSA admin user. 2. Now Assist adminSettingsManage LLMs. 3. Switch the LLM from Azure to Now LLM. 4. Verify the success modal. 5. Verify the 'sys one extend capability' table. 6. Observe that no capability is switched. {#xanadu-patch-7__ol_ufs_rrb_42c} Expected behavior: An NSA admin user is unable to switch the LLMs. Actual behavior: An NSA admin user should be able to switch the LLMs. |
| Virtual Agent PRB1856492 | Chat bot errors out due to a mismatched lock version | The chat bot errors out and exits the chat. | 1. In a chat bot conversation, enter the query: 'General Request for a Storage VM' to request this catalog item. 2. Go through the flow. {#xanadu-patch-7__ol_dgs_rrb_42c} Observe that bot throws the error, 'Syslog error: Lock version mismatch for conversationId 14c1dcb92b371a 1009f2f22ffe91bf1c - expected 13 and encountered 14'. |
| Virtual Agent PRB1857900 | A deflection log table doesn't set a 'no response' state when AI Search returns 'no answer found' |   | 1. Navigate to NAVA. 2. Type in a search term that has no synthesized result and no regular result. 3. Navigate to the deflection log table (sys_cs_deflection_log). 4. Check the record corresponding to this search. {#xanadu-patch-7__ol_kgs_rrb_42c} Notice that the State field isn't set to 'no response'. |
| Virtual Agent PRB1858305 | GAIC doesn't handle response max tokens of NULL for sys_generative_ai_config | If sn_vad_genai.com. glide.cs.one_extend .auto_proxy_enabled is set to false, the issue isn't reproducible. | 1. Provision an instance with Now Assist For Creator (nowassist-creator) plugin version 27.1.1 installed. 2. As a user with elevated privileges, open Service Now Studio. 3. Select NAP in ServiceNow Studio. 4. Type anything as a prompt. For example, 'I want to create an app to track new employee hires'. {#xanadu-patch-7__ol_rgs_rrb_42c} Expected behavior: Users get a response from the LLM. Actual behavior: There's a GAIC error complaining about missing data. |
| Virtual Agent PRB1858954 | Follow-up after a navigation skill isn't working |   | 1. Select NAP. 2. Enter 'show me list of unassigned incidents'. 3. Select incident. 4. Enter 'show list of open incidents'. {#xanadu-patch-7__ol_qkp_5q3_42c} Observe that a processing message keeps loading and no response is displayed. |
| Virtual Agent Web Client PRB1861185 | An animated icon isn't visible in NAVA when enabled |   | 1. Enable sn_nowassist_va.nass _animated_avatar_enabled. 2. Navigate to NAVA. 3. Type an utterance like 'what is spam'. {#xanadu-patch-7__ol_b1s_qvf_p2c} Expected behavior: An animated icon is visible next to the loading messages. Actual behavior: No icon loads next to loading messages. |
| Walk-Up Experience PRB1848443 | A badge reader throws an error: 'Could not find location queue associated with badge reader' | Starting from Xanadu, users who have the badge reader configuration set up are facing the issue where it states 'Could not find location queue associated with badge reader', even though there is a location queue defined with the badge reader. | 1. Log in as an admin. 2. Run the badgeReaderAPI. {#xanadu-patch-7__ol_ehs_rrb_42c} Expected behavior: The API should give a success message: 'User has been checked in'. Actual behavior: The API is throwing 'Could not find location queue associated with badge reader', even though there is a location available. |
| Workflow Contexts PRB1820829 | A fix causes a query to be executed when module access is requested | A SQL query against sys_kmf_crypto_module is run whenever access to a module is checked with CallerPolicyAccessManager .isModuleAccessible. For a field with a Column Level Encryption (CLE) configuration, this API is called one or more times for each canRead\|canWrite\|canCreate call that is made. When canRead is called multiple times for each form load, the query is run many times when loading a single record. |   |
| Work Order Management PRB1838614 | Logic fails to check for conflicts if the assignment group selected on the work order task (WOT) contains multiple group types | The business rule date checks for table sm_task fails to correctly check for conflicts if the assignment group on the WOT contains multiple group types. | 1. Impersonate a dispatcher and assign a task to an agent in a group with multiple types. 2. Assign a second task to the same agent at the same time.The time-conflict that should be displayed isn't displayed. 3. Unassign the task assigned in step 2. 4. Remove one of the types from the agent's group. 5. Execute step 2 again. {#xanadu-patch-7__ol_jhs_rrb_42c} The assignment fails because of the conflict. |
| Work Order Management PRB1853754 | Schedule conflicts aren't displayed for wm_manager when the contractor management plugin is installed | A conflict error message should be displayed when scheduled Work Order Tasks (WOT) conflict and are assigned to the same user with the wm_manager role. | 1. Provision an instance with the Field Service Management Contractor Management plugin installed. 2. Create a WOT. 3. Assign the WOT to a wm_manager. 4. Create another task that conflicts with the previous task. 5. Assign the WOT to a same wm_manager. {#xanadu-patch-7__ol_shs_rrb_42c} Expected behavior: The conflict error is displayed. Actual behavior: The conflict errors aren't displayed. |
[ ]

{#xanadu-patch-7__all-other-fixes}

## Fixes included {#xanadu-patch-7__fixes-included}

* [Xanadu Patch 6](https://www.servicenow.com/docs/7K24M4PP11ssDC6KWOaYbQ "The Xanadu Patch 6 release contains important problem fixes.")
* [Xanadu Patch 5](https://www.servicenow.com/docs/VyjSkd~sV6vf_eKMBpjiOQ "The Xanadu Patch 5 release contains important problem fixes.")
* [Xanadu Patch 4b Hotfix 1](https://www.servicenow.com/docs/DmydcR8mLlx2klNPmAc_KA "The Xanadu Patch 4b Hotfix 1 release contains fixes to these problems.")
* [Xanadu Patch 4b](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1915138)
* [Xanadu Patch 4](https://www.servicenow.com/docs/OgQh0ODWfyI4VhUYcHdOnA "The Xanadu Patch 4 release contains important problem fixes.")
* [Xanadu Patch 3](https://www.servicenow.com/docs/xFmrrIc0hj6QrbCtaex1ag "The Xanadu Patch 3 release contains important problem fixes.")
* [Xanadu Patch 2](https://www.servicenow.com/docs/xWd1yxeJXXiW4XVp_LWsYQ "The Xanadu Patch 2 release contains important problem fixes.")
* [Xanadu Patch 1](https://www.servicenow.com/docs/SeaTUwH9Ppxa1kbhUdLy9A "The Xanadu Patch 1 release contains important problem fixes.")
* [Xanadu security and notable fixes](https://www.servicenow.com/docs/kJKHkxnGv~e~lZlOXUyBtg "The Xanadu release contains important problem fixes.")
* [All other Xanadu fixes](https://www.servicenow.com/docs/yBFTl0lL7IReSmFoGpZGCA "The Xanadu release contains important problem fixes.")
{#xanadu-patch-7__ul_tmv_yn3_qcc}

*[\>]: and then