{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":42929,"path":"release-notes/australia-patch-1.md","title":"Australia Patch 1","bundle":null,"doc_type":null,"release":"australia","body":"\n# Australia Patch 1\n\nThe Australia Patch 1 release contains important problem fixes.\n\n-   **Australia Patch 1 was released on April 03, 2026.**\n    -   Build date: 03-31-2026\\_1137\n    -   Build tag: glide-australia-02-11-2026\\_\\_patch1-03-23-2026\n\n**Important:** For more information about how to upgrade an instance, see [ServiceNow upgrades](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/release-notes/upgrade.md).\n\nFor more information about the release cycle, see the [ServiceNow Release Cycle](https://support.servicenow.com/kb_view.do?sysparm_article=KB0547244).\n\n**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_view.do?sysparm_article=KB0743854).\n\nFor a downloadable, sortable version of the fixed problems in this release, click [here](https://downloads.docs.servicenow.com/enus/australia/rn/patches/PRBs-A01.00.xlsx).\n\n## Overview\n\nAustralia Patch 1 includes 372 problem fixes in various categories. The chart below shows the top 10 problem categories included in this patch.\n\n\\[Omitted image \"prb-chart-ap1.png\"\\] Alt text: Fixed issues grouped by problem categories bar chart\n\n## Security-related fixes\n\nAustralia Patch 1 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 Australia Patch 1, refer to [KB2914133](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2914133).\n\n## Changes in Australia Patch 1\n\n-   **[Access your ServiceNow data using Live Connect](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/accessing-your-servicenow-data-using-sql-api.md)**\n\n    Live Connect provides read-only access to your ServiceNow tables, allowing you to write SQL queries, create reports, and perform analysis while maintaining your existing security controls. This eliminates the need for data synchronization and ensures you work with current ServiceNow data.\n\n-   **[Associate a request header with a resource](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/associate-header-api-resource.md)**\n\n    The following procedure describes the process for manually associating a REST API request header with a resource. For details about automatically generating request header definitions in non-production instances, see [Automatically generate API request definitions](https://www.servicenow.com/docs/r/api-reference/rest-api-explorer/autogenerate-api-request-definitions.html).\n\n    The request headers that you added are included in the exportable OpenAPI specification in the REST API Explorer with a \"type: string\" schema definition. For more information about exporting OpenAPI specifications, see [Export to OpenAPI specification](https://www.servicenow.com/docs/r/api-reference/rest-api-explorer/export-openapi-specification.html)\n\n-   **[Associate query parameters with a resource](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/AssocQueryParmResource.md)**\n\n    The following procedure describes the process for manually associating a query parameter with a resource. For details about automatically generating query parameters for requests in non-production instances, see [Automatically generate API request definitions](https://www.servicenow.com/docs/r/api-reference/rest-api-explorer/autogenerate-api-request-definitions.html).\n\n-   **[Automatically generate API request definitions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/autogenerate-api-request-definitions.md)**\n\n    Use sample requests made to an API resource to generate request header associations, query parameter associations, and a request schema for that resource.\n\n-   **[Use cases for Live Connect](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/common-use-cases-for-sql-api.md)**\n-   **[Configure ServiceNow Live Connect JDBC driver on a client machine](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/configure-jdbc-driver.md)**\n-   **[Configure ServiceNow Live Connect ODBC driver on a client machine](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/configure-odbc-driver.md)**\n-   **[Configuring ServiceNow Vault](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/configuring-servicenow-vault.md)**\n\n    Learn how to install and configure ServiceNow Vault.\n\n-   **[Configuring Live Connect](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/configuring-sql-api.md)**\n\n    Configure your ServiceNow instance to enable Live Connect access, set up the necessary security controls, and install the appropriate drivers on your client machine.\n\n-   **[Live Connect configuration on your ServiceNow instance](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/configure-sql-api-overview.md)**\n\n    Configure your ServiceNow instance to enable Live Connect access, set up the necessary security controls, and install the appropriate drivers on your client machine.\n\n-   **[Connect DB Visualizer to JDBC driver](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/connect-dbvisualizer-jdbc.md)**\n\n    Overview of the three-step configuration process required to enable Live Connect access including prerequisites and expected outcomes.\n\n-   **[Connect Power BI Desktop to ODBC driver](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/connect-power-bi-odbc.md)**\n-   **[Create Access Control Lists \\(ACLs\\) for Live Connect](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/create-acls-sql-api.md)**\n-   **[Create IP filter criteria](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/create-ip-filter-criteria.md)**\n-   **[Assign roles and create service accounts](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/create-service-account.md)**\n-   **[Download the Live Connect drivers on a client machine](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/download-sql-api-drivers.md)**\n-   **[Define a REST API response header](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/define-scripted-api-response-header.md)**\n\n    Define one or more REST API response headers in a REST API.\n\n-   **[Define a REST API schema](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/define-scripted-rest-api-schema.md)**\n\n    Specify the expected data structure for requests or responses within a REST API by defining a schema.\n\n    The following procedure describes the process for manual schema definition. For details about automatically generating request schema definitions in non-production instances, see .\n\n-   **[Define an API resource request structure](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/add-schema-rest-api-request.md)**\n\n    Add a schema to a REST request record to define the request's expected data structure.\n\n    The following procedure describes the process for manually adding a request schema to a resource. For details about automatically generating request schema definitions in non-production instances, see [Automatically generate API request definitions](https://www.servicenow.com/docs/r/api-reference/rest-api-explorer/autogenerate-api-request-definitions.html)\n\n-   **[Define an API resource response structure](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/add-schema-rest-api-response.md)**\n\n    Add a schema and relevant response headers to a REST response to define the response's expected data structure.\n\n-   **[Define available query parameters](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/t_DefineAvailableQueryParameters.md)**\n\n    The following procedure describes the process for manually defining query parameters for a scripted REST API service. For details about automatically generating query parameters for requests in non-production instances, see [Automatically generate API request definitions](https://www.servicenow.com/docs/r/api-reference/rest-api-explorer/autogenerate-api-request-definitions.html).\n\n-   **[Define a scripted REST API request header](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/t_DefineRESTServiceHeaders.md)**\n\n    a scripted REST API request header\n\n    The following procedure describes the process for manual definition of a scripted REST API request header. For details about automatically generating request header definitions in non-production instances, see [Automatically generate API request definitions](https://www.servicenow.com/docs/r/api-reference/rest-api-explorer/autogenerate-api-request-definitions.html).\n\n-   **[Enhanced Requests Experience](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/employee-service-management/my-requests-update-intro.md)**\n\n\n\n-   **[Getting started with ServiceNow Live Connect](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/getting-started-with-servicenow-sql-api.md)**\n-   **[Integrate Live Connect Drivers with third-party BI tools](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/configure-drivers-bi-tools.md)**\n-   **[Install the ServiceNow Live Connect ODBC driver on a client machine](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/install-odbc-driver.md)**\n\n    Install the ServiceNow ODBC driver on your Windows client machine to enable connectivity between your Business Intelligence \\(BI\\) tools and ServiceNow data through the Live Connect.\n\n-   **[Install Live Connect on your ServiceNow instance](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/install-sql-api-plugin.md)**\n\n    Installing the Live Connect on your instance enables secure, read-only access to your instance data from external applications. You can integrate your data with external tools and analytics platforms to enhance your reporting and data analysis capabilities.\n\n-   **[Install ServiceNow Vault](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/install-vault.md)**\n\n    Install the ServiceNow Vault application and assign the required roles.\n\n-   **[Manage connected content from topic pages](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/employee-service-management/mnge-content-topics.md)**\n\n    Link your desired categories to the topics and track the additions and removals to have easier management of unconnected content.\n\n-   **[Minimum requirements and supported software for Live Connect](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/minimum-requirements-and-supported-softwares.md)**\n-   **[ServiceNow Otto and agentic AI release notes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/release-notes/now-assist-rn-landing.md)**\n\n    For Now Assist new features and changes, see [ServiceNow Otto and agentic AI release notes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/release-notes/now-assist-rn-landing.md).\n\n-   **[Route Live Connect calls to Read Replica](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/routing-sql-api-calls-to-read-replica.md)**\n\n    You can route Live Connect calls to Read Replica to optimize the performance of your ServiceNow instance.\n\n-   **[Scripted REST APIs](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/c_CustomWebServices.md)**\n\n    Schemas define a structure that can be used for API requests and responses, including data type, expected fields, and formats. You can define multiple schemas within a scripted REST API, which can be used to specify request and response contents of the resources within that API.\n\n-   **[ServiceNow Vault roles](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/vault-roles.md)**\n\n    Learn and set up the roles necessary to use ServiceNow Vault.\n\n-   **[Live Connect architecture](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/sql-api-architecture.md)**\n-   **[Live Connect reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/troubleshooting.md)**\n-   **[Supported SQL functions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/supported-sql-functions.md)**\n-   **[Test Live Connect ODBC driver connection](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/test-sql-api-odbc-driver-connection-using-interactive-sql.md)**\n-   **[Usage limitations for Live Connect](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/web-services/usage-limitations.md)**\n-   **[Use ServiceNow Otto to search the CMDB](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/na-cmdb-awf-search.md)**\n\n    Starting with ServiceNow Otto for CMDB v3.0, searches can include parent-child nodes spanning multiple tables and can traverse relationship graphs \\(searches that traverse the cmdb\\_rel\\_ci\\), for example, \"Search for servers that depend on databases\".\n\n\n## Notable fixes\n\nThe following problems and their fixes are ordered by potential impact to customers, starting with the most significant fixes.\n\n<table id=\"notable-fixes\" class=\"custom-rows\"><thead><tr><th class=\"filter\">\n\nProblem\n\n</th><th>\n\nShort description\n\n</th><th>\n\nDescription\n\n</th><th>\n\nSteps to reproduce\n\n</th></tr></thead><tbody><tr><td>\n\nAI Agents \\(Glide Family\\)\n\n PRB1994390\n\n</td><td>\n\nAfter a Zurich upgrade, hundreds of thousands of log entries are generated by CacheInvalidationEventHandler\n\n</td><td>\n\nThe message is 'No endpoints available for cache invalidation'. The source is com.glide.ui.ServletErrorListener.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nApplication Manager\n\n PRB1992835\n\n [KB2804238](https://hi.service-now.com/kb_view.do?sysparm_article=KB2804238)\n\n</td><td>\n\nA deprecated Classic App Manager URL causes issues on some instances\n\n</td><td>\n\nUsers have access to the Classic App Manager by navigating to the URL '/$allappsmgmt.do'. When they switched to new app manager later, and load the 'My company applications' page, that can corrupt the App Manager checksum cache, which causes the manual sync to fail.\n\n</td><td>\n\nRefer to the listed KB article for details.\n\n</td></tr><tr><td>\n\nCloud Encryption\n\n PRB1980759\n\n</td><td>\n\nPrevent erroneous tampered DARE Properties notifications emails from being set to users\n\n</td><td>\n\nThe error message, 'The tampering activities for Cloud Encryption properties have been found' is found in the logs.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nPerformance Telemetry\n\n PRB2003266\n\n [KB2897634](https://hi.service-now.com/kb_view.do?sysparm_article=KB2897634)\n\n</td><td>\n\nUpgrade from Australia RTP to a later Australia release fails\n\n</td><td>\n\nThe instance becomes stuck when upgrading from an Australia release to another Australia release \\(for example, RTP to EA\\). However, instances can upgrade from outside of Australia into Australia successfully \\(for example, Zurich to Australia\\).\n\n</td><td>\n\nRefer to the listed KB article for details.\n\n</td></tr><tr><td>\n\nPlatform Analytics Component API\n\n PRB1980521\n\n</td><td>\n\nDashboard filters are not applied for scriptable multivis\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nTime Card Management\n\n PRB1988000\n\n [KB2760220](https://hi.service-now.com/kb_view.do?sysparm_article=KB2760220)\n\n</td><td>\n\nManagers are no longer able to add time cards for their direct reports in the Time Sheet Portal\n\n</td><td>\n\nManagers are no longer able to add time cards for their direct reports and delegates in the Time Sheet Portal.\n\n</td><td>\n\nRefer to the listed KB article for details.\n\n</td></tr><tr><td>\n\nUX Framework\n\n PRB2002003\n\n [KB2901692](https://hi.service-now.com/kb_view.do?sysparm_article=KB2901692)\n\n</td><td>\n\nStuck semaphore due to the call glideUxInteroperableRoutesProvider.getInteroperableRoutesByIds\\(\\)\n\n</td><td>\n\n \n\n</td><td>\n\nRefer to the listed KB article for details.\n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1999010\n\n [KB2817637](https://hi.service-now.com/kb_view.do?sysparm_article=KB2817637)\n\n</td><td>\n\nThe scheduled job, 'Time out abandoned Virtual Agent \\(VA\\) conversation' closes the conversation\n\n</td><td>\n\n'Time out abandoned VA conversation' should not close the conversation if the idle timeout is not completed.\n\n</td><td>\n\nRefer to the listed KB article for details.\n\n</td></tr></tbody>\n</table>## All other fixes\n\n<table id=\"all-other-fixes\" class=\"custom-rows\"><thead><tr><th class=\"filter\">\n\nProblem\n\n</th><th>\n\nShort description\n\n</th><th>\n\nDescription\n\n</th><th>\n\nSteps to reproduce\n\n</th></tr></thead><tbody><tr><td>\n\nAccess Analysis Instrumentation API\n\n PRB1990716\n\n</td><td>\n\nAdd agentic support in access simulation and compare use access\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nAccess Control\n\n PRB1981898\n\n</td><td>\n\nNeed properties for better control of the scope where a security attribute script gets evaluated\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nActivity Stream\n\n PRB1996382\n\n</td><td>\n\nWhen setting glide.ui.escape\\_text to 'false', forms break\n\n</td><td>\n\n \n\n</td><td>\n\n1.  Open any Zurich instance.\n2.  Upload the sys\\_properties file for glide.ui.escape\\_text.\n3.  Run a /cache.do.\n4.  Load any relevant record, such as 'Incident'.\n\n Expected behavior: The record should load normally with the glide.ui.escape\\_text sys\\_property activated.\n\n Actual behavior: A blank screen with a basic message at the top will call out the ampersand issue.\n\n</td></tr><tr><td>\n\nActivity Stream\n\n PRB1998124\n\n</td><td>\n\nActivity stream citations cause an increased page load time\n\n</td><td>\n\n \n\n</td><td>\n\n1.  Navigate to an instance.\n2.  Open Service Operations Workspace.\n3.  Open any incident record with a large amount of activity stream entries \\(~2000 entries\\).\n4.  Open the browser's dev tools window.\n5.  Select the 'Performance' tab.\n6.  Select the **Record and reload** button.\n\n Expected behavior: The page load time shouldn't be affected by CitationHighlightBehavior.js and require less time.\n\n Actual behavior: The page takes about 6 seconds or more to fully load, and the 'Performance' tab displays that it is due to CitationHighlightBehavior.js.\n\n</td></tr><tr><td>\n\nAgent Chat\n\n PRB1989186\n\n</td><td>\n\nTaskUtilsSNC creates millions of sys\\_cs\\_collab\\_chat when collaborative chat is not enabled\n\n</td><td>\n\nThe sys prop com.glide.cs.collab.enabled is false on the instance, meaning collaborative chat is not enabled on the instance. Despite this, there are millions of sys\\_cs\\_collab\\_chat records created.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nAgent Chat\n\n PRB1990618\n\n</td><td>\n\nLive agent connection is not established with the utterance and **Contact** button for non-admin requestors\n\n</td><td>\n\nEven though there is an agent available online, the requestor sees no agents available in the Agent Workspace.\n\n</td><td>\n\n1.  Log in as an agent.\n2.  Mark the agent as online.\n3.  Log in as non-admin requestor.\n4.  Navigate to **/aix/employee/chat**.\n5.  Enter **Live agent**.\n\nNotice that no agent connection is established with the message 'Live agent engaged. Connecting you to a live agent now. Please hold while I transfer you to a human support representative' on the client side.\n\n6.  Select **Support**.\n\n Expected behavior: The live agent is connected and the work item is displayed in the Agent workspace.\n\n Actual behavior: No agent is available, even when the agent is available in the workspace.\n\n</td></tr><tr><td>\n\nAgent Chat\n\n PRB1997855\n\n</td><td>\n\nUpgrade the i18n library to support the BCP-47 variant\n\n</td><td>\n\nThe replacement library should support the broad specification requirements set out in IANA BCP-47, which include language, script and territory codes. This is a large file, so the library chosen may opt to contain a smaller subset.\n\n</td><td>\n\n1.  Have Dynamic Translation set up on Agent Chat.\n2.  Start a conversation with language 'fq'.\n\n Expected behavior: On the agent side, observe a message 'Message will be automatically translated from Canadian French'.\n\n Actual behavior: The language isn't displayed at all, or in some cases, the region code isn't correctly handled.\n\n</td></tr><tr><td>\n\nAgent Chat\n\n PRB2004301\n\n</td><td>\n\nAI agent prioritization is not functioning correctly when the 'Include AI Agents' option is enabled\n\n</td><td>\n\n \n\n</td><td>\n\n1.  Install glide.awa and nowassist-ai-agents plugins on a Zurich or Australia instance.\n2.  Enable 'Include AI Agents' for a assignment rule which has both AI agent and manual agents.\n3.  Start a incident.\n\n Observe that incident is not assigned to an AI agent as preference even though it is available.\n\n</td></tr><tr><td>\n\nAI Agents \\(Glide Family\\)\n\n PRB1981261\n\n</td><td>\n\nMake agent and tool columns non-mandatory in sn\\_aia\\_agent\\_tool\\_m2m and fix the empty cacheconfig name issue\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nAI Agents \\(Glide Family\\)\n\n PRB1997916\n\n</td><td>\n\nThe extra 'response' layer in the JSON input passed by the agent to a scripted tool, causing performance issues\n\n</td><td>\n\nThe final tool of creating the regulatory change tasks expects the input to be in the format - \\{ 'finalPlan\\_json': \\{...\\}, 'finalPlan\\_html': '...' \\} But with the latest code one 'response' layer is added, which causes performance issues.\n\n</td><td>\n\nScenario 1:\n\n 1.  Log in to an instance.\n2.  Navigate to **/now/risk/compliance/record/sn\\_grc\\_reg\\_change\\_regulatory\\_feed**.\n3.  Open a record.\n4.  Navigate to **AskNowAssist** &gt; **Get action plan**.\n5.  Select **Yes** after the action plan is displayed.\n\n Notice that number of regulatory tasks in the related list doesn't change, tasks are not being created.\n\n Scenario 2:\n\n 1.  Create a skill tool that outputs a JSON object.\n2.  Create a script tool that takes the skill output JSON as input.\n3.  Return that input as is for displaying in VA.\n\n Expected behavior: The JSON object returned by the skill tool should display in VA.\n\n Actual behavior: The JSON object will be wrapped/contained in a format like this: \\{ response: \\{ model\\_output: 'actual JSON object' \\}\\}\n\n</td></tr><tr><td>\n\nAI Agents \\(Glide Family\\)\n\n PRB2001188\n\n</td><td>\n\nTrue-up 6.0 to Australia\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nAI Agents \\(Glide Family\\)\n\n PRB2002014\n\n</td><td>\n\nData to glide from offglide is not logged with the actual user\n\n</td><td>\n\nWhen the user makes a set cache call to glide from offglide, they observe that any record updated or created does not have an actual user in the **created\\_by** or **updated\\_by** field.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nAI Agents \\(Glide Family\\)\n\n PRB2004770\n\n</td><td>\n\nThe worker\\_manager should be able to create/update AI User records\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nAI Search \\(glide\\)\n\n PRB1925238\n\n</td><td>\n\nAI Search should reuse the filter generated for each request instead of generating a filter again each time\n\n</td><td>\n\nThe pre-processing time with Genius Results takes more time.\n\n</td><td>\n\n1.  Navigate to **Search preview**.\n2.  Select a profile.\n3.  Perform a search.\n4.  Record the pre-processing time for search.\n5.  Navigate to that profile.\n6.  Remove all the Genius Result \\(GR\\) configurations.\n7.  Re-run the search in the 'Search' preview.\n8.  Observe the pre-processing time.\n\n Expected behavior: The pre-processing time with GR as opposed to without GR isn't different since the filter generated from the first request is being used.\n\n Actual behavior: The pre-processing time is more than double with GR.\n\n</td></tr><tr><td>\n\nAI Search \\(glide\\)\n\n PRB1988725\n\n</td><td>\n\nThe non-standard role name causes the KB not to be returned in early binding\n\n</td><td>\n\nThe KB is not returned when performing the search as a non-admin user.\n\n</td><td>\n\n1.  Open a base instance.\n2.  Create a non-stardard role containing an uppercase letter and space, such as 'CSC - Knowledge'.\n3.  Create a KB.\n4.  Fill the **Role** field with 'CSC - Knowledge'.\n5.  Perform a search as a non-admin user targeting that KB.\n\n Expected behavior: The KB is returned.\n\n Actual behavior: The KB is not returned.\n\n</td></tr><tr><td>\n\nAI Search \\(glide\\)\n\n PRB1989537\n\n</td><td>\n\nNew tables added in Knowledge Graph AI Search pipeline\n\n</td><td>\n\nNew tables added: sn\\_kg\\_tag\\_table, sn\\_kg\\_tag\\_column, sn\\_kg\\_tag\\_table\\_instruction, and sn\\_kg\\_tag\\_column\\_instruction.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nAI Search \\(glide\\)\n\n PRB1990639\n\n</td><td>\n\nLate binding API check doesn't work for child tables\n\n</td><td>\n\nThe log contains entries like '\\[ais\\] AclFilterGenerator: Exception during converting ACL for table kb\\_template\\_faq, use late-binding'.\n\n</td><td>\n\n1.  In ais\\_datasource, set 'force\\_late\\_binding' for KB to true.\n2.  Make sure KB plugins are installed to get child tables.\n3.  Run search using a profile that has KB as the search source.\n\n Observe that the log contains entries like '\\[ais\\] AclFilterGenerator: Exception during converting ACL for table kb\\_template\\_faq, use late-binding'. When the user sets force\\_late\\_binding to true, the KB and its child table ACLs should not be translated to filters.\n\n</td></tr><tr><td>\n\nAI Search \\(glide\\)\n\n PRB1991218\n\n</td><td>\n\nAny portal should be able to enable hybrid search\n\n</td><td>\n\nWhen the user tries to enable hybrid search on global search, enablement is blocked.\n\n</td><td>\n\nTry to enable hybrid search on global search.\n\n Observe that enablement is blocked.\n\n</td></tr><tr><td>\n\nAI Search \\(glide\\)\n\n PRB1992181\n\n</td><td>\n\nThere should be a secondary index in AI search\n\n</td><td>\n\nThere should be an auxiliary index in AIS to store pre-generated questions and the corresponding docs. This will help in improving the recall for search and suggesting queries as a user types.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nAI Search \\(glide\\)\n\n PRB1996321\n\n</td><td>\n\nAn AI Search dynamic filter makes two calls \\(one extra call\\) when filters are applied, and in the second call, additionalContext is null and doesn't return correct counts on pre-processing\n\n</td><td>\n\nWhen filters are set to the empty array, the additional call doesn't happen and it works as expected. The issue happens when filters are set.\n\n</td><td>\n\n1.  Implement AISDynamicFilter pre-processing.\n2.  Make an AI Search call by setting filters and passing additional context.\n\n Observe that an additional call is happening per search source. For the second call, the additionalContext value is null even though the additionalContext is passed as parameter to AI Search API call. If filters aren't applied, then the additional call doesn't happen. It happens when filters are applied and additionalContext is null when it should not be.\n\n</td></tr><tr><td>\n\nAI Search External User Mapping API\n\n PRB1916303\n\n</td><td>\n\nExternal Content REST API external\\_content/importUserPrincipals/\\{target\\_table\\}/\\{source\\_id\\} doesn't honor updates\n\n</td><td>\n\nThe first insert is not honored unless there is more than one group.\n\n</td><td>\n\n1.  Using v4 ingestion API, import the user principals payload.\n2.  Import user mapping.\n\nNotice the first one honors groups and user insert.\n\n3.  Update the payload to include another group.\n4.  Send POST.\n\nObserve that a group or user will be missing from the update.\n\n5.  Delete the user mapping, user script above with single group and user mapping =.\n6.  Send POST.\n\n Observe that the first insert is not honored unless more than one group is present.\n\n</td></tr><tr><td>\n\nAI Search\n\n PRB1796676\n\n</td><td>\n\nUsers can't create a custom AI Search matcher on an indexed column with an aliased column name\n\n</td><td>\n\nIt's not allowed by the business rule 'Verify index for exact match field'.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nAI Search\n\n PRB1822229\n\n</td><td>\n\nQuery Performance metrics are down because it is polluted with the Genius Result configuration, making it difficult to find required information\n\n</td><td>\n\nWhen logging performance time breakdown, E2E search takes more than 5 seconds forais\\_long\\_query\\_log. There are missing crucial performance metrics breakdown, and is polluted with Genius Result pre-processing and post-processing scripts.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nAI Search UX\n\n PRB1988802\n\n</td><td>\n\nadditionalContext is not passed through the Suggestions GQL API to AI Search, preventing DynamicFilters from working for Virtual Agent \\(VA\\) skills\n\n</td><td>\n\nWhen additionalContext is passed from the client to the Suggestions GQL API, it was not being threaded through the call chain to the AI Search Suggestion Reader. This causes DynamicFilters to not work properly, preventing VA Skills from being returned in suggestion results.\n\n</td><td>\n\nCall the Suggestions GQL API with additionalContext parameter containing DynamicFilter information.\n\n Observe that the VA Skills that should be filtered by DynamicFilters are not being properly filtered, and the additionalContext is lost in the call chain and never reaches the AI Search service where DynamicFilters are applied.\n\n</td></tr><tr><td>\n\nAI Search UX\n\n PRB1991226\n\n</td><td>\n\nSearch-based suggestions should have a user-friendly label for source\n\n</td><td>\n\n \n\n</td><td>\n\nCall the Suggestions GQL API with a term that will return search-based suggestions.\n\n Expected behavior: The payload has the source label field for user-friendly labels based on what is configured for the corresponding source's 'Source Facet Bucket' label on the Search Application.\n\n Actual behavior: There is no label based on the Source Facet Bucket.\n\n</td></tr><tr><td>\n\nAI Search UX\n\n PRB1994511\n\n</td><td>\n\nLabel in header-section\\_\\_identifier-container does not reflow\n\n</td><td>\n\nThe labels in div class 'header-section\\_\\_identifier-container' are truncated at 200% and 400%.\n\n</td><td>\n\n1.  Open a base instance with AI Search.\n2.  Navigate to /sp?id=search and search for something that will return results \\(for example, email, device\\).\n3.  Set your window size to 1280x1024.\n4.  Zoom in to 200% and 400%.\n\n Expected behavior: Content is not cut off at 200% and 400% zoom\n\n Actual behavior: Content is cut off at 200% and 400% zoom\n\n</td></tr><tr><td>\n\nAnalytics Export API\n\n PRB1995410\n\n [KB2810683](https://hi.service-now.com/kb_view.do?sysparm_article=KB2810683)\n\n</td><td>\n\nOn demand list visualization export to .xlsx\n\n</td><td>\n\nAn issue has been identified where on-demand exports of list data visualizations intended for XLSX format are instead exported as XLS files in the Zurich environment. This behavior differs from the Yokohama environment, which previously exported successfully in XLSX format.\n\n</td><td>\n\nRefer to the listed KB article for details.\n\n</td></tr><tr><td>\n\nApplication Manager\n\n PRB1971605\n\n</td><td>\n\nThe base version is grayed out in the new Application Manager\n\n</td><td>\n\nThe base version is grayed out in the new Application Manager, which stops to install the custom version created on the base version 1.0.0. The new Application Manager allows to install the custom version only on the latest version.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nApplication Manager\n\n PRB1971790\n\n [KB2827137](https://hi.service-now.com/kb_view.do?sysparm_article=KB2827137)\n\n</td><td>\n\nThe size of the cache string is over 33.55MB, the GAAA response is too large to save as attachment.\n\n</td><td>\n\nPost-release of killing entitlements, the large get\\_all\\_available\\_apps \\(GAAA\\) response is breaking the checkAvailableUpdates call in the UpdateChecker. Until the get\\_all\\_available\\_apps response size is reduced below the ~32MiB limit, the App Manager will continue to have cache issues.\n\n</td><td>\n\nRefer to the listed KB article for details.\n\n</td></tr><tr><td>\n\nApplication Rationalization\n\n PRB1990444\n\n</td><td>\n\nThe **Update Hierarchies** button shuffles the hierarchy randomly for sub-capabilities\n\n</td><td>\n\nIn the Enterprise Architecture Workspace \\(EAW\\), the **Update Hierarchies** button shuffles the hierarchy randomly for sub-capabilities when it updates for the first time.\n\n</td><td>\n\n1.  Navigate to **EAW** &gt; **Business portfolio**.\n2.  Create a sub-capability for some parent capability.\n3.  Add a few sub-capabilities \\(with names like Test 1, Test 2, Test 3, etc.\\).\n\nNotice that the capability is added to the bottom.\n\n4.  Select **Update Hierarchies**.\n5.  Refresh the page.\n\nNotice that the order of capabilities changed randomly.\n\n6.  Delete the current sub-capabilities.\n7.  Complete steps 2-5 again \\(add capabilities with the same names and order again\\).\n\n Notice that the order changes again and doesn't follow any logic.\n\n</td></tr><tr><td>\n\nAsset Management\n\n PRB1990771\n\n</td><td>\n\nAsset Analyst UI changes\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nAsset Management\n\n PRB1992982\n\n</td><td>\n\nQuery-range ACLs not present asset\\_parallel\\_job, ast\\_execution\\_queue and sn\\_hamp\\_import\\_files tables\n\n</td><td>\n\nThere are missing query\\_range ACLs on ast\\_execution\\_queue and asset\\_parallel\\_job tables, which are used by the Asset Management parallel job framework for task execution and worker coordination. Without query\\_range ACLs, the parallel job framework could experience access denied errors when querying task queues, causing job execution failures, performance issues, and broken monitoring functionality.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nAttachments to Records\n\n PRB1998825\n\n</td><td>\n\nRCA is generated from the script include 'AttachmentSensitive' and UI Page: attachment\n\n</td><td>\n\n \n\n</td><td>\n\n1.  Impersonate Abel Tuter.\n2.  Navigate to **sn\\_hr\\_core\\_case\\_workforce\\_admin.do?sys\\_id=**.\n3.  Select the **Manage attachment** icon.\n4.  Add an attachment.\n\n Observe the two RCAs generated Source as 'UI Page: attachment' and 'Script Include: AttachmentSensitive'.\n\n</td></tr><tr><td>\n\nAuthentication Factors\n\n PRB2002405\n\n</td><td>\n\nKBA using external sources\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nAuthentication Factors\n\n PRB2002406\n\n</td><td>\n\nVoice input for authentication parameters for non-KBA\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nAuthentication\n\n PRB1990715\n\n</td><td>\n\nToken Exchange API for Voice Service Agent\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nAutomated Test Framework \\(ATF\\)\n\n PRB1981503\n\n</td><td>\n\nRace condition for frontend coverage persistence and aggregation calculations\n\n</td><td>\n\nSometimes the frontend aggregation data is not accurate.\n\n</td><td>\n\n1.  Run an ATF test with a modified client script and UI action.\n2.  Immediately after the test ends, select **Calculate code coverage** on the test result page.\n\n Observe that sometimes the frontend aggregation data is not accurate, as all the code coverage from the frontend hasn't been fully processed and persisted.\n\n</td></tr><tr><td>\n\nAutomated Test Framework \\(ATF\\)\n\n PRB1997825\n\n [KB2806020](https://hi.service-now.com/kb_view.do?sysparm_article=KB2806020)\n\n</td><td>\n\nWhen the 'glide.script.block.client.globals' property is set to false, running an ATF test throws a client error with code coverage enabled\n\n</td><td>\n\n \n\n</td><td>\n\nRefer to the listed KB article for details.\n\n</td></tr><tr><td>\n\nBenchmarks\n\n PRB2000082\n\n</td><td>\n\nSuccess dashboard and benchmark Australia true up\n\n</td><td>\n\nTrue up versions for the Success Dashboard in Australia: itsm-analytics, app-benchmarks, success-dashboard-common, success-dashboard-core, and success-dashboard-itsm. This change is being made so that the ITSM licensing changes that are for Core ITSM would work as expected.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nBuild Agent \\(glide\\)\n\n PRB1997824\n\n</td><td>\n\nBase instance app issue blocks NAFC installation\n\n</td><td>\n\nNow Assist for Creator \\(NAFC\\) can't be installed because the BA app is not included as part of distribution.\n\n</td><td>\n\n1.  License NAFC for an Australia instance.\n2.  Attempt to install.\n\n Observe that it can't be installed because the BA app is not included as part of distribution.\n\n</td></tr><tr><td>\n\nBuild Agent \\(glide\\)\n\n PRB2002327\n\n</td><td>\n\nKeyword search returns full field content instead of relevant passages, causing excessive token consumption\n\n</td><td>\n\nThe keyword search handler returns content fields in their entirety or applies a naive substring from the start of the field. It has no awareness of where query terms actually appear in the text. For large fields \\(**Script**, **XML**, **Template**\\), the relevant matching content is often beyond what is returned and is discarded.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nBuild Agent \\(glide\\)\n\n PRB2002763\n\n</td><td>\n\nBuild Agent \\(BA\\) freemium install is blocked to due to hosted plugin, due to which NAFC install is incomplete\n\n</td><td>\n\nThe BA trial version fails to install due to the missing hosted plugin.\n\n</td><td>\n\n1.  Provision an Australia instance.\n2.  Navigate to Application Manager.\n3.  Select the **Sync Now** button.\n4.  Search Now Assist For Creator.\n5.  Select **Install**.\n\n Notice that the install is successful, but the **Install** button is still active because BA trial version fails due to the missing hosted plugin com.glide.app\\_build\\_agent\\_core.global.\n\n</td></tr><tr><td>\n\nCache\n\n PRB1991677\n\n</td><td>\n\nThe support for bulk loaded caches and unused entries cache should be removed\n\n</td><td>\n\nThis is to disable the bulk-loaded caches from CacheReplication, which causes large amounts of traffic.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nCache\n\n PRB1993310\n\n</td><td>\n\nQuery\\_cache doesn't flush on all nodes\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nCase and Knowledge Management for HR Service Delivery\n\n PRB1963168\n\n</td><td>\n\nThe HRSD Knowledge Graph is unavailable after an upgrade\n\n</td><td>\n\nThere's an issue with the Now Assist Knowledge graph. The user receives the error 'An unexpected error occurred. Please try again.'\n\n</td><td>\n\n1.  Impersonate a user who has access to the HR Portal.\n2.  Navigate to the HR Portal.\n3.  Initiate a Virtual Agent Chat.\n4.  Enter the prompt: 'Show me my open HR cases'.\n\n Expected behavior: Information about the user's open HR Cases is displayed.\n\n Actual behavior: The user receives the error 'An unexpected error occurred. Please try again.'\n\n</td></tr><tr><td>\n\nCase and Knowledge Management for HR Service Delivery\n\n PRB1985492\n\n</td><td>\n\nNew RCA records for attachment summarization\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nCase and Knowledge Management for HR Service Delivery\n\n PRB1991031\n\n</td><td>\n\nAttachment Summary is not working when the HR case is transferred from one HR service to another service for Now Assist\n\n</td><td>\n\nAttachment Summary doesn't work on the new HR case with attachments after using **Transfer case**.\n\n</td><td>\n\n1.  Open an HR case.\n2.  Upload an attachment.\n\nObserve that attachment summarization is working fine.\n\n3.  Select **Transfer case** from the side menu.\n\nObserve that modal opens.\n\n4.  Choose any transfer type \\(for example, 'transfer to a new case number'\\) and any New HR service \\(for example, Dental Benefits Inquiry\\).\n5.  Select **Ok**.\n\nObserve that this HR case transfers to a new HR case, and all the attachments are also copied to new HR case.\n\n6.  Select **Summarize** on the new HR case.\n\nObserve that attachment summarization is not available even though HR case has attachments.\n\n\n Expected behavior: Attachment summarization works on the new HR case with attachments after using **Transfer case**.\n\n Actual behavior: Attachment summarization doesn't work after using **Transfer case** on the on new HR case with attachments.\n\n</td></tr><tr><td>\n\nCase and Knowledge Management for HR Service Delivery\n\n PRB1995357\n\n</td><td>\n\nNew RCAs from Knowledge Center to HR Core to use Open Prompt\n\n</td><td>\n\nIssues are observed when using the Open Prompt in HR Agent Workspace. Users try the Advanced Knowledge editor page in HR Agent Workspace. This page contains Open Prompt, which is interactable and helps create an article using Gen AI. For the Open Prompt to work without any issues, new RCAs are required.\n\n</td><td>\n\n1.  Provision an instance with the Knowledge Recommendation plugin and Article Optimization plugins installed.\n2.  From the Knowledge Management properties, turn on the ece.\n3.  Create an article from the related list of any HR case.\n\n There's an RCA from KC to HR core.\n\n</td></tr><tr><td>\n\nCase and Knowledge Management for HR Service Delivery\n\n PRB1997710\n\n</td><td>\n\nUpdate base instance sn\\_hr\\_po version to latest 6.0.3\n\n</td><td>\n\nFor customers upgrading from a lower version to the latest version, the changes aren't applied as all the files are present in apply-once folder. A glide-fix was created, and the new version needs to be trued-up and backported to Australia.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nChange Management\n\n PRB1997296\n\n</td><td>\n\nChange templates should be created from model\n\n</td><td>\n\n**Create new template** should be enabled only if a model is selected, and the model should be passed to the change model page for creation.\n\n</td><td>\n\n1.  Navigate to **All** &gt; **Change** &gt; **Create new**.\n2.  Select **More actions**.\n\nObserve that **Create new template** is enabled.\n\n3.  Select any model.\n\n Observe that **Create new template** is disabled.**Create new template** should be enabled only if a model is selected, and the model should be passed to the change model page for creation.\n\n</td></tr><tr><td>\n\nChange Management\n\n PRB1997298\n\n</td><td>\n\nCreate change page in UI16 has the wrong color background\n\n</td><td>\n\nThe background of the create page is colored in Polaris and Coral themes. It should be neutral and match other pages.\n\n</td><td>\n\nNavigate to **All** &gt; **Change** &gt; **Create new**.\n\n Observe that the background of the create page is colored in Polaris and Coral themes.\n\n</td></tr><tr><td>\n\nCMDB CI Class Models\n\n PRB1996229\n\n</td><td>\n\nAdding default values takes 4.5 hours during upgrade\n\n</td><td>\n\nUpgrading a clone from Zurich to Australia takes over 13 hours; a default value alone takes 4.5 hours. The table is cmdb\\_ci\\_vm\\_object, the field is **persistence\\_type**, and the default value they're setting is unknown.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nCMDB Identification and Reconciliation\n\n PRB1997526\n\n</td><td>\n\nLRU eviction and dynamic IRE cache\n\n</td><td>\n\nDynamic IRE doesn't realize that some of its elements have been LRU evicted and doesn't attempt to rebuild the cache.\n\n</td><td>\n\n1.  Run dynamic IRE so that the cache gets initialized.\n2.  Evict some of dynamic IRE's keys from the cache manually.\n3.  Try and retrieve the evicted member from cache.\n\n Observe that dynamic IRE runs as though that element was never configured and does not exist.\n\n</td></tr><tr><td>\n\nColumn Level Encryption\n\n PRB1990541\n\n</td><td>\n\nAttachment upload defaults to 'None' encryption module in the workspace\n\n</td><td>\n\nAttachment upload defaults to 'None' encryption module in the workspace, where as in Classic View its working as expected.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nCondition Builder in Core UI\n\n PRB1991606\n\n</td><td>\n\nCondition builder can't interpret encodedQuery\n\n</td><td>\n\nThe condition builder conditions aren't rendered. When other fields in the form are updated \\(**Description**, **Name**, etc.\\), the condition is erased from the record.\n\n</td><td>\n\n1.  Create a new glide record on sys\\_archive table using a glide script.\n2.  Navigate to /sys\\_archive\\_list.do?sysparm\\_query=tableSTARTSWITHtask.\n3.  Find the archive rule with the name 'Created from glide script'.\n4.  Open the rule.\n\n Observe that the condition builder conditions aren't rendered. When other fields in the form are updated \\(**Description**, **Name**, etc.\\), the condition is erased from the record.\n\n</td></tr><tr><td>\n\nConfiguration Management Database \\(CMDB\\)\n\n PRB1814757\n\n</td><td>\n\nIn CI Class Manager, users without the application picker can't update entries associated with tables outside the global scope\n\n</td><td>\n\nLogic was added to block an update if the user scope and table scope don't match. This is correct behavior for an admin or developer, which has an application picker available, but other users operate in the global scope and therefore can't make updates. For such users, rather than block the update, the backend should instead default to the correct target scope.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nConfiguration Management Database \\(CMDB\\)\n\n PRB2000234\n\n</td><td>\n\nThe scoped scriptable API to convert an LLM's output from Text 2 Query to QB executable output\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nConfiguration Management Database \\(CMDB\\)\n\n PRB2000235\n\n</td><td>\n\nData structures that allow assembling Query Builder JSON in a script from an LLM response\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nContent Governance\n\n PRB1985066\n\n</td><td>\n\nUnable to reject Content Request Item \\(CRI\\)\n\n</td><td>\n\nApprovers cannot reject the CRI and it remains in a 'Requested' state.\n\n</td><td>\n\n1.  Install sn\\_cg and sn\\_cp.\n2.  Create a Content Request and CRI.\n3.  Add any content and schedule the content request item.\n4.  Add Abel Tutor as approvers to the CRI using 'Manage approvers'.\n5.  Move the CRI status to 'In Review'.\n6.  Impersonate the user 'Abel Tutor'.\n7.  Navigate to **hrm\\_todos\\_page**.\n8.  Find the CRI and reject it.\n\n Expected behavior: The approver can approve or reject the CRI successfully.\n\n Actual behavior: There is a console error on the page, and the CRI is not getting rejected and remains in a 'Requested' state.\n\n</td></tr><tr><td>\n\nContent Publishing\n\n PRB1897913\n\n</td><td>\n\n**Insert and Stay** doesn't capture changes when inserting for a new record\n\n</td><td>\n\nThe issue is specific to the Content Publishing package. The user reports **Insert and Stay** doesn't capture changes when inserting for new record. The new record still has previous values, leading to a degraded experience.\n\n</td><td>\n\n1.  Ensure that the Content Publishing package is installed.\n2.  Navigate to the sn\\_cd\\_content\\_portal list view.\n3.  Open any existing content type: URL - record.\n4.  Change the **Title** value.\n5.  Navigate to **Context Menu** &gt; **Insert and Stay**.\n\n Expected behavior: The changes should be captured and established in the new record.\n\n Actual behavior: It does not. Previous values are retained.\n\n</td></tr><tr><td>\n\nContent Publishing\n\n PRB1963246\n\n</td><td>\n\nIssue with content template duration calculation with a different date format\n\n</td><td>\n\nIf the user changes the date format in sys\\_property, content template duration calculation is ignored since calculation looks for specific date format of 'yyyy-DD-mm'.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nContent Publishing\n\n PRB1967769\n\n</td><td>\n\nAdd RCAs and KG Tag for querying News/Company Event content in Now Assist Virtual Agent \\(NAVA\\) for Now Assist for EC Pro\n\n</td><td>\n\nEnsure that the necessary RCAs and provided and approved so that NAVA returns a response.\n\n</td><td>\n\n1.  Navigate to **Knowledge Graph Tag** to create a new record.\n2.  Add relevant Content Publishing tables.\n3.  Provide a description for KG Tag.\n4.  **Save**.\n5.  Navigate to **Conversational Interfaces** &gt; **Assistants**.\n6.  Select **Manage Assistants** &gt; **Now Assist in Virtual Agent** &gt; **Information sources** &gt; **Knowledge Graph**.\n7.  Set 'Natural Language Query' with Enterprise Graph.\n8.  Under Tags, add the created tag from step 3.\n9.  **Save**.\n10. Create some sample news articles / company events.\n11. Navigate to **/esc** to ask NAVA simple queries on news, such as 'Show me a news article' or 'Show me a company event.'\n\n Observe that any RCA's necessary are provided/approved, and NAVA returns a response.\n\n</td></tr><tr><td>\n\nContent Publishing\n\n PRB1980740\n\n</td><td>\n\nNotification email content sends with an empty body when Content Analytics is not installed\n\n</td><td>\n\nThe subject is empty when it should be filled out, and the email body is 'undefined' in HTML.\n\n</td><td>\n\n1.  Navigate to **Content Publishing** &gt; **Create New** &gt; **Notification** &gt; **Email**.\n2.  Fill out the required details.\n3.  Add some rich text to the body.\n4.  Save and create a schedule content to send the email.\n5.  Check that the email was logged in the event queue with a valid parm2 value of the email body.\n6.  Navigate to **System Log** &gt; **Email**to find the record in the email logs once it's processed.\n\n Expected behavior: The subject is filled out as the email content title, along with a valid non-empty body\n\n Actual behavior: The subject is empty and email body has 'undefined' value in the HTML.\n\n</td></tr><tr><td>\n\nData Archiving to Object Store\n\n PRB1988599\n\n</td><td>\n\nMigrating small archive tables to columnar is not an efficient use of RaptorDB capabilities\n\n</td><td>\n\n \n\n</td><td>\n\n1.  Set up an instance for archive table migration.\n2.  Start the migration.\n\n Expected behavior: Only archive tables which meet a TBD threshold should be migrated. There should be a scheduled job to look for tables which were previously skipped, but can now be migrated.\n\n Actual behavior: All archive tables are migrated immediately.\n\n</td></tr><tr><td>\n\nData Archiving to Object Store\n\n PRB1999471\n\n [KB2820738](https://hi.service-now.com/kb_view.do?sysparm_article=KB2820738)\n\n</td><td>\n\notherBlobsInChunkExist includes non-storage fields in coordinate comparison, causing premature S3 object deletion\n\n</td><td>\n\nThe Archive Destroy job permanently removes archived records after they've aged past a configured retention period. It encounters a software defect that causes it to get stuck in a loop, repeatedly failing on the same set of records.\n\n</td><td>\n\nRefer to the listed KB article for details.\n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Access\n\n PRB1823749\n\n</td><td>\n\nIn GraphMetadataAPI, node/edge types should allow special characters\n\n</td><td>\n\nAn error appears that says only alphanumeric and underscore characters are supported.\n\n</td><td>\n\nWith JSON or GraphMetadataBuilder, create an edge with type 'Depends On:Used By'.\n\n Observe the error that says only alphanumeric and underscore characters are supported.\n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Access\n\n PRB1891525\n\n</td><td>\n\nError appears when querying overridden node in child graph\n\n</td><td>\n\nThe parent graph has a node with node\\_type as 'sys\\_user'. The child graph has a node with node\\_type 'User', which overrides the parent graph node. When the user tries to execute the cypher query, an error appears: 'java.lang.NullPointerException: Cannot invoke 'org.json.JSONObject.getString\\(String\\)' because 'sourceNode' is null'.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Access\n\n PRB1909452\n\n</td><td>\n\nScriptable GraphMetadata returns an unclear error message when KG's global graph \\(an extended graph\\) is run on the wrong scope\n\n</td><td>\n\nThe NullPointerException error message can be confusing. To troubleshoot the problem, the user should check if the graph exists or check if they're on matching scope.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Access\n\n PRB1932176\n\n</td><td>\n\nOutOfMemoryError when attempting to update the graph with as a parent graph\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Access\n\n PRB1942189\n\n</td><td>\n\nError message doesn't say that adding a WDF table with no primary key isn't allowed\n\n</td><td>\n\nThe error message says 'Error: Table named u\\_df\\_wdf\\_without\\_pk is not allowed in graph schema.' The user may not know that WDF with primary key is a qualification to be considered in KG.\n\n</td><td>\n\n1.  Create a data fabric table with no primary key.\n2.  Try to create a knowledge graph with that data fabric table.\n\n Expected behavior: An error message says that WDF tables with no primary key aren't allowed on the graph.\n\n Actual behavior: The error message says 'Error: Table named u\\_df\\_wdf\\_without\\_pk is not allowed in graph schema.' The user may not know that WDF with primary key is a qualification to be considered in KG.\n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Access\n\n PRB1960120\n\n</td><td>\n\nIn GraphQueryBuilder, an encoded query string with a blank value for the **int** field gives cytosm exception\n\n</td><td>\n\n \n\n</td><td>\n\n1.  Add the encoded query string 'priority=3^state' to the incident node.\n2.  Execute the query from GraphQueryBuilder.\n\n Observe the cytosm exception.\n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Access\n\n PRB1960791\n\n</td><td>\n\nIncorrect cypher results for the union of two different nodes with same return fields using glideRecordDynamic\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Access\n\n PRB1963974\n\n</td><td>\n\nAdd support for getJournalEntry for xglideRecordDynamic\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Access\n\n PRB1967640\n\n</td><td>\n\nClean up the dangling temp table\n\n</td><td>\n\ndbi.truncateTable\\(\\) which was fixed by PRB1820374, but created a dangling temp table without cleaning up.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Access\n\n PRB1967659\n\n</td><td>\n\nGraphQueryBuilder fails for a specific case with dot-walking in encoded in the query condition value\n\n</td><td>\n\nThis issue occurs with the table 'Incident' and the encoded query 'caller\\_id.sys\\_created\\_onSAMEASassigned\\_to.sys\\_created\\_on@week'.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Access\n\n PRB1968921\n\n</td><td>\n\nCount\\(\\*\\) throws an exception for Workflow Data Fabric tables\n\n</td><td>\n\nIt works fine with glide tables.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Access\n\n PRB1968949\n\n</td><td>\n\nParent edges aren't inherited for children\n\n</td><td>\n\nParent edges aren't inherited for children, but properties are inherited. For example, task edges aren't coming for an incident.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Access\n\n PRB1970704\n\n</td><td>\n\ngetJournalEntry not working when executed through javascript\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Access\n\n PRB1973087\n\n</td><td>\n\nGraphMetadata.get\\(\\) should respect node type to table migration\n\n</td><td>\n\nCached JSON is returned with node\\_type and the custom node type is given.\n\n</td><td>\n\n1.  Create a graph without specifying migratedToTable flag and custom node type \\(for example, User\\).\n2.  Specify migratedToTable flag.\n3.  Call get\\(\\) method.\n\n Expected behavior: The node\\_type should be the table name \\(for example, sys\\_user\\) and the custom node type \\(for example, user\\) should be given as a synonym.\n\n Actual behavior: Cached JSON is returned with node\\_type. The custom node type is given.\n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Access\n\n PRB1973286\n\n</td><td>\n\n'getForTables' throws an exception if table doesn't exist on the anowassist instance\n\n</td><td>\n\nThis causes Enterprise Graph to break.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Access\n\n PRB1977551\n\n</td><td>\n\nA few queries break with function not allowed error\n\n</td><td>\n\nThe queries were tested with strict security turned on and turned off, and they don't work in both cases.\n\n</td><td>\n\nRun any of the following queries:\n\n -   Select top 10 log\\(cost\\) from cmdb where cost != 0;\n-   Select top 10 log10\\(cost\\) from cmdb where cost !=0;\n-   Select top 10 mod\\(priority,2\\) from incident;\n-   Select top 10 repeat\\(first\\_name,2\\), first\\_name from sys\\_user;\n-   Select top 10 replace\\(first\\_name,''a'',''ba''\\), first\\_name from sys\\_user;\n-   Select top 10 right\\(first\\_name,2\\), first\\_name from sys\\_user;\n-   Select top 10 second\\(sys\\_created\\_on\\), sys\\_created\\_on from incident;\n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Access\n\n PRB1979253\n\n</td><td>\n\nReturn a value from GRD::getTableName\n\n</td><td>\n\nIt throws a NullPointerException error.\n\n</td><td>\n\nExecute the script.\n\n Notice that a NullPointerException error is thrown.\n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Access\n\n PRB1980455\n\n</td><td>\n\nSharing permissions are not enabled for newly created documents for the upgrade customer in the DMS Component\n\n</td><td>\n\nMultiple issues are observed: 1\\) Permissions are not enabled for newly created documents. 2\\) The version attachment size is not displaying. 3\\) There are improper error messages occur for missing permission configurations. 4\\) Attachments from Cloud are not working from the Connect External Cloud Check.\n\n</td><td>\n\nScenario 1:\n\n 1.  Log in to the instance.\n2.  Configure the Now Document component.\n3.  Navigate to **Service Operations Workspace \\(SOW\\)**.\n4.  Open any existing incident.\n5.  Create a document.\n6.  Select secondary actions, such as **Edit Metadata**.\n\n Expected behavior: Sharing permissions are enabled for newly created documents for Upgrade customers in the DMS component.\n\n Actual behavior: Sharing permissions are not enabled for newly created documents for Upgrade customers in the DMS component.\n\n Scenario 2:\n\n 1.  Log in to the instance.\n2.  Configure the Now Document component.\n3.  Navigate to **SOW**.\n4.  Open any existing incident.\n5.  Create a document through the Document component.\n6.  Select secondary actions, such as **Track Versions**.\n7.  Upload any attachment to create a version.\n\n Expected behavior: Version attachment size appears in the component.\n\n Actual behavior: Version attachment size is not appearing.\n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Access\n\n PRB1986124\n\n</td><td>\n\nFilter are not getting applied on the query, 'Give me name, company name and department name of users'\n\n</td><td>\n\nFilters are not getting applied on C2R, and returning records for department is not empty and company is not empty.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Access\n\n PRB1986459\n\n</td><td>\n\nThe 'Add OR Clause' with multiple filters is not working as expected\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Access\n\n PRB1986877\n\n</td><td>\n\nGraph JSON cache should respect the 'isTieredCachingEnabledForCacheable' property value\n\n</td><td>\n\nGraphCacheableJSONString should be used for a tiered cache instead of a regular cache.\n\n</td><td>\n\n1.  Disable tiered caching.\n2.  Call new sn\\_db.GraphMetadata\\(''graphName''\\).get\\(\\).\n\n Expected behavior: The tiered cache with GraphCacheableJSONString isn't used.\n\n Actual behavior: The GraphCacheableJSONString wrapper is used even though the value is in a regular cache.\n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Access\n\n PRB1987871\n\n</td><td>\n\nAdd API to get the display column name from Table Descriptor\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Access\n\n PRB1990139\n\n</td><td>\n\nKnowledge Graph support\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Access\n\n PRB1990516\n\n</td><td>\n\nWDF queries are not returning a response when result limit API option is passed\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Access\n\n PRB1997902\n\n</td><td>\n\nDatabaseView:extractTable doesn't properly handle views with selective fields included in them\n\n</td><td>\n\n \n\n</td><td>\n\n1.  Create a view with an explicit set of fields from a table.\n2.  Run extractTable.\n\n Observe the value for one of the fields that wasn't included in the view.\n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Access\n\n PRB1998050\n\n</td><td>\n\nglide-side changes for label population in picker tables\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Access\n\n PRB1999075\n\n</td><td>\n\nReparents are processed too late\n\n</td><td>\n\nThis is failing the validations in TableParentChange.java where it's ensured that table parents are only triggered during an upgrade. Thus, the re-parent attempts are aborted.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Management\n\n PRB1995171\n\n</td><td>\n\nSubject tests fail on MariaDB on track/datamanagement\n\n</td><td>\n\nColumnarTableSwapConsumerTest.verifyAccepting and DBColumnarOnlineAlterTest.verifyMigratingTable\\_ThrowsException unit tests fail on MariaDB.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Scale\n\n PRB1910342\n\n</td><td>\n\nHanding RR candidates present in glide.db.properties\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Scale\n\n PRB1987583\n\n</td><td>\n\nIllegalThreadStateException when restarting the AHAMonitor thread\n\n</td><td>\n\nThe AHAMonitor.start\\(\\) method throws IllegalThreadStateException when attempting to restart the monitor after it has been stopped and the thread has terminated.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Scale\n\n PRB1990629\n\n</td><td>\n\nArchive table dictionary entries are left in an inconsistent state after migration to RaptorDB\n\n</td><td>\n\nThe max length of the archive table dictionary length entry matches the actual SQL length.\n\n</td><td>\n\nMigrate an instance to RaptorDB.\n\n Expected behavior: The max length of the archive table dictionary length entry is mismatched with the actual SQL length.\n\n Actual behavior: The max length of the archive table dictionary length entry matches the actual SQL length.\n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Scale\n\n PRB1990845\n\n</td><td>\n\nPrevent aha-monitor starting in head-less glide node\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Data Scale\n\n PRB1999067\n\n</td><td>\n\nTopologyManager should demote after timeout when the DB is not available\n\n</td><td>\n\nTopologyManager should demote itself after a timeout if it can't participate in the elections.\n\n</td><td>\n\n1.  Create a FAILOVER request.\n2.  Attempt to slowdown the new PRI promotion by 60 seconds.\n\n Notice that glide side considers this as operation timed-out, and does not compute any new topology or detects the next failover.\n\n</td></tr><tr><td>\n\nDatabase Persistence - Graph\n\n PRB1947688\n\n</td><td>\n\nDatetime doesn't work with WDF tables\n\n</td><td>\n\nIf the user runs a query that uses datetime, it doesn't return any results.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Graph\n\n PRB1952043\n\n</td><td>\n\nUnable to create sys\\_meta\\_graph\\_edge record properly with source node and target node selected\n\n</td><td>\n\nThe nodes can't be selected from the UI or directly imported from the attachment.\n\n</td><td>\n\n1.  Create a sys\\_meta\\_graph record with two nodes added.\n2.  Create an edge between these two nodes.\n3.  Try to select the two nodes as source and target node.\n\n Observe that the nodes can't be selected from the UI or directly imported from the attachment.\n\n</td></tr><tr><td>\n\nDatabase Persistence - Graph\n\n PRB1973162\n\n</td><td>\n\nAnowassist has a huge prompt for KG\\(6.0.6\\) invocation, causing high processing times\n\n</td><td>\n\n \n\n</td><td>\n\n1.  Provision an anowassist instance with GenAI set up and platform 10.0.3 version and KG 6.0.6 installed.\n2.  Perform any transaction that invokes KG.\n\n Observe the prompt and token count.\n\n</td></tr><tr><td>\n\nDatabase Persistence - Graph\n\n PRB1974718\n\n</td><td>\n\nNull value optimization must handle a case where Genius Results are reused and null everything again\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Graph\n\n PRB1975734\n\n</td><td>\n\nDuplicate query execution for sys\\_scope \\(child of sys\\_package\\) in GraphUtils for every iteration/execution\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Graph\n\n PRB1975735\n\n</td><td>\n\nDuplicate query executions for sys\\_user during sample script iteration/execution\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Graph\n\n PRB1975738\n\n</td><td>\n\nAdd support for AglideRecordOptimizer in glideRecordDynamic, especially for ArrayLoader implementation\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Graph\n\n PRB1982912\n\n</td><td>\n\nDBSqlParser key injection must consider both local and cte keys when deciding whether to add additional ones in finalizeKeyInjection\n\n</td><td>\n\nAn error message appears: 'com.glide.db.DBGraphApiException: Error executing cypher: FAILED TRYING TO EXECUTE ON CONNECTION...'\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Graph\n\n PRB1992704\n\n</td><td>\n\nGetting 'com.snc.db.graph.GraphMetadataSerializationException: Edge type is required' exception on CMDB tables\n\n</td><td>\n\nThe exception, 'com.snc.db.graph.GraphMetadataSerializationException: Edge type is required.: org.mozilla.javascript.JavaScriptException: com.snc.db.graph.GraphMetadataSerializationException: Edge type is required' occurs.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Graph\n\n PRB1993285\n\n</td><td>\n\nSimple queries are timing out on Enterprise Graph and Enterprise Graph Mini\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Graph\n\n PRB1997411\n\n</td><td>\n\nThe 'C2R Paginated' API fails for aggregated queries\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Graph\n\n PRB1998627\n\n</td><td>\n\nReturn empty backing info rather than 'null' if there's no key for a select item\n\n</td><td>\n\nWhen a selectitem isn't mapped to a specific table/key, produce empty 'complex' backing info rather than 'null'. Null is reserved for a return if the select item doesn't exist.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - Graph\n\n PRB1999021\n\n</td><td>\n\nAlways use a table rather than its parent when injecting keys\n\n</td><td>\n\nWhen doing injections, it uses the primary key value, which is present in all the tables that make up a TPC class, but it may or may not include parents based on the select items/where clause. It's best to use the sys\\_id in the child class.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence\n\n PRB1992095\n\n</td><td>\n\nThere's an error in the cypher2ResultsPaginated API\n\n</td><td>\n\nThere's an error executing cypher: 'FAILED TRYING TO EXECUTE ON CONNECTION Syntax Error or Access Rule Violation detected by database \\(\\(conn=103967\\) Unknown column 'sys\\_user0.sys\\_id' in 'order clause'\\)'.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - WDF\n\n PRB1981897\n\n</td><td>\n\nUnable to retrieve the proper row count from glide Aggregate when using Group By Date/Floating Point/Decimal columns\n\n</td><td>\n\nThe issue with the count distinct query is found in Australia. When adding an aggregate on either a Date, Decimal, or Floating Point column, the user encounters an error about missing parameters for concat function. As a result, count of groups is an incorrect number of groups since the distinct count query failed. When executing the script, users observe the script output query failed and the row count does not output the proper number of groups.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - WDF\n\n PRB2001053\n\n</td><td>\n\nData Interface is generated with database views with datafabric tables that should have the ACL generated with the data\\_fabric operation on the view with the composite role\n\n</td><td>\n\nCurrently, the query on the data interface queries all the implementations which can be DB view, glide tables, and datafabric tables. However when there is a DB view as a part of the interface, it complains that there needs to be data\\_fabric operation ACL for the snloopback query.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDatabase Persistence - WDF\n\n PRB2002769\n\n</td><td>\n\nThe default security model for loopback data fabric queries is overly strict and will prevent user adoption\n\n</td><td>\n\nThe default behavior of data fabric should allow users to access tables with remote tables if they already have access to that table using read ACLs. Currently, the default behavior is to block all access.\n\n</td><td>\n\nAttempt to query an SN table with Trino.\n\n Expected behavior: By default, the user should have access if they have read access to the table.\n\n Actual behavior: The user must have specific data\\_fabric access granted to that table to run the query.\n\n</td></tr><tr><td>\n\nDatabase Views\n\n PRB1981902\n\n</td><td>\n\nRaptor DB view has mixed case prefix and '.' combination errors out\n\n</td><td>\n\n \n\n</td><td>\n\n1.  Create a DB view between task\\_sla and incident, and DB view table records with prefix with mixed case \\(for example, the prefix 'inC' for incident\\).\n2.  Have the where clause as 'task\\_sla.task = inC.sys\\_id'.\n\n Notice that the execution errors out.\n\n</td></tr><tr><td>\n\nData Fabric Table glide Services\n\n PRB1997363\n\n</td><td>\n\nSys\\_fields are silently dropped when importing a table from a local instance\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nData Fabric Table Glide Services\n\n PRB2002718\n\n</td><td>\n\nHandle the entitlement check of the new ZCC App\n\n</td><td>\n\nThe new ZCC app \\(sn\\_zcc\\_primary / sn\\_data\\_fabric\\_zcc\\) is not correctly handling the plugin ID after the ZCC app split.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nData Fabric Table glide Services\n\n PRB2004392\n\n</td><td>\n\nMetadata collectors multi-nested section **Choice** fields are not sent to the backend properly and auto-selected\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nData Fabric Table glide Services\n\n PRB2005520\n\n</td><td>\n\nFix DataFabricStatsAccumulator to support new plugin sn\\_zcc\\_primary\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nData Product Backend Services\n\n PRB2000970\n\n</td><td>\n\nThe asset **Internationalized Resource Identifier \\(IRI\\)** is not captured, which is needed for editing the data product\n\n</td><td>\n\nThe asset **IRI** is a required field for editing the data product, and its absence prevents users from performing edit operations on data products.\n\n</td><td>\n\n1.  Navigate to the Data Product module.\n2.  Create or open an existing data product.\n3.  Attempt to edit the data product.\n\n Observe that the asset **IRI** is not being captured/stored, and that the edit operation cannot proceed or fails due to the missing asset **IRI**.\n\n</td></tr><tr><td>\n\nData Snapshots\n\n PRB1987076\n\n</td><td>\n\nWhen the applied filter is removed, the values in the hierarchy breakdown revert to the original values even though the hierarchy toggle is still enabled\n\n</td><td>\n\nWhen filters on the dashboard with the applied breakdown hierarchy are removed, the hierarchy toggle does not toggle 'off'.\n\n</td><td>\n\n1.  Install the com.snc.pa.mlb and com.snc.pa.premium plugins.\n2.  Navigate to **Data snapshots**.\n3.  Create a new DS source with Data frequency as 'All Activity'.\n4.  Add a fact table.\n5.  Add supported fields in the fields section, such as assigned\\_to.\n6.  Navigate to **pa\\_cdc\\_breakdown\\_hierarchy**.\n7.  Add Manager Hierarchy as a record.\n8.  Ensure the scheduled jobs have run and scores are collected in pa\\_cdc\\_fact table and pa\\_cdc\\_sysuser table for the breakdown hierarchy.\n9.  Navigate to **Automated Indicators - Data Snapshots**.\n10. Create a new DS indicator by selecting the source created in step 2.\n11. Choose the standard calendar and daily frequency.\n12. Choose the 'Aggregate' as 'Count'.\n13. **Save** and submit the form.\n14. Navigate to **Dashboards**.\n15. Add any new visualization with the source created above with DB view as facts table.\n16. Add a filter on the dashboard with the breakdown hierarchy.\n\nObserve the scores.\n\n17. Later remove the applied breakdown hierarchy.\n\n Expected behavior: When all the filters are removed, the hierarchy ID is removed, but on the UI side the hierarchy toggle should toggle off.\n\n Actual behavior: When all the filters are removed, the hierarchy ID is removed, but on the UI side the hierarchy toggle is not toggling off.\n\n</td></tr><tr><td>\n\nData Snapshots\n\n PRB1994726\n\n</td><td>\n\nCache issue with heatmap visualization and pivot table in Dashboards\n\n</td><td>\n\nThe pivot table shows an empty matrix and the heatmap shows previously cached data. It should show 'No data available' when scores aren't available for both visualizations.\n\n</td><td>\n\n1.  Create an automated indicator with some combination of fields, like **Choice**, **Boolean** and **Reference** fields.\n2.  Run the data collection jobs to enable data for the created indicator \\(if not available already\\).\n3.  Create a heatmap visualization and pivot table.\n4.  Add them to created indicator.\n5.  In 'group by', select any **Reference** fields \\(for example, **Assigned\\_to**\\).\n6.  Add a filter to the groupby column configured in step 5.\n7.  Select a reference record for which the score is available from the filter.\n\nObserve the scores for that record on both visualizations.\n\n8.  Remove the previously selected record.\n9.  Add a record which doesn't have any scores.\n\n Expected behavior: It should show 'No data available' since the multivis API returns no scores.\n\n Actual behavior: The pivot table shows an empty matrix and the heatmap shows previously cached data.\n\n</td></tr><tr><td>\n\nData Snapshots\n\n PRB1996565\n\n</td><td>\n\nErrors appear in syslog after saving/updating a data snapshots formula indicator\n\n</td><td>\n\nA TableDescriptor exception is thrown in the sys log table.\n\n</td><td>\n\n1.  Provision an instance with com.snc.pa.mlb and com.snc.pa.premium installed.\n2.  Navigate to data snapshots formula indicator.\n3.  Create an indicator with any formula.\n\n Observe that a TableDescriptor exception is thrown in the sys log table.\n\n</td></tr><tr><td>\n\nDeclarative Actions\n\n PRB1995366\n\n</td><td>\n\nAI gradient support in Declarative Actions \\(DA\\) and UI actions in Workspace and Core UI\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDeveloper Sandboxes\n\n PRB1981414\n\n</td><td>\n\nUpgraded warning listener is not registered unless nodes are restarted\n\n</td><td>\n\nThe listener didn't run, resulting in no message created in sys\\_dsb\\_message.\n\n</td><td>\n\n1.  Enable DSBs.\n2.  Do not restart the node controller.\n3.  Create a sandbox.\n4.  Run the script in the controller node.\n5.  Check sys\\_dsb\\_message.\n\n Notice no message was created because the listener didn't run.\n\n</td></tr><tr><td>\n\nDeveloper Sandboxes\n\n PRB1991734\n\n</td><td>\n\nSandbox\\_user can't see the sandbox list in Sandbox Management Home\n\n</td><td>\n\nThe sandboxes list is empty, but allocated sandboxes shows '1'.\n\n</td><td>\n\n1.  Create a sandbox.\n2.  Switch to a sandbox\\_user account.\n\n Observe that the sandboxes list is empty, but allocated sandboxes shows '1'.\n\n</td></tr><tr><td>\n\nDirectSQL\n\n PRB1997847\n\n</td><td>\n\nDirectSQL doesn't support local mapped data fabric tables\n\n</td><td>\n\nThe path fails, so a change is needed in isDataFabricEngineQuery.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDirectSQL\n\n PRB2000509\n\n</td><td>\n\n'NOT BETWEEN' is translated as 'BETWEEN' with 'NOT' dropped\n\n</td><td>\n\n \n\n</td><td>\n\nUse the query: SELECT number, priority FROM incident WHERE priority NOT BETWEEN 2 AND 4 ORDER BY priority, number.\n\n Expected behavior: It returns incidents where priority is outside the range 2-4, such as 'priority = 1' or 'priority &gt;= 5'.\n\n Actual behavior: Returns incidents where priority is inside the range 2-4 because the 'NOT' is dropped and the condition becomes priority 'BETWEEN 2 AND 4'.\n\n</td></tr><tr><td>\n\nDirectSQL\n\n PRB2000510\n\n</td><td>\n\nSimple 'CASE' expression is not supported\n\n</td><td>\n\nThe execution fails with an exception.\n\n</td><td>\n\nUse the query: SELECT CASE priority WHEN 1 THEN 'Critical' WHEN 2 THEN 'High' WHEN 3 THEN 'Medium' ELSE 'Low' END AS priority\\_label, number FROM incident ORDER BY 1, 2.\n\n Expected behavior: It returns each incident's number with a human-readable priority label derived from the simple 'CASE' expression.\n\n Actual behavior: The execution fails with the exception, 'Switch statements in case expressions are not supported.'\n\n</td></tr><tr><td>\n\nDiscovery\n\n PRB1938058\n\n [KB2756546](https://hi.service-now.com/kb_view.do?sysparm_article=KB2756546)\n\n</td><td>\n\nSlow query from the status count optimizer impacts parallel launching of cloud app patterns\n\n</td><td>\n\n \n\n</td><td>\n\nRefer to the listed KB article for details.\n\n</td></tr><tr><td>\n\nDiscovery\n\n PRB1996875\n\n [KB2801169](https://hi.service-now.com/kb_view.do?sysparm_article=KB2801169)\n\n</td><td>\n\nCloud Infra Patterns are launched per datacenter, impacting GCP Discovery Schedules\n\n</td><td>\n\nGCP Discovery schedules take significantly longer to complete because the system launches one pattern execution per datacenter instead of one pattern per service account containing all datacenters. This results in a significant increase in probe executions.\n\n</td><td>\n\nRefer to the listed KB article for details.\n\n</td></tr><tr><td>\n\nDiscovery\n\n PRB2000665\n\n</td><td>\n\nTranslation log causes an exception, preventing Discovery completion\n\n</td><td>\n\n \n\n</td><td>\n\n1.  Initiate the Discovery process.\n2.  Trigger the translation log functionality during Discovery.\n\n Observe that an exception is thrown, and the Discovery process does not complete due to the exception.\n\n</td></tr><tr><td>\n\nDocument Intelligence Unified Backend\n\n PRB1988914\n\n</td><td>\n\nAdd functionality for Input Router to consider an entire document set\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nDynamic Translation for Agent Chat\n\n PRB1988564\n\n [KB2776693](https://hi.service-now.com/kb_view.do?sysparm_article=KB2776693)\n\n</td><td>\n\nIf Dynamic Translation for Agent Chat \\(DTAC\\) translation fails from agent to requester, the original message isn't sent\n\n</td><td>\n\nNote that messages from the requester to the agent still get delivered in the original language even though they aren't translated. Messages from the agent to requester don't get translated and don't get delivered.\n\n</td><td>\n\nRefer to the listed KB article for details.\n\n</td></tr><tr><td>\n\nEmail Notifications\n\n PRB2002403\n\n</td><td>\n\nExtend the 'NotificationsEmailAgentsUtils' global script include with methods for notification, template, and layout creation\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nEncryption\n\n PRB2000179\n\n</td><td>\n\nglide\\_encryption.set\\_value\\_support\\_cle.disabled property can be modified by the user\n\n</td><td>\n\nThe property can be set to 'true' by an admin user.\n\n</td><td>\n\n1.  Log in as an admin user.\n2.  Type sys\\_properties.list.\n3.  Search for the property glide\\_encryption.set\\_value\\_support\\_cle.disabled.\n\n Expected behavior: The admin user cannot set the property to 'true'.\n\n Actual behavior: The admin user can set the property to 'true'.\n\n</td></tr><tr><td>\n\nEncryption Support\n\n PRB1992606\n\n</td><td>\n\nDuplicate Attachment EFCs are created for tables\n\n</td><td>\n\nDuring the upgrade, the autoCLEHealthScan job in the sys\\_mass\\_encryption\\_job table detected unmigrated attachments. As a result, the 'CLE Unmigrated Attachments Health' indicator appears red, and the 'unmigrated\\_attachment\\_count' shows a value greater than 0.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nEvent Management\n\n PRB1923711\n\n</td><td>\n\nOnce the maximum size limit for impacted maintenance CIs is reached, the system is unable to re-evaluate them\n\n</td><td>\n\nWhen ImpactMaintenanceHandler.executeMaintenanceCalculation is triggered and the limit is reached, the maintenance job stops, and the system does not automatically re-evaluate the maintenance impact.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nEvent Management\n\n PRB1990100\n\n</td><td>\n\nEM disable/enable jobs fix scripts unnecessarily manipulate the upgrade\\_safe value during installation and upgrades\n\n</td><td>\n\nDuring upgrades within Zurich, some Event Management \\(EM\\) jobs can temporarily lose the upgrade\\_safe flag. This happens because the EM 'before upgrade' fix script may execute unexpectedly. When upgrade\\_safe is set to false on key EM scheduled jobs \\(for example, 'Event Management - process events' and related connector/coordinator jobs\\), those jobs may not run during the upgrade window. This can lead to delayed event processing or backlog while the upgrade is in progress.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nEvent Management\n\n PRB1996008\n\n</td><td>\n\nSometimes adjacent alerts aren't grouped even if there is a matching definition\n\n</td><td>\n\nThe problem happens in Zurich when 1\\) there are two tag-based definitions \\(D1 and D2\\) with the same or very similar filter and grouping conditions, and 2\\) the definition D1 has a lower order and shorter timeframe window, while the definition D2 has a higher order and wider timeframe window. The problem is that two adjacent alerts fit to both definitions, but they're created with interval that's greater than the timeframe of the definition D1. Instead of being grouped by the definition D2, the alerts remain ungrouped. So the cause of this error is incorrect handling of isolated alerts.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nExternal Content Connectors glide\n\n PRB1902996\n\n</td><td>\n\nScriptable API fails when the table is yet to be indexed\n\n</td><td>\n\n \n\n</td><td>\n\n1.  Install NAVA.\n2.  Create new connector for AWS.\n3.  Don't index anything.\n4.  Run the script.\n\n Notice the error in background scripts.\n\n</td></tr><tr><td>\n\nFlow Engine\n\n PRB1997767\n\n</td><td>\n\nFlow execution tracking\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nFlows \\(Family Channel\\)\n\n PRB1990711\n\n</td><td>\n\nText2flow glide changes\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nFlows \\(Family Channel\\)\n\n PRB1990712\n\n</td><td>\n\nExpose subflows and actions as Model Context Protocol \\(MCP\\) tools\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nFlows \\(Family Channel\\)\n\n PRB1995799\n\n</td><td>\n\nAI Search semantic search results aren't appearing for a non-admin user with only the flow\\_designer role\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nFlows \\(Family Channel\\)\n\n PRB2002799\n\n</td><td>\n\nAISearch stops working when upgrading to latest Australia release\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nForm Controller\n\n PRB1987560\n\n</td><td>\n\nService Locations form bundle reference lookup spinner loads infinitely\n\n</td><td>\n\nService Locations form reference lookup loads infinitely for Quote/Order/Opportunity entities in Australia glide, but works as expected in Yokohama and Zurich.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nForm Controller\n\n PRB1990803\n\n [KB2811745](https://hi.service-now.com/kb_view.do?sysparm_article=KB2811745)\n\n</td><td>\n\nUsers are unable to toggle checkboxes on system properties UI pages\n\n</td><td>\n\n \n\n</td><td>\n\n1.  Navigate to any instance.\n2.  Log in as an admin.\n3.  Open any system properties UI page.\n4.  Attempt to toggle any checkbox.\n\n Expected behavior: Users should be able to turn on or off checkboxes on properties pages to modify system configurations.\n\n Actual behavior: Checkboxes on UI properties pages are non-functional and can't be toggled.\n\n</td></tr><tr><td>\n\nglideRecord\n\n PRB1990713\n\n</td><td>\n\nMID Server core logic for Collector Framework\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nHelp Center\n\n PRB2003374\n\n</td><td>\n\nIntegrate sn-help-assistant in the Next Experience app shell\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nHelp Center\n\n PRB2003375\n\n</td><td>\n\nSupport dynamic guidance in the Help Centre\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nHermes \\(Family\\)\n\n PRB1986687\n\n</td><td>\n\nACL prevents topics being listed in hermes\\_topic\\_inspector for users without elevated privileges\n\n</td><td>\n\nOnly one topic will appear if multiple topics exist. The console tab will list a JavaScript error for loadCell.children\\[2\\].onclick code.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nHorizon Component Library\n\n PRB2004216\n\n</td><td>\n\nUpdate now-avatar properties to receive styling for AI avatars for AI Specialists\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nHR Service Delivery\n\n PRB1970657\n\n</td><td>\n\nRename searchSharePointDocumentsAsUser to searchKTDocumentsAsUser\n\n</td><td>\n\nThis is an update to a more generic name.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nHR Service Delivery\n\n PRB1985984\n\n</td><td>\n\nAdding RCAs to app-hr for app-cbs-hr for the migration of CBS to CBS for HR \\(app-cbs\\)\\)\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nHR Service Delivery\n\n PRB2002907\n\n</td><td>\n\nRCA is missing for ZTSD for HR\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nHTML Field Type Editor\n\n PRB1990982\n\n</td><td>\n\nPredictive text assistance\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nHTTP Client\n\n PRB1986204\n\n</td><td>\n\nThe **Test** UI action on the sys\\_soap\\_message\\_function table causes large table handling query against ecc\\_queue and causes memory contention\n\n</td><td>\n\nSelecting the **Test** UI action for a 'SOAP Message Function' \\[sys\\_soap\\_message\\_function\\] record that has a 'MID server' specified causes the platform to send a test request to the MID server, and then poll for a response from the ECC queue. The query does not pass a valid value for the filter on the response\\_to= filter, and so it can bring back hundreds to millions of rows, depending on how many rows are in the ECC queue.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nHTTP Client\n\n PRB1992475\n\n</td><td>\n\nAsynchronous HTTP client upgrade for complete feature change\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nIdentity\n\n PRB1981341\n\n</td><td>\n\nInclude trackable attribute in Machine Identity Console and Scripting Governance Tool's plugin.xml\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nInbound API Integration Usage Framework\n\n PRB1997896\n\n</td><td>\n\nHttpServletRequest is recycled during long transactions, which causes unhandled exceptions in HttpRequestAttributeAccessor\n\n</td><td>\n\nLong-running SOAP transactions, including ODBC queries, can fail to complete on Zurich instances due to an unhandled error during telemetry collection.\n\n</td><td>\n\nScenario 1:\n\n Attempt to query large datasets using ODBC.\n\n Scenario 2:\n\n To reproduce using only SOAP, increase the max limit and query 30k&amp;\\#43; records in a single request.\n\n</td></tr><tr><td>\n\nInbound API Integration Usage Framework\n\n PRB2000222\n\n</td><td>\n\nIntegration Filter used to measure API Access Volumes is not applied to SOAP and JSONv2 requests\n\n</td><td>\n\nCertain internal inbound SOAP &amp; JSONv2 integration API requests count towards a user's data egress \\(API Access Volume\\) usage. These APIs are used for ServiceNow products. The customer licenses separately or are for supporting internal capabilities and should not be considered data egress.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nIncident Management\n\n PRB1978573\n\n</td><td>\n\nError displayed while creating an Interaction in Service Operations Workspace \\(SOW\\)\n\n</td><td>\n\n \n\n</td><td>\n\n1.  Navigate to Service Operations Workspace.\n2.  Select **Create Interaction**.\n3.  Fill in the required fields.\n4.  Save the Interaction.\n\n Notice that an error banner is displayed stating insufficient access for query\\_range operation on sys\\_user.email.\n\n</td></tr><tr><td>\n\nIncident Management\n\n PRB1989167\n\n</td><td>\n\nMake SDA role available for all of the customers irrespective of ITSM Roles plugin installation\n\n</td><td>\n\nThe SDA role is installed only if ITSM Roles plugin is active on the instance, hence there are upgrade users still missing on this role. ITSM has introduced a new AI worker as part of ZTSD uptake and that AI worker uses the SDA role, hence the user must have the SDA role.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nIncident Management\n\n PRB1989959\n\n</td><td>\n\nRestrict AI-native ITSM good SKUs to 'Incident' and 'Request Management'\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nInstance Clone \\(Family\\)\n\n PRB1997371\n\n</td><td>\n\nClone the admin console, MIF fix, and true-up to 2.1.7\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nIntegration Hub\n\n PRB1989692\n\n</td><td>\n\nPage details are missing from the execution details for Datastream Actions when run via FlowAPI\n\n</td><td>\n\nThe 'Page Details' section is missing and the user is unable to view step-by-step execution data \\(Pagination Setup, Integration Metadata, Step Configuration, API request/response\\).\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nIntegration Hub\n\n PRB2003032\n\n</td><td>\n\nThe connection\\_admin user should be able to created/edit systems from WDF Connect Hub\n\n</td><td>\n\n \n\n</td><td>\n\n1.  Log in as user with the connection\\_admin role.\n2.  Navigate to WDF connect Hub from navigator.\n3.  Select **New** &gt; **System**.\n\n Expected behavior: The user should be able to create new a system.\n\n Actual behavior: The user is unable to create a new system.\n\n</td></tr><tr><td>\n\nKnowledge Graph \\(Family\\)\n\n PRB1986786\n\n</td><td>\n\nRenew the descriptions and automate the shipping pipeline for new tables, which should become the default\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nKnowledge Management\n\n PRB1981407\n\n</td><td>\n\nAfter Zurich, the **Source Task** field for knowledge articles isn't assigned\n\n</td><td>\n\nThis issue occurs when a user creates a feedback task record for a knowledge article. The feedback task allows knowledge managers to either edit the existing article or create a new one. However, when users attempt to create a new article from the feedback task, the new article doesn't reference the originating feedback task as it does in Yokohama. The **Source Task** field, which should contain this reference, appears in the article form view, but it is grayed out and empty.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nKnowledge Management\n\n PRB1992747\n\n</td><td>\n\nNow Assist KB creation pop-up is unable to continue with the KB creation when no tasks are available for search\n\n</td><td>\n\nThis issue occurs only in Native UI. Using the **Create knowledge** UI from Native UI during KB creation shows no options available to continue without selecting tasks. This blocks KB creation.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nKnowledge Management\n\n PRB1993428\n\n</td><td>\n\nRemove the dictionary for standard\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nKnowledge Management\n\n PRB1994772\n\n</td><td>\n\nNavigating to 'Create Knowledge' displays the interceptor page\n\n</td><td>\n\nThis occurs when the KCS plugin is enabled and the CSM table map is disabled.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nKnowledge Management\n\n PRB2006452\n\n</td><td>\n\nLaunch AI Native SKUs\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nLanguage and Translations\n\n PRB1991979\n\n</td><td>\n\nGenAI translations merge for Zurich\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nLifecycle Events\n\n PRB2000694\n\n</td><td>\n\nRCA for AttachmentSensitive script include needs to be checked in\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nList Administration\n\n PRB1990986\n\n</td><td>\n\nMulti-record actions for end user flows\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nList Administration\n\n PRB1990987\n\n</td><td>\n\nIntegrate a tracked list feature into the list experience\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nList Administration\n\n PRB1990988\n\n</td><td>\n\nTo improve the AI in-product experience, indicate a row that's been generated by AI\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nList Controller\n\n PRB1998776\n\n</td><td>\n\nFix for WorkspaceTabsTooltipIT.testWorkspaceTabsTooltip test failures\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nList Views\n\n PRB1979390\n\n</td><td>\n\n'Edit columns' is not working, and no illustration appears when selecting 'Backlog personalize panel'\n\n</td><td>\n\nThe added columns and the illustration are not displayed.\n\n</td><td>\n\n1.  Navigate to **Service Portal Workspace** &gt; **EAP**.\n2.  Select any team backlog.\n3.  Select **Personalize columns** in the header.\n4.  Select any columns and apply it.\n\n Notice the new columns are not added to the backlog presentational list, and when selecting **Backlog personalize panel**, notice there is no illustration is present.\n\n</td></tr><tr><td>\n\nMetricBase\n\n PRB1982775\n\n</td><td>\n\nTest Connection utility returns a false positive result in multi Clotho environments\n\n</td><td>\n\nThis issue was observed in multi-sharded and HA environments, and was not observed on a single endpoint Clotho.\n\n</td><td>\n\n1.  Provision an instance with multiple Clotho servers.\n2.  Run the Test Connection utility from the Metricbase Configuration page.\n3.  Change one of the fields in any one Clotho configuration to an invalid value. For example, provide an invalid username or give an invalid port number for the URL.\n4.  Note down the original value.\n5.  Run the Test Connection utility again.\n\nNotice that it returns true, when it should fail since one of the endpoints is invalid.\n\n6.  Change all configurations to an invalid one.\n\nNotice the Test Connection test now fails as expected.\n\n7.  Restore all endpoints to their correct values.\n8.  Run Test Connection again.\n\n Notice that it passes now.\n\n</td></tr><tr><td>\n\nMetricBase\n\n PRB1985056\n\n</td><td>\n\naha-monitor thread blocked by ClothoClientManager synchronization during database switchover\n\n</td><td>\n\nIt is unable to process database switchovers, causing nodes to stall.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nMetricBase\n\n PRB1994130\n\n</td><td>\n\nWeekly rollups happen on Thursday and monthly rollups happen a random day within the first week of next month\n\n</td><td>\n\nThe rollup should always be executed based on the provided endTime parameter.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nMetricBase\n\n PRB2000747\n\n</td><td>\n\nBoolean literals are not parsed correctly in the 'where' clause, preventing queries\n\n</td><td>\n\nAn execution error occurs.\n\n</td><td>\n\n1.  Create a Boolean Data Type metric.\n2.  Run the script in scripts background.\n\n Expected behavior: Valid query result.\n\n Actual behavior: An error occurs, 'Script execution error: Script Identifier: null.null.script, Error Description: com.snc.clotho.ClothoException: com.glide.db.glideSQLException: Element doesn't exist. Table: mb\\_dex\\_installed\\_app\\_metrics col: false.'\n\n</td></tr><tr><td>\n\nMID Server\n\n PRB2002402\n\n</td><td>\n\nTrace collector epic for Zurich\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nMobile Platform\n\n PRB1990141\n\n</td><td>\n\nMobile AI gradients update\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nMobile Platform\n\n PRB1995814\n\n</td><td>\n\nOffline-online-offline incidental list doesn't load after syncing records that were created offline\n\n</td><td>\n\nThe error 'Could not find application content in offline data' appears.\n\n</td><td>\n\n1.  Log in to the agent app.\n2.  Download an offline cache.\n3.  Go offline.\n4.  Create a **Work order task** &gt; **Incidental**.\n5.  Open the incidental.\n6.  Add activity stream attachments.\n7.  Sync.\n8.  Go online.\n9.  Go back offline.\n10. Load the **Work order task** &gt; **** &gt; **Incidental**list again.\n\nObserve the error 'Could not find application content in offline data'.\n\n\n Expected behavior: The incidental list loads offline and displays the created incidental with activity stream entries.\n\n Actual behavior: The offline-online-offline incidental list doesn't load after syncing records that were created offline.\n\n</td></tr><tr><td>\n\nMobile Platform\n\n PRB2000325\n\n</td><td>\n\nCell redirection action fails in Offline Mode after completing a task when multiple conditional buttons share the same cell location\n\n</td><td>\n\nThe user observes the error 'Cannot find application content in offline data.'\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nMultimodal Service \\(Family Channel\\)\n\n PRB1990234\n\n</td><td>\n\nUpdate the MMService plugin to support MMS async backend\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nMultimodal Service \\(Family Channel\\)\n\n PRB1996320\n\n</td><td>\n\nJWT claims generation updates\n\n</td><td>\n\nThe attachment table name is no longer needed since using the sys\\_mm\\_result record ID as the claim in the JWT.\n\n</td><td>\n\nCreate a record with an attachment on a table configured in glide.platform\\_mm\\_service.supported\\_tables.\n\n Observe the results in the sys\\_mm\\_result table , and the error message in the 'Error message' column.\n\n</td></tr><tr><td>\n\nNatural Language Query \\(Family Release\\)\n\n PRB1993465\n\n</td><td>\n\nMetadataInvalidationListener creates a NLQ-related tables hashset for every DB action, causing an increase in young object generation and also adding to performance cost\n\n</td><td>\n\nIn the hot code path, the isNLQRelatedTables is called and it creates a list first and converts into a hashset for every DB action.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nNext Experience Unified Navigation\n\n PRB1887581\n\n</td><td>\n\nSelecting a new chat desktop notification doesn't bring focus to the tab that changed\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nNow Assist for Retail Service Management \\(RSM\\)\n\n PRB1999697\n\n</td><td>\n\nTrue up versions correction for Retail AI Bundle in Australia\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nNow Assist for Spoke Generation\n\n PRB1968315\n\n</td><td>\n\nAdding granular roles in text2spoke\n\n</td><td>\n\nAdding granular roles in text2spoke, and adding wdf\\_builder instead of admin.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nNow Assist in Document Intelligence\n\n PRB1999314\n\n [KB2916056](https://hi.service-now.com/kb_view.do?sysparm_article=KB2916056)\n\n</td><td>\n\nServiceNow Now Assist In Document Intelligence \\(NADI\\) skill execution is blocked for inactive skill configurations\n\n</td><td>\n\nNADI Store application's 'Extract information from documents' and 'Multimodal Chat' skills may experience silent failures through the NADI release due to the skills being inactive by default. No error is surfaced, but skill execution is blocked. These skills are expected to be active by default upon an upgrade. The problem affects any capability that routes through DocIntel GenAI APIs without activating the skills explicitly in Now Assist Admin.\n\n</td><td>\n\nRefer to the listed KB article for details.\n\n</td></tr><tr><td>\n\nNow Assist Panel\n\n PRB1988915\n\n</td><td>\n\nPass context from Now Assist Portal to workspace\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nNow Assist Panel\n\n PRB1995707\n\n</td><td>\n\nWhen using Now Assist sidebar to summarize an incident, formatting for bullet pointed details \\(for example, LAs and CIs\\) are formatted improperly in Incident Summarization\n\n</td><td>\n\n \n\n</td><td>\n\n1.  Open an instance.\n2.  Navigate to any summarizable incident record.\n3.  In the Now Assist sidebar, start a new chat.\n4.  Enter, 'Summarize this incident.'\n\n Expected behavior: It is in a well-formatted summary.\n\n Actual behavior: The bulleted item text appears on separate line from bullets.\n\n</td></tr><tr><td>\n\nNow Assist Panel\n\n PRB2001558\n\n</td><td>\n\nScript fix to migrate voice input flag from NAA to Agent Studio running even for new users\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nOneExtend\n\n PRB1998719\n\n</td><td>\n\nPrime skills can be executed through background scripts when only foundation apps are installed for AI Native SKU\\]\n\n</td><td>\n\nThis issue occurs on an instance that has asset subscription for Sentiment analysis for procurement case and only SPO - foundation app installed, which is installing NAFP - Foundation.\n\n</td><td>\n\n1.  Open an instance.\n2.  Open **Now Assist Admin** &gt; **Finance &amp; Supply Chain** &gt; **Sourcing &amp; procurement operations**.\n\nNotice that the sentiment analysis skill is hidden here.\n\n3.  Open background scripts.\n4.  Run the code to execute the sentiment analysis skill.\n\n Notice that the record sentiment analysis invoked.\n\n</td></tr><tr><td>\n\nOneExtend\n\n PRB1999920\n\n</td><td>\n\nBuilderEntityCache uses 100+ MB in Australia on Now Support, and it is mostly duplicate data due to domain keys\n\n</td><td>\n\nThe cache is using a key based on the domain, so if 100 users load the same thing it will end up with 100 of the same entries in the cache. But it does not consider that all of the domains are actually using the same object.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nOneExtend\n\n PRB2002764\n\n</td><td>\n\nKAA policy changes for supporting wrapped token\n\n</td><td>\n\nScripted rest endpoints need to support BFF wrapped tokens.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nOneExtend\n\n PRB2003281\n\n</td><td>\n\nInstall log sync service only if com.glide.cs.genai is installed\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nOneExtend\n\n PRB2004072\n\n</td><td>\n\nMosaic execution path needs to be handled via off-glide property\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nOneExtend\n\n PRB2004938\n\n</td><td>\n\nMetadata changes to support Data Separation\n\n</td><td>\n\nMosaic currently doesn't send the domain hierarchy to mosaic as a part of the metadata sync. We need this to enforce data separation at the mosaic end.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nOutsourced Customer Service \\(Family Release\\)\n\n PRB1998333\n\n</td><td>\n\nRemove a few UI page ACLs in cs\\_base/if/ocs plugin\n\n</td><td>\n\nRecords appear when none are supposed to appear.\n\n</td><td>\n\n1.  Open a list of ACL roles.\n2.  Apply the filters 'Application is OCS'and 'ACL.application is global'.\n\n Expected behavior: No records appear.\n\n Actual behavior: 8 records appear.\n\n</td></tr><tr><td>\n\nPerformance Analytics\n\n PRB1995310\n\n</td><td>\n\nNull pointer exception is returned when creating a formula indicator from background scripts\n\n</td><td>\n\nThe user should be able create a formula indicator without any errors when valid data is passed. Instead, the error 'Cannot invoke 'java.util.Map.containsKey\\(Object\\)' because 'nameToSysIdMap' is null' is returned.\n\n</td><td>\n\n1.  Navigate to the background scripts execution page.\n2.  Run a script to create a formula indicator using the automated indicator.\n3.  Check whether a formula indicator is created.\n\n Expected behavior: The user can create the formula indicator without any errors when valid data is passed.\n\n Actual behavior: The error 'Cannot invoke 'java.util.Map.containsKey\\(Object\\)' because 'nameToSysIdMap' is null' is returned.\n\n</td></tr><tr><td>\n\nPerformance Analytics\n\n PRB1999049\n\n [KB2828943](https://hi.service-now.com/kb_view.do?sysparm_article=KB2828943)\n\n</td><td>\n\nThere's malformed pa-ai-canvas.properties, as they are missing commas in the entire dependency list\n\n</td><td>\n\nIn oob-pa-ai-apps/src/main/oob\\_apps/pa-ai-canvas.properties, the 3.0.14-dependencies block has no commas between any dependency entries. Every line uses backslash continuation without comma separators.\n\n</td><td>\n\nRefer to the listed KB article for details.\n\n</td></tr><tr><td>\n\nPlatform Analytics Component API\n\n PRB1995297\n\n</td><td>\n\nKPI Details artifact has missing navigation icons\n\n</td><td>\n\nThe kp-details page doesn't have an icon next to the title that navigates back to the library page.\n\n</td><td>\n\n1.  Open Platform Analytics Workspace.\n2.  Open library.\n3.  Select **Indicators**.\n4.  Select an indicator.\n\n Observe that the indicator opens in a new page. The kp-details page doesn't have an icon next to the title that navigates back to the library page.\n\n</td></tr><tr><td>\n\nPlatform Analytics Dashboard API\n\n PRB1969752\n\n</td><td>\n\nCached toolbox items cause options to remain in a previously selected language\n\n</td><td>\n\nWhile working on the Platform Analytics Dashboard and Data Visualization modules, users have observed that the language in the right-hand menu changes automatically without any user action. The issue occurs intermittently. Sometimes, it appears only in a single browser session, while at other times it affects multiple browsers simultaneously. No consistent trigger has been identified so far. Users report that refreshing the page or clearing the cache may temporarily resolve the issue, but it can recur unpredictably.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nPlatform Analytics Dashboard API\n\n PRB1970352\n\n</td><td>\n\nNot enforcing the ACL in DataManagerService.getWidgetProps\n\n</td><td>\n\nACLs in DataManagerService.getWidgetProps should not be enforced.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nPlatform Analytics Dashboard API\n\n PRB1983811\n\n</td><td>\n\nUnexpected response format for users without assigned roles\n\n</td><td>\n\nThe API should return properly formatted JSON with error code, but instead it returns an invalid format.\n\n</td><td>\n\nRun GetMobileVisualizationIT\\#verifyAsNoRoleUser.\n\n Expected behavior: The API returns properly formatted JSON with error code.\n\n Actual behavior: The API returns an invalid format.\n\n</td></tr><tr><td>\n\nPlatform Analytics Dashboard API\n\n PRB1989067\n\n</td><td>\n\nRemove the info banner on Core UI dashboard overview page\n\n</td><td>\n\nThe new 'com.glide.par.coreui.migration\\_banner.enabled' system property was introduced to configure the appearance of the migration banner.\n\n</td><td>\n\n1.  Set the system property com.glide.par.unified\\_analytics.enabled to false.\n2.  Navigate to the CoreUI dashboard overview page: $pa\\_dashboards\\_overview.do.\n\n The following info banner is displayed: 'If you can't find the dashboard you're looking for, try the Platform Analytics library. Visit Platform Analytics experience.'\n\n</td></tr><tr><td>\n\nPlatform Analytics Dashboard API\n\n PRB1989343\n\n</td><td>\n\nAfter a glide upgrade, dashboard HTML rich text widgets are missing spaces that originally separate the boldfaced text\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nPlatform Analytics Dashboard API\n\n PRB2000628\n\n</td><td>\n\nDashboardWidgetDao.update\\(\\) does not persist **widget\\_props** field\n\n</td><td>\n\nWhen updating a dashboard widget record via DashboardWidgetDao.update\\(\\), the **widget\\_props** field is not written to the par\\_dashboard\\_widget table. The create\\(\\) method correctly calls gr.setValue\\(WIDGET\\_PROPS, widget.getWidgetProps\\(\\)\\), but the update\\(\\) method is missing this call. This causes widget-level property overrides \\(for example, followFilters, header color, header title\\) to be saved on initial widget creation but silently lost on any subsequent dashboard save.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nPlatform Analytics Dashboard API\n\n PRB2002612\n\n</td><td>\n\nFilters should expose the new filter **Custom ID** field\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nPlatform Analytics Migration API\n\n PRB1972851\n\n</td><td>\n\nHide the info message if 'com.glide.par.coreui\\_single\\_migration.enabled' property is 'false'\n\n</td><td>\n\n \n\n</td><td>\n\n1.  Create CoreUI dashboard \\(pa\\_dashboards\\).\n2.  Add Dynamic content block to it.\n3.  Set 'com.glide.par.coreui\\_single\\_migration.enabled' system property to 'false.'\n\n Expected behavior: The info message should be hidden\n\n Actual behavior: The info message is shown.\n\n</td></tr><tr><td>\n\nPlatform Analytics Migration API\n\n PRB1982635\n\n</td><td>\n\nSupport for report\\_group and report\\_global roles to edit visualizations\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nPlatform Analytics Migration API\n\n PRB1986034\n\n</td><td>\n\nUnified property is not set to 'true' after all content is activated\n\n</td><td>\n\n \n\n</td><td>\n\n1.  Set 'com.glide.par.unified\\_analytics.enabled' to 'false'.\n2.  Navigate to **Migration Center**.\n3.  Perform bulk migration.\n4.  Activate all content.\n5.  Check the unified property.\n\n Expected behavior: Unified property is set to 'true'.\n\n Actual behavior: Unified property remains false.\n\n</td></tr><tr><td>\n\nPlatform Analytics Migration API\n\n PRB1988855\n\n</td><td>\n\nStatic content block in core UI after migration has HTML tags in the Next Experience rich text visualization\n\n</td><td>\n\n \n\n</td><td>\n\n1.  Create a core UI dashboard.\n2.  Add a static content block.\n3.  Add some contents within them, such as an embedded URL.\n4.  Select the **Migrate to Next Experience** button to migrate the dashboard to Next experience.\n\n Notice that in the migrated Next Experience dashboard, the rich text has HTML tags in them.\n\n</td></tr><tr><td>\n\nPlaybook Experience Core\n\n PRB1988859\n\n</td><td>\n\nPlaybookContextSnapshotService returns a stale cache when the process definition is reactivated\n\n</td><td>\n\nUpon returning to the workspace after reactivating the launch properties in the playbook the UI step shows outdated information.\n\n</td><td>\n\n1.  Create a Playbook with launch properties.\n2.  Activate it.\n3.  View it in the playbook workspace demo.\n4.  Return to the playbook.\n5.  Modify the launch properties, such as title description.\n6.  Reactivate it.\n7.  Return to the workspace.\n8.  Refresh it.\n\n Notice the record generator/launcher UI step carries stale/outdated information.\n\n</td></tr><tr><td>\n\nPlaybook Experience Core\n\n PRB1995058\n\n</td><td>\n\nThe playbook portal page briefly shows 'There is no playbooks available' when a record is triggered\n\n</td><td>\n\nThis only happens in custom layout type.\n\n</td><td>\n\n1.  Navigate to a playbook with a custom layout type.\n2.  Once the record generator is loaded, trigger the record by selecting **C****ontinue**.\n\n Expected behavior: The playbook loads properly.\n\n Actual behavior: The page shows 'There is no playbooks available' briefly.\n\n</td></tr><tr><td>\n\nPlaybook Experience\n\n PRB1978220\n\n</td><td>\n\nOld record generator forms that have forms selected show 'Show Create Record Form' is false when it should be true\n\n</td><td>\n\nAll records in the list are 'false', when they should be 'true' if a form view is selected.\n\n</td><td>\n\n1.  Install the Process Automation Experience Demo plugin with demo data.\n2.  Navigate to **/sys\\_playbook\\_experience\\_record\\_generator\\_list.do**.\n\n Expected behavior: In the list and on the record, all the records that have 'Show Create Record Form' as 'true' if a form view is selected.\n\n Actual behavior: All the records in 'Show Create Record Form' are false in the list.\n\n</td></tr><tr><td>\n\nPlaybook Experience\n\n PRB1986143\n\n</td><td>\n\nThe **Declarative** action on the workspace form is executing twice in Zurich\n\n</td><td>\n\nThis behavior was observed from the browser console logs, where the same log entries appear multiple times during a single execution, indicating duplicate runs of the action. This is likely due to DECLARATIVE\\_ACTION\\#CLIENT\\_SCRIPT\\_EXECUTION\\_REQUESTED leaking out to the parent form, so that two forms are handling the action. The playbook component should catch this and set stopPropogation to 'true' so it doesn't leak to the parent form.\n\n</td><td>\n\n1.  Open a Zurich base instance.\n2.  Configure a record generator for any form, such as incident.\n3.  Add a field decorator for a field on that form by navigating to **All** &gt; **Field decorator**.\n    1.  Set the table to 'Incident'.\n    2.  Set the type to 'Client script'.\n    3.  Have the script console.log something.\n    4.  Enable this for all configurable workspaces.\n4.  Navigate to a workspace.\n5.  Create a new record to see the record generator.\n6.  Select the **Field decorator** within the form of the record generator.\n\n Expected behavior: There is only one log.\n\n Actual behavior: In the console, it is logged twice.\n\n</td></tr><tr><td>\n\nPlaybook Experience\n\n PRB1986820\n\n</td><td>\n\nForm section labels are not displayed at runtime\n\n</td><td>\n\nWith the migration to the Form Controller in Zurich, the form preset configuration was applied. This preset is designed to hide form section labels, which results in the labels not being displayed at the runtime.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nPlaybooks \\(Family Channel\\)\n\n PRB1983780\n\n</td><td>\n\nThe **Create Flow Data** action gives the error, 'Unable to get source record of Process Automation Activity type'\n\n</td><td>\n\nThis issue occurs in the global scope.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nPlaybooks \\(Family Channel\\)\n\n PRB1991515\n\n</td><td>\n\nAfter a restart, the stage is still displayed even when the conditions aren't met\n\n</td><td>\n\nRemnants from the previous playbook lanes remain visible, although they appear in a 'PENDING' state. However, those lanes are reached, they update correctly.\n\n</td><td>\n\n1.  Navigate to **Configurable Workspace** &gt; **Lists** &gt; **AGR Connections** &gt; **All**.\n2.  Create a record with subcategory 'WebEDI'.\n3.  Proceed with Playbook.\n4.  When asked for 'Fast Follower', select **True**.\n5.  Proceed with Playbook until 'Packaging Data Exchange' \\(lane 7\\) is reached.\n6.  Perform the complete Playbook restart.\n7.  Proceed with Playbook to 'Validate Connection Type' \\(activity 1.4\\) activity.\n8.  Change the subcategory to 'ClassicEDI'.\n9.  When asked for Fast Follower, select **False** and proceed.\n10. Proceed with Playbook until 'Testing' \\(lane 9\\) is reached.\n11. Perform the complete Playbook restart again.\n12. Proceed with Playbook to 'Validate Connection Type' activity.\n13. Change the subcategory to 'WebEDI'.13. When asked for Fast Follower, select **False** and proceed.\n\nObserve that the 'Fast follower' phase is initiated even if the fast follower is not marked, which isn't correct. Also, observe that even if the subcategory is 'WebEDI' now, the phases / activities for 'ClassicEDI' are still initiated, which isn't correct.\n\n\n Expected behavior: If fast follower is set to true, then WebEDI and ClassicEDI don't appear on the playbook. If fast follower is set to false, then WebEDI or ClassicEDI appear on the playbook.\n\n Actual behavior: If fast follower is set to true, WebEDI and ClassicEDI appear on the playbook. If fast follower is set to false, then fast follower, WebEDI, and ClassicEDI appear on the playbook.\n\n</td></tr><tr><td>\n\nPlaybooks \\(Family Channel\\)\n\n PRB2002088\n\n</td><td>\n\n**Locals** field is missing the **Enable AI agent** field\n\n</td><td>\n\nThe **Locals** field on activity context is missing the **enable\\_ai\\_agent** field.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nPlaybooks\n\n PRB1985747\n\n</td><td>\n\nThe 'On-demand' checkbox should not exist for create asset page in 29.0.x\n\n</td><td>\n\nThis shouldn't occur for 29.0 versions.\n\n</td><td>\n\nCreate a new playbook.\n\n Notice that 'Is On-Demand Playbook' is present on the 'Create new playbook' page.\n\n</td></tr><tr><td>\n\nProcess Mining\n\n PRB1997134\n\n</td><td>\n\nFinding step criteria on OR conditions doesn't work\n\n</td><td>\n\nWhen the user mines the finding, it matches more records than expected and doesn't honor the step criteria.\n\n</td><td>\n\n1.  Create a finding definition.\n2.  Create an OR condition.\n3.  Give step criteria \\(not cross-step criteria\\) to one or more of the OR conditions.\n4.  Mine the finding.\n\n Expected behavior: It matches the correct number of records which qualify for the step criteria.\n\n Actual behavior: It matches more records than expected and doesn't honor the step criteria.\n\n</td></tr><tr><td>\n\nProcess Mining\n\n PRB1998650\n\n</td><td>\n\nsn\\_gaf dependency is blocking A NAFC true-up install\n\n</td><td>\n\nThe sn\\_gaf dependency is missing, which blocks the true-up install.\n\n</td><td>\n\nNavigate to **Process Mining** &gt; **sn\\_icu** &gt; **sn\\_gaf NAFC**.\n\n Notice that a true-up install is blocked due to a missing sn\\_gaf dependency.\n\n</td></tr><tr><td>\n\nRemote Process Synchronization \\(Family Release\\)\n\n PRB1961089\n\n</td><td>\n\nThe the 'Inbound' state is in error, and inbound queue processing is blocked until this is addressed\n\n</td><td>\n\nThis issue occurs even when the setup is successful, and the 'Consumer registration' state is moved to the 'Closed Complete' state on 'Impactuat.'\n\n</td><td>\n\nUpdate the instance.\n\n Notice that the inbound status of the RPS connection moves to an error state with following error, 'The current operation ended in state: ERROR. Detail: Error: Cannot find function map in object .,Detail: Cannot find function map in object. Adding 'ih\\_sync\\_inbound\\_queue\\_record' in attachments.'\n\n</td></tr><tr><td>\n\nRequest Management\n\n PRB1992589\n\n</td><td>\n\nCreate workflowStageProcessor script includes for getting stages\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nRequest Management\n\n PRB2002306\n\n</td><td>\n\nTurn on comments for CTASKs\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nResource Management\n\n PRB1981411\n\n</td><td>\n\nThe capacity is not displaying accurately, it appears in the Estimate outside plan section in Capacity Planning\n\n</td><td>\n\nWhen the user creates a demand and creates assignments for it, and selects **Create Project** in the demand, it will create project from demand. However, the resource allocation's **planning\\_item** field does not update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nREST APIs\n\n PRB1986190\n\n</td><td>\n\nScriptable OpenAPI spec support\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nREST APIs\n\n PRB1986192\n\n</td><td>\n\nOpenAPI response header support for REST services\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nREST APIs\n\n PRB1986194\n\n</td><td>\n\nOpenAPI request and response support for REST services\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nRetail Core\n\n PRB1999694\n\n</td><td>\n\nTrue up versions correction for the Retail bundle\n\n</td><td>\n\nThe same build shouldn't operate in different ways when it's installed via Store vs true-up. There should have been a different release record that was A specific and that should have been trued up.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nRoles\n\n PRB1973601\n\n</td><td>\n\nPotential load lot of future time limited roles, which may increase memory footprint\n\n</td><td>\n\n \n\n</td><td>\n\n1.  Create time limited role window for 'admin' role for future start and end time, assign it to abel.tuter.\n2.  Log in as abel.tuter.\n\n Even though all future time limited roles are not needed now, it will load in heap memory as a result of below PR.\n\n</td></tr><tr><td>\n\nScripted REST APIs\n\n PRB1996583\n\n</td><td>\n\nThere's high latency of the REST API scriptable\n\n</td><td>\n\nThe existing scriptable methods jsFunction\\_getDetailedServices and jsFunction\\_getDetailedServicesWithOAuthPolicy had the withSchemaContent flag hardcoded to true, forcing retrieval of schema information for every API resource, which the MCP team doesn't need in the first step. This fix exposes withSchemaContent as an explicit parameter, letting the caller decide based on their use case.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nScripted REST APIs\n\n PRB2000233\n\n</td><td>\n\nAutogenerate OpenAPI specification content\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nSearch Administration\n\n PRB1968215\n\n</td><td>\n\nElements must only use supported ARIA attributes for the**Search catalog** field for Service Portal \\(SP\\)\n\n</td><td>\n\n \n\n</td><td>\n\n1.  Ensure there are multiple requests raised in SP.\n2.  Launch a base instance.\n3.  Navigate to **Request** on the header menu and activate it.\n\nNotice that multiple records will be displayed.\n\n4.  Choose any request.\n5.  Open the Request summary.\n6.  Navigate to **Search catalog**.\n\nNotice that menu items are displayed.\n\n7.  Run 'Evinced Flow Analyzer' and AXE devtool.\n\nObserve the issue.\n\n\n Expected behavior: The ARIA attribute is not allowed as seen in 'aria-selected='false'' and an element's role supports its ARIA attributes.\n\n Actual behavior: Elements only use supported ARIA attributes, as seen in the element location: sn-search-combobox,sn-search-combobox-desktop,.-search-popover\\_\\_item--is-active.\n\n</td></tr><tr><td>\n\nServer-side scripts\n\n PRB1994381\n\n</td><td>\n\nDiscovery has issues on some node after upgrading to Australia RP2\n\n</td><td>\n\nAfter upgrading to Australia RP2 or later, Javascript running in app nodes fails to call Java functions. The following warning appears: '\\*\\*\\* WARNING \\*\\*\\* Evaluator: com.glide.script.RhinoEcmaError: undefined is not a function.' This impacts various features, including Discovery and Event Management.\n\n</td><td>\n\n1.  Open a Zurich instance with multiple nodes.\n2.  Upgrade the instance from Zurich to Australia RP2.\n3.  Run a quick Discovery or discover a few IPs.\n\n Notice that the Shazzam probe creation or Shazzam sensors processing has an error. The Shazzam probe isn't created with a name \\(likely skipping some business rules\\), and Shazzam sensor processing doesn't create the further probes in the chain. This results in discovery not running effectively.\n\n</td></tr><tr><td>\n\nServiceNow Data Catalog \\(glide\\)\n\n PRB1997719\n\n</td><td>\n\nThere are generic UI defects in the data collector\n\n</td><td>\n\nThe URL value is truncated after saving and reloading.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nServiceNow Data Catalog \\(Glide\\)\n\n PRB2003264\n\n</td><td>\n\nMetadata collectors can't decrypt all passwords configured by the dcg-cc store app\n\n</td><td>\n\nWhen configuring dcg-cc to store an AWS access and secret key in the aws\\_credentials table, the AWS key is missing and doesn't appear on the list of **Password** fields.\n\n</td><td>\n\n1.  Configure dcg-cc to store a **password2-type** field in the connection.extended attributes for a collection.\n2.  Deploy the app to glide.\n3.  Open wdf-meta/metadata-collector.\n4.  Configure a collector.\n5.  Select **Run**.\n6.  Set a breakpoint in the KOS SPI class 'AbstractKosCollectorProvide'.\n\nNotice that an encrypted string for the password, encrypted with a glide-specific key, which the collector doesn't have access to.\n\n7.  Configure dcg-cc to store an AWS access and secret key in the aws\\_credentials table.\n8.  Open wdf-meta/metadata-collector.\n9.  Configure a collector that requires AWS credentials.\n10. Select **Run**.\n11. Set a breakpoint in the KOS SPI class 'AbstractKosCollectorProvider'.\n\n Notice that the AWS secret key is missing, and that it isn't on the list of the six **Password** fields that work.\n\n</td></tr><tr><td>\n\nServiceNow Data Catalog \\(glide\\)\n\n PRB2005266\n\n</td><td>\n\nIllegalStateException in tableAccessCheck\\(\\) when executing glide RDF queries\n\n</td><td>\n\nThe RdfGraphStoreJSIT.writeMaxSizeTriple test is failing in the eco tests for the 'dcg-rdf-api-test' project.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nSidebar \\(Family Release\\)\n\n PRB1996759\n\n</td><td>\n\nNull check for threadMember is incomplete for CollabMessageDto\n\n</td><td>\n\nThe user can send a message but it's greyed out in the chat window until the user refreshes. The last sent message in a collab chat record doesn't update, so the discussion card in the utility menu never updates.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nSoftware Asset Data Import\n\n PRB1979790\n\n</td><td>\n\nFix in-field error messages for SW model and PPN\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nSoftware Asset Data Import\n\n PRB1991257\n\n</td><td>\n\nUser can't select a software model if multiple are found for PPN\n\n</td><td>\n\nSelecting **Import** just reloads the page without automatically selecting a software model, and a software model can't be selected from the field without clearing PPN.\n\n</td><td>\n\n1.  Create a PPN and two software models with details matching that PPN's DMAP.\n2.  Import an entitlement with that PPN.\n\nObserve that an entitlement import error is generated with the reason 'Multiple software models found for the Publisher Part number. Please choose a software model.'\n\n\n Expected behavior: There is handling for this situation, either preventing duplicate software models from being created, picking one of the duplicates during import or after selecting the **Import** button, or allowing users to select a software model without needing to clear the **PPN** field.\n\n Actual behavior: Selecting **Import** just reloads the page without automatically selecting a software model, and a software model can't be selected from the field without clearing PPN.\n\n</td></tr><tr><td>\n\nSoftware Asset Data Import\n\n PRB1993170\n\n</td><td>\n\nPass the auto-incremenator using the unique ID of the table rather than using the contract number\n\n</td><td>\n\nThere should be automation for both scenarios: 1. Uploading the docs, finishing the flow, and importing another doc to the same contract. 2. The asset covered from both docs should be part of the same contract.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nSoftware Asset Data Import\n\n PRB2001908\n\n</td><td>\n\nRename the **Ignore** button to **Exclude**\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nSoftware Asset Data Import\n\n PRB2001911\n\n</td><td>\n\nUpdate text on the content opt-in page\n\n</td><td>\n\nSoftware entitlement details are extracted from software contracts using AI. Opt-in to the content service to help improve the prediction for product, publisher, and edition values.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nSoftware Asset Management\n\n PRB2000639\n\n</td><td>\n\nBackport workspace changes of Job Failure Troubleshooting for Australia\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nSQL API \\(Server\\)\n\n PRB1989263\n\n</td><td>\n\nCannot execute a query against a physical representation of a long table name using SqlParser in physical mode\n\n</td><td>\n\nSqlParser throws an exception for the long table name, when the query should instead return a response with no records.\n\n</td><td>\n\n1.  Create a table with a very long table name, such as u\\_very\\_long\\_table\\_name\\_abcdefghijklmnopqrstuvwxyz.\n2.  Send a rest request to Trino Connector API /api/now/integration/trino/query/sql?sql\\_type=physical&amp;connector\\_type=loopback with body containing the following: SQL query: SELECT \\* FROM .\n\n Expected behavior: The query returns a response with no records since the table doesn't contain any data.\n\n Actual behavior: The SqlParser throws an exception, 'Invalid table name.'\n\n</td></tr><tr><td>\n\nSQL API \\(Server\\)\n\n PRB1999140\n\n</td><td>\n\nUpdate the rate limit on SQL calls to 500/hour\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nStream Connect Core\n\n PRB1988698\n\n</td><td>\n\nA zboot error on anowassist regarding sys\\_kafka\\_topic\\_m2m\\_sys\\_sc\\_topic\\_alias\n\n</td><td>\n\nThe error occurs: 'glide SysLog \\*\\*\\* ERROR \\*\\*\\* STREAM\\_CONNECT: SCUpgradeZToA: Got exception while executing fix script: Required table sys\\_kafka\\_topic\\_m2m\\_sys\\_sc\\_topic\\_alias not found on instance.'\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nStream Connect Core\n\n PRB1998573\n\n</td><td>\n\nInstalling the 'ETL Consumer Kafka' plugin shouldn't enable 'Managed Hermes'\n\n</td><td>\n\nThis dependency should be broken.\n\n</td><td>\n\nInstall the 'ETL Consumer Kafka' plugin.\n\n Observe that 'Managed Hermes' is installed.\n\n</td></tr><tr><td>\n\nSystem Events\n\n PRB2001375\n\n</td><td>\n\nThe next discovery in the daisy chain is not triggered when the current discovery is cancelled\n\n</td><td>\n\nWhen discovery is cancelled, it generates two events, discovery.canceled and discovery.complete. Whenever discovery.cancelled is picked up first, triggers the next discovery. When discovery.complete is picked up first, it does not trigger the discovery as the script action 'Discovery Run Next'. With that, discovery.complete exits on the condition 'current.state == 'Canceled' or canceledEventExists. When discovery.cancelled is picked after this, 'Discovery Run Next' exits on the condition that there is already a processed discovery.complete event for this status record.\n\n</td><td>\n\n1.  Make a daisy chain of discovery schedules to trigger one after another.\n2.  Set 'Even if canceled' to 'true'.\n3.  Run discovery and cancel it.\n\n Notice that even though the next discovery should be triggered, it does not always happen.\n\n</td></tr><tr><td>\n\nSystem Import Sets\n\n PRB1981092\n\n</td><td>\n\nProtocol version max length is not configurable for SCP and other data source file retrieval types utilizing SSH connections\n\n</td><td>\n\nThe protocol version reverts to the default version size.\n\n</td><td>\n\n1.  Create a file type data source with the retrieval method SCP.\n2.  Make a connection where the protocol version is longer than the default 512 characters.\n\n Notice that it takes the default protocol version size because there are no parameters being set to alter the default configuration of the SSHEngine/SSHConfig from the glideSSHSessionPool.\n\n</td></tr><tr><td>\n\nTransaction Logs\n\n PRB1997038\n\n</td><td>\n\nThe **http\\_response\\_code** field in the syslog\\_transaction table should be read-only\n\n</td><td>\n\n \n\n</td><td>\n\nOpen a syslog\\_transaction record in form view.\n\n Observe that the **http\\_response\\_code** field may be editable.\n\n</td></tr><tr><td>\n\nTransaction Management\n\n PRB1996223\n\n</td><td>\n\nModify parameters for TimeBasedStatusSampler for better memory state tracking\n\n</td><td>\n\nThe parameters for TimeBasedStatusSampler are used for Memory Health Checks by Loanable Semaphore. The NodeHealthChecker takes too long to identify the high memory pressure, so the parameters should be modified for better memory state tracking.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nUI Field Administration\n\n PRB1962435\n\n</td><td>\n\nThere's an incident form load issue due to the missing macro sn\\_wwna\\_nacm\\_component, which causes a performance issue\n\n</td><td>\n\nWhen loading an incident form, the local host log is consistently flooded with the 'DBMacro WARNING \\*\\*\\* WARNING \\*\\*\\* Macro missing: sn\\_wwna\\_nacm\\_component', and this is causing the form to load slowly.\n\n</td><td>\n\n1.  Open any incident record in the instance.\n2.  Navigate to **System Diagnostics** &gt; **Session Debug** &gt; **Enable All**.\n\n Observe the error in the localhost log, users notice the warning called many times: 'DBMacro WARNING \\*\\*\\* WARNING \\*\\*\\* Macro missing: sn\\_wwna\\_nacm\\_component'.\n\n</td></tr><tr><td>\n\nUI Field Administration\n\n PRB1970358\n\n</td><td>\n\nZboot error comes from WWNA\n\n</td><td>\n\nThe zboot error is in the localhost logs.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nUI Field Administration\n\n PRB1990980\n\n</td><td>\n\nAdd backend support for the multi-section configuration and fetch configurations in the UI to create the BE layer\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nUI Field Administration\n\n PRB1990983\n\n</td><td>\n\nSupport core IT use cases\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nUI Form Administration\n\n PRB1993356\n\n</td><td>\n\nThe g\\_form.addModerateMessage\\(\\) API should display in a purple color both in UI16 and workspace, but displays in an 'AI' color in UI16\n\n</td><td>\n\n \n\n</td><td>\n\nIn on-load client script, add the line: 'g\\_form.addModerateMessage\\('moderate msg'\\)'.\n\n Expected behavior: A purple color should be displayed for alerts.\n\n Actual behavior: It displays an AI color.\n\n</td></tr><tr><td>\n\nUI Form Administration\n\n PRB1993929\n\n [KB2908761](https://hi.service-now.com/kb_view.do?sysparm_article=KB2908761)\n\n</td><td>\n\nRCAs are created with the source as 'sys\\_ws\\_operation.do? sys\\_id=6986d96dff7322102ae8ffffffffff48' for HR apps\n\n</td><td>\n\nAn RCA is generated: 'RCA triggered - 'Read operation on table 'sn\\_doc\\_html\\_template' from scope 'Global' was denied. The application 'Document Templates' must declare a Restricted Caller Access privilege. Please contact the application admin to update their access requests'. None should be generated.\n\n</td><td>\n\nRefer to the listed KB article for details.\n\n</td></tr><tr><td>\n\nUI Form Administration\n\n PRB1994242\n\n</td><td>\n\nWhen 'glide.ui.escape\\_text' is set to false, forms break\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nUI Form Administration\n\n PRB1998771\n\n [KB2898934](https://hi.service-now.com/kb_view.do?sysparm_article=KB2898934)\n\n</td><td>\n\nInstalling the com.glide.ai\\_record\\_activity plugin doesn't create the sys\\_ai\\_record\\_activity table, causing NullPointerException errors\n\n</td><td>\n\nThe user observes errors getting records for sys\\_ai\\_record\\_activity: java.lang.NullPointerException.\n\n</td><td>\n\n1.  Install the GenAI Q4 feature or upgrade an existing instance.\n2.  Ensure the plugin com.glide.ai\\_record\\_activity is installed.\n\n Observe the system logs or error output about an error getting a record for sys\\_ai\\_record\\_activity: java.lang.NullPointerException.\n\n</td></tr><tr><td>\n\nUI Form Administration\n\n PRB2003359\n\n</td><td>\n\nAdd a presence avatar for an AI specialist\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nUI Form Administration\n\n PRB2003360\n\n</td><td>\n\nRemove the badge and pop-up modal from the 'Presence' icon\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nUI Form Administration\n\n PRB2004264\n\n</td><td>\n\nUpdates to support AI Specialist and draft note\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nUpgrade Center\n\n PRB1991306\n\n</td><td>\n\nOn upgrade from Xanadu or Yokohama to Zurich, a 'Before' fix script runs even though it's not supposed to\n\n</td><td>\n\nThe syslog contains relevant log messages.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nUX Framework\n\n PRB1969282\n\n</td><td>\n\nPerformance issues on various templates on the mainline due to frame change\n\n</td><td>\n\nThis issue was observed in templates such as 'Core UI - Polaris Direct Homepage Load', 'Direct Incident List - Configurable Workspace', and 'Direct Incident Form - Configurable Workspace'.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nUX Framework\n\n PRB1990140\n\n</td><td>\n\nFramework support for the AI screen reader Store app\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nUX Framework\n\n PRB1991443\n\n</td><td>\n\nSupport a form alert for AI gradient\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nUX Framework\n\n PRB1996169\n\n</td><td>\n\nScreen reader doesn't announce the status message 'Extend your session'\n\n</td><td>\n\nThe screen reader should announce the entire message inside the timeout pop-up.\n\n</td><td>\n\n1.  Install NVDA screen reader.\n2.  Open an instance.\n3.  Wait for the timeout pop-up 'Extend Your Session' to appear \\(timeout is update 'glide.ui.session\\_timeout' in system property\\).\n\n Observe that the screen reader doesn't announce the status message 'Extend Your Session'.\n\n</td></tr><tr><td>\n\nUX Framework\n\n PRB1997499\n\n</td><td>\n\nThe sn-canvas-tabs component displays a record preview popover on hover that is inaccessible to screen reader users\n\n</td><td>\n\nIn configurable workspaces, there's a top level tab navigation region made up of the sn-canvas-tabs component. Hovering over a record tab in this region with a mouse triggers a popover to display a short preview of key fields on the record, like **Short description**, **State** and more. This is crucial information for agents to quickly differentiate between multiple tabs at a glance, but keyboard and screen reader users can't trigger or access the popovers.\n\n</td><td>\n\n1.  Navigate to a configurable workspace, such as Service Operations Workspace.\n2.  Open at least two records.\n3.  In the top level navigation tabs, hover over a deselected record tab.\n4.  Note that a popover appears with a short summary of key fields for the record, such as **Short description**, **Priority**, and **State** \\(varies by table\\).\n5.  Attempt to navigate record tabs with the screen reader enabled.\n\n Expected behavior: When a tab for a record has focus, the preview popover also appears and remains visible. Screen reader users should hear the details in the preview popover announced.\n\n Actual behavior: When the user navigates through the tabs, screen reader users report confusion because a record number isn't enough detail for many to remember which tab is which, and they aren't aware they are missing the preview popover details.\n\n</td></tr><tr><td>\n\nVirtual Agent Designer Legacy\n\n PRB1992505\n\n</td><td>\n\nHTML rendering issues in alert analysis\n\n</td><td>\n\n \n\n</td><td>\n\n1.  Navigate to Now Assist panel.\n2.  Run alert analysis.\n\n Notice that the response contains HTML tags.\n\n</td></tr><tr><td>\n\nVirtual Agent Designer Legacy\n\n PRB2002310\n\n</td><td>\n\nSkills applicability changes as per the AI Native guidelines\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nVirtual Agent Designer Legacy\n\n PRB2006402\n\n</td><td>\n\nAI connector node should hide custom skills based on foundation, advanced and prime plugins\n\n</td><td>\n\nIn scenario 1, the custom skill in the skill type should only be available when there are no platform type installations on the instance or when the installation type is prime. It should be hidden in the skill type of AI connector node for advanced and foundation. In scenario 2, when there is no custom skill in the skill type, the AI agent should be selected on default for AI connector node. In scenario 3, the AI agents that are specific to list of subscription profiles sn\\_ai\\_plat\\_fdn, sn\\_ai\\_plat\\_adv or sn\\_ai\\_plat\\_prm in sys\\_gen\\_ai\\_asset\\_subscription table should also be specific in the AI agents dropdown list of the AI connector node. AI agents that are not accessible for certain subscription profile should also be restricted to select from AI connector node.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1960339\n\n</td><td>\n\nThe **Use an AI agent** action moves to a 'Waiting' state when called inside a flow-logic component\n\n</td><td>\n\nIn a use case where calling the agent multiple times in a single subflow/flow using the flow-logic, the agent is initially called, but the second call goes into 'Waiting' state and no other calls go through. In the second call to the same agent \\(with a different objective\\), the execution record's state is 'Ready' and the message 'Conversation data is not populated' occurs for the second record. This leads the action to be in 'Waiting' state. The sysevent record is also not created.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1971595\n\n</td><td>\n\nClick metrics and deflection log\n\n</td><td>\n\n \n\n</td><td>\n\n1.  Ensure **Citation** can be selected in the Synthesized Results.\n2.  Update the output type.\n3.  Track the previous clicks in sys\\_cy\\_analytics.\n4.  Write back the 'state' of the citation clicked/auto-started to the 'Output' type column for completed asset tracking.\n5.  Ensure citation/asset selection in Virtual Agent writes the correct deflection type, such as Catalog ≠Synthesized.\n6.  Update the deflection log to filter out small talk to avoid unnecessary records.\n\n Observe that for agentic execution, the ending state is written back to the deflection log.\n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1974845\n\n</td><td>\n\nThe FDIHServiceImpl object holds significant memory\n\n</td><td>\n\ncom.glide.cs.qlue.module.fdih.FDIHServiceImpl is holding high memory\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1976905\n\n</td><td>\n\n'Error parsing additional context JSONObject\\[''conversation''\\] not found' issue for NLU Conversations\n\n</td><td>\n\nThe error log occurs in the syslog when the user attempts a regular NLU conversation and it goes through a search flow.\n\n</td><td>\n\n1.  Attempt to have a regular NLU conversation.\n2.  Ensure it goes through a search flow.\n\n Expected behavior: Flow goes through and the user receives results.\n\n Actual behavior: Flow errors out and goes to the fallback topic. When checking the syslog, the error log 'Error parsing additional context: JSONObject\\['conversation'\\] not found' is seen.\n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1977219\n\n</td><td>\n\nThe **Max wait time**/no agent message isn't rendering hyperlinks in Portal, but it's working in Teams\n\n</td><td>\n\nWhen a URL is given in the **Max wait time** message field of the awa\\_queue table, it's returning a hyperlink in Virtual Agent \\(VA\\) but working in Teams VA.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1980625\n\n</td><td>\n\nSkill name is missing the serializer, which appears to affect promoted VA topics from not showing as translated in VA\n\n</td><td>\n\nThis issue was observed for \\[sys\\_gen\\_ai\\_skill\\].skill\\_name.\n\n</td><td>\n\n1.  Change the language to any language, such as French.\n2.  Navigate to **/esc**.\n3.  Trigger the 'Hello' message.\n\n Notice the untranslated string.\n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1983341\n\n</td><td>\n\nGreeting message is displayed at the end of the topic invocation in Now Assist Virtual Agent \\(NAVA\\)\n\n</td><td>\n\nThe greeting is seen after selecting **Skill execution** from the Genius results. The greetings topic skips the greeting if global\\_search\\_text is present, but is undefined.\n\n</td><td>\n\n1.  Setup NAVA Enhanced chat without full page search on Service portal \\(SP\\).\n2.  Use a search term on SP which provides a skill execution option, such as 'notification'.\n3.  Select the **Skill execution** option from the Genius results.\n\n Notice the greeting.\n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1983377\n\n</td><td>\n\nIn Enhanced Chat, the virtual\\_agent flag is always set to false\n\n</td><td>\n\nIn Enhanced Chat, the virtual\\_agent flag has never been set to true. If users are starting the conversation in Virtual Agent \\(VA\\), irrespective of the assistant, the flag must be set to true.\n\n</td><td>\n\n1.  Set up NAVA with Enhanced Chat.\n2.  Start a conversation in VA.\n3.  Check the virtual\\_agent flag on an interaction.\n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1984195\n\n</td><td>\n\nInteractions are reused every time the startVoiceInteraction Voice API is invoked\n\n</td><td>\n\nThe API should create a new interaction, but instead it reuses the interaction if it's active. This used to work correctly in Yokohama, but is now failing.\n\n</td><td>\n\nInvoke the startVoiceInteraction voice API to create an interaction.\n\n Expected behavior: The API creates a new interaction every time it is invoked.\n\n Actual behavior: The API reuses the interaction if it's active.\n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1987016\n\n</td><td>\n\nUnread message call is made even before the session is established\n\n</td><td>\n\nA call to get unread messages occurs before the session established. This can be seen on the console logs.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1988044\n\n</td><td>\n\nhasUnreadMessages value for conversations in the chat history widget does not matches with values in the 'Recent chat updates' widget using OffglideScriptObject.getConversationsByConsumerAccount\\(\\)\n\n</td><td>\n\nThe chat history widget 'now-lbf-chat-client' is using cache to show an 'unread' status for conversations. The 'Recent chat updates' widget is using the OffglideScriptObject.getConversationsByConsumerAccount\\(\\) API to fetch the latest five active conversations from the database. The 'unread' status for conversations in both widgets do not match.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1988112\n\n</td><td>\n\nAll the closed chats have the same name\n\n</td><td>\n\nThis issue occurs in Now Assist panel \\(NAP\\).\n\n</td><td>\n\n1.  Select **NAP**.\n2.  Select **Chat history**.\n\n Notice that all the closed chats have the same name.\n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1989830\n\n</td><td>\n\nAdditional assistantAttribues for Knowledge Graph NLQ: knowledge\\_graph\\_anchor\\_tables, knowledge\\_graph\\_focus\\_table, knowledge\\_graph\\_focus\\_record\\_id\n\n</td><td>\n\nTo execute KG-NLQ, certain attributes are needed to be passed to the tool. Presently, AO is getting following Knowledge Graph keys in assistantAttributes: knowledge\\_graph\\_name, knowledge\\_graph\\_sys\\_id, knowledge\\_graph\\_nlq\\_schema\\_sys\\_id, knowledge\\_graph\\_nlq\\_tags, knowledge\\_graph\\_nlq\\_schema, knowledge\\_graph\\_tags. For Now Assist panel \\(NAP\\) conversation, additional attributes are required: knowledge\\_graph\\_anchor\\_tables knowledge\\_graph\\_focus\\_table knowledge\\_graph\\_focus\\_record\\_id. This is in parity with glide implementation of kgnlq.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1990020\n\n</td><td>\n\nThe **Show more** button appears during streaming even when it's disabled\n\n</td><td>\n\nThe **Show more** button should be hidden, but appears for a long response for the synthesized response and is hidden after streaming is done.\n\n</td><td>\n\n1.  Ensure 'sn\\_nowassist\\_va.synthesized\\_response.shorten\\_response.disabled' is set to 'true' so that the **Show More** button is hidden for the synthesized response.\n2.  Ensure streaming is on.\n\n Expected behavior: On setting the property to 'true', **Show More** is hidden even while streaming.\n\n Actual behavior: When a long response shows up for the synthesized response, **Show More** is still shown during streaming and gets hidden after streaming is done.\n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1990179\n\n</td><td>\n\nLanguage Detection from French to English doesn't show the topic name in English\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1990700\n\n</td><td>\n\nClean up sys\\_ui\\_message for translation/update translation for contextual actions\n\n</td><td>\n\nWhen the user ends the conversation, the closing conversation message isn't translated to the user language.\n\n</td><td>\n\n1.  Change the user language to anything other than English.\n2.  In NLU mode, end the conversation.\n\n Expected behavior: The closing conversation message is translated to the user language.\n\n Actual behavior: The 'hi' contextual action isn't translated to the user language.\n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1991070\n\n</td><td>\n\nIn the middle of a topic tool execution when CLOSURE intent is detected, the conversation is stuck\n\n</td><td>\n\n \n\n</td><td>\n\n1.  Start a topic execution, such as 'Order stationary' \\(which has a couple of questions to ask to the user\\).\n2.  When the tool execution starts and the first question is asked to the user, give the reply, 'Exit immediately.'\n\n Notice that the conversation gets stuck, and no incoming payload is sent to AO.\n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1991780\n\n</td><td>\n\nExecution gets stuck in the playground and in Now Assist panel \\(NAP\\) with the subflow/flow tool if there is no valid input\n\n</td><td>\n\nThis issue may occur any time a tool needs an input. There should be proper error handling in these scenarios.\n\n</td><td>\n\n1.  Choose an agent, such as 'Order fruit flavored chocolate.\n2.  Enter an utterance, such as 'order'.\n\n Notice that the execution is stuck and the input returns empty, leading the execution to be stuck.\n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1992132\n\n</td><td>\n\nThe Virtual Agent \\(VA\\) link menu items are not displayed correctly\n\n</td><td>\n\nIn Enhanced Chat, VA link menu doesn't show the labels the way it shows on the standard chat. Instead it shows the label as plain text and shows the link below. If the link is longer, it increases the width of the 'Contact support window'. It should only show the label and shouldn't show the link.\n\n</td><td>\n\n1.  Open the Menu items from the branding.\n2.  Add a long link.\n\n Notice that the width of the window increases beyond the chat window, and the label is shown in plaint text and the link shows.\n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1992697\n\n</td><td>\n\nLive agent messages need to use callback URL to send to the user\n\n</td><td>\n\nLive agent messages are not being sent to the requester on lab instances because the URL in the http\\_connection for off glide conversation messages is not correct. Live agent requests need to have a callback URL to send to the off glide conversation so that the messages go through.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1992728\n\n</td><td>\n\nRequest ID missing in mosaic logs for conversation server requests\n\n</td><td>\n\nThe request ID is null in mosaic logs.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1992729\n\n</td><td>\n\nAdd preferred skills handling for Open Graph \\(OG\\)\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1993583\n\n</td><td>\n\nLLM calls time out after 60,000 milliseconds\n\n</td><td>\n\nEven when the system property 'com.glide.cs.dynamic.capability.timeout.f6f9e6e71bc38210f4200d81ec4bcb30' is set to 180 seconds, the LLM call times out after 60 secs.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1994599\n\n</td><td>\n\nOff glide code introduced an issue for DTAC when the agent sends a message to the requester\n\n</td><td>\n\nThe dynamic translation for messages doesn't work when the agent sends messages to the requester. It throws NPE.\n\n</td><td>\n\n1.  Create a Zurich instance.\n2.  Set up NAVA.\n3.  Set up DTAC.\n4.  Start a conversation between a requester and agent.\n5.  Make sure the requester is in a non-English language and the agent is in English.\n\n Observe that dynamic translation for messages doesn't work when the agent sends messages to the requester. It throws NPE.\n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1996246\n\n</td><td>\n\nWorkflow transfer context isn't working on Zurich\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1997012\n\n</td><td>\n\nDo not allow 'backup/fallback' URLs to be used for glide messages sent to OGCS\n\n</td><td>\n\nThe callback\\_url and pod\\_ip must be present in the tool execution request, or the Live Agent context, or the session context \\(for session-related messages back to OGCS\\).\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB1999793\n\n</td><td>\n\nRemove admin role\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB2001326\n\n</td><td>\n\nBot installation throws an error\n\n</td><td>\n\nAdmin is redirected to an error page.\n\n</td><td>\n\n1.  Provision an instance with the latest Google Chat plugin \\(3.0.0\\) installed.\n2.  Navigate to CI Admin Settings page for Channels and select **Google Chat** &gt; **Integrate with Now Virtual Agent**.\n\n Notice that Admin is redirected to an error page.\n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB2003421\n\n</td><td>\n\nWhen localization is enabled and the agent is triggered in a non-English language through Now Assist VIrtual Agent \\(NAVA\\) or Now Assist panel \\(NAP\\), the agent fails to execute\n\n</td><td>\n\nA mismatch is caused because AIA uses the untranslated English name.\n\n</td><td>\n\n1.  Enable localization.\n2.  Start a conversation in NAVA using a non-English language\n\n Expected behavior: Agent is executed successfully.\n\n Actual behavior: Agent fails to execute because the agent name lookup in AIA always uses the English \\(untranslated\\) name for comparison, causing a mismatch when a translated name is returned by the Unified Planner.\n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB2006393\n\n</td><td>\n\nPlan to release the disambiguation feature\n\n</td><td>\n\nThis is a product update.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nVirtual Agent\n\n PRB2006856\n\n</td><td>\n\nSerial number when conversation moves across nodes\n\n</td><td>\n\nVirtual Agent gets stuck. New messages are sent but the client doesn't render them until the page is reloaded.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nVirtual Agent Web Client\n\n PRB1825407\n\n</td><td>\n\nUnable to change ServiceNow VA message for com.glide.cs.general.multi\\_file\\_size\\_exceed\\_msg\n\n</td><td>\n\nEven if the value within com.glide.cs.general.multi\\_file\\_size\\_exceed\\_msg is modified, the following message is displayed: 'Looks like that file was too big to upload. 10 MB is the max.'\n\n</td><td>\n\n1.  Log in to a Washington DC instance.\n2.  Navigate to **sys\\_property - com.glide.cs.general.multi\\_file\\_size\\_exceed\\_msg**.\n3.  Modify the value.\n4.  Clear the cache.\n5.  Create a virtual agent topic within designer.\n6.  Add a 'File Picker' component.\n7.  Test it by adding a file that's more than 10MB.\n\n Observe that the following message is displayed, even if the value within com.glide.cs.general.multi\\_file\\_size\\_exceed\\_msg is modified: 'Looks like that file was too big to upload. 10 MB is the max.'\n\n</td></tr><tr><td>\n\nVirtual Agent Web Client\n\n PRB1976753\n\n</td><td>\n\nMessages sent in the new chat are some times getting merged with messages in the previous chat\n\n</td><td>\n\nThe new input is merged in the previous conversation.\n\n</td><td>\n\n1.  Start a new chat.\n2.  Give some input.\n3.  Start another chat before the response comes in.\n4.  Give a new input in the new chat.\n\n Notice the response from the previous chat sometimes show up in the new chat, and when refreshing the page, it's all in the same conversation, and the new input entered is merged in the previous conversation.\n\n</td></tr><tr><td>\n\nVirtual Agent Web Client\n\n PRB1978992\n\n</td><td>\n\nThe Portal Banner Carousel shows multiple widgets added for a single one\n\n</td><td>\n\n \n\n</td><td>\n\n1.  Log in with admin access.\n2.  Navigate to **sp\\_config** page.\n3.  Select **Designer**.\n4.  Add a page.\n5.  Add a container.\n6.  Add the Portal Banner Carousel widget.\n\nVerify only one widget was added on the Service Portal designer based on the page carousel.\n\n7.  Verify the widget works when opened in the new page.\n8.  Add another widget \\(simple list widget\\) to see if it's properly added.\n9.  Add the following variables in Coral theme:\n    -   now-dropdown-list--background-color-focus\n    -   now-assist-selfservice\\_FAB\\_icon\n    -   now-dropdown-list--background-color.\n\n Notice that they are displayed on the Network tab when the page loads.\n\n</td></tr><tr><td>\n\nVirtual Agent Web Client\n\n PRB1983355\n\n</td><td>\n\nMarkdown to HTML parsing issues when there are special characters in the payload\n\n</td><td>\n\n \n\n</td><td>\n\n1.  Create a topic in the designer with a text node with an response message containing a \\` \\(backtick\\) character.\n2.  Test the topic.\n\nNotice the response shows unintended HTML.\n\n\n Expected behavior: Parsing is broken and links are highlighted.\n\n Actual behavior: The HTML output is broken.\n\n</td></tr><tr><td>\n\nVirtual Agent Web Client\n\n PRB1992017\n\n</td><td>\n\nThe 'Thank you' text stays in chat even after sending and receiving response\n\n</td><td>\n\nThis issue occurs with Now Assist panel \\(NAP\\).\n\n</td><td>\n\n1.  Log in to an instance.\n2.  Open NAP.\n3.  Enter, 'What is spam' followed by 'Thank you.'\n\n Expected behavior: The 'Thank you' text disappears after the message is sent.\n\n Actual behavior: The 'Thank you' text says in the chat even after sending and receiving response. It is also observed that other prompts like 'What is spam' appear in the chat until a response gets generated.\n\n</td></tr><tr><td>\n\nVirtual Agent Web Client\n\n PRB1996311\n\n</td><td>\n\nAdd the 'fetchDocuments' attribute to be passed in contextData of the session API call request data parameters when switchContextConversation is 'true' and parsed from AIEL\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nVirtual Agent Web Client\n\n PRB1997398\n\n [KB2817799](https://hi.service-now.com/kb_view.do?sysparm_article=KB2817799)\n\n</td><td>\n\nThe now-chat-window library build is missing the rem multiplier, which causes tiny text in the ENHANCED\\_CHAT full screen portal\n\n</td><td>\n\nThe now-chat-window component renders with small text \\(10px instead of 16px\\) when loaded via the ENHANCED\\_CHAT path on Service Portal pages that set the root font-size to 62.5%. This as caused by changing the font-size in full-page.scss from an absolute pixel value to a rem-based theme variable.\n\n</td><td>\n\nRefer to the listed KB article for details.\n\n</td></tr><tr><td>\n\nVirtual Agent Web Client\n\n PRB1997587\n\n</td><td>\n\n'Start a new chat' from contextual Now Assist panel \\(NAP\\) doesn't map the conversation with a record\n\n</td><td>\n\n \n\n</td><td>\n\n1.  Open a Service Operations Workspace \\(SOW\\) incident record.\n2.  Launch contextual NAP by setting switchContextConversation on AIEX launcher.\n3.  Pick a non-active conversation under the 'Incident' tab in the NAP conversation picker.\n\nNotice that 'Start a new chat' shows at bottom.\n\n4.  Select a conversation.\n\n Notice that the conversation opened doesn't get mapped to a record.\n\n</td></tr><tr><td>\n\nVirtual Agent Web Client\n\n PRB1999442\n\n</td><td>\n\nThe live agent avatar changes when an image is sent\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nWalk-Up Experience\n\n PRB1981055\n\n</td><td>\n\nImage on the 'Walk up reservation' page does not display for users without a walk up role\n\n</td><td>\n\nUsers checking in via URL cannot see the logo image in the portal unless they have the role 'sn\\_walkup.walkup\\_manager'.\n\n</td><td>\n\n1.  Impersonate a user who doesn't have the Walk-Up manager role.\n2.  Navigate to the **Walk-up portal** to check in.\n\n Notice that the image will not appear on the page.\n\n</td></tr><tr><td>\n\nWord Document APIs\n\n PRB1987080\n\n</td><td>\n\nWord doc APIs fall back error separation handling for shared services\n\n</td><td>\n\n \n\n</td><td>\n\n1.  Log in to ServiceNow.\n2.  Hit Word doc APIs with the wrong URL.\n\n Observe that the fallback doesn't happen in a 404 case.\n\n</td></tr><tr><td>\n\nWord Document APIs\n\n PRB1987850\n\n</td><td>\n\nIssue with document sync when paragraph properties do not exist\n\n</td><td>\n\nAn error occurs when attempting to sync the document. This issue occurs when the document was generated using ChatGPT or other AI tools, or when content controls are positioned on blank text.\n\n</td><td>\n\n1.  Make changes to the content control fields with 'Track Changes' on.\n\nObserve that the selected paragraph should not have any styling.\n\n2.  Attempt to replace the value.\n\n Notice that it will throw an error.\n\n</td></tr><tr><td>\n\nWork Order Management\n\n PRB1998755\n\n</td><td>\n\nAnalytics data in manager mobile is not consistent with manager view\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nZero Copy Connector for ERP \\(Family Channel\\)\n\n PRB2000572\n\n</td><td>\n\nThe com.glide.erp.core plugin has a namespace 'sn\\_erp\\_integration' which creates the conflict for the scope name for the zccforerp app, which is blocking public script includes\n\n</td><td>\n\nThe com.glide.erp.core plugin has a namespace 'sn\\_erp\\_integration' which is creating the conflict for the scope name for zccforerp app which is blocking public script includes.\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nZero Copy Connectors \\(glide\\)\n\n PRB1995609\n\n</td><td>\n\nThe Trino REST API throws an exception for tables with long names \\(&gt; 30 characters\\), because 'nonce' is generated as the table name\n\n</td><td>\n\nWhen accessing a Workflow Data Fabric \\(WDF\\) table that references a glide table with a name &gt; 30 characters, the Trino REST API throws an NPE: '2026-02-19 14:52:28 \\(041\\) TRINO\\_REST-thread-37 8ECE056F474F32105679CCA4F16D437A txid=06cec96f474f TimingLogger \\*\\*\\* ERROR \\*\\*\\* Problem occurred while fetching DB response: Cannot invoke 'java.util.Set.iterator\\(\\)' because 'sqls' is null java.lang.NullPointerException: Cannot invoke 'java.util.Set.iterator\\(\\)' because 'sqls' is null'.\n\n</td><td>\n\n1.  Create a glide table with &gt;30 characters.\n2.  Create a WDF table with a column that references a column in the glide table.\n3.  Open the WDF table and include the reference column in the list view.\n\n An error displays on the page.\n\n</td></tr><tr><td>\n\nZing Text Indexing and Search Engine\n\n PRB1996302\n\n</td><td>\n\nInstalled applications aren't shown in application manager when the instance is upgraded to Australia\n\n</td><td>\n\nAfter upgrading an instance to Australia, installed applications \\(present in sys\\_store\\_app\\) aren't visible in the Application Manager UI when searched by name or scope. The issue occurs because the application isn't indexed by Zing Text Indexing and the Search Engine, which is required for search results to display correctly. This issue affects instances with customizations where 1\\) the root table is not marked as Text Index, 2\\) a child table is marked as Text Index at Collection level, and 3\\) there are no columns within the hierarchy that are marked as Text Index.\n\n</td><td>\n\n1.  Access the Application Manager on an upgraded instance.\n\n2.  Search for an installed application by name or scope.\n\n\n Observe that the application doesn't appear in the search results, even though it's listed as installed in the classic view.\n\n</td></tr></tbody>\n</table>## Fixes included\n\nUnless any exceptions are noted, you can safely upgrade to this release version from any of the versions listed below. These prior versions contain PRB fixes that are also included with this release. Be sure to upgrade to the latest listed patch that includes all of the PRB fixes you are interested in.\n\n-   [Australia EA Hotfix 1](https://www.servicenow.com/docs/r/release-notes/australia-patch-0-hf-1-PO.html)\n-   [Australia security and notable fixes](https://www.servicenow.com/docs/r/release-notes/australia-security-notables.html)\n-   [All other Australia fixes](https://www.servicenow.com/docs/r/release-notes/australia-all-other-fixes.html)\n\n**Parent Topic:**[Available patches and hotfixes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/release-notes/available-versions.md)\n\n"}}