| \n\nProblem\n\n | \n\nShort description\n\n | \n\nDescription\n\n | \n\nSteps to reproduce\n\n |
|---|---|---|---|
| \n\nDatabase Persistence - WDF\n\n PRB2024733\n\n [KB3137449](https://hi.service-now.com/kb_view.do?sysparm_article=KB3137449)\n\n | \n\nReports containing reference-type catalog item variables \\(lookup\\) fail to render data after upgrading to the Australia release\n\n | \n\nAfter upgrading to the Australia release, reports that contain reference-type catalog item variable columns fail to render data correctly. The affected reference-type variables don't resolve their lookup values, and their presence in the report additionally causes all other columns — including native table fields such as **Number**, **Created**, and **Closed** — to render as empty across all rows.\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nKey Management Framework \\(KMF\\) for Platform Encryption\n\n PRB2058369\n\n [KB3140571](https://hi.service-now.com/kb_view.do?sysparm_article=KB3140571)\n\n | \n\nMID Server is unable to fetch credentials after upgrading to Zurich or Australia\n\n | \n\nIn certain versions, there's a Unified Secrets Gateway \\(USG\\) service for credential management. During the upgrade to those versions, a system trigger script is designed to automatically execute and populate the sys\\_secret\\_identity \\_group\\_member table with the MID Server identity group mappings required for USG authentication. However, this trigger fails to complete successfully, leaving the table incompletely populated. As a result, the MID Server can't authenticate with USG and fails to retrieve credentials.\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nMulti-Instance Framework\n\n PRB2040054\n\n [KB3119447](https://hi.service-now.com/kb_view.do?sysparm_article=KB3119447)\n\n | \n\nThere's a flood of 'Unable to find vtable operation for operation id \\{\\}' messages that's generating millions of records in an instance for every Flow Designer execution\n\n | \n\nIn a cloned instance, the root cause of the flood of errors messages 'Unable to find vtable operation for operation id \\{\\}' in the syslog is sn\\_mif\\_vtable\\_ operation\\_context.vtable \\_operation is empty.\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nNow User Experience\n\n PRB2038702\n\n [KB3134148](https://hi.service-now.com/kb_view.do?sysparm_article=KB3134148)\n\n | \n\nA scoped public UI page isn't accessible without a login unless 'Name' is used vs a scoped endpoint in a sys\\_public record\n\n | \n\nIt should be accessible without a login, so a user can complete the authentication from Outlook.\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nSystem Events\n\n PRB1969068\n\n | \n\nThe 'Events process 0' job yields to memory pressure, causing event processing delays\n\n | \n\nWhen node memory pressure is high \\(live set ≥ ~91%\\), the JobYieldCheck mechanism triggers a yield on events process 0 despite it being a priority 25 \\(high priority\\) job. High-priority jobs should not be subject to automatic yield throttling, as this directly delays critical event processing and can result in P1 incidents. The memory pressure itself may be transient or difficult to diagnose quickly — heap dumps often show no obvious culprit, and identifying the root cause of elevated memory usage takes time. During that window, events process 0 is repeatedly yielded, stalling event processing pipelines that users depend on for time-sensitive operations. JobYieldCheck WARNING Job=events process 0 yields due to memory pressure logged on affected nodes. Node memory is sustained at 91–93% of max, with live set at ~91.44% \\(~1.28GB\\). glide.memory.watcher logs no active transaction warnings alongside persistent memory pressure status = true. There's only a single job visible in the queue during the yield window, yet throttling still triggers. However, users expect priority 25 jobs \\(events process 0\\) should not be yielded under memory pressure conditions. Yield throttling should be restricted to lower-priority workloads.\n\n | \n\n \n\n |
| \n\nTable Rotation\n\n PRB1959672\n\n [KB3071677](https://hi.service-now.com/kb_view.do?sysparm_article=KB3071677)\n\n | \n\nShard tables aren't created on an initial plugin install\n\n | \n\nWhen a plugin is manually installed, shard tables aren't created automatically.\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nUX Framework\n\n PRB2027095\n\n [KB3102030](https://hi.service-now.com/kb_view.do?sysparm_article=KB3102030)\n\n | \n\nThe latest component asset isn't selected when multiple asset associations exist in sys\\_ux\\_lib\\_ component\\_ m2m\\_asset, which impacts AI summary cards on UI Builder workspaces\n\n | \n\nWhen the AI summary card component was upgraded, its asset name changed from now-ai-summary-card/index to uxc-generative-ai/index. The upgrade doesn't clean up the old asset association, so the sys\\_ux\\_lib\\_component\\_m2m\\_asset table ends up with two associations for the same component \\(old and new asset\\). The component-to-asset selection query in GlideUxComponent DefProvider. getAssetNames ByComponentSysIds\\(\\) had no ordering and relied on default DB ordering. When duplicate associations exist, this could return the stale now-ai- summary-card/index asset, which is incompatible with the latest Platform AI Agents and Skills app. As a result the AI summary card fails to load on UI Builder workspaces. Classic UI uses a different rendering path, so it is unaffected.\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nProblem\n\n | \n\nShort description\n\n | \n\nDescription\n\n | \n\nSteps to reproduce\n\n |
|---|---|---|---|
| \n\nActivity Stream\n\n PRB2027954\n\n | \n\nAn activity filter's field's slushbucket initially has every field selected when the glide.ui.\\{table\\}\\_activity.fields property doesn't exist\n\n | \n\nFor non-task tables with an empty 'glide.ui.<table>\\_activity.fields' property, 'FilterFieldRepo.getTablePropertyFilters\\(' returned a hardcoded 'DEFAULT\\_FIELDS' constant. This default set was designed for task tables and didn't reflect the actual fields on the table, causing incorrect or missing fields in the activity stream.\n\n | \n\n1. Verify that the record is a non-task table record.\n2. Verify that the glide.ui.\\{table\\}\\_activity.field isn't set.\n3. On an instance, in UI16, create a interaction record.\n4. Select the **Filter Activity** button, all of the fields should be selected.\n5. Select the **Configure fields** to bring up that the slushbucket now aligns with the fields in the 'Filter Activity'.\n\n |
| \n\nActivity Stream\n\n PRB2040417\n\n | \n\nThe **Copy** button on the VTB view can't access copyJournalContent or GlideUIDefault\n\n | \n\nThe content doesn't get copied to the clipboard API and doesn't show the 'Copied to clipboard' notification.\n\n | \n\n1. On any instance, navigate to **All** > **Visual Task Boards**.\n2. Create a freeform board.\n3. Add a card on the newly-created board.\n4. Open the card and add a work note or comment.\n5. Select the **Copy journal content** button.\n\n Expected behavior: The content is copied to the clipboard API and shows a 'Copied to clipboard' toast.\n\n Actual behavior: The content doesn't get copied to the clipboard API and doesn't show the 'Copied to clipboard' notification.\n\n |
| \n\nAgent Chat\n\n PRB2021594\n\n | \n\nAn agent chat box isn't enabled when work is offer re-routed post blind queue transfer\n\n | \n\nIn most recent Australia release, ServiceNow CSM Workspace agent isn't able to type messages in the chat input box after they are re-routed an interaction that was rejected by a previous agent. The chat box should be enabled after re-routing acceptance.\n\n | \n\n \n\n |
| \n\nAgent Chat\n\n PRB2031080\n\n | \n\nSetting 'Disable agent inactivity check for API' to true makes the presence states disappear from the presence state picker in workspace's inbox\n\n | \n\nThe presence state picker should display all available states, even when 'Disable agent inactivity check for API' is set to true.\n\n | \n\n1. Log in to an instance.\n2. Navigate to the awa\\_presence\\_state table.\n3. Select **Update Personalized List** using the gear icon.\n4. Add the 'Disable agent inactivity check for API' column to the list view.\n5. Set the value of 'Disable agent inactivity check for API' to true for the 'Available' presence state.\n6. Navigate to Service Operations Workspace \\(SOW\\).\n7. Select the inbox icon.\n\nThe 'Available' option isn't displayed.\n\n8. Set the value of 'Disable agent inactivity check for API' back to false for the 'Available' presence state.\n\n See that the 'Available' option is displayed in the SOW presence state picker.\n\n |
| \n\nAgent Chat\n\n PRB2033499\n\n | \n\nImprove the presence state picker in workspace's inbox based on the new flag 'show\\_in\\_workspace' instead of 'Disable agent inactivity check for API'\n\n | \n\n \n\n | \n\n \n\n |
| \n\nAgent Chat\n\n PRB2051353\n\n | \n\nAgent presence indicator should be shown in the 'Transfer to Agent' list for third party\n\n | \n\nWhen searchTargetList is set, a list of agents is shown, but there's no presence indicator.\n\n | \n\n1. Create and offer a third party messaging interaction to a CSM Agent.\n2. Select the **Transfer to Agent** quick action.\n\n Expected behavior: It shows a list of agents along with presence indicator when searchTargetList is set.\n\n Actual behavior: It shows a list of agents with no presence indicator when searchTargetList is set.\n\n |
| \n\nAgent Chat\n\n PRB2052028\n\n | \n\nIntegration users can't read sys\\_cs\\_conversation\\_member for creating wrap up segment\n\n | \n\nThe wrap up segment creation fails with a 400 status and the error message: 'Failed to create wrap-up segment. Segment not found in implementations for extension point: interactionSegment'.\n\n | \n\n1. Create a third party messaging interaction.\n2. Offer to a CSM Agent.\n3. Call REST API to create a wrap up segment for that interaction and agent.\n\n Expected behavior: The wrap up segment is created and the API returns success.\n\n Actual behavior: The wrap up segment creation fails with a 400 status and the error message: 'Failed to create wrap-up segment. Segment not found in implementations for extension point: interactionSegment'.\n\n |
| \n\nAgent Chat\n\n PRB2055561\n\n | \n\nRename Now Assist, Moveworks and AI experience to ServiceNow Otto\n\n | \n\nThe **Sparkle** button for CRR should be replaced with the new **Otto** button. **CRR** button's tooltip 'Write with Now Assist' should be replaced with 'Write with AI'. Finally, the **Sparkle** icon and its label in the recommendation modal should be replaced with the **Otto** icon.\n\n | \n\n \n\n |
| \n\nAgent Chat\n\n PRB2055562\n\n | \n\nRename of Now Assist, Moveworks and AI experience to ServiceNow Otto\n\n | \n\n \n\n | \n\n \n\n |
| \n\nAgent Chat\n\n PRB2058031\n\n | \n\nAdd a missing flag on 'Requires ACL authorization'\n\n | \n\nA fix has ensured that the 'Requires ACL authorization' flag on 'Conversation Server' graphQL schema is set to true. However, due to a discrepancy in syncing branches, only the ACL changes added are live and not the graphQL schema changes.\n\n | \n\n \n\n |
| \n\nAgent Chat\n\n PRB2063949\n\n | \n\nSome messages are hidden on the agent's side when hideControl is true and contains searchText\n\n | \n\n \n\n | \n\n \n\n |
| \n\nAgile Development\n\n PRB2026219\n\n | \n\nThe **Group capacity** field is read only in sprint records\n\n | \n\n \n\n | \n\n1. Navigate to an instance.\n2. Navigate to the table 'rm\\_sprint.list'.\n3. Open any sprint record.\n\n Note that **Group capacity** \\(points\\) is read-only.\n\n |
| \n\nAI Agents \\(Glide Family\\)\n\n PRB2034699\n\n | \n\nGenAIMetadata M2MDaoImpl createAIAGenAI MetadataM2M doesn't assert that the genAILogId parameter is not NULL\n\n | \n\nThis causes a full table scan of the sys\\_gen\\_ai\\_ log\\_metadata table. This code is invoked by the AsyncMessageProcessor.\n\n | \n\n \n\n |
| \n\nAI Agents \\(Glide Family\\)\n\n PRB2037758\n\n | \n\nAI Agents randomly throw a tool execution error: 'Failed to execute async FDIH tool'\n\n | \n\nAt any random tool call, the AI Agent throws: 'Sorry, there was a problem on my side trying to complete this request. Try asking again later'. In logs, it shows 'FDIH async tool call exception'.\n\n | \n\n1. Log in to an instance.\n2. Invoke the Quote AI agent.\n3. Input a multi-paragraph, conversational prompt.\n\n Observe that, at any random tool call, it throws: 'Sorry, there was a problem on my side trying to complete this request. Try asking again later'. In logs, it shows 'FDIH async tool call exception'.\n\n |
| \n\nAI Agents \\(Glide Family\\)\n\n PRB2051367\n\n | \n\nTTL isn't honored in sys\\_og\\_conversational \\_cache\\_configuration in the absence of any other invalidation rule\n\n | \n\nThe persona section doesn't show the new memories immediately, but they're visible after 24 hours.\n\n | \n\n1. Set up LTM extraction on Glide \\(enable sys\\_prop use\\_new\\_ltm\\).\n2. Set up DARE with memory enabled \\(in pipeline.yaml, set enable\\_user\\_persona\\).\n3. Create a conversation with some details that are a candidate for LTM extraction \\(for example, 'I like cycling'\\).\n4. Verify that memories are extracted \\(the ltm job runs every hour\\).\n5. After new memories have been extracted, check the persona section.\n\n Observe that it doesn't show the new memories. However, they will be visible after 24 hours.\n\n |
| \n\nAI Agents \\(Glide Family\\)\n\n PRB2059351\n\n | \n\nRecord scope should override the user session scope\n\n | \n\nFor AI Agents, when any record of a user instance is used, the record scope should override the user session scope of the MSP as per the domain separation policy. However, that's not happening. For example, when an AI Agent with a retriever tool is triggered by any record in a user instance \\(like C1\\), it fetches KBs/results from all the user instances under that MSP.\n\n | \n\n \n\n |
| \n\nAI Agents \\(Glide Family\\)\n\n PRB2059390\n\n | \n\nRole masking isn't unset when running a workflow\n\n | \n\n \n\n | \n\n \n\n |
| \n\nAI Experience Framework - Glide\n\n PRB2034740\n\n | \n\naiux\\_service/ chat\\_check\\_access should work with the default experience name to query the deployment document ID\n\n | \n\nThere should be a way to query by experience name so that there is no need to force pass a sys\\_id each time.\n\n | \n\n \n\n |
| \n\nAI Experience Framework - Glide\n\n PRB2036766\n\n | \n\nExperience cache population only emits the default theme\n\n | \n\nMulti-theme \\(user-criteria\\) themes are missing from the edge cache, so targeted users get the wrong theme.\n\n | \n\n \n\n |
| \n\nAI Experience Framework - Glide\n\n PRB2061584\n\n | \n\nTrue-up the AI UX Builder Store app\n\n | \n\n \n\n | \n\n \n\n |
| \n\nAI Gateway - Security\n\n PRB2052119\n\n | \n\nAs part of the name change, update error strings in MCPOAuthConstants.java that reference 'Now Assist' to 'ServiceNow Otto'\n\n | \n\nThe changes will be made in Zurich and Australia. Also, an additional change is needed for the description in glide/glide-ai-security-scan.\n\n | \n\n \n\n |
| \n\nAI Search \\(Glide\\)\n\n PRB1859571\n\n | \n\nA search retrieval agent returns an incorrect catalog item URL\n\n | \n\n \n\n | \n\n \n\n |
| \n\nAI Search \\(Glide\\)\n\n PRB2052168\n\n | \n\nNo\\_answer Genius Result is streamed intermittently\n\n | \n\nA Genius Result rarely shows, but it should not show at all.\n\n | \n\n1. Navigate to /sp.\n2. Search for something that gives a no\\_answer result, like 'baseball world series'.\n\n Observe that a Genius Result rarely shows. It should not show at all.\n\n |
| \n\nAI Search \\(Glide\\)\n\n PRB2054276\n\n | \n\nThe fix script shouldn't backfill non-default sources\n\n | \n\nWhen the user upgrades to an instance with additional sources in the multi-content feature, the additional sources are marked as 'Included'.\n\n | \n\nUpgrade an instance without additional sources in the multi-content feature to a version with the feature.\n\n Observe that the additional sources are marked as 'Included'.\n\n |
| \n\nAI Search \\(Glide\\)\n\n PRB2054932\n\n | \n\nIn Moveworks API V2, support linking ServiceNow Security Center \\(SSC\\) to a search profile\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nAI Search \\(Glide\\)\n\n PRB2054938\n\n | \n\nFor the Moveworks API V2, return chunks when passing an additional flag\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nAI Search \\(Glide\\)\n\n PRB2058047\n\n | \n\nIndexing with multiple semantic indexing configurations with the same name on different models isn't working\n\n | \n\nWhen multiple semantic index configurations are created on the same datasource with the same semantic field name but different embedding models, only the first configuration is loaded into the active semantic index field cache. Subsequent configurations are silently ignored, so ingestion and search only use one embedding model for that field. Only one embedding model is used for indexing and search when multiple semantic index configurations share the same semantic field name. Additional configurations with the same semantic field name are not visible in getSemanticIndexFieldMapping\\(\\). No error or warning is logged when the duplicate-name configurations are skipped. Thus, multi-embedding model support for a single semantic field is broken. Configurations are silently lost during cache population. This affects ingestion, search, and any callers that rely on getSemanticIndexFieldMapping\\(\\).\n\n | \n\n1. Create two active ais\\_semantic\\_ index\\_configuration records on the same datasource with the same semantic\\_field\\_name but different embedding\\_models values.\n2. Add valid component fields via ais\\_semantic\\_ component\\_field for each record and set a valid semantic\\_ snippetization\\_configuration.\n3. Flush the datasource object cache \\(AisConfiguration CacheManager. flushDatasource ObjectCache\\(\\)\\).\n4. Call AisConfiguration. get\\(\\).getSemantic IndexFieldMapping\\('kb\\_knowledge','kb\\_knowledge'\\).\n\n Observe that only one SemanticFieldConfiguration is returned for semantic\\_search and the other is silently dropped.\n\n |
| \n\nAI Search\n\n PRB1875924\n\n [KB3137872](https://hi.service-now.com/kb_view.do?sysparm_article=KB3137872)\n\n | \n\nAI search ingestion sticks when the 'Size in Bytes' column has an empty value in sys\\_attachment for an attachment that has a size more than 25MB\n\n | \n\n \n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nAI Search\n\n PRB1902419\n\n | \n\nThe conversation ID isn't logged to the sys\\_search\\_event table\n\n | \n\n \n\n | \n\n1. On an AI Search-enabled instance, start a new chat with Virtual Agent \\(VA\\).\n2. Enter 'what is spam'.\n3. Flush queued signals.\n4. Open the sys\\_search\\_event table, and if necessary, add the **Conversation ID** field to the list/form.\n\n Expected behavior: Since it was from VA, there should be a conversation.\n\n Actual behavior: The conversation ID is empty.\n\n |
| \n\nAI Search UX\n\n PRB2004411\n\n | \n\nRefactor the synthesized Genius Result presence filter from Data Broker into the Java layer\n\n | \n\nCurrently, the logic to conditionally execute the synthesized Genius Result — specifically, the filter that checks whether a Genius Result is present before execution — lives in the Data Broker transform layer \\(UX layer\\). This means the filter isn't automatically applied across all clients and must be manually maintained per-client in the Data Broker. This logic must be moved into the Java layer so that it is applied universally and automatically for all users, reducing duplication and the risk of inconsistent behavior across different consumers of the Search API.\n\n | \n\n1. Review the Data Broker transform at sys\\_ux\\_data\\_ broker\\_transform\\_ 0c735fb4530422104 accddeeff7b12dd.xml\\#L44.\n2. Observe that the conditional filter that gates execution of the synthesized Genius Result on its presence.\n3. Note that this filter only applies to clients using this specific Data Broker transform; it isn't enforced at the Java/API layer.\n\n A user that bypasses or doesn't use this Data Broker transform doesn't have the filter applied, resulting in potentially inconsistent or unintended behavior around synthesized Genius Result execution.\n\n |
| \n\nAI Search UX\n\n PRB2014714\n\n | \n\nIgnore Genius Result's limit for citations in sync mode\n\n | \n\n \n\n | \n\n1. On an AI Search enabled instance with synthesized response configured for portal, navigate to a portal and complete a query that yields a synthesized response.\n2. Set the system property 'glide.ais.query. disable\\_async\\_mode' to true.\n3. Do same search in portal.\n\nThe user should still get a synthesized response.\n\n4. Open the search application \\(presumably NAVA\\) and set the Genius Result limit to 1.\n5. Do the same search in portal.\n\n Expected behavior: Users still get a synthesized response.\n\n Actual behavior: No Genius Result renders because of no citations.\n\n |
| \n\nAI Search UX\n\n PRB2038703\n\n | \n\nInstance creation failure for com.glide.search. graphql.query. Suggestions from service portal's typeahead AIS Suggestions API\n\n | \n\nWhen something is searched for in the portal's typeahead, no suggestions appear and AIS Suggestions API calls in the network tab return 'Instance creation failure for: com.glide.search. graphql.query. Suggestions', and 'DataFetchException'.\n\n | \n\n \n\n |
| \n\nAI Search UX\n\n PRB2054213\n\n | \n\nURLs with special characters like $ break streaming for non-Virtual Agent clients\n\n | \n\nStreaming starts successfully, but it stops partway through and the full answer is never rendered.\n\n | \n\n1. Open an AIS-enabled instance.\n2. Make sure 'Synthesized Response' is enabled in portal.\n3. Navigate to the portal with Now Assist enabled.\n4. Search for 'How can I reset my password?'.\n\n Expected behavior: The full answer streams successfully.\n\n Actual behavior: Streaming starts successfully, but it stops partway through and the full answer is never rendered.\n\n |
| \n\nAI Search UX\n\n PRB2054952\n\n | \n\nRename Now Assist to Otto within AI Search components\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nAI Search UX\n\n PRB2056856\n\n | \n\nReplace the sparkle icon animation with the Otto animation for synthesized Genius Results \\(GR\\)\n\n | \n\n \n\n | \n\n1. Open an instance with multi-content GR configured.\n2. Navigate to portal/global search.\n3. Search for a query that returns a synthesized GR.\n4. Check the loader in the GR component when the loading state is showing.\n\n Expected behavior: The loader state shows the Otto animation.\n\n Actual behavior: The loader state shows the sparkle icon animation.\n\n |
| \n\nAI Search UX\n\n PRB2057349\n\n | \n\nRename Now Assist to Otto for typeahead suggestions\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nAI Search UX\n\n PRB2073716\n\n | \n\nFor non-admin users, search results and suggestion navigation on portals are redirecting to platform view\n\n | \n\nAfter upgrading to Australia Patch 5 or Zurich Patch 12, non‑admin users performing a search on a portal \\(for example, /esc\\) experience incorrect navigation. Selecting a regular search result or a suggested search result opens the record in the platform view rather than within the portal.\n\n | \n\nScenario 1:\n\n 1. Upgrade an instance to Australia Patch 5 or Zurich Patch 12.\n2. Log in as a non‑admin user.\n3. Perform a search on a portal, such as /esc or /sp.\n4. Select the regular search result that is returned.\n\n Observe that the record opens in platform view instead of the portal.\n\n Scenario 2:\n\n 1. Upgrade an instance to Australia Patch 5 or Zurich Patch 12.\n2. Log in as a non‑admin user.\n3. Enter a search term on a portal, such as /esc or /sp, without submitting the search.\n4. Select a suggested search result in the typeahead drop-down list.\n\n Observe that the record opens in platform view instead of the portal.\n\n |
| \n\nAlumni Center\n\n PRB2054850\n\n | \n\nAdd a null check when using getRefRecord\\(\\)\n\n | \n\n \n\n | \n\n \n\n |
| \n\nAnalytics Data API\n\n PRB1973007\n\n | \n\nThe Platform Analytics 'pivot table' unit type doesn't persist\n\n | \n\nWhen creating a pivot table using two tables as the data sources, the 2nd and 3rd columns swap their values.\n\n | \n\n1. Create a pivot table visualization within a dashboard.\n2. Add in two tables as data sources.\n3. Create four columns on the pivot table, with the first two column being a count of each respective table and the last two columns a sum of all the values with other columns.\n4. Save the visualization.\n5. Exit editing mode.\n6. Refresh the dashboard.\n\n When the order of the columns is the count of table 1, count of table 2, sum of table 1's column, sum of table 2's column, and when users refresh the dashboard, the 2nd and 3rd columns values swap, with the values from column 3 appearing in column 2 and vice versa.\n\n |
| \n\nAnalytics Data API\n\n PRB2039649\n\n | \n\nThe Platform Analytics dashboard ignores the data source filter\n\n | \n\nThe 'Is one of' operator doesn't function as expected on the source. The issue is reproducible in Australia with the Data Visualization plugin version 29.1.0 and in Zurich with version 28.5.0. However, the functionality works as expected in Yokohama with version 28.0.29 and in Zurich with version 28.4.5.\n\n | \n\n1. Open an instance.\n2. Create an indicator scorecard visualization.\n3. Select **Number of Incidents** as the data source.\n4. Apply a source condition using the 'Is one of' operator.\n5. Select the required priority values.\n\n Expected behavior: Only the selected priority is reflected.\n\n Actual behavior: All priorities are reflected in the indicator scorecard visualization.\n\n |
| \n\nAnalytics Data API\n\n PRB2050449\n\n | \n\nNext Experience Widgets load with an 'Unable to generate chart' error\n\n | \n\nThe error reads: 'Error Unable to generate chart. Cannot invoke 'com.glide. glideobject. GlideDateTime.after \\(com.glide. glideobject. GlideDateTime\\)' because 'scoresModifiedAt' is null.'.\n\n | \n\n \n\n |
| \n\nAnalytics Data API\n\n PRB2053974\n\n | \n\nBubble chart bubbles render horizontally in Platform Analytics Workspace \\(PAW\\) instead of distributed across both X and Y axes\n\n | \n\nAfter upgrading to Australia, bubble charts in PAW now render bubbles horizontally \\(all on Y = -1\\) instead of being distributed diagonally across both X and Y axes as expected. The same configuration in the Classic Reporting module \\(sys\\_report.LIST\\) correctly displays bubbles distributed across both axes. The bubbles are rendering and not stacking, but the axis distribution logic differs between PAW and Classic Reporting. In Classic Reporting, bubbles are positioned diagonally across both X and Y axes. Each rating value \\(Dissatisfied, N/A, Satisfied, Very Satisfied\\) appears at a distinct \\(X, Y\\) coordinate pair. In PAW, all bubbles are rendered on the same horizontal line \\(Y = -1\\), with X-axis variation only. There's no Y-axis differentiation.\n\n | \n\n1. Navigate to **Platform Analytics** > **Library** > **Data Visualizations**.\n2. Select **Create data visualization**.\n3. Choose **Bubble** as the data visualization type.\n4. Add the asmt\\_metric\\_result table as the data source.\n5. Add a custom condition: Metric is 'How likely is it that you would recommend this service to others?'.\n6. Select **Run** and then add this source.\n7. In the 'Dimensions' section, set the **Group by** to 'Metric definition' and apply.\n8. Select **Run**.\n\n Expected behavior: Bubbles should be distributed across both X and Y axes, matching the Classic Reporting output. Each unique combination of Row \\(Actual Value\\) and Column \\(Actual Value\\) should result in a distinct \\(X, Y\\) coordinate pair on the visualization.\n\n Actual behavior: All bubbles are aligned horizontally at Y = -1, with X-axis values varying. The chart is unreadable and does not match the intended visualization.\n\n |
| \n\nAnalytics Export API\n\n PRB2021342\n\n | \n\nThe email layout in an Platform Analytics scheduled export doesn't match the received email format\n\n | \n\nPlatform Analytics scheduled reports aren't honoring the email body configured when the field **omit\\_if\\_no\\_records** is true.\n\n | \n\n \n\n |
| \n\nApplication Install Engine\n\n PRB2056922\n\n | \n\nInstall engine reads the dependencies from package.json with a fall back to the previous way when not available\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nApplication Manager\n\n PRB2022268\n\n | \n\nThe application manager sys\\_app\\_version displays duplicate records for the same application and version, which is causing the app to be 'Installation blocked'\n\n | \n\nAs part of the AI testing, it's been observed that the app installations are blocked. The sys\\_app\\_version displays duplicate records for the same application, which is causing the app installations to be blocked, despite the app versions being available as well as the license checks having successfully completed.\n\n | \n\n1. Navigate to an instance.\n2. Navigate to App Manager.\n3. Open any app \\(for example, sn\\_ai\\_itsm\\_cont\\) which is licensed and validated on CI \\(usageanalytics\\) prod, but has yet showed 'Not Licensed'.\n4. Select **Install**.\n5. It just fails with 'Installation blocked' on that app itself.\n6. Open sys\\_app\\_version table.\n7. Check the app/scope id.\n\n Expected behavior: It should have only one record for that app and a specific app version.\n\n Actual behavior: It has multiple records for the same app and app version.\n\n |
| \n\nApplication Manager\n\n PRB2057729\n\n [KB3140027](https://hi.service-now.com/kb_view.do?sysparm_article=KB3140027)\n\n | \n\nUsers can't publish custom-scoped applications after upgrading to Zurich or Australia\n\n | \n\n \n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nAsset Management Common\n\n PRB2024372\n\n | \n\nRelated lists aren't rendered in Hardware Asset Workspace despite existing in an configuration\n\n | \n\nCertain related lists such as 'Hardware', 'Software licenses', 'Bundles', and 'Other' assets aren't displayed in Hardware Asset Workspace even though they are present in the Workspace configuration. Analysis confirmed that the related lists exist in the latest configuration \\(physical\\_asset\\_workspace view\\) and are conditionally loaded. The issue results in only a subset of related lists being visible in Hardware Asset Workspace while others remain hidden.\n\n | \n\n \n\n |
| \n\nAsset Management\n\n PRB2025075\n\n [KB3052414](https://hi.service-now.com/kb_view.do?sysparm_article=KB3052414)\n\n | \n\nA catalog task isn't created in Hardware Asset's refresh flow\n\n | \n\nThere's similar issues with the other flows as well, like transfer order, transfer order line, and contract approval.\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nAsynchronous Message Bus \\(AMB\\)\n\n PRB2040279\n\n | \n\nAdd bearer token authentication support to Asynchronous Message Bus \\(AMB\\) client library\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nAuthentication Factors\n\n PRB2037251\n\n | \n\nUpdate interactions post-identification and authentication\n\n | \n\nThe 'Interactions' table has only 'Guest' resolved. It should have the user reference resolved post-identification and authentication.\n\n | \n\n \n\n |
| \n\nAuthentication Factors\n\n PRB2066684\n\n | \n\nMatch KB identification phone numbers are ignoring special characters\n\n | \n\nQuestions with the category 'phone number' aren't matched against formatted stored phone numbers during voice agent identification flow.\n\n | \n\n \n\n |
| \n\nAutomated Test Framework \\(ATF\\)\n\n PRB2012913\n\n | \n\nTests fail with an error: 'Timed out waiting for intent feedback <Intermittent, slow loading forms, SAP>'\n\n | \n\nWhen Automated Test Framework \\(ATF\\) sends an intent to the UXF framework, the intent is received by UXF but is silently terminated/consumed without any feedback being returned to the caller. There's no success response, failure response, error message, or 'action not available' status sent back. Because of this, ATF can't determine whether the request failed due to unsupported actions, missing configuration, processing errors, or temporary issues. This prevents ATF from performing retries, fallback handling, or proper error recovery.\n\n | \n\n \n\n |
| \n\nAutomated Test Framework \\(ATF\\)\n\n PRB2017949\n\n | \n\nThere's stuck execution trackers due to Automated Test Framework \\(ATF\\)'s new feature metadata tracing\n\n | \n\nFor invalid metadata table names in sys\\_traced\\_metadata records, the generateMissingPayloadHashes throws an error and causes the final payload hash calculation execution trackers to be stuck.\n\n | \n\n1. Ensure that metadata tracing is on.\n2. Run a test on a table with a long name \\(such as 'sys\\_og\\_conversational \\_cache\\_configuration', more than 40 characters\\).\n\n Observe that the sys\\_traced\\_metadata records truncate the long table name \\(sys\\_traced\\_metadata records save table names up to 40 characters whereas metadata table names can be up to 80 characters in length\\). Observe at the end of the test, there's stuck sys\\_execution\\_trackers while generating payload hashes for the sys\\_traced\\_metadata records because the truncated metadata table name is invalid. It thus throws an error.\n\n |
| \n\nBusiness Calendar Filter Options\n\n PRB1977276\n\n | \n\nFilter values included with the 'Fiscal Calendar' \\(com.snc.fiscal\\_calendar\\) plugin aren't translated\n\n | \n\nFilter values included with the 'Fiscal Calendar' \\(com.snc.fiscal\\_calendar\\) plugin aren't translated when users change their language preferences. If a user switches to French \\(Canada\\), the filter value 'Next 3 fiscal months' should be translated as 'es 3 prochains mois fiscaux'. However, if a user switches to French \\(Canada\\), the filter value 'Next 3 fiscal months' is actually translated as '3 Fiscal Months suivant'. There are multiple other filter values included with the plugin that are affected.\n\n | \n\n1. Provision an instance with a language other than English and the 'Fiscal Calendar' \\(com.snc.fiscal\\_calendar\\) plugin installed.\n2. In English, open any list that can use 'Fiscal Calendar' list filters for a date range.\n3. Set the language to anything other than English.\n4. Refresh the page.\n\n Notice that the filter value still displays some of the text in English.\n\n |
| \n\nCanonicalization Data Services \\(CDS\\)\n\n PRB2053470\n\n | \n\nData uploaded to cds\\_server\\_staging table is blocked within instances\n\n | \n\nThis issue occurs in instances where the property 'glide.cmdb.canonical.URL' is set to https://<instance\\_name>.service-now.com/ and ends with '/'. Unfortunately, that is the base instance value, and it affects the upload portion of CDS.\n\n | \n\n \n\n |
| \n\nCase and Knowledge Management for HR Service Delivery\n\n PRB2023216\n\n | \n\nShip the required RCAs per the analysis result\n\n | \n\nAlso, analyze those RCAs for which the analysis result said not to ship. Trigger automation and verify the result if there are any failures.\n\n | \n\n \n\n |
| \n\nCase and Knowledge Management for HR Service Delivery\n\n PRB2023219\n\n | \n\nShip the required RCAs as per the analysis result\n\n | \n\n \n\n | \n\n \n\n |
| \n\nCase and Knowledge Management for HR Service Delivery\n\n PRB2025681\n\n | \n\nDue to 'getRefRecord', a RCA is generated in the Oracle HCM job execution that should be marked as 'Allowed'\n\n | \n\nDue to the use of 'getRefRecord' in the script include, a RCA record is generated with the source scope as: 'HR Service Delivery integration with Oracle HCM'. the target scope as 'Human Resources: Core', the target as: 'Table: HR Profile', and the operation as 'Read' after running the Oracle HCM job. This RCA should be marked as 'Allowed' and pushed to the repo.\n\n | \n\n1. Provision an instance with Oracle HCM related plugins installed.\n2. Navigate to the Oracle HCM Cloud Integration Source record.\n3. Ensure that on the Integration Service record, **Workers** is active.\n4. Select the **Run Job** button.\n\n After some time, the RCA record is generated when 'Job Transform Map' starts running. This RCA is created by the source 'Script Include: OracleHCMJob TransformHelperSNC' where 'getRefRecord' is used.\n\n |
| \n\nCase and Knowledge Management for HR Service Delivery\n\n PRB2028299\n\n [KB3061412](https://hi.service-now.com/kb_view.do?sysparm_article=KB3061412)\n\n | \n\nIn Platform Analytics, an ACL isn't letting an admin user modify or create data visualizations in dashboards or data visualizations\n\n | \n\nWhen editing any visualization in a dashboard with the sn\\_hr\\_er\\_case table as a data source, the visualization can't access its data source. As a result, metrics are turned off and can't be edited, preventing updates or modifications to the visualization. There is error: 'You don't have access to the data source used in this visualization'.\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nCase and Knowledge Management for HR Service Delivery\n\n PRB2055197\n\n | \n\nIn Alumni Center, update RCAs in HR Core for the getRefRecord\\(\\) for Australia\n\n | \n\n \n\n | \n\n \n\n |
| \n\nChange Management\n\n PRB2035555\n\n | \n\nThe 'All' filter on the 'Create Change' page doesn't display all standard change templates when a template has no category or catalog\n\n | \n\nWhen the 'All' filter is selected for standard change templates on the 'Create Change' page, not all templates are displayed. This is because one template has no category. The null category errors the 'can category be read by user' check.\n\n | \n\n \n\n |
| \n\nChange Management\n\n PRB2035924\n\n [KB3093597](https://hi.service-now.com/kb_view.do?sysparm_article=KB3093597)\n\n | \n\nStandard changes created from a problem aren't linked to the parent task\n\n | \n\nThe issue is reproducible if users untick the 'Two step' checkbox under **Change** > **Administration** > **Standard Change Properties** and then perform **cache.do** > **Clear Cache**. A standard change created from a task \\(incident/problem\\) aren't linked to a parent task. If users **Check Conflicts** before saving a child change from a project requested item, it won't attach the change to the parent item.\n\n | \n\n \n\n |
| \n\nChange Management\n\n PRB2052987\n\n | \n\nNewChangeRedirectProcessor only checks the system-wide glide.ui.polaris.experience property and ignores per-user glide.ui.polaris.use preference when deciding Next Experience redirect for Create Change\n\n | \n\nThe file app-itsm/glide-service-mgt/ src/main/plugins/ com.snc.change\\_request/ update/sys\\_processor\\_ 0af16f2d53631010 34d1ddeeff7b12b6.xml \\(NewChangeRedirectProcessor, path new\\_change\\_redirect\\), line 76: var polarisEnabled = 'gs.getProperty\\('glide.ui.polaris.experience', false\\) === 'true';' — only reads instance-wide sys\\_property, ignores per-user preference glide.ui.polaris.use \\(sys\\_user\\_preference table\\), the documented mechanism for per-user Next Experience toggle. The user opted out at a user level, but still was redirected into Next Experience's create-change flow when the system property is on. polarisEnabled check should account for both glide.ui.polaris.experience \\(system\\) and glide.ui.polaris.use \\(user preference\\) — not the system property alone.\n\n | \n\n1. Turn on the system property glide.ui.polaris.experience = true and com.snc.change\\_ request.next\\_ create\\_page = true.\n2. Set the sys\\_user\\_ preference glide.ui.polaris.use = false for a specific test user \\(system unchecked, User = test user\\).\n3. Log in as that user.\n4. Trigger **Create New Change** \\(module or UI action\\) so the request hits the new\\_change\\_redirect processor.\n5. Observe the redirect.\n\n Expected behavior: The redirect respects the user-level opt-out and goes to sn\\_chg\\_model \\_ui\\_landing.do \\(UI16\\).\n\n Actual behavior: The redirect goes to now/change-management/create-change/ \\(Next Experience\\), ignoring the user preference.\n\n |
| \n\nChange Management\n\n PRB2053039\n\n | \n\nIn the 'Change risk assessment' answer generator skill flow, replace the Now Assist terminology with Otto rebranding\n\n | \n\nThe suggestion message should contain 'Check answers generated by AI for accuracy'.\n\n | \n\n1. Navigate to **SOW** > **Change Request**.\n2. Select **Assess Risk** in the 'Overview' tab.\n3. Select **Generate Answers**.\n4. Wait until risk assessment completes answer generation.\n5. Open risk assessment.\n\n Observe that the suggestion message doesn't contain 'Check answers generated by AI for accuracy'.\n\n |
| \n\nCMDB Identification and Reconciliation\n\n PRB2021886\n\n | \n\nNull dbquery results must be preserved as null instead of wrapped\n\n | \n\n \n\n | \n\nRun a payload for a non-existing table that has a sys\\_id in the payload.\n\n Where encryption wrappers are constructed, dbq.execute\\(\\) would normally return null when querying this non-existent table. Now, code is wrapping the null.\n\n |
| \n\nColumn Level Encryption\n\n PRB2005360\n\n | \n\nOn an encrypted **HTML** field, getElement\\(fieldName\\) returns a GlideElement with a value of 'null' instead of an empty string \\(''\\), causing the condition ge == null to evaluate as true\n\n | \n\nThe field value conversion logic checks for encryption before validating whether the value exists. When encryption is enabled on an empty field, the system attempts to process a null value through the encryption path, which returns the literal string 'null' instead of handling it as an empty value.\n\n | \n\n \n\n |
| \n\nCondition Builder\n\n PRB2054935\n\n | \n\nCreate a sys property to determine the Glide version for condition builder\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nConfiguration Management Database \\(CMDB\\)\n\n PRB1994587\n\n | \n\nA race condition between IRE LazyWriter and Deletion Strategy causes the configuration item \\(CI\\) state to flip incorrectly\n\n | \n\nA CI's state is flipping from installed to stale during Discovery \\(delete strategy execution\\). A race condition occurred between IRE's asynchronous batch update of the **last\\_discovered** field using 'db.executeLazy\\(\\)' and the execution of the Deletion Strategy. The LazyWriter delay caused the Deletion Strategy to process stale 'last\\_discovered' values, marking valid CIs as retired despite their presence in the payload.\n\n | \n\n \n\n |
| \n\nConfiguration Management Database \\(CMDB\\)\n\n PRB2017559\n\n | \n\nThe health configuration cache is ineffective due to a shared cache eviction\n\n | \n\nThe getHealthConfiguration\\(\\) method in HealthConfigManager.java is not getting effective cache hits. The current implementation caches per \\(metricSysId + className + domainId\\) key, creating a few hundred cache entries. Since this is a shared cache, entries get evicted before they can be reused, resulting in repeated DB queries for records that never change during processing.\n\n | \n\n1. Create health configuration rules and observe the cache entry through cache\\_inspect.do.\n2. Create a pressure on the system to cause cache eviction.\n\n Observe in the code path that the cache is rebuilt every time there is an eviction. The caching path is controlled via sys\\_property and only applies to the non-domain path.\n\n |
| \n\nConfiguration Management Database \\(CMDB\\)\n\n PRB2020295\n\n | \n\nINSERT\\_NOT\\_ALLOWED\\_FOR\\_SOURCE incorrectly classified as a partial error causes the cmdb\\_ire\\_partial\\_payloads table to bloat and an out of memory \\(OOM\\) error\n\n | \n\nWhen an IRE data source rule blocks inserts for a class and data source, affected records are incorrectly saved as partial payloads. Since the block is permanent, these partial payloads can never complete — each retry creates a new entry, causing the cmdb\\_ire\\_partial\\_payloads table to grow unboundedly. If the partial payload contains a large number of related or lookup items, this can also lead to OOM on app nodes.\n\n | \n\n \n\n |
| \n\nConfiguration Management Database \\(CMDB\\)\n\n PRB2021367\n\n | \n\nImplement totals calculation for the group view when applying a class filter qualifier configuration\n\n | \n\n \n\n | \n\n \n\n |
| \n\nConfiguration Management Database \\(CMDB\\)\n\n PRB2026628\n\n | \n\ngetRefRecord\\(\\) scoping bypass due to directive changes\n\n | \n\n \n\n | \n\n \n\n |
| \n\nConfiguration Management Database \\(CMDB\\)\n\n PRB2030304\n\n | \n\nOrphanProcessor skips CIs and reprocesses records after batch timeouts due to unordered HashMap iteration\n\n | \n\nWhen the CMDB Health orphan metric job times out MID-run on large datasets, it saves an incorrect resume position and silently skips CIs on the next run. As a result, orphan CIs appear healthy in the dashboard even though they are actual orphans, leading to inaccurate health scores.\n\n | \n\n1. Set up a class with a large enough population of orphan CIs such that processing exceeds five minutes.\n2. Trigger the CMDB Health orphan batch job.\n3. Allow the job to run until the five minute batch timeout fires MID-loop.\n4. Observe the checkpoint value stored in MetricProcessorStatus for that class — it's an arbitrary sys\\_id, not the lexicographically highest one processed.\n5. On the next scheduled run, observe that orphan CIs with sys\\_ids smaller than the stored checkpoint are not evaluated and not reported as failures.\n\n |
| \n\nConfiguration Management Database \\(CMDB\\)\n\n PRB2037178\n\n | \n\nA relationship editor \\(child\\) entry incorrectly displays a '\\*' suggested marker when only the parent direction is configured in cmdb\\_rel\\_type\\_suggest\n\n | \n\nAfter upgrading from Yokohama to Australia, the CI relationship editor's 'Suggested relationship types' list displays both the parent and child directions of a configured suggested relationship with the '\\*' suggested marker, even when only one direction was configured in the cmdb\\_rel\\_type\\_suggest table. For example, a cmdb\\_rel\\_type\\_suggest record is created with base\\_class = Windows Server, dependent\\_class = Business Service, and direction Connects to \\(parent\\). When the relationship editor is opened for a Windows Server CI, the list shows two entries instead of one: \\* Connects to::Connected by \\(Parent\\) and \\* Connects to::Connected by \\(Child\\). Both entries appear with the leading \\*, suggesting both directions are configured. Only the \\(parent\\) direction was actually configured. Users selecting from the suggested list can't distinguish which direction was the configured one. Because the list is sorted alphabetically and the \\(Child\\) entry sorts before \\(Parent\\), the misleading default selection can result in CI relationships being created in the inverse direction of the customer's intent — silently introducing incorrect CMDB data. The \\* suggested marker should only appear on the direction that is actually configured in cmdb\\_rel\\_type\\_suggest. The \\(Child\\) entry for a parent-only suggested relationship should either not appear in the suggested-marker group, or appear without the \\* prefix.\n\n | \n\n1. Navigate to the 'Suggested Relationships' module.\n2. Insert a record using an unused relationship.\n3. Open the relationship editor from the relationships formatter on a Windows server CI.\n\n Expected behavior: Only the added suggested relationship from one direction is expected.\n\n Actual behavior: Observe two relationship choices for the relationship.\n\n |
| \n\nConfiguration Management Database \\(CMDB\\)\n\n PRB2052583\n\n | \n\nReferences to 'Now Assist' for the duplicate CI remediator should be renamed to Otto\n\n | \n\n \n\n | \n\n \n\n |
| \n\nConnections and Credentials\n\n PRB2034770\n\n | \n\nA scoped app is unable to update the http\\_connection record\n\n | \n\nScoped applications need to update http\\_connection records that they themselves created and own. Because the table-level ACL blocks all cross-scope writes, there's currently no supported path for a scoped app to modify its own connection records. The http\\_connection table is a platform \\(global\\) table whose cross-scope access policy grants only read access to all application scopes. In the earlier ServiceNow-managed scoped app flow, Claroty CTD via Service Graph Connector relied on the existing platform-owned Connection and Credential creation path to create http\\_connection and related credential records. The available scriptable sn\\_cc.ConnectionBuilder APIs cover create scenarios such as createConnectionAlias and createConnectionAndCredential, so the absence of a scoped update path didn't surface when the use case was limited to creation.\n\n | \n\n1. Navigate to Service Graph Connector for Claroty CTD.\n2. Create a connection with the provided connection\\_url.\n\n Expected behavior: It should be able to update the connection record for the child sys\\_alias's http\\_connection record.\n\n Actual behavior: Updating on http\\_connection isn't allowed from any scoped app due to tables's cross-scope access policy.\n\n |
| \n\nContent Experiences\n\n PRB2036902\n\n | \n\nA change in HRApprovalAccessUtilsSNC causes schedule content approvals to fail without a new RCA\n\n | \n\n \n\n | \n\n1. Provision an instance with HR Core installed.\n2. Create a schedule with approvers such that one rejection rejects the whole schedule.\n3. Approve any number of the requests, saving at least one \\(0:X-1\\).\n4. Reject one.\n\n Expected behavior: The schedule is rejected as normal.\n\n Actual behavior: An RCA error occurs.\n\n |
| \n\nContent Experiences\n\n PRB2054955\n\n | \n\nRCA for app-ex-ai-agents in Content Publishing for the getRefRecord directive\n\n | \n\n \n\n | \n\n \n\n |
| \n\nContract Management\n\n PRB2040201\n\n [KB3140742](https://hi.service-now.com/kb_view.do?sysparm_article=KB3140742)\n\n | \n\nAssets covered on a contract aren't added through an Multiple Record Associator \\(MRA\\) pop-up\n\n | \n\nIn the 'add action' over MRA pop-up, there's a slight change by the platform. It is now performing a GlideRecordSecure insert instead of GlideRecord. It is validating for create and write ACLs on clm\\_m2m\\_contract\\_asset.asset and clm\\_m2m\\_contract\\_asset.contract fields. There's ACLs where it allows the respective operations only if they are blank. This is clearing out the **Contract** and **Asset** field values during creation. So, records which are created don't have these fields and aren't displaying in the related list.\n\n | \n\n \n\n |
| \n\nContracts Core\n\n PRB2036700\n\n | \n\nAdd the needed RCA as part of the getRefRecord\\(\\) scoping bypass directive changes\n\n | \n\n \n\n | \n\n \n\n |
| \n\nConversational Appointment Booking\n\n PRB2054247\n\n | \n\nTrue-up Conversation Appointment Booking for GetRefRecord directive changes\n\n | \n\nAfter making the required changes as part of the directive, all the three flows \\(schedule an appointment, reschedule an appointment and cancel an appointment\\) should work when the caller scope access is restricted.\n\n | \n\n \n\n |
| \n\nCustomer Operations for Customer Service Management\n\n PRB2035611\n\n | \n\nFix GetRefRecord scoping bypass\n\n | \n\nOn CSManagementUtils, guard the getRefRecord\\(\\) result before calling getLabel\\(\\) to prevent an error when a reference field has no associated record. Also, on CSQueryBRUtil, add a null check on entityGR before calling isValid\\(\\) to prevent an error during dot-walked field validation.\n\n | \n\n \n\n |
| \n\nCustomer Service Case Action Status\n\n PRB2011771\n\n | \n\nKeep the 'Major Case' related list consistent in app-csm-action-status and app-major-issue-management\n\n | \n\nIf users reinstall or upgrade app-csm-action-status again after Major Case is installed, the related list on Major Case is different. The newly added-in app-major-issue-management is gone.\n\n | \n\n \n\n |
| \n\nCustomer Service Management\n\n PRB2002976\n\n [KB3141009](https://hi.service-now.com/kb_view.do?sysparm_article=KB3141009)\n\n | \n\nAn advanced qualifier reference that uses 'current' isn't functioning as expected in CSM Workspace\n\n | \n\nAdvanced reference qualifiers that rely on the 'current' object fail when templates are applied in Workspace. However, the same functionality works as expected in 'Classic UI \\(UI16\\)'. During template application in Workspace, the platform passes corrupted or incomplete serialized data to 'GlideRecordEncoder.decode\\(\\)'. As a result, the current GlideRecord is returned without field values.\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nDatabase Persistence - Data Access\n\n PRB2013282\n\n | \n\nColumns are created with a 'u\\_' prefix\n\n | \n\nAfter TableSchemaManager .alter\\(\\).execute\\(\\) adds a column, TableDescriptor returns the new column but the column name is different from what was supplied. The new column was created with a 'u\\_' prefix in the column name. This behavior is different from table creation, where columns are created with exactly the same name supplied for column\\_name.\n\n | \n\n1. Alter a table using the 'Table Management' API.\n2. Add a column.\n\n Expected behavior: Create a column exactly as specified.\n\n Actual behavior: It adds a 'u\\_' prefix to the column.\n\n |
| \n\nDatabase Persistence - Data Dictionaries\n\n PRB2050936\n\n | \n\nLet the 'Table Management' Java API create a table/column in a scope without a scope prefix\n\n | \n\nMetricBase must create tables in the DEX scope without applying the scope prefix, as it applies the mb\\_ prefix to metricbase table. The API should be changed and require a scope object by default.\n\n | \n\nUse the TableManagement Java API to create a table in any custom scope.\n\n Observe that a scope prefix is added to the table.\n\n |
| \n\nDatabase Persistence - Data Scale\n\n PRB1942731\n\n | \n\nIf sequences exist to reduce redundant queries, SequenceAtomicCounter.get could cache\n\n | \n\n \n\n | \n\n \n\n |
| \n\nDatabase Persistence - Graph\n\n PRB2026586\n\n | \n\ntoLower\\(\\) and toUpper\\(\\) functions aren't supported in WHERE and RETURN\n\n | \n\nAfter creating a query with GraphQueryBuilder, users of GraphQueryBuilder API should be able to get the encoded query representation as a transferrable serialization of the query. Cypher's toLower\\(\\) and toUpper\\(\\) functions aren't supported anywhere in the builder — neither in WHERE predicates nor in RETURN projections.\n\n | \n\n \n\n |
| \n\nDatabase Persistence - Graph\n\n PRB2026589\n\n | \n\nCOUNT\\(DISTINCT x\\) can't be represented with GraphQueryBuilder API\n\n | \n\nAfter creating a query with GraphQueryBuilder, users of GraphQueryBuilder API should be able to get the encoded query representation as a transferrable serialization of the query. Aggregate\\('COUNT', x\\) only ever emits COUNT\\(x\\). There's no way to express COUNT\\(DISTINCT x\\), which is the only correct answer when multiple paths can reach the same node.\n\n | \n\n \n\n |
| \n\nDatabase Persistence - Graph\n\n PRB2026590\n\n | \n\nORDER BY isn't stored in Encoded QueryModel\n\n | \n\nAfter creating a query with GraphQueryBuilder, users of GraphQueryBuilder API should be able to get the encoded query representation as a transferrable serialization of the query. RETURN alias — the AS clause is dropped when using buildEncodedQuery\\(\\), so any consumer of the encoded query has no way to know what column name the user asked for. ORDER BY / LIMIT / SKIP — these have no representation in QueryModel at all, so they're dropped whole on round-trip.\n\n | \n\n \n\n |
| \n\nDatabase Persistence - Graph\n\n PRB2040734\n\n | \n\nSys\\_class\\_name doesn't come as property from getForTables\n\n | \n\n \n\n | \n\n \n\n |
| \n\nDatabase Persistence - Graph\n\n PRB2051205\n\n | \n\nInline node properties in the cypher are dropped in the encoded query when using with useCypher\\(\\)\n\n | \n\nIf there are inline properties in the cypher passed to useCypher, the returned encoded query doesn't contain that query.\n\n | \n\n \n\n |
| \n\nDatabase Persistence - Graph\n\n PRB2052676\n\n | \n\nCache flushes are triggered, even when the cache is not used/populated\n\n | \n\nThe number of cache flush messages for the table 'cmdb\\_rel\\_ci' is in the 80 million+ range every hour. In a way, it's making 80 million inserts into the sys\\_cache\\_flush table. 'cmdb\\_rel\\_ci' is paired with 'graph\\_cmdb\\_rel\\_type\\_cache'. The cache graph\\_cmdb\\_rel\\_type\\_cache isn't enabled, but the cache pairing is still in a static block and is active.\n\n | \n\n \n\n |
| \n\nDatabase Persistence - Graph\n\n PRB2053774\n\n | \n\nSupport initializing GraphQueryBuilder with a cypher query string via the JavaScript API\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nDatabase Persistence\n\n PRB2075293\n\n [KB3150595](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB3150595)\n\n | \n\nAfter the upgrade to Australia Patch 5, auto-increment columns are failing inserts with the duplicate\\_key error\n\n | \n\nAustralia Patch 5 \\(AP5\\) introduced a change to how certain database auto-increment sequences are managed. Under specific conditions, this change can cause the sequence used to generate new record identifiers to become invalid or out of sync with the database. When this occurs, attempts to create new records may fail. As a result, transient state records may not be created as expected in tables with the auto-increment field. This impacts many functional areas relying on the sequence record to track orders of states, logs or messages. This defect fix is included in the weekly patch due to its severe impact on multiple major functionalities across the platform.\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nDatabase Persistence - WDF\n\n PRB1931544\n\n | \n\nUsers should be warned/blocked from setting up a reference field that is ineligible\n\n | \n\nAs of Australia, it currently enforces the reference key assignment only in the WDF Hub mapping page and not on sys\\_dictionary or sys\\_db\\_object. When creating/editing the remote table through the hub, there's a method called 'com.glide.datafabric. schemamapping. RemoteTableDef\\#validateReference'. This method verifies that the reference table and the reference key are valid. If the reference table table doesn't exist/cannot be accessed, or if the reference key's data type is not in the list of allowed types, it blocks the table from being created/updated and throws an error message to the user in the UI. Following this approach, it can add the null value check in this method and throw the appropriate error message to the user.\n\n | \n\n \n\n |
| \n\nDatabase Persistence - WDF\n\n PRB2038399\n\n | \n\nThere's a pagination issue\n\n | \n\n \n\n | \n\n1. Open the 'List' view of a data interface.\n2. Order by one column.\n3. Navigate to the next page.\n4. Check the data.\n\nThe same page is displayed.\n\n\n See that the limit isn't applied to the query.\n\n |
| \n\nDatabase Persistence - WDF\n\n PRB2040034\n\n | \n\nIn Australia, all database columns that start with a number have 'yy\\_' added to the start of the name, causing a syntax error\n\n | \n\nWhen querying a table in the Australia release and the DB column starts with a number, it adds a 'yy\\_' to the SQL query, breaking the collection of data and making a list view show nothing. Error: 'Syntax Error or Access Rule Violation detected by database \\(ERROR: column x\\_snc\\_potatofarm \\_0\\_farmers0.yy \\_1stname does not exist. Hint: Perhaps you meant to reference the column 'x\\_snc\\_potatofarm \\_0\\_farmers0.1stname'. Position: 259\\)'.\n\n | \n\n1. Create a scoped app.\n2. Create a table.\n3. Create some data on that table.\n4. Add a column that name starts with a number.\n5. Navigate back to the list view.\n\n See that its blank, but the count displays that there's records.\n\n |
| \n\nDatabase Persistence - WDF\n\n PRB2050923\n\n | \n\nProvide unified server-side API's fetch primary key details for Data Fabric and standard ServiceNow tables\n\n | \n\n \n\n | \n\n \n\n |
| \n\nDatabase Persistence - WDF\n\n PRB2052538\n\n | \n\nData interface tables are unable to fetch data with remote table as the implementation\n\n | \n\nCurrent remote table support requires that the vtable is provider backed.\n\n | \n\n1. Open a remote table.\n2. Create a data interface table with the fields matching with the remote table.\n3. Navigate to 'Interface M2M'.\n4. Configure the m2m mappings.\n5. Navigate to the <new\\_table>\\_list.do.\n\n Expected behavior: The table displays the data.\n\n Actual behavior: No data is displayed.\n\n |
| \n\nDatabase Persistence - WDF\n\n PRB2080099\n\n | \n\nLeadingDigitLegacyColumnIT fails on Australia\n\n | \n\nOn an Australia patch, running against Oracle, any column rename involving a column whose logical name begins with a digit fails with: 'ORA-00957: duplicate column name'. This is because the generated statement collapses the source and target names into the same identifier.\n\n | \n\n \n\n |
| \n\nData Fabric Table Glide Services\n\n PRB2018015\n\n | \n\nThe Zero Copy Connector \\(ZCC\\) Hub UI becomes unresponsive/times out if a large number of schemas and tables are retrieved\n\n | \n\nWhen large amounts of schemas and tables \\(~20k\\) are retrieved in an API call, the function 'refreshSchemasAndTables\\(\\)' takes a long time to execute compared to the underlying persistence API 'GlideDataFabric EngineService. getInstance\\(\\). getAllTablesForCatalo'. This is on the magnitude of 2.25 seconds vs 40 seconds.\n\n | \n\n1. Navigate to ZCC Hub on an instance.\n2. Create a connection with large number of schemas and tables \\(~20k schemas and tables\\).\n\n Expected behavior: The 'Data Assets' page loads schemas and table and is responsive.\n\n Actual behavior: The 'Data Assets' page times out during loading.\n\n |
| \n\nData Privacy \\(Classic\\)\n\n PRB2031050\n\n | \n\nThe 'Run Once Data Privacy' job takes days to complete after segment creation on large tables \\(300M+ records\\)\n\n | \n\n \n\n | \n\n1. Provision an instance with the Data Privacy plugin installed on a large clone.\n2. Set up a privacy configuration on a table with a large number of records \\(300M+\\).\n3. Configure a 'Run Once' dp\\_job and trigger it.\n\n Expected behavior: The job should complete within a few hours after segment creation \\(dp\\_work\\_item\\).\n\n Actual behavior: The job takes days to complete.\n\n |
| \n\nData Privacy \\(Classic\\)\n\n PRB2031271\n\n | \n\nRollback of a scheduled anonymization job doesn't refresh the activity stream UI for **Journal** fields \\(work\\_notes, comments\\)\n\n | \n\nWhen a scheduled Data Privacy anonymization job is rolled back, the **Journal** field values \\(work\\_notes and comments\\) are correctly restored in the sys\\_journal\\_field table. However, the activity stream UI continues to display the anonymized values because sys\\_activity table \\(used by Service Operations Workspace\\) and sys\\_history\\_set/sys\\_history\\_line \\(used by UI16 List and Form views\\) aren't refreshed upon rollback. The **Description** field doesn't exhibit this issue. This is inconsistent behavior introduced when journal type anonymization support was added.\n\n | \n\n1. Open an instance with Data Privacy enabled.\n2. Configure a scheduled anonymization job targeting **Journal** fields \\(**work\\_notes**, **comments**\\) on the Incident table.\n3. Run the anonymization job.\n4. Confirm the fields are masked in both the database and the UI.\n5. Execute a rollback of the anonymization job.\n6. Verify in sys\\_journal\\_field that the original values have been restored.\n7. Navigate to the affected Incident record in both UI16 and Service Operations Workspace.\n\n Observe that the activity stream still displays the anonymized values even though the database was reverted.\n\n |
| \n\nData Privacy \\(Classic\\)\n\n PRB2032551\n\n [KB3140437](https://hi.service-now.com/kb_view.do?sysparm_article=KB3140437)\n\n | \n\nLLM prompt creation takes ~800 ms, though it used to be 200-300 ms\n\n | \n\nThe root cause was determined as the introduction of 'Sensitive Data Trail system processors', which had a large default timeout \\(20 seconds\\). The processors were scanning all 32 data patterns on an prompt of ~130K characters, taking an additional ~400 ms in latency.\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nData Privacy \\(Classic\\)\n\n PRB2039058\n\n | \n\nReal time anonymization \\(RTA\\) for child tables separate from parent tables\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nData Privacy \\(Classic\\)\n\n PRB2039332\n\n | \n\nIncrease the maximum size limit of the incoming request to Data Privacy APIs from 1M to 10M\n\n | \n\nThe Data Privacy API only supports up to 1M character long prompts. However, a simple prompt on Virtual Agent may result in prompts larger than 1M characters, which causes the prompt's response to get stuck. Prompts of extra large size should be processed by the Data Privacy API.\n\n | \n\n \n\n |
| \n\nData Privacy \\(Classic\\)\n\n PRB2040595\n\n | \n\nPost-clone anonymization of child workers is incorrectly cancelled due to parent job type mismatch\n\n | \n\nThe post-clone data privacy anonymization job uses a parent-child architecture; one parent job distributes work to multiple child worker jobs that process tables in parallel. The issue is in how the child workers look up their parent job record. In the post-clone flow, the parent job is stored in a different table type than the child workers' lookup code expects. Because the lookup fails with 'data protection job is not valid,' each child worker is cancelled immediately.\n\n | \n\n \n\n |
| \n\nData Product Backend Services\n\n PRB2027724\n\n | \n\nUsers are unable to edit reference type details on DTT when editing a data interface\n\n | \n\nThere's no error, but it doesn't work.\n\n | \n\n \n\n |
| \n\nData Snapshots\n\n PRB1995292\n\n | \n\nA data snapshot indicator timeseries API returns empty data instead of the expected single-span score when the request startTime and endTime are the same date\n\n | \n\n \n\n | \n\n1. Configure a data snapshot indicator \\(pa\\_datasnapshot\\_indicator\\) with a boolean condition.\n2. Send a POST request to /api/now/analytics/data with a timeseries data configuration where:\n 1. The startTime and endTime are set to the same date/time\n 2. A business calendar is used\n 3. The date falls within a valid span for that calendar period\n3. Observe the API response data array.\n\n Expected behavior: The API returns the single-span score for the calendar period that covers the requested date.\n\n Actual behavior: The API returns an empty data array — the single span covering the requested date is silently truncated/ignored.\n\n |
| \n\nDate Picker\n\n PRB2029576\n\n [KB3061444](https://hi.service-now.com/kb_view.do?sysparm_article=KB3061444)\n\n | \n\nThere's a regression on GlideDateTime.setDisplayValue\n\n | \n\nAny script that calls setDisplayValue\\(\\) with an ISO-format string \\(yyyy-MM-dd HH:mm:ss\\) on an instance where glide.sys.date\\_format is set to anything not in FORMAT\\_LIST \\(for example, dd-MM-yyyy, MM/dd/yyyy, etc.\\) produces incorrect dates in Zurich.\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nDecision Graph for Context Engine \\(Family\\)\n\n PRB2056900\n\n | \n\nGlide changes for machine learning integration needed for Distinguished Encoding Rules \\(DER\\) mining\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nDecision Graph for Context Engine \\(Family\\)\n\n PRB2056902\n\n | \n\nInstrument 'Ask For' approval action Instance Observer \\(IO\\) during flow execution for context graph tracing\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nDecision Graph for Context Engine \\(Family\\)\n\n PRB2056905\n\n | \n\nRate-limited flow trace eligibility evaluation\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nDecision Graph for Context Engine \\(Family\\)\n\n PRB2056908\n\n | \n\nScaffolding for the decision-graph module\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nDecision Graph for Context Engine \\(Family\\)\n\n PRB2056910\n\n | \n\nCache decision weightage for a low-latency runtime lookup\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nDecision Graph for Context Engine \\(Family\\)\n\n PRB2056912\n\n | \n\nAdding or deleting a feature dictionary should make mined patterns inactive\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nDeclarative Actions\n\n PRB2055766\n\n | \n\nThe related list UI actions to update rows are failing on m2m if the field being updated is read-only\n\n | \n\nThe UI action calls AssetAutomationAPI. completeAssetDisposalTask. This has current.update, which fails. If the read-only flag is removed from the **Stage** field in the sn\\_hamp\\_m2m\\_hw \\_asset\\_disposal table, then it works.\n\n | \n\n1. Navigate to **Hardware Asset Workspace** > **Inventory** > **Disposal order**.\n2. Create a disposal order.\n3. Navigate to the related list.\n4. Add an asset to the disposal order.\n5. Open **Verify task** from the related list.\n6. Select the row.\n7. Select **Verify**.\n\n Observe that the action fails to update.\n\n |
| \n\nDeveloper App Shell\n\n PRB2052364\n\n | \n\nFix GetRefRecord scoping bypass\n\n | \n\n \n\n | \n\n \n\n |
| \n\nDeveloper Sandboxes\n\n PRB2054240\n\n | \n\nThe scheduler claim mutex \\(sys\\_mutex\\) isn't sandbox-aware and forces DSB nodes to contend for a cluster-wide lock, causing scheduled-job pickup delay\n\n | \n\n \n\n | \n\n1. On a multi-node instance \\(50+ nodes\\), turn on Developer Sandboxes.\n2. Create at least 20-30 sandboxes.\n3. Multiple isolated sys\\_triggers should exist in the sandboxes.\n4. Pull stats.do?include=otel.scheduler\\* on the sandbox's node.\n\nObserve that claim\\_lock\\_time averages above one second \\(expected ~13ms\\), jobs\\_lateness averaging 300+ seconds, and worker capacity used is very low.\n\n5. Compare against a controller node on the same instance.\n\nClaim\\_lock\\_time is still elevated but jobs\\_lateness stays within a few seconds, because base nodes don't pin an entire platform triggers on one node.\n\n\n |
| \n\nDevOps Change Velocity\n\n PRB2052626\n\n | \n\nGetRefRecord scoping bypass for the 6.2.1 release\n\n | \n\n \n\n | \n\n \n\n |
| \n\nDiscovery\n\n PRB2015204\n\n | \n\nUpdate the IP address to retired when the network interface card's \\(NIC\\) is updated to 'Retired'\n\n | \n\nIn the IP-Based Discovery plugin, the business rule \\(BR\\) 'Discovery - Set IP Address to Absent' only sets the IP address to absent. When the NIC is retired, it doesn't set the IP address to 'Retired', leaving orphaned or outdated IP addresses. The BR should handle the retired scenario as well.\n\n | \n\n \n\n |
| \n\nDiscovery\n\n PRB2023232\n\n | \n\nSome Sybase processes running on Linux don't meet the classifier conditions to trigger the sybase pattern, resulting in an incomplete Discovery\n\n | \n\nThe Sybase Process classifier has these conditions: Command contains 'dataserver', parameters contains 'sqlsrvr', and parameters matches regex '-\\[Dd\\]\\\\s+'. The regex breaks down as follows: -\\[Dd\\]\\\\s+ matches a literal hyphen, \\[Dd\\] matches either uppercase D or lowercase d, and \\\\s+ matches one or more whitespace characters \\(space, tab, etc.\\). It matches a hyphen, followed by D or d, followed by at least one space. If a process running returns a parameters string starting with \\['parameters':'-d/data/master.dat\\] this doesn't meet the condition for this regex and the pattern doesn't trigger, despite the process being a valid Sybase process.\n\n | \n\n \n\n |
| \n\nDiscovery\n\n PRB2029641\n\n | \n\nUpdate Store app true-up for ITOM Licensing Store app 3.13.0\n\n | \n\n \n\n | \n\n \n\n |
| \n\nDiscovery\n\n PRB2059465\n\n | \n\nDiscovery patterns fail to launch for sub-accounts/datacenters when glide.discovery. retire\\_stale\\_accounts is turned on\n\n | \n\nIn Cloud Discovery, schedules configured to discover all sub-accounts under a master account, with enabling glide.discovery.retire\\_stale\\_accounts and glide.discovery.cdu. auto\\_refresh\\_sub\\_accounts \\_and\\_ldcs , Discovery patterns fail to launch for sub-accounts/datacenters \\(only the service account discovery launches\\).\n\n | \n\n \n\n |
| \n\nDocument Management\n\n PRB2056202\n\n | \n\nReplace 'Now Assist' and 'Sparkle' with 'ServiceNow Otto' in screenshots, images, and icon assets\n\n | \n\nAll UI visual elements should be updated across SmartDocs, Doc to Voice, and SmartRedact to reflect the ServiceNow Otto branding changes. This includes both images/screenshots and icon assets.\n\n | \n\n \n\n |
| \n\nDocument Management Services\n\n PRB2039067\n\n | \n\nSmart redaction with redaction codes and notes for documents\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nDocument Management Services\n\n PRB2056919\n\n | \n\nSmartDocs enablement in UI16 and ServicePortals\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nDocument Viewer\n\n PRB2056915\n\n | \n\nSupport in document viewer for the doc to voice agent\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nDynamic Schema\n\n PRB2037531\n\n | \n\nThere's failing DynamicSchema aggregate ITs\n\n | \n\nIn Australia, in the db-dynamic-schema-test package, the following ITs are failing: DynamicSchemaAggregatesIT and DynSchQueryAggregates\\*IT. The expression added to the GROUP BY isn't listed in the SELECT clause.\n\n | \n\n \n\n |
| \n\nEmail Notifications\n\n PRB1948259\n\n | \n\nSelectAll and **Delete** buttons aren't working in Email Viewer\n\n | \n\n \n\n | \n\n1. Log in as an admin user.\n2. Navigate to CSM Workspace and open a case record.\n3. From mini composer, send an email with some documents attached.\n4. Update the email status to 'sent' from send-ready in the sys\\_email.list table.\n5. Open the email from the 'Emails' tab in the case record.\n\nThe email opens in the Email Viewer view\n\n\n Expected behavior:**SelectAll** should select all the attachments. The **Delete** button should delete the selected attachments.\n\n Actual behavior:**SelectAll** isn't selecting all the attachments. The **Delete** button isn't functioning properly.\n\n |
| \n\nEmail Notifications\n\n PRB2001946\n\n | \n\nThe **RemoveAll** button shouldn't be present in the email viewer\n\n | \n\n \n\n | \n\n1. Log in as an admin user.\n2. Navigate to Customer Service Management workspace.\n3. Open a case record.\n4. From the mini composer, send a email with some documents attached.\n5. Update the email status to 'sent' from send-ready in the sys\\_email.list table.\n6. Open the email from the 'Emails' tab in the case record.\n7. Select **Select All**.\n8. Select the **3 dots** and verify.\n\n Expected behavior: The **RemoveAll** button shouldn't be present in the email viewer.\n\n Actual behavior: The **RemoveAll** button is visible in the email viewer.\n\n |
| \n\nEmail Notifications\n\n PRB2019162\n\n | \n\nIntroduce batch support for subscriptions in NotificationRecipientBuilder\n\n | \n\nNotification events are taking a longer time to process \\(5-7 seconds\\).\n\n | \n\n1. Log in to an instance.\n2. Create a subscribable notification record.\n3. Create 1800+ subscriptions.\n4. Trigger a notification.\n\n Expected behavior: The notification should be sent to all recipients without much delays.\n\n Actual behavior: The notification is generated but its processing consumed a significant amount of time.\n\n |
| \n\nEmail Notifications\n\n PRB2036855\n\n | \n\nAgent workspace case emails display multiple 'To' names if the email recipient has multiple contact records\n\n | \n\nIf a contact has more than one contact record in the system \\(same email address\\), the system displays the names of all the contacts when viewing an email sent to that person on a case.\n\n | \n\n1. Navigate to customer\\_contact table.\n2. Create multiple contact records with the same name and email address, but a different user ID.\n3. Navigate to CSM workspace.\n4. Create a case.\n5. Add one of the contacts created as the case contact.\n6. Send an email to that contact.\n7. Open the sent email.\n\n Expected behavior: Only one contact is displayed in the**To** field.\n\n Actual behavior: The**To** field lists all the contacts with the same name and email address.\n\n |
| \n\nEmail Notifications\n\n PRB2050616\n\n | \n\nEmail client APIs shouldn't be public\n\n | \n\n \n\n | \n\n \n\n |
| \n\nEmbedded Help\n\n PRB2056339\n\n | \n\nReplace all occurrences of 'Now Assist' text with 'AI' across the Help Center and embedded help\n\n | \n\n \n\n | \n\n1. Open Help Center or embedded help.\n2. Open a document that was created using AI-generated help.\n\n Observe that 'Now Assist' text is displayed for AI-generated help articles.\n\n |
| \n\nEmployee Profile\n\n PRB2011497\n\n | \n\nThere's a dot-walking RCA error when moving from the 'Learning' scope to the 'Employee profile' scope\n\n | \n\nAn attempt to dot-walk to table sn\\_employee\\_profile present in the 'Employee profile' scope from the 'Learning' scope was blocked. The reference field employee belongs to the sn\\_lep\\_challenge table. The operation type was: GET\\_REF\\_RECORD.\n\n | \n\n \n\n |
| \n\nEmployee Profile\n\n PRB2021875\n\n | \n\ngetRefRecord\\(\\) changes for Opportunity Marketplace \\(OPM\\) and TD Core in Employee Profile\n\n | \n\n \n\n | \n\n \n\n |
| \n\nEvent Management\n\n PRB2034593\n\n | \n\nAn event field mapping rule from the type 'Map field' using regex causes an error in event processing\n\n | \n\nWhen having an event field mapping rule from type 'Map field' using regex and a matching event is processed, if the **Additional info** field contains the source field JSON as the value, the event finishes in an error state.\n\n | \n\n1. Create some event field mapping rule from the type 'Map field' using regex.\n2. Create an event with **Additional info** containing nested JSON, where one of the keys matches the regex and its value is a JSON object.\n\n Expected behavior: Event processing should complete successfully without errors and an alert should created.\n\n Actual behavior: Event processing fails, and the event is moved to the error state.\n\n |
| \n\nEvent Management\n\n PRB2052731\n\n | \n\nRemove the step in mixed grouping that allows alerts to join existing groups before the grouping definitions are run in order\n\n | \n\nThe mixed grouping engine handles alerts in two steps. First, it checks whether an alert can join a group that already exists—without following the order the definitions are set up in. After, it goes through all the definitions in their proper order, where it's also allowed to create new groups. The first step disregards the configured definitions order; as a result, an alert can end up in a group created by a lower-priority rule instead of a higher-priority definition. The definition order exists specifically to control which definition gets to group an alert first, so skipping it defeats the purpose of the order. In conclusion, the two-step process should be removed. The mixed grouping engine should go through the definitions once, in order. For each definition, it should allow alerts to either join an existing group or create a new one.\n\n | \n\n1. Create two grouping definitions, Definition A and Definition B, with Definition A placed ahead of Definition B in the rule order.\n2. Send alerts A1 and A2 that fit Definition B.\n3. Wait for the grouping job to run.\n4. Create Group B.\n5. Send alerts A3 and A4 that fit both Definition A and Definition B.\n6. Wait for the grouping job to run.\n7. Check which group A3 and A4 end up in.\n\n Expected behavior: A3 and A4 form a new group created under Definition A, because Definition A comes first in the rule order.\n\n Actual behavior: A3 and A4 are added to the existing Group B.\n\n |
| \n\nEvent Management\n\n PRB2053524\n\n | \n\nAzure monitor for 'Issue' integration, and UI enhancements in Express List and alert record\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nField Service Task Bundling\n\n PRB2064856\n\n | \n\nDynamic bundling creates unassigned bundles\n\n | \n\n \n\n | \n\n1. Verify that Dynamic Scheduling, Task Bundling, and Task Grouping plugins are active.\n2. Enable the sys\\_property 'com.snc.dynamic. scheduling.bundle\\_ before\\_scheduling'.\n3. Set the Task Grouping rules \\(Same Location\\) and policy.\n4. Create two work order tasks \\(WOT\\) in the draft.\n5. Once the WOTs are moved to the 'Qualified \\(Pending Dispatch\\)' state, the tasks should be bundled using Dynamic Bundling and Dynamic Schedule the tasks automatically.\n\n |
| \n\nFlow Engine\n\n PRB1943894\n\n | \n\nLooping over records using 'built in iterator' is significantly slower than the normal GlideRecord iteration\n\n | \n\nFlow engine should take a similar amount of time to iterate over records and script or Java when no quiescing occurs, but run times are 16.8x - 73.6x slower.\n\n | \n\n \n\n |
| \n\nFlow Engine\n\n PRB2001686\n\n | \n\nThere's multiple queries to fetch a flow plan record\n\n | \n\nWhen the plan isn't cached, it takes two queries. When run again with the plan already cached, it takes only one query.\n\n | \n\n \n\n |
| \n\nFlow Engine\n\n PRB2001694\n\n | \n\nReduce multiple sys\\_flow\\_context select queries\n\n | \n\nIn GlideRecord, before updating, it queries to get the DB state of the record to populate the 'previous' object for business rules. This can be avoided if 'fPopulatePrevious FromMemory' is set to true. It can be set by calling GlideRecord:: setPopulatePrevious FromMemory.\n\n | \n\n1. Create any simple flow.\n2. Execute it in background scripts.\n\n Observe that there is 'select query' before every update.\n\n |
| \n\nFlow Engine\n\n PRB2029887\n\n | \n\nFlow engine is ~200x slower than the equivalent script on 1000 elements, as eager Val.displayValue dominates input wrapping for large collections\n\n | \n\nA flow that takes a large ComplexObjectCollection as input executes ~200x slower than the equivalent Rhino background script doing the same work. For a 1000-element ForEach input, per-invocation wall-clock is ~143 ms \\(vs ~0.7 ms for the equivalent script\\). The slowdown scales with the input collection size; small inputs are affected less, but flows that pass large lists as input are heavily impacted even on the user-default execution path \\(reporting off, trace off\\). There's no functional break as the flow produces correct output, but the per-invocation cost is dominated by work that the engine never reads on the default path.\n\n | \n\n \n\n |
| \n\nFlow Engine\n\n PRB2034134\n\n | \n\n'Require' statements throw a JavaScript exception error in Australia's Flow Designer\n\n | \n\n \n\n | \n\n \n\n |
| \n\nFlow Engine\n\n PRB2038121\n\n | \n\nRestore the Flow Engine FlowObjectDef cache\n\n | \n\nThis removes redundant sys\\_hub\\_action \\_type\\_definition read per quick-action execution.\n\n | \n\n \n\n |
| \n\nFlow Engine\n\n PRB2054195\n\n | \n\nThe 'ForEach' iteration on GlideRecord does eager canRead checks on all the records\n\n | \n\n \n\n | \n\n1. Create a subflow.\n2. Add a **lookuprecords** action on the sys\\_user table with active = true and a max count of 10.\n3. Add ForEach flow logic with the input as lookuprecords output.\n4. Add a log inside ForEach.\n\n In GRProxy, before starting the loop it internally loops over all the records in GlideRecord and collects sys\\_ids and skipped counts by doing a canRead check.\n\n |
| \n\nFlow Engine\n\n PRB2054201\n\n | \n\nIntroduce a cache in FlowRecompileChecker\n\n | \n\nThe eviction policy is too broad for execution settings in ProcessPlanCache. Any change to any execution setting evicts all plans but should only effect one. Instead, it should evict a process plan directly when its execution settings change.\n\n | \n\n \n\n |
| \n\nFlow Engine\n\n PRB2062691\n\n | \n\nAction Fabric flow complexity is insufficient for pricing estimation exercises\n\n | \n\nThe complexity\\_bucket attribute contains values grouped into bucket\\_0\\_10, bucket\\_11\\_50, and likely no other buckets.\n\n | \n\n1. Perform MCP requests on an instance with Action Fabric telemetry.\n2. View the Action Fabric telemetry via Clickhouse or logged data.\n\n Expected behavior: The exact complexity of the MCP flows are recorded.\n\n Actual behavior: The complexity\\_bucket attribute contains values grouped into bucket\\_0\\_10, bucket\\_11\\_50, and likely no other buckets.\n\n |
| \n\nFlows \\(Family Channel\\)\n\n PRB2054449\n\n | \n\nRefactor all occurrences of 'Now Assist' in Flow Designer, Action Designer, and Flow Diagram to 'ServiceNow Otto'\n\n | \n\n \n\n | \n\n \n\n |
| \n\nFlows \\(Family Channel\\)\n\n PRB2056022\n\n | \n\nOtto directive renaming for the call skill step plugin\n\n | \n\nThe plugin name is being changed from 'Now Assist Skill' to 'AI Skill' \\(or 'AI Skill Step'\\). The step name is being changed from 'Call Now Skill Step' to 'Call AI Skill Step'. Also, the plugin and step description should be updated where applicable.\n\n | \n\n \n\n |
| \n\nGlobal Ranking\n\n PRB2035527\n\n | \n\nUsers aren't able to delete a scrum task from cross-scope\n\n | \n\n \n\n | \n\n1. Navigate to Collaborative Work Management \\(CWM\\) Workspace.\n2. Open any board.\n3. Turn on the 'Story & Scrum' task.\n4. Add story & scrum tasks records to the board.\n5. Try to delete the scrum task.\n\nObserve that the shadow task is deleted but the actual scrum task isn't deleted.\n\n6. Refresh the board.\n\nObserve that the deleted scrum task reappears.\n\n\n |
| \n\nHermes \\(Family\\)\n\n PRB2026691\n\n | \n\nTCP connection establishment and SSL handshake occur every minute\n\n | \n\nTCP connection establishment and SSL handshake occur every minute even when the health check is skipped under the 150-second threshold. The unnecessary overhead should be remediated.\n\n | \n\n \n\n |
| \n\nHermes \\(Family\\)\n\n PRB2026695\n\n | \n\nIdentify and eliminate duplicate health checks where two Hermes services point to the same Hermes cluster\n\n | \n\nNormally, it'd be expected that Glide apps would use different bootstraps. Given the special condition, when the Kafka bootstraps are the same, it should avoid the duplicate connections/healthchecks between the 2 services.\n\n | \n\n \n\n |
| \n\nHiring Experiences\n\n PRB2031986\n\n | \n\nThe 'Last Month' option under 'My job requests' in the hiring portal displays data of requisitions created in the current month\n\n | \n\nFor the 'Last Month' filter in the hiring portal, the UI displays the current month record because it's using >= beginningOfLastMonth\\(\\), which pulls in June \\(this month\\) records too. The platform's native filter uses sys\\_created\\_onONLast month, which is properly bounded to just the previous month.\n\n | \n\n \n\n |
| \n\nHiring Experiences\n\n PRB2057166\n\n | \n\nGetRefRecord scoping bypass fix\n\n | \n\n \n\n | \n\n \n\n |
| \n\nHorizon Component Library\n\n PRB2052114\n\n | \n\nReplace the 'Sparkle' icon with the Otto Lottie animation in AI and loader experiences\n\n | \n\n \n\n | \n\n \n\n |
| \n\nHorizon Component Library\n\n PRB2052172\n\n | \n\nSuppress console statements so browser tools aren't flooded\n\n | \n\n \n\n | \n\nView the 'Theme behavior' console output.\n\n The console output should only be logged when env = development.\n\n |
| \n\nHorizon Empty State Component\n\n PRB2050333\n\n | \n\nUpdate ai-general illustration\n\n | \n\nThe sparkle illustration should use the new Otto logo instead.\n\n | \n\n1. Open an instance.\n2. Create a experience in UI Builder.\n3. Add an empty state component to the stage.\n4. In the config panel, locate the illustration property.\n5. Select **AI general** from the drop-down list.\n\n Expected behavior: The empty state shows the Otto logo.\n\n Actual behavior: The empty state shows sparkles.\n\n |
| \n\nHorizon Icon Component\n\n PRB2032851\n\n | \n\nAdd the Otto icon to the library\n\n | \n\n \n\n | \n\n1. Navigate to an instance.\n2. Create a experience in UI Builder.\n3. Add a now-button-iconic component to the stage.\n4. In the configuration panel, locate the drop-down list for the icon property .\n5. Search for 'sn-sparkmoji-logo'.\n\n Expected behavior: See the new Otto logo.\n\n Actual behavior: The icon is missing.\n\n |
| \n\nHorizon Icon Component\n\n PRB2050318\n\n | \n\nUpdate all 'Sparkle' icons\n\n | \n\nIcons with the Otto logo should be shown instead.\n\n | \n\n1. Open an instance.\n2. Create an experience in UI Builder.\n3. Add a now-button-iconic component to the stage\n4. In the config panel, locate the icon property.\n5. Search for an icon.\n\n Expected behavior: Icons with the Otto logo are shown.\n\n Actual behavior: Icons with sparkles are shown.\n\n |
| \n\nHR e-signature\n\n PRB2035247\n\n | \n\nRCA for Content Experience\n\n | \n\nSpecifically, eesign for getRefRecord directive.\n\n | \n\n \n\n |
| \n\nHR Service Delivery\n\n PRB2014389\n\n | \n\nRCAs are generated for 'Populate Manager Reportee Count Using Eligible Users' and 'EmployeeHubOrg ChartReporteeUtilSNC'\n\n | \n\nDuring nightly test case execution, two RCAs are generated for the new scripts: - sys\\_script\\_include \\_a302f8807873 f250f877079523d275e1 and - sysauto\\_script\\_ 33a5e72453f7 b210f2ebff c230e5e69d. It is causing test failures.\n\n | \n\n \n\n |
| \n\nHR Service Delivery\n\n PRB2021314\n\n | \n\nThe **Cancel** UI action in an HR case checks for 'mandatory' after the case is canceled\n\n | \n\nThe **Cancel** UI action is invoking hr\\_CaseAjax.cancelAction\\(\\). In this function, state and work notes are updated from the server script. Inside the callback function, there's g\\_form.save\\(\\), which checks the mandatory and saves the form. If the data is already saved from the server script, the system shouldn't check the mandatory.\n\n | \n\n \n\n |
| \n\nHR Service Delivery\n\n PRB2035482\n\n | \n\ngetRefRecord updates to Australia\n\n | \n\n \n\n | \n\n \n\n |
| \n\nHR Service Delivery\n\n PRB2052205\n\n | \n\nIn Australia and Zurich, RCAs generated in HR Core and HR Employee Relations must be added back to track/HR\n\n | \n\n \n\n | \n\n \n\n |
| \n\nHR Service Delivery\n\n PRB2052632\n\n | \n\nThe **header\\_config\\_\\*** fields are missing from the sn\\_hr\\_core\\_service table in Zurich and Australia\n\n | \n\n**header\\_config\\_\\*** fields missing from sn\\_hr\\_core\\_service table in Zurich and Australia.\n\n | \n\nOpen a Zurich or Australia instance with the sn\\_hr\\_core and EC Core plugins installed.\n\n Observe that the **header\\_config\\_\\*** fields are missing from the sn\\_hr\\_core\\_service table.\n\n |
| \n\nIdentification and Reconciliation API\n\n PRB2028002\n\n | \n\nFix three dynamic IRE UI messaging and wording issues and the system properties in the update folder\n\n | \n\n \n\n | \n\n \n\n |
| \n\nIdentification and Reconciliation API\n\n PRB2034883\n\n | \n\nUsers can add or edit identification rules for hardware's child classes while dynamic IRE is enabled\n\n | \n\nIf dynamic IRE is enabled, users shouldn't be able to see or edit identification rules on the hardware hierarchy.\n\n | \n\n1. Enable dynamic IRE.\n2. Navigate to hardware or any of the child classes.\n\n Observe that static rules are displayed and editable, even though dynamic IRE is enabled.\n\n |
| \n\nIdentity\n\n PRB1964703\n\n | \n\nA federated ID isn't generated for all the users in the instance\n\n | \n\nThere's also instances where a federated ID isn't generated for some users even when they have a unique user\\_name and email.\n\n | \n\n \n\n |
| \n\nInbound API Integration Usage Framework\n\n PRB1988771\n\n [KB3082116](https://hi.service-now.com/kb_view.do?sysparm_article=KB3082116)\n\n | \n\nIPAccessListFilter handling for malformed IP addresses\n\n | \n\nInbound REST API calls coming through proxy servers \\(x-forwarded-for header with multiple IP's\\) or malformed IP address can sometimes fail in Zurich and Australia instances.\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nInbound API Integration Usage Framework\n\n PRB2034837\n\n | \n\nRecord data egress usage for integration requests\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nInbound API Integration Usage Framework\n\n PRB2034838\n\n | \n\nDomain separation support for Inbound API Integration Framework\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nInnovation Management\n\n PRB2055588\n\n | \n\nGetRefRecord scoping bypass for app-ppm\n\n | \n\n \n\n | \n\n \n\n |
| \n\nInnovation Management\n\n PRB2055611\n\n | \n\nGetRefRecord scoping bypass for app-common\n\n | \n\n \n\n | \n\n \n\n |
| \n\nInstall Base Management Store\n\n PRB2059577\n\n | \n\nInstall base items and sold products should support RAC fallback mechanism\n\n | \n\nThe functions \\_skipFetchEntities and getQRfallbackRoles should be overridden in CSMRelationshipServiceSNC in CSMRelationshipService \\_InstallBaseRelatedParty to allow this fallback mechanism.\n\n | \n\n \n\n |
| \n\nInstance Clone \\(Family\\)\n\n PRB2032595\n\n | \n\nDeactivate the 'Target Instance Validate' business rule \\(BR\\) on an instance table to support OAuth-based authentication of clone targets from the Clone Admin Console\n\n | \n\n \n\n | \n\nOn any Australia instance, add a target instance through the Clone Admin Console.\n\n The instance is inserted into the table post-successful authentication, but there's an unnecessary BR that runs the authentication again to validate it. This BR was used in the legacy version of the clone and isn't required with the Store app.\n\n |
| \n\nInstance Clone \\(Family\\)\n\n PRB2051479\n\n | \n\nClone cleanup script fixes\n\n | \n\n \n\n | \n\n \n\n |
| \n\nInstance Clone \\(Family\\)\n\n PRB2051483\n\n | \n\nIn Clone Admin Console, declare v.2.2.4 to ensure that OAuth is used\n\n | \n\n \n\n | \n\n \n\n |
| \n\nInstance Data Replication \\(IDR\\)\n\n PRB1940978\n\n | \n\nThere's many IDR-DCTComparisonJobs on an instance\n\n | \n\nThis is likely only a cosmetic issue and not hurting performance. Instances have at least one IDRDCTComparisonJob per node, which seems excessive. For instances with many nodes, this ends up being the majority of IDR jobs. There's only a few consumer jobs per instance \\(not per node\\).\n\n | \n\n1. On an instance running a version lower than Australia and configured with multiple nodes, open the sys\\_trigger table.\n2. See if there's multiple IDRDCTComparisonJob records present.\n\n |
| \n\nIntegrated Email Client\n\n PRB2051938\n\n | \n\nA Now Assist reference in Email Client must be changed to Otto\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nIntegration Hub\n\n PRB2056938\n\n | \n\nRename the 'Now Assist for Spoke Generation API Support' Glide plugin\n\n | \n\n \n\n | \n\n \n\n |
| \n\nIntegration Hub Spokes\n\n PRB2053392\n\n | \n\nUsers can recover box webhook HMAC signing keys via timing oracle on JavaScript == comparison and forge events to trigger arbitrary subflows\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nKnowledge Center\n\n PRB2076447\n\n | \n\nThe Auto-fix plugin update blocks the Australia Patch 5m upgrade in loadsim release testing\n\n | \n\nThe plugin upgrade thread handling becomes stuck in an error loop triggered by a null pointer. It never exits or advances, leaving the upgrade 'hung'. This happens when the upgrade plugin loader reaches the knowledge center update that adds in the auto-fix and auto-fix enable property.\n\n | \n\n \n\n |
| \n\nJVM at Scale\n\n PRB2032235\n\n [KB3078521](https://hi.service-now.com/kb_view.do?sysparm_article=KB3078521)\n\n | \n\nMemory watcher isn't logging active transactions in the Australia release\n\n | \n\n \n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nKnowledge Graph \\(Family\\)\n\n PRB2016914\n\n | \n\nUpdate the structure to keep the Knowledge Graph configuration file in the same folder as the released description version and dynamic configuration for the Install Server URL\n\n | \n\n \n\n | \n\n \n\n |
| \n\nKnowledge Graph \\(Family\\)\n\n PRB2052948\n\n | \n\nImplement batch insert logic for affinity jobs to improve insert latency\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nKnowledge Management\n\n PRB2022138\n\n | \n\ngetRefRecord\\(\\) scoping bypass update\n\n | \n\nIt must ship an RCA for HR tables for the knowledge scope sn\\_km\\_gen\\_ai.\n\n | \n\n \n\n |
| \n\nKnowledge Management\n\n PRB2031464\n\n | \n\nThe Knowledge Base Article \\(KBA\\) is text not visible in the workspace\n\n | \n\nThis issue occurs with custom templates that contain fields of mixed data types like HTML, string, date.\n\n | \n\n1. Create such a template with mixed data types.\n2. Create an article fill, and fill non-**HTML** field as well.\n3. Insert a block in one of the fields.\n4. Save this article.\n5. Attempt to searching this article on 'SOW/CSM/KC'.\n6. Select the article\n\n Notice that it will open the kb\\_view page of the article, and renders the article content as empty.\n\n |
| \n\nKnowledge Management\n\n PRB2033473\n\n [KB3144003](https://hi.service-now.com/kb_view.do?sysparm_article=KB3144003)\n\n | \n\nAn article title isn't displayed in the Knowledge Article print view \\(sysparm\\_media=print\\) from Service Portal on the Australia release\n\n | \n\nAn article title isn't displayed in the Knowledge Article print view \\(sysparm\\_media=print\\) from Service Portal on the Australia release due to a JavaScript error in KBViewArticle.jsdbx, while it works as expected in Zurich.\n\n | \n\n \n\n |
| \n\nKnowledge Management\n\n PRB2054012\n\n | \n\nRename app-common 'Now Assist' to Otto\n\n | \n\n \n\n | \n\n \n\n |
| \n\nKnowledge Management\n\n PRB2054937\n\n | \n\nTrue up Store apps NAKM, KC, KCInWorkspaces and ECE\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nKnowledge Management\n\n PRB2058947\n\n | \n\nUpdate versions for the base instance Knowledge Management apps to include Australia and Zurich fixes\n\n | \n\n \n\n | \n\n \n\n |
| \n\nKnowledge Management\n\n PRB2060905\n\n | \n\nUpdating versions for the base instance Knowledge Management apps to include Australia and Zurich fixes\n\n | \n\nThere are fixes in app-knowledge-center, app-knowledge-gen-ai, app-kb-uib, and sn-enhanced-content-editor.\n\n | \n\n \n\n |
| \n\nLegal Digital Forensics\n\n PRB2036701\n\n | \n\nAdd the needed RCA as part of the getRefRecord\\(\\) scoping bypass directive changes\n\n | \n\n \n\n | \n\n \n\n |
| \n\nLegal Hold Notification\n\n PRB2055600\n\n | \n\nAdd the needed RCA as part of the getRefRecord\\(\\) scoping bypass directive changes\n\n | \n\n \n\n | \n\n \n\n |
| \n\nLegal Matter Management\n\n PRB2036702\n\n | \n\nAdd the needed RCA as part of the getRefRecord\\(\\) scoping bypass directive changes\n\n | \n\n \n\n | \n\n \n\n |
| \n\nLegal Request Management\n\n PRB2036703\n\n | \n\nAdd the needed RCA as part of the getRefRecord\\(\\) scoping bypass directive changes\n\n | \n\n \n\n | \n\n \n\n |
| \n\nList Administration\n\n PRB2009991\n\n | \n\n'Workflow'-type fields are displaying as 'Pending - has not started' for all values\n\n | \n\nThis requires a single-line change that adds a defensive .clone\\(\\) call to deep-copy the choice list before WorkflowIcons.process\\(\\) mutates it. This prevents the shared cache from being poisoned by in-place label overwrites.\n\n | \n\n1. Navigate to the table schema for the 'Incident' table.\n2. Create a custom field named 'Test column' with the field type set to 'Workflow'.\n3. Configure 2-3 choice options for the newly created custom field.\n4. Select 2-3 incident records and set values for the 'Test column' field using any of the available options.\n5. Open UI Builder.\n6. Create an experience and page by using the 'List Page' template.\n7. Once the page is created, navigate to it on the instance.\n8. From the sidebar navigation, navigate to **Incidents** > **All**.\n9. Select the Personalize fields button on the list page.\n10. Add the Test column custom field to the visible columns.\n\nObserve that the workflow stages for the custom workflow type field appear empty.\n\n11. Open any incident record that has a value set for this field \\(can be opened in classic view as well\\).\n12. If the field is not visible, add it to the 'Form' view.\n\nObserve that the field displays 'Pending - has not started'. Note that even when the field value is changed via background script, it continues to display 'Pending - has not started'.\n\n\n Expected behavior: The display value should be as per available choices.\n\n Actual behavior: It displays 'Pending - has not started' even after changing value. 'Pending - has not started' is not even available as a choice option for a field.\n\n |
| \n\nList Administration\n\n PRB2030898\n\n | \n\nThe 'Selected stage' icon isn't applied when WorkflowIcons has already assigned a default icon\n\n | \n\n \n\n | \n\n1. Open the latest Australia instance.\n2. Open an articles list in Knowledge Center.\n\n See that workflow states are displaying as 'No workflow stages available'.\n\n |
| \n\nList Administration\n\n PRB2044745\n\n | \n\nNow-record-list-connected sends encodedRecord as \\{\\} instead of ''\n\n | \n\nThe variables contain 'encodedRecord': \\{\\} \\(empty object\\). It's treated as a non-empty, non-nil value, so the advanced qual is evaluated against an empty 'current' and wrong/empty results are returned. This is reproducible across base instances, but works correctly in Classic UI16.\n\n | \n\n1. In a workspace \\(for example, CSM/incident\\), open an incident record.\n2. From the right sidebar, select **Create Template**.\n3. Select **+** to add a field.\n4. Add a reference field that uses an advanced/dynamic reference qualifier referencing the 'current' object.\n5. Open the picker \\('Search for Record'\\).\n6. Inspect the getReferenceListLayout / nowRecordListConnectedReference GraphQL call.\n\n Expected behavior: EncodedRecord is '', so the advanced/dynamic qualifier is correctly skipped when no 'current' is available. This matches the UI16 template behavior.\n\n Actual behavior: The variables contain 'encodedRecord': \\{\\} \\(empty object\\). It's treated as a non-empty, non-nil value, so the advanced qual is evaluated against an empty 'current' and wrong/empty results are returned.\n\n |
| \n\nList Administration\n\n PRB2053781\n\n | \n\nThe new AI list badge in UI16 breaks list cell content wrapping\n\n | \n\n \n\n | \n\n \n\n |
| \n\nList AI Indicators\n\n PRB2051786\n\n | \n\nThe horizontal scroll for AI-tagged items in the groupedBy list is broken\n\n | \n\nWhen the user scroll to the right, the field isn't visible.\n\n | \n\n \n\n |
| \n\nList AI Indicators\n\n PRB2055051\n\n | \n\nUpdate the Otto indicators in seismic workspace lists\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nList AI Indicators\n\n PRB2055052\n\n | \n\nUpdate the Otto indicators in UI16 lists\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nManager Hub\n\n PRB2054008\n\n | \n\nIn Manager Hub, add a null check when using getRefRecord\\(\\)\n\n | \n\n \n\n | \n\n \n\n |
| \n\nMentoring\n\n PRB2056277\n\n | \n\ngetRefRecord\\(\\) scoping bypass for mentoring\n\n | \n\n \n\n | \n\n \n\n |
| \n\nMID Server\n\n PRB2063491\n\n | \n\n'LinkedHashMap$Entry' objects connected to the LRU take a couple MB\n\n | \n\nThese objects are from 'ecc\\_queue\\_authorization\\_policy'.\n\n | \n\n1. Open a local instance.\n2. Connect to the MID Server.\n3. Create a heap dump.\n\n Notice that entries of 'LinkedHashMap$Entry' for ecc\\_queue\\_authorization\\_policy have over 3MB for each entry.\n\n |
| \n\nMobile Experience for Field Service Management\n\n PRB2053984\n\n | \n\nBackport getRef changes to Field Service Management \\(FSM\\) Mobile\n\n | \n\n \n\n | \n\n \n\n |
| \n\nMobile Platform\n\n PRB2033559\n\n | \n\nAdd a null check for using getRefRecord\\(\\) in the script include\n\n | \n\nEnforce cross scope access restrictions when using GlideElementReference. jsFunction\\_getRefRecord\\(\\).\n\n | \n\n1. Create two scoped apps: App A and App B.\n2. In App B, create Table B with caller restriction turned on.\n3. In App A, create Table A with a reference field pointing to Table B.\n4. Don't grant RCA access from App A to Table B.\n5. Insert a record in Table A referencing a record in Table B.\n6. From the App A script, call current.ref\\_to\\_b.getRefRecord\\(\\).\n\n Expected behavior: Access is denied, null is returned, and a violation is logged.\n\n Actual behavior: The call returns a valid record instead of null.\n\n |
| \n\nMobile Platform\n\n PRB2039101\n\n | \n\nA device pin on mobile devices can't be turned off for Government Community Cloud \\(GCC\\) users\n\n | \n\n \n\n | \n\n1. Log in to a mobile device for a GCC instance.\n2. Note that the device pin is turned on.\n\n See that changing the device encryption enabled property doesn't turn off the pin.\n\n |
| \n\nMobile Studio\n\n PRB2034896\n\n [KB3085639](https://hi.service-now.com/kb_view.do?sysparm_article=KB3085639)\n\n | \n\nsn\\_maib app fails to auto-upgrade when installed\n\n | \n\nThis is due to an incorrect app\\_id declaration in the oob-app properties file.\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nMulti-Instance Framework - Core\n\n PRB2063884\n\n | \n\nMIF Hermes doesn't refresh the cluster configuration when the local hermes\\_cluster\\_config has no primary or after a datacenter-rule change, causing stale/failed cluster resolution for remote owners\n\n | \n\nWhen instance A sends a MIF async message to instance B, it needs B's Hermes cluster details \\(datacenter + Kafka bootstrap servers\\). A keeps a saved copy in the hermes\\_cluster\\_config table and reads it in HermesProducerClient.getClusterInfoSet. Today that method only calls B's live endpoint \\(/api/now/hermes \\_cluster\\_info, tier-2\\) when A has no saved rows for B. Two gaps result: 1. Saved rows but no primary — if A has rows for B where no one is is\\_primary\\_for\\_service=true \\(scenario like only a single non-primary cluster row\\), the method does not refresh. And method ensureTopicLocationForInstance\\(String owningInstance\\) then finds primaryCluster == null and the send fails with 'No primary cluster found'. 2. Stale rows after a datacenter change — if a MIMIR rule change moves B's cluster to a new DC, A's saved rows are outdated but still look complete \\(they have a primary\\), so tier-1 returns them and A never re-discovers → messages Navigate to the old cluster.\n\n | \n\n1. Verify that Instance A has a saved Hermes cluster rows for instance B \\(service MIF-Hermes\\) pointing to B's old datacenter, or a single row that isn't marked primary.\n2. Send a MIF async message from A to B.\n\n Expected behavior: A resolves B's current cluster details and sends to the correct datacenter.\n\n Actual behavior: A uses the old/incomplete saved config and sends to the wrong datacenter, or fails with 'No primary cluster found'.\n\n |
| \n\nMultimodal Service \\(Family Channel\\)\n\n PRB2051440\n\n | \n\nOn-demand MMS submission fails\n\n | \n\nThe issue occurs on instances where the multimodal service URL is configured via sys\\_service\\_endpoint instead of the system property.\n\n | \n\n1. Open an instance with the MMS plugin active.\n2. Leave glide.platform\\_mm\\_service.service\\_url empty.\n3. Configure the Multimodal service endpoint via an active sys\\_service\\_endpoint record.\n4. Confirm that the batch/scheduled MMS job reaches the service.\n\nObserve that it resolves the URL from sys\\_service\\_endpoint.\n\n5. Call new MultimodalServiceUtil\\(\\) .submitOnDemand\\(attachmentSysId, query\\).\n\n Observe that the on-demand MMS submission fails.\n\n |
| \n\nNext Experience Unified Navigation\n\n PRB2019091\n\n | \n\nIf beyond the 5MB limit, a localStorage limit blocks headerMenuItems from being cached\n\n | \n\n \n\n | \n\n1. Open an instance with thousands of apps and tens of thousands of modules, enough to make the menu payload be over 5MB.\n2. Clear the caches and refresh the page.\n\n Notice that the menu request is made on each load because the object isn't cached due to being too large.\n\n |
| \n\nNext Experience Unified Navigation\n\n PRB2053821\n\n | \n\nUpdate to Otto branding in Next Experience\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nNow Assist in Virtual Agent\n\n PRB2056609\n\n | \n\nChange the Knowledge Graph \\(KG\\) defaults in NAVA and Now Assist Portal\n\n | \n\nToday, the KG default is User NLQ graph. That should be changed so the defaults are: In Now Assist Virtual Agent for natural language query, change the graph to Enterprise Graph \\(Small\\) and select the tag as 'VIRTUAL AGENT DEFAULT TAG'. In Now Assist Panel for natuaral language query, change the graph to Enterprise Graph \\(Small\\) and select the tag as 'NOW ASSIST PANEL DEFAULT TAG'.\n\n | \n\n \n\n |
| \n\nNow Assist Nextwave Experience\n\n PRB2059502\n\n | \n\nAdd sys\\_props for caching in sys\\_og\\_conversational \\_cache\\_configuration\n\n | \n\nIf props are enabled on the instance, that should be reflected via cache service instantly.\n\n | \n\n \n\n |
| \n\nNow Assist Nextwave Experience\n\n PRB2061245\n\n | \n\nSessionController shouldn't try to refresh AuthorizationInfoBundle, as this is done in the Glide handshake process\n\n | \n\nWhen a topic execution is initiated, the conversation ID isn't available in certain Glide log entries' context maps, which complicates troubleshooting across different trace IDs instead of a unified conversation ID. The conversation ID should be available in the cache and topic execution context map in the syslog table.\n\n | \n\n \n\n |
| \n\nOAuth\n\n PRB2018183\n\n | \n\nThe unallowed system property glide.oauth. jwt.token\\_request .honor\\_claim\\_keys is included in an upgrade payload, resulting in a misleading 'skipped' upgrade log entry\n\n | \n\nDuring a Zurich upgrade, the system property glide.oauth. jwt.token\\_request .honor\\_claim\\_keys \\(from com.snc.platform.security.oauth\\) appears as a skipped entry. This property is not allowed by design and therefore never loaded into sys\\_properties on user instances.\n\n | \n\n1. Navigate to **All** > **Upgrade Center** > **Upgrade History**.\n2. Open the record of upgrading in Zurich.\n3. Select the **Skipped Changes to Review** tab.\n4. Select the skipped record for sys\\_properties\\_ 107762282f223210 3698319c003f9b2f.xml.\n\n |
| \n\nOAuth\n\n PRB2052671\n\n | \n\nSupport to create an OAuth entity record within the caller scope\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nOn-Call Scheduling\n\n PRB1975559\n\n | \n\nOn-call contact information isn't visible for some users for some attempts\n\n | \n\nThis issue only occurs when logged in as a user.\n\n | \n\n \n\n |
| \n\nOn-Call Scheduling\n\n PRB2034496\n\n | \n\nIn a SMS action in a the subflow 'On-Call', the 'Check Assignment Response' doesn't use Notify\n\n | \n\nThe 'On‑Call: Check Assignment Response' flow uses the legacy SMS send action instead of the Notify‑based SMS action.\n\n | \n\n \n\n |
| \n\nOn-Call Scheduling\n\n PRB2039960\n\n | \n\nThe NotifyUtils check for notification devices should return empty when the ACL check is successful\n\n | \n\n \n\n | \n\n \n\n |
| \n\nOneExtend\n\n PRB2041342\n\n | \n\nAI Summary card stays in perpetual loading state\n\n | \n\nThis issue occurs for some Business Application records using the Record Summarization capability. There are no LLM calls and no errors.\n\n | \n\n1. Navigate to APM Workspace.\n2. Open a Business Application record.\n\nObserve that the AI Summary card stays in perpetual loading.\n\n3. Check sys\\_generative\\_ai\\_log.\n\nObserve that there's no LLM call logged for this request.\n\n4. Check syslog.\n\nObserve that there's no errors; the full pipeline completes with cache HIT.\n\n5. To compare with a working BA record, navigate to service-now.com/now/apm/application-rationalization.\n6. Select the **Now Asisst** icon on business apps.\n\n Observe that the summary is generated. It generates LLM calls and renders correctly.\n\n |
| \n\nOneExtend\n\n PRB2056745\n\n | \n\nGuardian preprocess flow resolves getGeoRoutingDetails\\(\\) multiple times per request in NowLLMIntegration GuardianProvider\n\n | \n\nNowLLMIntegration GuardianProvider. shouldUseGatewayService\\(\\) and addLLMGatewayRoutingHeader\\(\\) each independently call through to GeoRoutingServiceImpl .getGeoRoutingDetails\\(\\) > resolveGeoRoutingDetails\\(\\). ShouldUseGatewayService\\(\\) itself is invoked from multiple call sites across a single request's lifecycle \\(transformRequest, generateTrustBuilderInputs, tryLogTrustBuilderResults, and twice within getUrl\\(\\)\\). None of these calls are memoized, so resolveGeoRoutingDetails\\(\\) re-executes its full resolution logic \\(potentially including the licensing entitlement API call\\) on every invocation within the same request, even though the underlying geo-routing state can't change MID-request.\n\n | \n\n1. Trigger a Guardian moderation request that routes through NowLLMIntegration GuardianProvider \\(LLM\\_GENERIC\\_ SMALL\\_MODERATIONS model\\).\n2. Trace/log calls into GeoRoutingServiceImpl .resolveGeoRoutingDetails\\(\\) \\(or set a breakpoint\\) during a single request's transformRequest\\(\\)/getUrl\\(\\) lifecycle.\n\n Observe that resolveGeoRoutingDetails\\(\\) executes repeatedly \\(up to six times found via code trace\\) instead of once per request. When the 0$ SKU entitlement isn't active, each of these calls re-invokes the expensive isEntitlementActive WithLicensingAPI\\(\\) licensing call, since resolveGeoRoutingDetails\\(\\) has no per-request memoization. Only the underlying getGeoRoutings\\(\\) /getGeoRoutingConfigs\\(\\) cache calls are cached via ADomainAwareCache.\n\n |
| \n\nOneExtend\n\n PRB2056991\n\n | \n\nLog reasoning tokens for 3P providers and Now LLM\n\n | \n\nA new field, reasoning\\_token\\_count, naming is aligned to existing token fields. The field is added to the GenAI log table. The field is populated for reasoning-capable models across all supported providers. For non-reasoning models, or when a provider returns no reasoning count, the field defaults to zero \\(documented\\) rather than null-ambiguous. A single, documented convention is applied to stored token values: store the provider's raw output\\_tokens and reasoning\\_tokens separately such that reasoning\\_tokens ≤ output\\_tokens, allowing it to derive answer-only tokens as output − reasoning. Existing consumers of the log are unaffected, and total-token reconciliation still holds.\n\n | \n\n \n\n |
| \n\nOneExtend\n\n PRB2057127\n\n | \n\nMultiple GenAI logs are created in skill chaining execution\n\n | \n\nOneExtend Execute and ExecuteSecure are missing the offGlideChainingEnabled flag.\n\n | \n\nExecute a skill chaining.\n\n Observe that the Generative AI logs are created two times.\n\n |
| \n\nOneExtend\n\n PRB2059503\n\n [KB3142021](https://hi.service-now.com/kb_view.do?sysparm_article=KB3142021)\n\n | \n\nSummarization records aren't displaying a proper response\n\n | \n\nIncident, Change, Case summarizations are failing with errors when users select the **Summarize** button: 'Summarization could not be completed because access to the base table Case was unsuccessful'. Error logs: 'Error sending to unified\\_short\\_url\\_active\\_1...Status 500 - \\[Internal Server Error\\] \\[\\{'success':false,'statusCode':429,'message':'Too many concurrent data insert operations in progress - additional rebuild request being ignored','timestamp':'2026-07-17T07:00:17.752637494Z','results':\\{\\}\\}\\]'.\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nOperational Technology Visibility\n\n PRB2031853\n\n | \n\ngetRefRecord\\(\\) scoping bypass for Operational Technology \\(OT\\) core and OT Service Management\n\n | \n\n \n\n | \n\n \n\n |
| \n\nPerformance Analytics\n\n PRB1802682\n\n | \n\nThe score for average duration of a DB view is incorrect when compared with the list view for both data snapshots and classic Platform Analytics \\(PA\\)\n\n | \n\nA Glide record sets a default value of '0' for null values. Classic PA uses the Glide record.\n\n | \n\n1. Turn on data snapshots for the indicator in incident SLA DB view.\n2. Ensure to remove any scripted breakdowns.\n3. Add 'AVG of Business Duration' with units as 'Time'.\n4. Run data collection for both data snapshots and classic PA.\n5. Compare scores.\n\n See that classic PA shows 11 hours 28 minutes, data snapshots shows 8 hours 35 minutes, and list view shows 20 hours 40 minutes.\n\n |
| \n\nPerformance Analytics\n\n PRB1949829\n\n | \n\nBreakdown elements aren't displaying consistently on the 'workbench' widget\n\n | \n\nOn the 'workbench' widget, all the elements are displaying for a breakdown when the **Timeseries** field has a value and the value of the property 'com.snc.pa. scorecard.breakdown. chart.max\\_rows' hasn't been changed.\n\n | \n\n \n\n |
| \n\nPerformance Analytics\n\n PRB2032037\n\n | \n\nThe Platform Analytics dashboard filters ignore Element Security Lists and display 'Nothing is available'\n\n | \n\nIf the user sets up an Element Security List for a breakdown source that's used as a filter in a Platform Analytics dashboard, the filter shows 'Nothing is available'. This happens even though the user has valid access to the dashboard and the underlying data.\n\n | \n\n \n\n |
| \n\nPerformance Analytics\n\n PRB2035061\n\n | \n\nCore UI widgets render blank data for fiscal and business calendar indicators\n\n | \n\nHighcharts has been upgraded from version 10.3.3 to 12.3.0. As part of this upgrade, some legacy Highcharts utility methods used by the Core UI dashboards \\(legacy pa\\_dashbaord\\) and widgets have been deprecated or replaced in the newer version. Any usage of older Highcharts APIs or utility methods should be reviewed and updated to use the latest supported alternatives available in Highcharts 12.3.0.\n\n | \n\n1. On any instance in \\(or after\\) Australia's build, create any indicator source with:\n\n**Standard calendar** > **fiscal quarter or fiscal year**\n\n2. Create the indicators with these sources and run data collection jobs to populate scores.\n3. Navigate to KPI Details/Analytics Hub with these indicators and make sure that the charts are visible.\n4. Create core UI widgets and link the with the newly created indicators.\n5. Create a core UI Dashboard and add the widgets.\n\n Expected behavior: The same data as shown in the Analytics Hub is to be rendered.\n\n Actual behavior: All the business calendar or fiscal calendar indicator widgets render blank data.\n\n |
| \n\nPerformance Analytics\n\n PRB2050693\n\n | \n\ninjectWidgetContent re-executes already-loaded scripts via document.body.appendChild, causing a widget regression\n\n | \n\ninjectWidgetContent in canvasUtils.js strips all <script src> tags from the widget HTML and re-injects them via document.body.appendChild. For scripts already loaded at page render time via Jelly <g:requires>, this causes re-execution, which corrupts initialized state and breaks widget functionality.\n\n | \n\n \n\n |
| \n\nPerformance Analytics\n\n PRB2054497\n\n | \n\nData snapshot indicator charts fail to render\n\n | \n\nIt can't encode an object during JSON serialization.\n\n | \n\nOn an Australia instance, open any dashboard with a data snapshot indicator chart.\n\n Observe that the chart fails to render. Check the server logs for: ''Cannot encode object' / JsonMappingException through reference chain: LinkedList\\[0\\] -> DataSnapshots DataService$1\\['response'\\]'.\n\n |
| \n\nPlatform Analytics Component API\n\n PRB1961798\n\n | \n\nRecords aren't deleted from report stats or the 'Visualization metadata' table\n\n | \n\n \n\n | \n\n \n\n |
| \n\nPlatform Analytics Component API\n\n PRB2021236\n\n | \n\nIn an instance migrated to Australia, reports display Name = None for non-global domains\n\n | \n\nWhen a instance with core UI reports is migrated to Australia, any reports that aren't in the global domain don't have the name set.\n\n | \n\n \n\n |
| \n\nPlatform Analytics Component API\n\n PRB2031447\n\n | \n\nA data visualization type is duplicated post-Australia upgrade\n\n | \n\nWhen in the **Platform Analytics** > **Library** > **Data Visualization** > **Landing** page under the 'Count' section, and putting a filter with the condition type as 'single score', there are duplicate values in the total.\n\n | \n\n1. **All** > **Platform Analytics** > **Data visualization**.\n2. Try adding a filter on the **Type** fiel.\n3. While adding a filter condition, observe it has more than one single score.\n\n |
| \n\nPlatform Analytics Component API\n\n PRB2037528\n\n | \n\nIn Australia, data visualizations created by non-admin users aren't visible by that user on the 'Overview' page under **Quick Access** > **Created by me**\n\n | \n\n \n\n | \n\n1. On an Australia instance, impersonate a non-admin user.\n2. Navigate to **Platform Analytics** > **Data Visualizations** > **Library**.\n3. Select **Create data visualization** to create a data visualization \\(any type, any data source\\).\n4. Navigate to **Platform Analytics** > **Data Visualizations** > **Library** > **Overview**.\n5. Under 'Quick Access', select **Created by Me**.\n\nObserve that the data visualization doesn't appear.\n\n6. Repeat the same as an admin user.\n\nNote that the visualization does appear.\n\n\n |
| \n\nPlatform Analytics Component API\n\n PRB2075761\n\n | \n\n'sn\\_app\\_analytics\\_w' app upgrades are inconsistent\n\n | \n\n \n\n | \n\n \n\n |
| \n\nPlatform Analytics Component API\n\n PRB2039912\n\n | \n\n'vertical\\_bar' is displayed in the value format on the data visualization library page\n\n | \n\n \n\n | \n\n1. Turn on the v\\_table property to see Core UI reports in the data visualization library.\n2. Search for 'Top 15 most helpful articles'.\n3. Check the type of the report.\n\n Expected behavior: The type should be 'Vertical bar'.\n\n Actual behavior: The type is 'vertical\\_bar'.\n\n |
| \n\nPlatform Analytics Component API\n\n PRB2040129\n\n | \n\nOptimize the reparenting script\n\n | \n\n \n\n | \n\n1. Upgrade a Zurich instance to Australia.\n2. Navigate to the dashboard/data visualization library page.\n\n Expected behavior: Dashboards/data visualization are there in the library page list.\n\n Actual behavior: Dashboards/data visualization aren't shown in the library page list.\n\n |
| \n\nPlatform Analytics Component API\n\n PRB2079191\n\n | \n\nRemove sys\\_script\\_fix\\_ ee3a858a4b 8203101a31117 f2974612b.xml\n\n | \n\nThe script sys\\_script\\_fix\\_ ee3a858a4b 8203101a31117 f2974612b.xml introduced in Australia Patch 5 is causing upgrade delays due to the huge number of records.\n\n | \n\n1. Log in to a Zurich instance.\n2. Ensure that there are more than 100K records in report\\_table.\n3. Verify that the following isn't present:\n - The report\\_table field in report\\_stats table\n - The analytics\\_visualization\\_metadata table\n4. Verify that the script is not present in the instance: /nav\\_to.do?uri = sys\\_script\\_fix.do? sys\\_id= ee3a858a4b 8203101a31117 f2974612b.\n5. Upgrade the instance to Australia Patch 5.\n\n Observe that there are significant delays due to sys\\_script\\_fix\\_ ee3a858a4b 8203101a31117 f2974612b.xml.\n\n |
| \n\nPlatform Analytics Dashboard API\n\n PRB2037426\n\n | \n\nscoreType is forced to 'latest' for non-aggregate indicators due to an undefined aggregateIndicator check\n\n | \n\nWhen a visualization widget uses a classic indicator \\(sourceType: 'indicator'\\) with applyDateRange enabled, the scoreType property is incorrectly forced to 'latest' even when the metric is not an aggregate indicator. This happens because the aggregateIndicator check in the scripted policy evaluates 'undefined !== ''' as 'true', even though the metric object doesn't have an 'aggregateIndicator' property at all. The user loses the ability to select other score types \\(sum, average, etc.\\) for non-aggregate indicators, and any previously configured scoreType value \\(for example, 'sum'\\) is overwritten to 'latest'.\n\n | \n\n1. Add a single-score \\(or any visualization that uses the shared date-range policy\\) widget to a dashboard.\n2. Configure it with a classic PA indicator data source \\(sourceType: 'indicator'\\) that isn't an aggregate indicator \\(for example, 'Number of new requested items'\\).\n3. Enable 'Apply date range' \\(applyDateRange: true\\).\n4. Set scoreType to 'sum' \\(or any value other than 'latest'\\).\n5. Open the widget configuration again.\n\n Expected behavior: The scoreType remains 'sum' and all score type options are available in the drop-down list.\n\n Actual behavior: The scoreType is forced to 'latest' and the drop-down list is inactive.\n\n |
| \n\nPlatform Analytics Dashboard API\n\n PRB2038900\n\n | \n\nPlatform Analytics Release \\(PAR\\) dashboard's saved filters drop on 'GET' \\(200, empty filters\\) when a referenced saved/library filter is unresolvable \\(deleted or cross-domain\\)\n\n | \n\nFiltersService.removeInvalidFilter \\(inline path\\) had a guard that returned '' whenever availableFilters.size\\(\\) didn't match the layout's filter-component count. getAvailableFilters can't resolve a stored\\_component whose par\\_component\\_filter record is deleted or domain-invisible, so a single unresolvable reference caused all of the dashboard's saved filters to be discarded for every user. The PUT path does no validation and saves correctly; only the GET-time validation drops them. On domain-separated \\(MSP\\) instances, this is easily hit because dashboards in user sub-domains reference global saved filters.\n\n | \n\n \n\n |
| \n\nPlatform Analytics Dashboard API\n\n PRB2039418\n\n | \n\nList migration logic should be added for the highlighted values config\n\n | \n\nWhen the user upgrades, the corresponding properties should be migrated to the new list visualization.\n\n | \n\n1. On a Yokohama instance, create a list-simple visualization.\n2. Enable fetchHighlightedValues.\n3. Add some highlightedvalueconfigid to the list-simple visualization.\n4. Upgrade to Zurich, Australia, or Brazil.\n\n Observe that the corresponding properties are migrated to the new list visualization.\n\n |
| \n\nPlatform Analytics Dashboard API\n\n PRB2050123\n\n [KB3131331](https://hi.service-now.com/kb_view.do?sysparm_article=KB3131331)\n\n | \n\nGlideClearDashboardCache is undefined in Australia, causing four business rules \\(BR\\) to fail on every Platform Analytics \\(PA\\) dashboard save and widget loss and save failures\n\n | \n\nThe Java class GlideClearDashboardCache \\(com.snc.par. dashboards.glide.script. ClearDashboardCache, annotated @GlideScriptable\\) isn't registered in the Rhino scripting scope. The class is present in the com.snc.par.dashboards OSGi bundle JAR, but isn't accessible as a Rhino scriptable — typeof GlideClearDashboardCache returns undefined. Four business rules in com.snc.par.dashboards call this class with no try/catch on every INSERT, UPDATE, and DELETE against par\\_dashboard, par\\_dashboard\\_canvas, par\\_dashboard\\_widget, and par\\_dashboard\\_permission. When a user saves a PA dashboard, these BRs throw RhinoEcmaError: 'GlideClearDashboardCache' isn't defined \\(logged as WARNING in the node log, firing 14+ times per transaction\\). Two failure modes: \\(1\\) dashboard save fails with 'Your dashboard could not be saved', or \\(2\\) save succeeds but in-memory cache not flushed — stale canvas layouts cause widgets to disappear from tabs on subsequent loads.\n\n | \n\n \n\n |
| \n\nPlatform Analytics Dashboard API\n\n PRB2050660\n\n | \n\nPar\\_dashboard\\_tab records are created unintentionally when a non-admin user accesses an inactive dashboard\n\n | \n\nWhen a non-admin user accesses an inactive \\(deactivated\\) Platform Analytics dashboard through the workspace URL, one or two new par\\_dashboard\\_tab records are created unintentionally.\n\n | \n\n1. Impersonate a user.\n2. Navigate to **Platform Analytics** > **Library** > **Dashboards**.\n3. Create a dashboard without any dashboard tabs.\n4. Open the dashboard record using a URL like 'https://<instance-id>.service-now.com/par\\_dashboard.do?sys\\_id=<sys\\_id>'.\n5. Clear the **Active** option.\n6. Update the record.\n7. As the same user as step 1, access the dashboard via a URL like 'https://<instance-id>.service-now.com/now/platform-analytics-workspace/dashboards/sys-id/<sys\\_id>'.\n8. Check par\\_dashboard\\_tab.\n\n Expected behavior: The par\\_dashboard\\_tab doesn't have a record for the test dashboard.\n\n Actual behavior: Once the user accesses the inactive dashboard, one or two new par\\_dashboard\\_tab records are created unintentionally.\n\n |
| \n\nPlatform Analytics Dashboard API\n\n PRB2053337\n\n | \n\nThere's an increased response time of Core UI dashboards in Australia\n\n | \n\nThe response times of Pa\\_Dashboard transactions degraded by 2000ms compared. This is coming from increase in SQL time.\n\n | \n\n \n\n |
| \n\nPlatform Analytics Dashboard API\n\n PRB2058867\n\n | \n\nReduce the call cost on calling isPaPremium for every dashboard get call\n\n | \n\nOn instances with large dashboard counts \\(thousands of dashboards\\), this multiplies an expensive entitlement check across the full dataset, causing high memory usage, semaphore exhaustion, node failover, and an out of memory error.\n\n | \n\n \n\n |
| \n\nPlatform Analytics Filters\n\n PRB1993721\n\n | \n\nA dashboard's Year to Date \\(YTD\\) filter fails to apply on a list unless it's reset\n\n | \n\nA dashboard's YTD filter doesn't consistently apply the correct date range to list widgets, resulting in incorrect list results until the YTD filter is manually cleared or reset.\n\n | \n\n \n\n |
| \n\nPlatform Analytics Filters\n\n PRB2021606\n\n | \n\nAn interactive filter can be cleared via a double click even when the 'Allow User to Clear Filter' option is turned off\n\n | \n\nUsers are able to clear the applied interactive filter by double-clicking the selected filter value even when the 'Allow user to clear filter' option is turned off in the filter configuration and clear filter option isn't appearing. Additionally, when multiple interactive filters are configured with filter interactions/dependencies, the dependent filters still display the option to clear the filter. This behavior creates inconsistency with the expected functionality of the 'Allow user to clear filter' setting, as users are still able to clear filters through alternate interactions.\n\n | \n\n1. Create a dashboard.\n2. Add a visualization with an interactive filter.\n3. Configure the interactive filter to turn off the option 'Allow user to clear filter'.\n4. Apply/select a filter value on the dashboard.\n\nObserve that there's no 'Clear filter' option.\n\n5. Double-click the selected filter value.\n\nObserve that the filter is cleared even though the clear option is turned off.\n\n6. Configure another interactive/dependent filter.\n\nObserve that the dependent filter still displays the option to clear the filter.\n\n\n Expected behavior: When the 'Allow user to clear filter' option is turned off, users shouldn't be able to clear filters through any UI interaction, including double-click actions or dependent filter interactions.\n\n Actual behavior: Filters can still be cleared through double-click interaction and dependent filters display clear filter options despite the setting being turned off.\n\n |
| \n\nPlatform Analytics Filters\n\n PRB2031107\n\n | \n\nThe 'Allow user to clear filter' option isn't auto-checked in the filter designer\n\n | \n\n \n\n | \n\n1. Configure one single select, one multi select, and one date filter type separately from filter designer.\n2. Add a source if needed, based on the filter type.\n3. Save the filter.\n4. Open each filter.\n5. Check the 'Advanced' option.\n\n Expected behavior: The 'Allow user to clear filter' option should be auto-checked.\n\n Actual behavior: The 'Allow user to clear filter' option isn't auto-checked.\n\n |
| \n\nPlatform Analytics Filters\n\n PRB2031506\n\n | \n\nThe 'Follow' filter toggle option is missing in a cascading filter\n\n | \n\n \n\n | \n\n1. Create a Next Experience dashboard.\n2. Add two filters, one on sys\\_user\\_group and another on sys\\_user.\n3. In the configuration panel of the filter on sys\\_user, check the 'Follow other' filter section.\n\n Expected behavior: The filter on sys\\_user has the option to follow the sys\\_user\\_group filter.\n\n Actual behavior: No available option is displayed.\n\n |
| \n\nPlatform Analytics Migration API\n\n PRB2034116\n\n | \n\nUpgrading from Yokohama to Zurich causes all pa\\_widgets to be migrated after upgrade\n\n | \n\nThe pa\\_widgets table doesn't have an active field.\n\n | \n\n \n\n |
| \n\nPlatform Analytics Migration API\n\n PRB2037846\n\n | \n\nThe Migration Center summary count doesn't match the list count for fully migrated dashboards\n\n | \n\nThe Get Migration Summary Scripted API needs to be updated so that it calculates the total number of migrated dashboards in the same way as the Migrated List.\n\n | \n\nScenario 1:\n\n 1. Create a few Core UI dashboards.\n2. Migrate them.\n3. Navigate to the PAR Dashboards table.\n4. Delete one or more migrated dashboards.\n\n Observe that the Migrated List count and the Summary count don't match.\n\n Scenario 2:\n\n 1. Create a Core UI dashboard containing a Dynamic Content widget.\n2. Migrate the dashboards.\n3. Navigate to the par\\_coreui\\_migration \\_bridge\\_dashboard table.\n4. Remove the record\\(s\\) associated with the dashboard that contains the Dynamic Content widget.\n\n Observe that the Migrated List count and the Summary count don't match.\n\n |
| \n\nPlatform Analytics Migration API\n\n PRB2057808\n\n | \n\nRemove unified User with elevated privileges only\n\n | \n\nRemoving the write for User with elevated privileges only for the com.glide.par.unified \\_analytics.enabled property.\n\n | \n\n \n\n |
| \n\nPlaybooks \\(Family Channel\\)\n\n PRB2025987\n\n | \n\nA user can't view a playbook without record create access\n\n | \n\n \n\n | \n\n \n\n |
| \n\nPlaybooks \\(Family Channel\\)\n\n PRB2034002\n\n | \n\nThere's canLaunchPlaybook and launchPlaybook inconsistency for run strategy\n\n | \n\ncanLaunchPlaybook\\(enforceRunStrategy=true\\) returns true but the subsequent launchPlaybook call throws PlaybookInvalidInputException: 'The playbook specified can't be launched because of its run strategy for the same playbook and parent record'.\n\n | \n\n \n\n |
| \n\nPlaybooks \\(Family Channel\\)\n\n PRB2052473\n\n | \n\nThe getPlaybookContextParentRecord API should be exposed as scriptable\n\n | \n\nThe Playbook MCP tool code doesn't use the existing API getPlaybookContexts ByParentRecord to launch and continue playbook execution. This API internally handles all validation and permission access, which results in duplicate logic. The current java API should be exposed as a scriptable API to use at Playbook MCP tool.\n\n | \n\n1. Add any compatible playbook as MCP tool.\n2. Try to launch playbook through the Claude client.\n\n Observe that it launches playbook, but it uses custom logic to validate access and permission.\n\n |
| \n\nPlaybooks \\(Family Channel\\)\n\n PRB2052669\n\n | \n\n'Completed By'/'Completed On' for activity contexts\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nPortfolio Planning with PPM, Agile 2.0, and SAFe\n\n PRB2055648\n\n | \n\nGetRefRecord scoping bypass for app-apw-internal-int\n\n | \n\n \n\n | \n\n \n\n |
| \n\nPPM Standard\n\n PRB2037975\n\n | \n\nRelax RIDAC table business rules\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nProcess Mining\n\n PRB2022864\n\n | \n\nUsers are unable to edit access for Now Assist creator's 'Work Notes Analysis' skill\n\n | \n\n \n\n | \n\n1. Navigate to a Zurich instance.\n2. Impersonate any admin user.\n3. Navigate to Now Assist Admin.\n4. Open **Creator** > **Skill** > **Work Notes Analysis**.\n5. Try to add an extra role beside the given role.\n\n Expected behavior: The user should have edit permission to edit.\n\n Actual behavior: The user is unable to edit permissions.\n\n |
| \n\nProcess Mining Workspace\n\n PRB2007466\n\n | \n\nWhen feedback given by user is changed and navigates to another UI, on a revisit, the **Feedback** button switches from the previous state to new\n\n | \n\n \n\n | \n\n1. Generate highlights for any of the findings on a mined project.\n2. Submit feedback via the icon.\n3. Navigate to any other page or open any other finding.\n4. Navigate back to the same highlights and make a thumbs down.\n\n Expected behavior: Feedback shouldn't be switched back and forth. The new state should be preserved even if the user navigates to other screens.\n\n Actual behavior: When the user comes back to the finding where feedback is given, the feedback is switched from the previous state to the new state.\n\n |
| \n\nProcess Mining Workspace\n\n PRB2024798\n\n | \n\nSummary top banner metrics isn't displaying until the project is reopened or the page is refreshed\n\n | \n\n \n\n | \n\n \n\n |
| \n\nProcess Mining Workspace\n\n PRB2029472\n\n | \n\nThe **Intent and activity analysis** button is enabled on findings without process configuration\n\n | \n\n \n\n | \n\n1. Don't configure intent and activity analysis on process configuration.\n2. Navigate to the 'Summary and insights' page of the mined project.\n3. Open the findings in the 'Opportunity details' page.\n4. Select the **Investigate** tab.\n\n Observe that intent and activity analysis is turned on. It should be turn off without the proper configuration.\n\n |
| \n\nProcess Mining Workspace\n\n PRB2030093\n\n | \n\nRe-triggering 'Generate highlights' after an error displays no loading indicator or feedback that a process is running\n\n | \n\n \n\n | \n\n1. Navigate to an improvement opportunity with a high number of records \\(~30k\\).\n2. Attempt to generate highlights.\n\nObserve that an error is displayed.\n\n3. After the error, select **Generate highlights** again.\n\n Expected behavior: The UI should go into 'progress' mode, before displaying the result/error.\n\n Actual behavior: No loading indicator, spinner, or any visual feedback is displayed to the user to indicate that a process is running.\n\n |
| \n\nProcess Mining Workspace\n\n PRB2030109\n\n | \n\nAn errored scheduled task leaves the component stuck at 'Loading contents...' indefinitely\n\n | \n\n \n\n | \n\n1. Navigate to an improvement opportunity with a high number of records \\(~30k\\).\n2. Attempt to generate highlights.\n\n Observe that the scheduled task errors out, and that the highlights component remains stuck displaying 'Loading contents..' indefinitely and never surfaces the error state to the user. The loading message should be replaced with an error message.\n\n |
| \n\nProcess Mining Workspace\n\n PRB2050830\n\n | \n\nWipe out promin\\_metered \\_usage\\_data across non-prod and rely on the Glide non-prod/prod property, not on the Open/Closed property\n\n | \n\nWhen users clone production to a sub-prod instance, the sub-prod promin\\_metered \\_usage\\_data table is wiped and replaced with prod's data, so sub-prod reflects a copy of prod rather than real usage. When users clone prod to several sub-prods at once, each carries prod's usage table. Subscription Management's flat aggregation then counts the same prod records once per instance, so reported usage scales linearly with the number of sub-prods a customer maintains, independent of actual mining behavior.\n\n | \n\n \n\n |
| \n\nProcess Mining Workspace\n\n PRB2052878\n\n | \n\nOtto directive for process mining\n\n | \n\nThe Otto rebrand should be completed for work notes analysis, intent and activity analysis, process highlights, generate process config with AI, and playbook mining.\n\n | \n\n \n\n |
| \n\nProject Management\n\n PRB2006929\n\n | \n\nDeleting a project task with MS Project creates an orphaned resource request\n\n | \n\n \n\n | \n\n1. Log in to any instance.\n2. Open the new Project Workspace.\n3. Select the **New** button to create a project.\n4. Select the menu button **\\(...\\)** > **Import from MS project**.\n5. Upload a MS Project schedule.\n6. Create a resource request for Project Tasking.\n7. Navigate to the resource module as the resource manager and approve the task.\n8. As the project manager, delete the task in the MS Project schedule.\n9. Return to the project record.\n10. Re-upload the updated MS Project.\n\n Expected behavior: The reupload of the schedule isn't permitted because of the related record or if it does allow the reupload, it should cascade the delete to the related records.\n\n Actual behavior: The resource manager can still see the resource request, but the task name is blank.\n\n |
| \n\nProject Management\n\n PRB2023802\n\n | \n\nThe PowerPoint export service loses the connection\n\n | \n\nThe export functionality is broken. When using the export feature, it displays 'Unable to complete request'. There are no log entries available for this error message. In order to exclude issues with the built-up service, there are regular pings every 15 minutes from the instance to the backend service, but those pings stop at the end of the day. After manually updating the entry in sys\\_service\\_endpoint, the pings start and exporting to PowerPoint is available.\n\n | \n\n \n\n |
| \n\nReleaseOps - Family\n\n PRB1951541\n\n | \n\nupdate\\_set\\_admin needs access to 'Promote Update Set'\n\n | \n\nThe UI action condition currently requires the admin role, but should allow for both 'admin' and 'update\\_set\\_admin'.\n\n | \n\nAs a user with role update\\_set\\_admin \\(and not admin\\), complete an update set.\n\n Expected behavior: The**Promote Update Set** UI action is available.\n\n Actual behavior: It isn't available.\n\n |
| \n\nReporting\n\n PRB2040639\n\n | \n\nRequire authentication on a scripted rest API reporting\\_alias\n\n | \n\n \n\n | \n\n \n\n |
| \n\nReporting\n\n PRB2058918\n\n | \n\nLogging when there's an RVACL exception doesn't work for visualizations and only for Core reports\n\n | \n\nGlide.rest.debug = true can't be set on instances, so it needs a dedicated sys property to allow RVACL exception logging for the failed path. Only Core UI reports are tracked in the code and not visualizations.\n\n | \n\n \n\n |
| \n\nRequest Management\n\n PRB2050782\n\n | \n\nAn approval summary displays the incorrect attachment\n\n | \n\nIn Service Operations Workspace \\(SOW\\), attachment records displayed on approval records are inconsistent with the actual request item. When multiple request items contain attachments with the same file name, SOW resolves and displays the attachment from a different record \\(incorrect sys\\_id\\). The attachment file name appears correct, but the underlying file content belongs to a different request item. This behavior isn't reproducible in Classic UI, where attachments are always correctly associated with the respective record. The issue doesn't occur when the attachment file names are unique.\n\n | \n\n \n\n |
| \n\nScheduled Jobs\n\n PRB2015240\n\n | \n\nCreate a guard rail to protect the scheduler against misconfigured nodes to avoid impact to critical jobs\n\n | \n\nMisconfigured nodes can severely impact the job scheduler, causing business critical jobs to not get executed.\n\n | \n\n1. On a two \\(or more\\) node cluster, configure one of the nodes to have schedulers=any and participation=standby.\n2. Create 1000 pinned jobs with priority=100 and pin to that node.\n3. Wait a few minutes.\n\n Observe that both this node's and other nodes' pinned jobs with priority>=100 no longer execute.\n\n |
| \n\nSchedule Optimization\n\n PRB2022407\n\n | \n\ngetRefRecord\\(\\) scoping bypass for the 1.0.1 release\n\n | \n\n \n\n | \n\n \n\n |
| \n\nSecurity Data Filters\n\n PRB1967733\n\n | \n\nA security data filter \\(SDF\\) is applied redundantly via dotwalk paths, causing missing records in 'OR' queries\n\n | \n\nThis has two distinct symptoms caused by the same underlying duplication. One, when querying a parent table with 'OR' conditions dotwalking into multiple child tables simultaneously, the parent SDF was applied three times — once directly and once per dotwalk CE path — producing conflicting conditions that returned zero records instead of the expected results. Two, when querying a table with a field-based SDF, records where that field was empty/null were incorrectly excluded. This was caused by the same SDF being applied redundantly via a dotwalk CE, which caused the combined filter condition to exclude null matches.\n\n | \n\n \n\n |
| \n\nServer-side scripts\n\n PRB2051345\n\n [KB3128196](https://hi.service-now.com/kb_view.do?sysparm_article=KB3128196)\n\n | \n\nAutomatically created KittyScript exemptions are incorrect when using 'new GlideRecord'\n\n | \n\nWhen GuardedScript/KittyScript checks scripts in the exemption table, it does by checking a \\_normalized\\_ version of the script, where all literals are removed to ensure that it deduplicates similar scripts where the only difference is \\(say\\) a 'sys\\_id'. This normalization does \\_not\\_ apply to the constructor of 'GlideRecord' where it doesn't want a blanket execption for \\_all\\_ tables.\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nService Catalog Builder\n\n PRB2030878\n\n | \n\n'Mode' defaults incorrectly when not specified in the catalog item configuration, blocking item submission from Builder\n\n | \n\nThe root cause is a missing default value for the 'mode' property in the catalog-item component configuration \\(now-ui.json\\).\n\n | \n\n1. Navigate to UI Builder.\n2. Create an experience and a page.\n3. Add the catalog item component to the page and provide the sys\\_id.\n4. Preview the page and submit the item.\n\n Expected behavior: The item should get submitted.\n\n Actual behavior: The item isn't submitted.\n\n |
| \n\nService Catalog Portal Widgets\n\n PRB2054951\n\n | \n\nServiceNow Otto rebranding for catalog item slot-fill\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nService Catalog\n\n PRB2054931\n\n | \n\nServiceNow Otto rebranding for catalog item generation with Text2Catalog family support\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nService Level Management\n\n PRB2001036\n\n [KB3137219](https://hi.service-now.com/kb_view.do?sysparm_article=KB3137219)\n\n | \n\nIn SLACalculatorNG, an unbounded schedule/DurationCalculator cache causes memory growth during bulk SLA recalculation\n\n | \n\nDuring bulk SLA recalculation, SLACalculatorNG accumulates one GlideSchedule and one DurationCalculator instance per unique schedule+timezone combination into unbounded object maps \\(this.schedules and this.durationCalculators\\). These maps are never evicted and grow proportionally to the number of distinct schedule/timezone pairs encountered across all task\\_sla records in the query. In instances with many SLA definitions backed by different schedules, this results in unbounded heap growth for the lifetime of the bulk calculation, degrading instance performance and potentially causing out-of-memory conditions under load.\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nService Mapping\n\n PRB1971609\n\n | \n\nService Mapping Discovery runs an instance out of memory during the rediscovery process in case there are 100K discovered services in Operational Status\n\n | \n\nThe code queries for all cmdb\\_ci\\_service\\_discovered records with operational\\_status=1 without any limit. If a user has enough cmdb\\_ci\\_service\\_discovered records with operational\\_status=1, then the instance can immediately be run out of memory while building an array of the results. 0 means no limit: getAllDiscoveredBusinessServices\\(conditions, null, 0\\).\n\n | \n\n1. Create 100K discovered services in Operational Status.\n2. Run 'All Application' Discovery.\n\n |
| \n\nService Mapping\n\n PRB2036299\n\n | \n\nAfter upgrading to Australia, parent.process.pid fails to resolve, which causes the 'Get Process' operation to return the full process list instead of the targeted parent process\n\n | \n\nThe user can run a customised Tomcat WAR pattern for Service Mapping discovery. Following the Australia upgrade, step two of the 'Identification' section stops working during Service Mapping discovery. The step uses a 'Get Process' operation with process\\_id = get\\_attr \\{'parent.process.pid'\\} to locate the parent Windchill Java process. This expression fails to resolve, causing the step to run with no PID filter and return the entire process list on the host instead of the targeted parent process.\n\n | \n\n1. Upgrade to the Australia release.\n2. Run discovery on the service map with Tomcat CI.\n\n Observe that the 'Get Process' operation returns the full process list from the host instead of the targeted parent process.\n\n |
| \n\nServiceNow SDK \\(Glide\\)\n\n PRB2013533\n\n | \n\nThere's an unhelpful error when installing an app with an invalid scope prefix\n\n | \n\nError: '\\[now-sdk\\] ERROR: Exception occurred while installing application/nUnable to install application as application was null. Error: Exception occurred while installing application/nUnable to install application as application was null'.\n\n | \n\nCreate an app with now-sdk init without a valid auth saved.\n\n The resulting app has an x\\_ prefix and gives an error when trying to install on an instance.\n\n |
| \n\nServiceNow SDK \\(Glide\\)\n\n PRB2033218\n\n | \n\nFluent App metadata deletions aren't propagated when installing from the app repo\n\n | \n\nThe issue occurs because of missing sysmetadatadelete records.\n\n | \n\n1. Delete metadata from Fluent App.\n2. Build and deploy to the instance.\n3. Publish to the app repo from the instance.\n4. Install it on a different instance that doesn't contain the delete from app-repo.\n\n Expected behavior: The delete is applied and the metadata is removed.\n\n Actual behavior: The metadata not removed.\n\n |
| \n\nServiceNow Studio \\(Family Channel\\)\n\n PRB2063560\n\n | \n\nTrue up the Glider Store app\n\n | \n\n \n\n | \n\n \n\n |
| \n\nService Portal\n\n PRB2056735\n\n | \n\nUpdate the accessibility voice-input toggle label in Service Portal for the Otto rename\n\n | \n\nAs part of the 'Now Assist to Otto' rename, the accessibility toggle label must be updated in Service Portal. It's currently 'Enable voice input for Now Assist in Virtual Agent'. The new value will be similar to 'Enable voice input for ServiceNow Otto'.\n\n | \n\n \n\n |
| \n\nService Portal\n\n PRB2056737\n\n | \n\nPortal-core widget UI and theming for new Otto onboarding modal in the Service Portal\n\n | \n\nThe modal introduces users to the ServiceNow Otto experience on first login. Because Lit-based workspace components can't be embedded in angular portals, a dedicated Service Portal implementation is required. The widget lives in the platform layer and is shared across all portals. No per-portal or user uptake is required.\n\n | \n\n \n\n |
| \n\nService Portal\n\n PRB2056743\n\n | \n\nEligibility and admin control for new Otto onboarding modal\n\n | \n\n \n\n | \n\n \n\n |
| \n\nSidebar \\(Family Release\\)\n\n PRB2058602\n\n | \n\nTyping indicator no longer works\n\n | \n\n \n\n | \n\n1. Open two browsers.\n2. Log in as two different users.\n3. Create a sidebar chat for the two users.\n4. Start typing.\n\n Observe that there is no typing indicator.\n\n |
| \n\nSmart Assessments for Field Service\n\n PRB2054418\n\n | \n\nBackport getRef changes to app-smart-assessment-mobile\n\n | \n\n \n\n | \n\n \n\n |
| \n\nSmart Assessments Mobile\n\n PRB2054417\n\n | \n\nBackport getRef changes to app-smart-assessment-mobile\n\n | \n\n \n\n | \n\n \n\n |
| \n\nSoftware Asset Reconciliation\n\n PRB2000893\n\n | \n\nRecon updates are dropped by a database, causing license metric results \\(LMR\\) and product results to not update\n\n | \n\n \n\n | \n\n \n\n |
| \n\nSoftware Lifecycles\n\n PRB2004396\n\n | \n\nA calculated lifecycle should consider other phase start dates before creation\n\n | \n\n \n\n | \n\n \n\n |
| \n\nSoftware Lifecycles\n\n PRB2010294\n\n | \n\nMatching a common platform enumeration \\(CPE\\) to DMs should ignore CPEs that are version less\n\n | \n\nsn\\_itam\\_samp. MatchVulnerableSoftware ToDiscoveryModels should ignore CPEs that are a version less. Vulnerabilities are reported against versions of a product, but due to National Vulnerability Database \\(NVD\\) data or corrupted NVD data, CPEs may be a version less.\n\n | \n\n \n\n |
| \n\nSoftware Lifecycles\n\n PRB2012476\n\n | \n\nMatching a common platform enumeration \\(CPE\\) to DMs should ignore CPEs edition and software edition\n\n | \n\nThere are two **Edition** fields on CPE, 'Edition' and 'Software Edition'. It queries against both, but 'Edition' is a legacy and deprecated field from the old 2.2 standard. 'Software Edition' was introduced in 2.3.\n\n | \n\n \n\n |
| \n\nSource-to-Pay Operations \\(Glide\\)\n\n PRB2057105\n\n | \n\ngetRefRecord\\(\\) scoping bypass directive changes\n\n | \n\n \n\n | \n\n \n\n |
| \n\nStandard Ticket Page\n\n PRB2054934\n\n | \n\nServiceNow Otto rebranding for Now Assist in 'Standard Ticket' page family\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nStream Connect Core\n\n PRB2019118\n\n | \n\nGenerative AI logs are missing\n\n | \n\n \n\n | \n\n \n\n |
| \n\nStream Connect Core\n\n PRB2036772\n\n | \n\nStream Connect fails to authenticate with Kafka brokers requiring OAUTHBEARER as the SASL mechanism, blocking connectivity\n\n | \n\nWhen a broker is configured to require OAUTHBEARER, the Kafka client initiates a SASL handshake and signals the OAUTHBEARER mechanism. Without a registered token callback handler, the client cannot respond with a valid bearer token, causing the handshake to fail. The connection is dropped and no meaningful error is surfaced to the administrator beyond a generic authentication failure.\n\n | \n\n1. Configure an external Kafka broker with the SASL mechanism set to OAUTHBEARER and a valid OAuth 2.0 token endpoint.\n2. In Stream Connect, navigate to the credential configuration for Message Replication and attempt to select OAUTHBEARER as the SASL mechanism.\n\n Observe that OAUTHBEARER isn't available as a selectable mechanism in the credential configuration UI.\n\n |
| \n\nSystem Import Sets\n\n PRB2033737\n\n [KB3070753](https://hi.service-now.com/kb_view.do?sysparm_article=KB3070753)\n\n | \n\nrole mis\\_server can't read database credentials for a JDBC data source when it uses an alias\n\n | \n\n \n\n | \n\n \n\n |
| \n\nSystem Import Sets\n\n PRB2038233\n\n | \n\nJDBC connections are left dangling and unclosed\n\n | \n\nEvery time the user issues a change credential signal to MID during a JDBC import, the number of open connections grows.\n\n | \n\n1. Set up a MID server with a long running JDBC import that can be run through it.\n2. Start an import.\n3. While it's running, issue a change credentials signal to MID using the 'Refresh Credentials' related link on the MID server record.\n4. Repeat.\n5. Check the database for open connections from MID.\n\n Observe that the number of open connections grows each time.\n\n |
| \n\nSystem Web Services\n\n PRB2029605\n\n | \n\nThere's hourly reoccuring OAuth authentication failures on an outbound REST from ST ServiceNow to CG ServiceNow: 'User is not authenticated. OAuth token has expired or has not been retrieved'\n\n | \n\nThe reported issue affects the outbound integration between ServiceNow and the external ServiceNow instance through the iPaaS layer using OAuth 2.0 Client Credentials authentication. The integration fails specifically during the final one-minute window before the OAuth access token expiration. During normal token validity, the integration works successfully. Starting one minute before token expiration, outbound calls from ServiceNow fail. Failures occur in: REST Message, REST API Step, Flow Designer executions, and custom scripts. Once the token fully expires, ServiceNow successfully retrieves a new token and the integration resumes functioning normally.\n\n | \n\n \n\n |
| \n\nTable Builder\n\n PRB2052385\n\n | \n\nBackport GetRefRecord scoping bypass changes\n\n | \n\n \n\n | \n\n \n\n |
| \n\nTags\n\n PRB2039548\n\n | \n\nIn Australia, tags aren't saved for 'active = false' records for non-admin users\n\n | \n\n \n\n | \n\n \n\n |
| \n\nTalent Feedback\n\n PRB2056254\n\n | \n\ngetRefRecord\\(\\) scoping bypass for talent feedback\n\n | \n\n \n\n | \n\n \n\n |
| \n\nTask Plan Templates\n\n PRB1978400\n\n | \n\nAuto-populating the value of a task plan **Feature** field in a task plan template document isn't dymanic\n\n | \n\nThe domain separations script needs an additional check for the global domain.\n\n | \n\n1. Navigate to the sn\\_task\\_plan\\_ template\\_document table.\n2. Select the **New** button.\n\nThe task plan **Feature** field is auto-populated.\n\n3. Navigate to the sn\\_task\\_ plan\\_feature table and delete the document feature.\n4. Create a record with the sn\\_task\\_plan\\_ template\\_document feature table with the name 'Document'.\n5. Navigate to the sn\\_task\\_plan\\_ template\\_document table.\n6. Select the **New** button.\n\nThe task plan **Feature** field isn't auto-populated now.\n\n\n |
| \n\nTerritory Planning\n\n PRB2039182\n\n | \n\nUpdating potential territories for a task doesn't work as expected\n\n | \n\nThe business rule that updates the potential territories is currently triggered only when the location changes. It doesn't consider the **consider\\_potential\\_territories \\_for\\_schedule\\_optimization** boolean field.\n\n | \n\n1. Create a work order task.\n2. Change the location to see the eligible territories as per the new changed location.\n\n Expected behavior: The Business Rule that updates the potential territories should consider the**consider\\_potential\\_territories \\_for\\_schedule\\_optimization** boolean field.\n\n Actual behavior: The Business Rule that updates the potential territories is currently triggered only when the location changes and doesn't consider the **consider\\_potential\\_territories \\_for\\_schedule\\_optimization** boolean field.\n\n |
| \n\nThird-party Software\n\n PRB2032449\n\n | \n\nThe Kitty script changes should be reverted\n\n | \n\nThe changes to the Kitty script are no longer required. Everything works fine; the dashboard loads and there's no exception in the syslog table.\n\n | \n\n \n\n |
| \n\nTime-Limited User Roles\n\n PRB1972197\n\n | \n\nWhen a user is logged in, updating an existing record with a new end time in the 'Time limited user roles' tablec causes never ending information messages on all pages\n\n | \n\n \n\n | \n\n1. Open a Zurich instance.\n2. In a separate browser or incognito window, log in with a user that has an 'itil' role.\n3. In another window, log in with a user who has an 'admin' role.\n4. With the admin user, navigate to **All** > **User administration** > **Time-limited roles**.\n5. Create a record that grants an 'admin' role to the user.\n6. With the user that had only an 'itil' role but received the 'Time limited admin' role, open an incident list and then a record.\n\n Expected behavior: Users see an information message once.\n\n Actual behavior: Users see a message about roles that are granted or removed, but closing them isn't helping.\n\n |
| \n\nTrace Collector - Family Release\n\n PRB2056896\n\n | \n\nTrace collector MID code\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nTrace Collector - Family Release\n\n PRB2059215\n\n | \n\nAzure classic trace collector doesn't consider Credential IDs for AI and ML services\n\n | \n\nAzureTraceCollector ignores credential IDs supplied as config update parameters. It only considers credential alias names.\n\n | \n\n \n\n |
| \n\nUI Actions\n\n PRB2051051\n\n | \n\nThe field error message isn't shown when the error comes from the backend via business rule abortAction\n\n | \n\nThe error message isn't shown for the **short\\_description** field in Australia. However, it's visible in Faster or PAXE Integration.\n\n | \n\n1. Create an Insert/Update business rule with abortAction \\(for example, current.short\\_description.setError\\('Error!'\\); current.setAbortAction\\(true\\);\\).\n2. Create a incident.\n3. Fill in the mandatory fields.\n4. Attempt to save it.\n\n Observe that the error message isn't shown for the **short\\_description** field.\n\n |
| \n\nUI Field Administration\n\n PRB2054948\n\n | \n\nServiceNow Otto rebranding for AI indicators, AI indicator pop-overs, and Task intelligence predicition\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nUI Field Administration\n\n PRB2054949\n\n | \n\nIndexName GraphQL component and choice fallback\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nUI Field Administration\n\n PRB2054953\n\n | \n\nInject '\\*' options into composite\\_name table and field picker choice lists\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nUI Form Administration\n\n PRB2019275\n\n | \n\nThere's layout and scrollbar flickering when entering info, internal and external, in HTML **Journal** fields\n\n | \n\nThere's layout and scrollbar flickering when entering info, internal and external, in HTML **Journal** fields, caused by automatic browser window resizing. The issue occurs randomly and is not related to a specific case or text size.\n\n | \n\n1. Change the glide.ui. journal.use\\_html system property to true.\n2. Open any incident in any workspace.\n3. Type multiple lines in internal info or copy/paste some text until the scroll bar appears.\n4. Remove enough lines so that it's one new line away from displaying the scroll bar.\n5. Type some words randomly to add enough words to create a line.\n\n Observe the flickering issue.\n\n |
| \n\nUI Form Administration\n\n PRB2033143\n\n [KB3139369](https://hi.service-now.com/kb_view.do?sysparm_article=KB3139369)\n\n | \n\nThe 'Preview this record' icon isn't working in the Safari browser\n\n | \n\nSelects on the button components and controls isn't working in Safari for UI16. This issue is only reproducible in the Safari browser. Non-Safari browsers aren't impacted and they don't face this issue.\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nUI Form Administration\n\n PRB2054945\n\n | \n\nOtto brand change in form notification messages\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nUI Form Administration\n\n PRB2056498\n\n | \n\nThe parentRecordSysId is missing from ORM Workspace payload template, so the getFilterQuery API breaks\n\n | \n\nThe getFilterQuery REST API \\(/api/now/ related\\_list\\_item\\_filter/ getFilterQuery\\) is being updated to require four mandatory parameters: tableName, parentFieldName, parentRecordSysId, and referencedFieldName. The Configurable Workspace for Order Management \\(sn\\_app\\_orm\\_wksp\\) payload definition doesn't include parentRecordSysId in its payload template. Once the change occurs, any UI action using the payload receives a 400 error from the API.\n\n | \n\n1. Provision an instance with the plugin com.sn\\_app\\_orm\\_wksp installed.\n2. Activate the plugin.\n3. Trigger any UI action that uses the payload definition for event mappings.\n\n Observe that the call to /api/now/ related\\_list\\_item\\_filter/ getFilterQuery returns \\{'error': 'Invalid inputs'\\}.\n\n |
| \n\nUpgrade Center\n\n PRB1950446\n\n | \n\nThe 'Flow Designer' module directs to 'Page Not Found' after an instance upgrade on some nodes\n\n | \n\nThe **Process Automation** > **Flow Designer** module redirects to 'Page Not Found' on some nodes after an instance upgrade. The main issue is that nodes tried to download app packages from Store, but Store responded with a 400 error because the platform version for the instance isn't updated on the Store end yet, and the request is considered incompatible. However, during an upgrade, it shouldn't request app packages from Store.\n\n | \n\n \n\n |
| \n\nUpgrade Center\n\n PRB2016580\n\n | \n\nAfter upgrading instances from Zurich to Australia, several records show up on the skipped list belonging to the sn\\_glider or sn\\_build\\_agent with error 'Unable to compare, unable to find a current record'\n\n | \n\nAfter upgrading a Zurich instance to Australia the upgrade monitor will have a list of skipped records. But when trying to resolved issue, users observe the error: 'Unable to compare, unable to find a current record' when trying to compare to current.\n\n | \n\n1. Provision a Zurich instance.\n2. Make sure that the plugin sn\\_glider and sn\\_build\\_agent are not on the latest version.\n3. Upgrade the instance to Australia.\n4. Post upgrade review the skipped records.\n5. Filter for scripts or records that are part of the sn\\_glider or sn\\_build\\_agent.\n6. Open a record that is skipped and click on the UI action.\n7. Compare to Current.\n\n Observe the error.\n\n |
| \n\nUpgrade Center\n\n PRB2056920\n\n | \n\nBulk app updates feature Glide changes\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nUX Framework\n\n PRB2004013\n\n | \n\nFilters aren't appearing in the dashboard\n\n | \n\nFilters aren't appearing in dashboard in an initial dashboard load.\n\n | \n\n1. In cache.do, select **Clear Cache** and **Clear All Browser Caches**.\n2. Open a dashboard presenting multiple filters.\n\n Observe that the filters aren't loading.\n\n |
| \n\nUX Framework\n\n PRB2035397\n\n | \n\nAfter typing in an input field on record page load, the focus shifts intermittently\n\n | \n\nAfter a few words, the focus shifts to the 'Tags' section and it continues to write in that section.\n\n | \n\n1. Navigate to CSM/FSM workspace.\n2. Open the list module.\n3. Navigate to 'All Cases'.\n4. Open any case form with tags displayed on it.\n5. Start typing in an input field \\(for example, **Compose comments**\\).\n\n Expected behavior: The user continues to type and the focus remains in the typing area.\n\n Actual behavior: After a few words, the focus shifts to the 'Tags' section and it continues to write in that section.\n\n |
| \n\nUX Framework\n\n PRB2039881\n\n | \n\nGLOBAL\\_NAVIGATION\\_REQUESTED isn't routing to a feature after selecting a hard refresh of the page\n\n | \n\n \n\n | \n\n \n\n |
| \n\nUX Framework\n\n PRB2054946\n\n | \n\nKeyboard shortcut remapping for admins and users\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nVirtual Agent for Customer Service \\(Store\\)\n\n PRB1998239\n\n | \n\nAn outdated file in the Virtual Agent store plugin causes integration tests to fail\n\n | \n\n \n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB1895195\n\n | \n\nWhen the user enters an invalid/partial utterance, an error appears and the conversation is closed\n\n | \n\nDynamic capability executor can trigger multiple capabilities with different payloads. However, dynamic capability executor fails when duplicate capability IDs are passed.\n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB1914417\n\n | \n\nStopping agentic conversation shows an undefined message\n\n | \n\n \n\n | \n\n1. Start any agentic flow from Dispatcher Workspace, Now Assist Panel, NASS, or Playground.\n2. Select the **Stop** button once it's displayed.\n\n Observe the undefined message is displayed.\n\n |
| \n\nVirtual Agent\n\n PRB1952103\n\n | \n\nRemove showNoSkillsConfigured options passed when requesting the skill picker control in Now Assist Portal \\(NAP\\)\n\n | \n\nPreviously, a message was displayed to the end user if no applicable skills were configured for the logged-in user in NAP. Now that NAP also supports QnA, users will still be able to search knowledge articles, so this message is no longer required.\n\n | \n\n1. Make sure no skills are configured for the current user.\n2. Launch NAP.\n\n Observe a message reading: 'Looks like no skills are configured' and the conversation ends.\n\n |
| \n\nVirtual Agent\n\n PRB1960129\n\n | \n\nA conversation abruptly ends after a cold start conversation with a pre-chat survey enabled\n\n | \n\nThe conversation ends after the survey is complete.\n\n | \n\n1. Enable pre-chat survey.\n2. Navigate to Teams.\n3. Type 'what is spam'.\n4. Complete the pre-chat survey.\n\n Expected behavior: The user should get a response related to the query from step 3.\n\n Actual behavior: The conversation ends after the survey is complete.\n\n |
| \n\nVirtual Agent\n\n PRB1962876\n\n | \n\nAn interaction record form doesn't always pop up when receiving an inbound call\n\n | \n\nAn interaction record form doesn't always pop up when receiving an inbound call from multiple sources in short time.\n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB1980327\n\n | \n\nA chat dynamic greeting isn't localized correctly\n\n | \n\nBecause the message doesn't go down the correct API path to resolve to sys\\_ui\\_message, and it can't honor the dynamic greeting.\n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB2009200\n\n | \n\nFor the 'Resume' flow, work notes are added as the guest user\n\n | \n\n \n\n | \n\n1. Trigger the ZTSD flow with a query that has a valid KB resolution available.\n2. Impersonate as the subject person.\n3. Ask a query that can be answered by an existing KB article.\n\nThe 'Resume' flow is triggered.\n\n4. Open the corresponding case and check the 'Work Notes' section.\n\n Expected behavior: Work notes should be added under the impersonated HR L1 worker.\n\n Actual behavior: Work notes are added under the guest user.\n\n |
| \n\nVirtual Agent\n\n PRB2026682\n\n | \n\nConversation history of language detection confirmation disrupts a user response\n\n | \n\nAccording to Search QnA, the prompt isn't structured to support the intermediate language selection turn. That should be removed from the conversation history.\\`.\n\n | \n\n1. Configure language detection.\n2. Start a conversation in any standard chat.\n3. Type an utterance in a different language.\n4. The user is presented with 'You are typing in xyz language, do you want to switch' - select **Yes**.\n\n Expected behavior: The language should switch and the synthesized response should be displayed.\n\n Actual behavior: The langue switches but the response is 'How can I help you with your laptop'.\n\n |
| \n\nVirtual Agent\n\n PRB2031232\n\n | \n\nThe 'Litjs' widget isn't displaying on the Now Assist panel\n\n | \n\n \n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB2031583\n\n | \n\nNon-topic skills are dropped from the skill picker when all applicable topic skills have a visible design category\n\n | \n\nThe picker shows the topic skills grouped under their design categories, but the non-topic skills are absent. No 'Others' category is created and the non-topic skills aren't rendered.\n\n | \n\n1. Configure a VA/NowAssist conversation with:\n - At least one non-TOPIC skill that is applicable and visible \\(optionally, mark it as promoted in the context profile\\).\n - At least one TOPIC-type skill that is applicable and visible.\n2. Ensure every applicable topic skill has at least one visible design category \\(sys\\_cb\\_topic\\_category with visible = true\\).\n3. Trigger the skill picker \\(for example, via SystemScriptObject.jsFunction \\_sendSkillPickerControl → VASkillService.sendSkillPicker\\).\n\n Expected behavior: Non-topic skills appear in the picker regardless of whether the applicable topic skills all carry visible design categories. For example, they could appear under 'Others'.\n\n Actual behavior: Non-topic skills are omitted whenever there is more than one applicable topic skill and all applicable topic skills have a visible design category.\n\n |
| \n\nVirtual Agent\n\n PRB2031991\n\n | \n\n'Get details of problem agent' returns additional duplicate closure messages along with the expected closing message\n\n | \n\nWhen the user enters a closing utterance, the agent returns multiple closure messages, and the last two messages are duplicated.\n\n | \n\n1. Open Now Assist Portal.\n2. Enter an utterance like 'Help me get details of a problem'.\n\nObserve that the agent returns a response like 'Could you please provide the problem number you'd like details for?'.\n\n3. Enter an utterance like 'See you later'.\n\n Expected behavior: The agent returns a response like 'Understood. Feel free to return anytime if you need help.'\n\n Actual behavior: Additional closure messages show up, and the last two messages are duplicated. For example, the agent might return the following: 'Understood. Feel free to return anytime if you need help. Thanks for chatting! I will go ahead and close this conversation now. I'm here if you need anything else. It looks like you're finished with this chat, so I will go ahead and close it. It looks like you're finished with this chat, so I will go ahead and close it.'.\n\n |
| \n\nVirtual Agent\n\n PRB2034975\n\n | \n\nInteractions are throwing an error of 'technical issues' intermittently\n\n | \n\nA few interactions intermittently throw 'I'm having technical issues and won't be able to continue this conversation'.\n\n | \n\n1. Ensure the following is installed:\n - Now Assist in Virtual Agent Plugin: 15.0.8\n - Now Assist in Virtual Agent Configurations: 8.0.8\n - Generative AI Controller: 12.1.2\n2. Open a Zurich instance.\n3. In Now Assist Virtual Agent \\(NAVA\\), initiate a conversation.\n4. Impersonate an agent who is made available to take interactions.\n5. Initiate a live agent configuration.\n\n Observe the message, 'I'm having technical issues and won't be able to continue this conversation' occurs intermittently.\n\n |
| \n\nVirtual Agent\n\n PRB2035888\n\n | \n\nA Guardian-triggered async\\_search early-return leaves a stale task ID in the context\n\n | \n\n \n\n | \n\n1. Send a prompt that Guardian flags and see that it's displayed correctly.\n2. See that the first request is still active but times out later.\n3. Send a second utterance that triggers skill Discovery immediately.\n4. Wait for a timeout from the first message to occur to display a 'sorry' message in the conversation.\n\n Expected behavior: The second utterance responds normally.\n\n Actual behavior: 'Sorry, there was a problem on my side' appears. The second utterance result is dropped.\n\n |
| \n\nVirtual Agent\n\n PRB2037636\n\n [KB3108272](https://hi.service-now.com/kb_view.do?sysparm_article=KB3108272)\n\n | \n\nAgent messages containing URLs aren't displaying correctly in the internal transcript\n\n | \n\n \n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nVirtual Agent\n\n PRB2054519\n\n | \n\nRename five assistant names from 'Now Assist' to 'Otto'\n\n | \n\nThe old assistant names should be renamed as following: 'Now Assist in Virtual Agent' > 'ServiceNow Otto for Virtual Agent', 'Now Assist Panel – Platform' > 'ServiceNow Otto panel – Platform', 'Now Assist Panel – Developer' > 'ServiceNow Otto panel – Developer', 'Now Assist Voice Deployment' > 'ServiceNow Otto voice', 'Now Assist in Virtual Agent - N' > 'New chat assistant - 1', and 'Now Assist Voice Development - N' > 'New voice assistant - N'.\n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB2055706\n\n | \n\nSnc\\_internal role is missing on sys\\_cs\\_conversation write ACL when the 'Explicit Roles' plugin is also active\n\n | \n\nSince the snc\\_internal role is never associated to the ACL, any users with snc\\_internal role can't upload files from NextWave conversation experience. The /api/now/upload/attachment API checks for write access on the actual record itself before allowing file upload, so the upload API is failing.\n\n | \n\n1. Provision a Zurich instance with the 'Explicit Roles' plugin \\(com.glide.explicit\\_roles\\) and the Conversation Server plugin \\(com.glide.cs\\) installed.\n2. Navigate to an ACL on sys\\_cs\\_conversation table with write operation on record.\n\n Observe that that only the snc\\_external role is added. The snc\\_internal role is never associated to this ACL.\n\n |
| \n\nVirtual Agent\n\n PRB2056495\n\n | \n\nCentral cache doesn't return the correct entry if the cache is updated from a different cluster\n\n | \n\nIn the central cache log, the following message apepars: 'Negative cache hit — Glide previously returned null for this key'.\n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB2057596\n\n | \n\nRename 'Now Assist Virtual Agent' to Otto for topics in Glide\n\n | \n\n \n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB2058728\n\n | \n\nChat summary isn't generated on instances with the Spanish translation plugin\n\n | \n\nAfter ending a chat between a requester and an agent, the summary doesn't generate. This occurs when one person is using Spanish and the other is using English.\n\n | \n\n1. Provision an instance with the Spanish translation plugin installed.\n2. Set Spanish as the language for the requester.\n3. Set English as the language for the agent.\n4. Make sure DT is enabled.\n5. As the requester, initiate a chat and connect with the agent.\n6. Exchange around 20 messages.\n7. As the requester, end the chat.\n\n Observe that the chat summary doesn't generate.\n\n |
| \n\nVirtual Agent\n\n PRB2059089\n\n | \n\nThe Otto session isn't aware of the logged-in user for 'assets managed by me' queries\n\n | \n\nThe Otto/AICT chat session isn't aware of the logged-in user by default. When a user asks a question like 'Can you give me the assets managed by me?', the assistant returns the complete/unfiltered list of assets instead of applying a managed\\_by = current user filter. The filter is only applied when the user explicitly names themselves in the query. The assistant should recognize 'me'/'my' references and automatically apply the logged-in session user's context without requiring explicit clarification.\n\n | \n\n1. Log in as an AICT user.\n2. Ask Otto: 'Can you give me the assets managed by me?'.\n\nObserve that the full/unfiltered asset list is returned instead of being filtered to the current user.\n\n3. Ask explicitly by name, for example: 'assets managed by <username>'.\n\n Observe that the managed\\_by = current user filter is correctly applied.\n\n |
| \n\nVirtual Agent\n\n PRB2059632\n\n | \n\nBuildPolicyConfig should be aligned with sys\\_now\\_assist \\_va\\_persona\\_detail schema\n\n | \n\nNo policy configs are returned because buildPolicyConfig doesn't target sys\\_now\\_assist\\_ va\\_persona\\_detail and doesn't filter by persona\\_detail\\_type = Policy.\n\n | \n\n1. Create an active record in sys\\_now\\_assist\\_va\\_persona\\_detail:\n - Deployment = a valid deployment sys\\_id.\n - Persona\\_detail\\_type = Policy.\n - Name = Test Policy.\n - Description = Test policy description.\n - Prompt\\_value = Test policy instruction.\n2. For the same deployment, create another active persona-detail record with persona\\_detail\\_type = Tone and prompt\\_value = Friendly.\n3. Trigger the assistant-config handshake for that deployment via next wave.\n4. Inspect policyConfigs in the response.\n\n Expected behavior: One policy config entry is returned, containing the sys\\_id, name, description, active, and instruction from the policy persona-detail record. Non-policy persona-detail records are excluded.\n\n Actual behavior: No policy configs are returned because buildPolicyConfig doesn't target sys\\_now\\_assist\\_va\\_persona\\_detail and doesn't filter by persona\\_detail\\_type = Policy.\n\n |
| \n\nVirtual Agent\n\n PRB2060897\n\n | \n\nThe 'promoted-skills' API doesn't return non-discoverable skills\n\n | \n\n \n\n | \n\n1. Create a skill.\n2. Call the 'promoted-skills' API.\n\n Expected behavior: The skill should be returned.\n\n Actual behavior: The skill isn't returned.\n\n |
| \n\nVirtual Agent\n\n PRB2061042\n\n | \n\nFixes are needed for guest user support for OffGlide\n\n | \n\nAdditional rest endpoints need a public role. The NextWave token needs to be turned on for bff exchange.\n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB2061520\n\n | \n\nCalling the 'Bg channel' API with the same session ID isn't resuming the conversation\n\n | \n\n \n\n | \n\n1. Create a incident and assign it to the ZTSD worker.\n2. Once solution is proposed, reply with new comments.\n\n Expected behavior: The conversation, which is waiting for input, should resume back.\n\n Actual behavior: Creating a conversation and execution plan with the workflow as 'Default VA Workflow'.\n\n |
| \n\nVirtual Agent\n\n PRB2063396\n\n | \n\nParallel tools execution aren't running in record domain\n\n | \n\n \n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB2064355\n\n | \n\nAuto Chat executions are faulted\n\n | \n\nThere is an intermittent failure in fetching the JWT token from CS, which is causing the faulted conversations.\n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB2064833\n\n | \n\nA domain is set to null after user input\n\n | \n\n \n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB2066077\n\n | \n\nAdd the reduce\\_items\\_list\\_polling toggle\n\n | \n\n \n\n | \n\n \n\n |
| \n\nVirtual Agent Web Client\n\n PRB1933088\n\n | \n\nProcessing loader is displayed even after getting a response\n\n | \n\n \n\n | \n\n1. Select **Now Assist Portal**.\n2. Enter 'Summarize a record/conversation'.\n3. Select the discovered skill.\n\n Observe that the loader is still displayed, even after getting the record number question.\n\n |
| \n\nVulnerability Response Integration with Microsoft Defender for IoT \\(Azure\\)\n\n PRB2031861\n\n | \n\ngetRefRecord\\(\\) scoping bypass for AzureVR\n\n | \n\n \n\n | \n\n \n\n |
| \n\nWindow Manager\n\n PRB2041392\n\n [KB3142333](https://hi.service-now.com/kb_view.do?sysparm_article=KB3142333)\n\n | \n\nThere's a UI bug when opening the Now Assist panel\n\n | \n\nWhen a user has a menu pinned \\(whether it's the All menu, Favorites, History, etc.\\) and they open the Now Assist panel, the pinned menu turns into a blank white pane. The menu that was pinned also then reappear in the list of other unpinned menus, although the name of the pinned menu still also appears next to the ServiceNow logo with a blank pane beneath it. The blank menu can generally be recovered by opening it from the list of unpinned menus \\(where it has reappeared\\) and re-pinning it , refreshing the page, or resizing the window. However, there is some inconsistency in whether refreshing or resizing the window always fixes it. If users refresh with the blank menu pinned and the Now Assist panel still open, the Now Assist panel then becomes blank and can only be dismissed/recovered by pinning something else, like sidebar discussions, to the right of the screen to get rid of it. This behavior happens most consistently when a user with a pinned menu logs in and opens the Now Assist panel for the first time after their start screen loads. However, it does also happen MID-session sporadically if users unpin/re-pin different menus and open/close the Now Assist panel frequently.\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nWindow Manager\n\n PRB2052078\n\n | \n\nResize doesn't work at run time, only on creation time\n\n | \n\nThe talk modal needs to be a fixed size. The user dragging it smaller breaks the layout, so the grip should be disabled at runtime.\n\n | \n\nTry \\{canResize: false\\}.\n\n Expected behavior: The gripper disappears.\n\n Actual behavior: There's no change.\n\n |
| \n\nWindow Manager\n\n PRB2052105\n\n | \n\nSetWindowProperties ignores empty headingLabel and it can't clear a window's title at runtime\n\n | \n\nThe previous title stays. '' and null are silent no-ops.\n\n | \n\n1. Open a window with a heading \\(for example, the canvas window with any headingLabel\\).\n2. Call setWindowProperties\\(windowId, \\{ headingLabel: '' \\}\\).\n\n Expected behavior: The heading clears, resulting in a blank title.\n\n Actual behavior: The previous title stays. '' and null are silent no-ops.\n\n |
| \n\nWork Order Management\n\n PRB2034992\n\n | \n\nBackport changes for getRefRecord\\(\\) changes\n\n | \n\n \n\n | \n\n \n\n |
| \n\nWork Order Management\n\n PRB2053534\n\n | \n\nThe 'Location update when PSO is populated' business rule isn't needed anymore\n\n | \n\nThe business rule sets and syncs the **Location** field on the work order from the provider organization, and the same location is applied to the work order task. This seems confusing, since the provider org and location don't necessarily have to be the same. The provider org refers to who is responsible for the work, while the location refers to where the work happens.\n\n | \n\n1. Create a work order.\n2. Update the provider organization.\n\n Expected behavior: The location remains unchanged.\n\n Actual behavior: The location changes to the provider organization location.\n\n |
| \n\nApp name\n\n | \n\nVersion number\n\n | \n\nRelease notes\n\n |
|---|---|---|
| \n\n@servicenow/sn-ai-engagement-experience\n\n | \n\n3.5.3\n\n | \n\nChanged\n\n Updated branding of Now Assist to ServiceNow Otto to align with the new branding guidelines.\n\n Fixed\n\n - Resolved Core IT installation override of agenticWorkflowsRoute property.\n- Updated the access control to ensure ITIL users do not have unintended access.\n- Fixed ServiceNow Otto panel in portal to render when web embeddables is enabled.\n\n |
| \n\n@servicenow/sn-enhanced-content-editor\n\n | \n\n31.25.0\n\n | \n\nOTTO Rebranding.\n\n |
| \n\nAccounts Payable Invoice Processing\n\n | \n\n13.1.6\n\n | \n\nA new Jurisdiction table included to capture tax jurisdiction, type, and authority information. Tax types are enhanced to capture and auto-populate tax jurisdiction details when users add tax lines to invoices.\n\n This release includes fixes for reported defects to improve product stability.\n\n - Fixed an issue that could cause auto-reject to fail during invoice exception processing.\n- Fixed an issue on invoice processing case where user is unable to update when requested by is empty.\n\n |
| \n\nAccounts Payable Operations integration with Document Intelligence\n\n | \n\n13.1.3\n\n | \n\nThis release includes fixes for reported defects to improve product stability.\n\n |
| \n\nAdmin Center\n\n | \n\n6.2.1\n\n | \n\nChanged\n\n Admin Home MVP redesign: Initial AIUX-based redesign and user experience refresh.\n\n |
| \n\nAdvanced Approval Management\n\n | \n\n2.4.0\n\n | \n\nNew\n\n Show amount of time that has passed since an approval action was taken by approval users/groups in the approval card.\n\n |
| \n\nAdvanced Approval Management AI\n\n | \n\n1.1.1\n\n | \n\nNew\n\n - Enable sales agents and approvers to add ad-hoc approvers from Claude Desktop.\n- Enable sales agents to recall approval requests from Claude Desktop.\n\n |
| \n\nAES Application Object Templates\n\n | \n\n29.2.6\n\n | \n\nApp is a dependency of App Engine Studio. Please see App Engine Studio for release notes.\n\n |
| \n\nAES Application Object Wizard Components\n\n | \n\n29.2.6\n\n | \n\nApp is a dependency of App Engine Studio. Please see App Engine Studio for release notes.\n\n |
| \n\nAgent Client Collector for Visibility Content\n\n | \n\n1.11.0\n\n | \n\nACC is now certified on below list of Operating Systems - Red Hat Enterprise Linux \\(RHEL\\) 10 - x86\\_64Rocky Linux 10 - x86\\_64Oracle Linux 10 - x86\\_64Ubuntu Linux - ARM64 \\(aarch64\\).\n\n Improved Oracle Java Discovery using process based detection - complementing the FBD solution for a more accurate solution.\n\n |
| \n\nAgent Client Collector Framework\n\n | \n\n6.6.3\n\n | \n\nFixes:\n\n 1. Clean up of .pem and .bin files in the upgrade directory during upgrades of the ACC RPM agent on Linux hosts.\n\n 2. Upgraded OpenSSL version to 3.4.6 and net-imap to 0.5.15 that will resolve the security vulnerabilities.\n\n 4. Fixed Windows instllation for acc version greater than 6.5.1 due to servicenow user creation error.\n\n |
| \n\nAgentic Contact Center for Banking\n\n | \n\n1.4.4\n\n | \n\nChanged\n\n - Updated internal application components to support ongoing platform enhancements.\n- Updated 'ServiceNow Otto' branding for Agentic Contact Center for Banking.\n\n |
| \n\nAgentic Contact Center for Insurance\n\n | \n\n1.3.2\n\n | \n\nChanged\n\n Updated 'ServiceNow Otto' branding for Agentic Contact Center for Insurance.\n\n |
| \n\nAgent Workspace for HR Case Management\n\n | \n\n4.6.2\n\n | \n\nCritical Functionality Fixes: Resolved critical issues preventing core case management workflows from functioning properly.\n\n - Fixed the 'Create HR Case' action bar button that was bypassing mandatory field validation on Interaction records, allowing incomplete cases to be created.\n- Restored the functionality of the Close Complete button that had been unresponsive, preventing agents from transitioning cases to the 'Awaiting Acceptance' or 'Closed Complete' states.\n- Re-enabled Approve and Reject buttons on approval sub-record forms that were missing in Agent Workspace.\n- Fixed drag-and-drop Transfer Case functionality in the Triaging Dashboard that was not responding to user actions.\n\n Form and amp; Field Handling: Improved form rendering and field behaviour to provide a smoother user experience.\n\n - Resolved intermittent read-only field issues on Move Attachments where the Topic Details and Document Type fields were locked despite selection, blocking attachment workflows.\n- Eliminated misleading validation error messages on the Transfer Case modal COE field that appeared even when the field was correctly auto-populated.\n- Corrected information message alignment in the Preview Document modal during document template generation.\n- Enhanced the case creation form to clarify why the Next button is disabled when the search field is empty and how Skip Verification relates to the primary form flow.\n\n Data Filtering and amp; Logic: Fixed how data is filtered and displayed across HR Agent Workspace lists.\n\n - Corrected HR Service filtering on the Case Creation page to consistently use the Subject Person field instead of following whichever field \\(Subject Person or Opened for\\) was changed last, ensuring eligible services always appear.\n- Resolved the Delegated HR Cases and Delegated HR Tasks lists that showed no records.\n\n Performance and amp; UI Optimization: Enhanced performance and resolved display issues to ensure smooth operation at scale.\n\n - Optimized attachment loading to eliminate page hangs and unresponsiveness when the system contains a large number of attachments in the Move Attachments feature.\n- Removed console errors that were being flooded when loading the Move Attachments page in UI Builder, improving debuggability and development experience.\n- Fixed file access permission handling for users with limited roles who received 'File Does Not Exist' errors when accessing Summary Report attachments, even though attachments were properly created.\n\n Localization and amp; Internationalization: Enhanced support for international users by fixing date format hardcoding in HR Agent Workspace. Date formats now properly respect locale settings and language plugins, ensuring correct date display for users with non-English language settings \\(e.g., Japanese date formats for Japanese language plugin users\\) and supporting localized deployments globally.\n\n |
| \n\nAI Admin Center\n\n | \n\n5.1.9\n\n | \n\nNew\n\n Generally available.\n\n New public API \\(script include\\) exposes automation-opportunity data globally.\n\n New Lit.JS user experience only \\(selected users\\).\n\n - AI readiness: Single hub for all activation-ready skills and AI agents; filter by type, metrics with change indicators, activate, expand for details, re-run assessment.\n- Monitor tab: Cross-repo analytics in a new sidebar entry \\(Overview, Performance Explorer, Business Value widgets\\).\n- System property registry: Browse/search/filter AI properties by domain and editability; view details; edit eligible single-value and boolean properties in-UI with audit logging \\(masked, multi-value excluded\\).\n- Upgrade readiness pre-check: AI-specific impact report vs target releases - at-risk customizations, changed behaviors, deprecated features, new config options, with remediation and exports.\n- AI Agent Advisor: Create/edit custom data sets, define cost profiles, new views for OOTB agents and clusters, including step pages.\n- AI Search integrated into the discover flow.\n- Self-healing AI agent skill support added to AI Agent Advisor.\n- Automation opportunity backend wired into shared AI Readiness and Asset Inventory components for ready-to-activate.\n\n Changed\n\n Generally available.\n\n Otto rebranding: all Now Assist Center references updated to AI Admin Center.\n\n Lit.JS only \\(selected users\\).\n\n - AI Optimization renamed to AI Readiness, with updated filters, components, and design across Health, Ready-to-Activate, Data Quality tabs.\n- Ready-to-Activate table refactored with snow-list.\n- Plan Upgrade adopts snow-list and August UI tweaks; category filter pills removed, sub-filter pills retained.\n- Customizations tab \\(Upgrade Pre-Check\\): Action-button nav to file details, more filters, breadcrumb mapping, better consistency.\n- Instance Health stream shows all inactive agents and OOTB skills ready to activate.\n- Data Quality tab adds an Estimated Effort column.\n- Localization standardized via aiux-services i18n.\n- Accessibility verified and fixed across all pages.\n- Typography tokens and rules established.\n- Snow-design-system components made Horizon 2.0-compliant on Home, Agent Advisor, Opportunity Detail.\n- Now Assist Admin refactored for Lit.JS/Horizon 2.0 - Model Mgmt/Versions, Experiences, Edit Model Providers, DT Languages.\n- Sidebar adopts latest karuna side-nav and top header \\(navigation, logout, impersonate, scope-picker\\).\n- 'New version available' indicator added to the AI Readiness page.\n- Agent Advisor resolution steps and modal updates for OOTB agents.\n- AI Agent Advisor settings/list pages show updated timestamps, cost-profile fields, cluster mapping.\n- AI Readiness Overview tab adds graph components for Health, Data Quality, Ready-to-Activate metrics.\n- System Property Registry supports cross-scope edits with scope-aware, role-accurate UI.\n- Upgrade Pre-Check supports async run orchestration and per-file review.\n\n Fixed\n\n Generally available.\n\n NAA KAA Auth dependency removed; Skills config now uses SkillConfig instead of the REST API.\n\n Lit.JS only \\(selected users\\).\n\n - UI/stability: Blank-page loads, broken AI Solution page, dark theme, missing nav loaders, Otto Panel images, 'Loading Now Assist...' hang.\n- Navigation: Failing menu/workspace redirection and a broken Home 'View All' control.\n- AI Readiness/Instance Health: disabled Re-Run Assessment button, missing AI Solution count, skill-activation and rapid-action-card display issues.\n- Agent Advisor/Agent-Miner/Automation Opportunity: Page-load latency, missing Activate button for inactive configs, savings-projection count error, minor list/resolution defects.\n- Asset Inventory: Asset details not displaying and skill-type asset-page rendering.\n- Localization: Translation gaps and 5.1 localization warnings across Lit and UI Builder.\n- Access/roles: Updated nac\\_user access on settings sub-pages; Agent-miner role scoping.\n\n Removed\n\n Generally available.\n\n Platform-app dependencies eliminated; platform apps now function independently.\n\n Lit.JS only \\(selected users\\).\n\n Pre-built automation workflows no longer accessible or visible.\n\n |
| \n\nAI Agent Advisor\n\n | \n\n1.3.2\n\n | \n\nNew\\* Recommend out-of-the-box agents alongside top problems - AI Agent Advisor now surfaces recommended ServiceNow AI Agents directly alongside discovered opportunities in the same view.\\* Pre-generate agents for recommendations in AI Agent Studio and AI Admin Center \\(formerly Now Assist Center\\) - Agents are pre-generated for matched recommendations, reducing time to creation from Agent Studio and AI Admin Center.\\* Surface AI Agent Advisor recommendations as insights in AI Control Tower - Automation opportunities discovered by AI Agent Advisor are now visible as insights within AI Control Tower.\\* Mining custom tables and fields - AI Agent Advisor can now analyze custom tables and fields, expanding opportunity discovery beyond standard incident and case data.Changed\\* Minor updates to UI - Removed the summary bar on list view, updated the list view columns and list view filtering.Fixed\\* No major defect fixes.\n\n Removed\\* Nothing major removed in this release.\n\n |
| \n\nAI Agents for AIOps\n\n | \n\n1.11.3\n\n | \n\n--- AI Generated Release Notes ---.\n\n New\n\n - Operator-reopened alerts get full AI investigation automatically. When a human operator reopens an alert that the AI previously closed as noise, the system bypasses noise classification for the rest of that alert's lifecycle and runs a complete investigation - ensuring human overrides are respected and learned from.\n- ServiceNow Otto for ITOM branding is now applied. The Now Assist for ITOM app has been renamed to ServiceNow Otto for ITOM throughout the application.\n\n Changed\n\n - AI Specialist alert reassignment behavior has been enhanced. When the AI Specialist completes investigation or remediation on an alert originally assigned to a human operator, the alert is automatically reassigned back to the original owner, unless the alert was closed as noise or manually reassigned during AI processing. Audit trails and work notes reflect the reassignment, and configuration options allow admins to enable or disable this behavior.\n- Automatic triggering of AI Specialist on assigned alerts is now configurable. By default, the AI Specialist does not take over alerts already assigned to a human operator. This condition can be edited by admins if needed.\n- Manual triggering of AI Specialist now preserves alert ownership. When the AI Specialist is manually triggered on an alert assigned to a human operator, the alert is reassigned back to the operator at the end of execution. Feature flags control whether noisy alerts or previously assigned alerts are reassigned.\n- Alert closure by AI now records closure reason for downstream processing. When the AI auto-closes an alert, a durable marker is recorded indicating the closure was AI-driven, enabling correct handling on future reopen events.\n- Operator override flag and additional alert lifecycle data are now stored durably. A new JSON field on the AI session record captures operator overrides and other lifecycle facts, supporting robust reopen and investigation workflows.\n\n Fixed\n\n The Alert Investigation 'Related Changes' flow no longer causes excessive memory usage or out-of-memory errors that could lead to node restarts. The system now handles related changes efficiently during alert investigation.\n\n |
| \n\nAI Agents for Core Business Suite\n\n | \n\n3.3.2\n\n | \n\nUpdated to support the latest version of the dependent apps.\n\n |
| \n\nAI Agents for CSM - Complaint Case\n\n | \n\n1.5.1\n\n | \n\nApp renamed to Complaint Case AI Agent Collection.\n\n |
| \n\nAI Agents for Customer Success Management\n\n | \n\n2.7.12\n\n | \n\nMeeting related fixes.\n\n |
| \n\nAI Agents for Employee Experience\n\n | \n\n2.3.4\n\n | \n\nUpdated to support the latest version of the dependent apps.\n\n |
| \n\nAI Agents for Health Log Analytics\n\n | \n\n1.1.1\n\n | \n\nChanged\n\n Internal naming conventions.\n\n |
| \n\nAI Agents for HR Service Delivery\n\n | \n\n7.2.1\n\n | \n\n--- AI Generated Release Notes ---.\n\n New\n\n - AI Specialist now communicates ticket reassignment to users. When a ticket is reassigned from the AI Specialist to a human HR Agent, users receive a clear notification outlining next steps and expectations.\n- MCP server repository established for multi-tool development. The MCP server repository is now structured to support parallel tool development, with a baseline Hello World implementation and initial CI pipeline in place.\n\n Changed\n\n - AI workers migrated to DARE architecture. AI workers now operate on the DARE architecture, with all previous off-glide workflows tested to ensure uninterrupted functionality.\n- ZTSD L1 worker template compared and validated against OOB HR L1 worker template. All new, changed, or removed properties introduced by the ZTSD platform team have been identified and tested for correctness. Documentation of differences is complete.\n\n Fixed\n\n Removed\n\n HR Policy and HR Benefits removed from profile capabilities. Profile capabilities no longer display HR Policy and HR Benefits, leaving only relevant HR options for editing.\n\n |
| \n\nAI Agents for ITAM\n\n | \n\n4.7.0\n\n | \n\nHardware Asset Workspace and Software Asset Workspace now feature ServiceNow Otto, replacing all previous references to Now Assist.\n\n |
| \n\nAI Agents for Meetings\n\n | \n\n1.0.6\n\n | \n\nThis release introduces AI Agents for Meetings \\(sn\\_meeting\\_ai\\_ag\\), a new standalone plugin that delivers AI-driven meeting creation. The AI Agent monitors risk records and proposes complete meeting drafts automatically, with additional entry points available via a 'Create Meeting' action on Engagement and Touchpoint forms and through the Now Assist conversational panel.\n\n |
| \n\nAI Agents for Retail Service Management\n\n | \n\n1.5.1\n\n | \n\nChanged the plugin name \\(AI Agents for Retail Service Management\\).\n\n |
| \n\nAI agents for SLO\n\n | \n\n2.1.2\n\n | \n\nAll customer-facing references to 'Now Assist' have been updated to 'ServiceNow Otto' throughout the interface, documentation, and support materials. The product functionality remains the same, but you will see the ServiceNow Otto name and branding everywhere you interact with your AI agent.\n\n |
| \n\nAI Agents for Talent\n\n | \n\n6.0.0\n\n | \n\nNow Assist introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n |
| \n\nAI Agents for Telecommunications, Media and Technology\n\n | \n\n6.1.2\n\n | \n\nOtto Rebranding Changes.\n\n |
| \n\nAI Agents for Universal Request\n\n | \n\n1.1.2\n\n | \n\n- Changed: Renamed the app to 'AI Agents for Universal Request' as per Otto rebranding.\n- Fixed: When the UR Agentic workflow kicks in and creates a HR case, Case is getting created but the HR Service field is empty and not getting populated.\n\n |
| \n\nAI Agents for Workplace Service Delivery\n\n | \n\n3.3.8\n\n | \n\nNew\n\n Changed\n\n ServiceNow Otto is the new AI experience brand. This change is reflected in the name of ServiceNow products. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features.\n\n Fixed\n\n Removed\n\n |
| \n\nAI Analytics\n\n | \n\n5.2.5\n\n | \n\nNew\n\n - Granular analytics for AI asset evaluations and performance - Users can now access detailed evaluation KPIs for deployed AI assets, including manual and automated evaluations, asset consumption metrics, and trendlines with benchmarks. The analytics dashboard supports custom date range filters and provides granular feedback indicators for conversation interactions, negative feedback reasons, and free-text comment usage.\n- Auto Evaluation dashboard with KPI cards and asset type filtering - The Auto Eval dashboard now displays KPI cards for asset health, evaluation status, and monthly assists, with filtering by asset type \\(agent, skill, assistant\\).\n- Detailed asset evaluation pages and asset lists - Users can view individual asset evaluation details, including latest scores, evaluation run history, and benchmark trendlines. Asset lists are available for auto evaluation, supporting drill-down and comparison.\n- Performance Explorer Skills tab with skill detail panel - The Performance Explorer now includes a Skills tab showing skill usage, feedback quality, unique users, and allows drill-down to detailed metrics for each skill, including Guardian safety indicators.\n- Custom date range filter for analytics dashboards - Users can select custom start and end dates for dashboard data, with selections persisting during sessions.\n\n Changed\n\n Now Assist rebranding - All analytics screens, dashboard titles, and icons have been updated to reflect ServiceNow Otto for interactive surfaces and AI for background metrics.\n\n |
| \n\nAI Authoring for Catalog Builder\n\n | \n\n7.4.1\n\n | \n\nRebranding: The 'Now Assist' branding in conversational Catalog Builder has been replaced with 'ServiceNow Otto', backed by new automated test coverage.\n\n |
| \n\nAI Control Tower Core\n\n | \n\n8.0.8\n\n | \n\nDiscovery & Inventory\n\n New\n\n Multi-tenant credential support for hyperscaler connectors.\n\n Changed\n\n - Enhanced asset enrichment with cloud-native metadata and AI system relationship mapping.\n- Relationship mapping with Business applications \\(requires EA entitlement\\).\n- Simplified asset states and status which replaces lifecycle phase and lifecycle status in asset record view.\n\n Removed\n\n Legacy single-tenant discovery connectors.\n\n |
| \n\nAI Control Tower for ServiceNow Otto\n\n | \n\n6.0.4\n\n | \n\nAuto-installed app for all ServiceNow AI products.\n\n |
| \n\nAI Dashboard Insights\n\n | \n\n1.3.4\n\n | \n\nNew\n\n - Personalized dashboard summary output.\n- Improved summary for multi-page lists.\n- Configurable default active skills in AI Admin Hub.\n- Support for updated third-party models.\n\n Changed\n\n Renamed Otto context menu labels.\n\n |
| \n\nAI Data Explorer\n\n | \n\n5.2.6\n\n | \n\nChanged\n\n - UI improvements for data source view information.\n- Otto rebranding for AI Data Explorer experience.\n- AI Data Explorer skills made compatible with Default activation of Out-of-box skills in Now Assist Admin Console.\n\n |
| \n\nAI Data Kit\n\n | \n\n8.2.4\n\n | \n\n- Added validations to ensure Dataset and Data Collection names are unique.\n- All in-product UI strings, labels, tooltips, banners, and documentation that mention 'Now Assist' were retranslated and repackaged in line with the Otto naming guidelines.\n- Discovery Experience - DataKit Admins and analysts can search for datasets by either name or description.\n\n |
| \n\nAI Desktop Actions\n\n | \n\n5.0.3\n\n | \n\nChanged\n\n Updated the AI experience branding in AI Desktop Actions to align with ServiceNow Otto naming and visual guidelines.\n\n |
| \n\nAI Desktop Actions Core\n\n | \n\n5.0.3\n\n | \n\nChanged\n\n Updated the AI experience branding in AI Desktop Actions to align with ServiceNow Otto naming and visual guidelines.\n\n |
| \n\nAI Enhanced Recommended Actions\n\n | \n\n1.0.5\n\n | \n\nNew\n\n Updated to support the ServiceNow Otto brand.\n\n |
| \n\nAI Experience Framework\n\n | \n\n1.0.12\n\n | \n\nThis app contains the core AIUX framework that powers the next generation of AI Native Experiences by providing a unified platform for designing, deploying, and managing intelligent user interfaces. This store app specifically contains the key metadata tables for managing key entities such as pages, widgets, experiences, and page routes, which power the new experiences. The plugin ensures that customers can leverage AI native experiences such as Employeeworks, build new experiences, and develop custom widgets, all while maintaining compliance with industry standards and scalability requirements.\n\n Key Note: This is a free plugin and does not have any AI licensing requirements.\n\n |
| \n\nAI Experience Framework Skills\n\n | \n\n1.3.2\n\n | \n\n- Introduce support for creating widgets in the new format, ensuring compatibility with the pro-code developer experience.\n\n |
| \n\nAI for document designer\n\n | \n\n22.5.1\n\n | \n\nNew\n\n AI-powered Word content generation now supports advanced third-party models. Users can generate and manage Microsoft Word report content using new AI models, including Gemini 3.5 Flash \\(with fallback to 2.5 Pro\\), GPT-5.4-mini, and Claude 4.5 Haiku, improving content accuracy and performance.\n\n Changed\n\n ServiceNow Otto Branding Updates: Updated the application to reflect the new ServiceNow Otto branding, replacing Now Assist references and providing a more consistent AI experience across the platform.\n\n |
| \n\nAIOps Agentic Workforce\n\n | \n\n2.2.3\n\n | \n\nChanged\n\n - The autonomous workflow now supports AWS Claude as an AI agent provider, improving compatibility with additional AI services.\n- The alert investigation insight prompt now accepts longer input, allowing for more detailed queries.\n- The Impact Agent search has been improved to return more relevant related issues.\n\n |
| \n\nAIOps Dashboards\n\n | \n\n26.5.2\n\n | \n\nNew\n\n - AIOps 360 view dashboard now quantifies AI-driven operational value. The dashboard introduces a widget that displays the time saved by AI, counting the alerts AI closed as insignificant or analyzed and provided insights or next-step recommendations, contributing to time savings \\(Note that Admins can adjust the time-saving definitions for this calculation\\).\n- Adding a new resolution type for alerts closed as insignificant, 'Closed by AI'. This info is added to the AIops 360 view dashboard heatmap chart for improved visibility of AI-driven outcomes.\n\n |
| \n\nAIOps Experience\n\n | \n\n27.2.17\n\n | \n\nNew\n\n - AI value is now visible on the AIOps 360 dashboard. A new widget shows estimated time saved based on how many alerts were resolved and analyzed by AI, giving operations teams a real-time view of AI's impact on their workload.\n- Express lists now support color-coded visual cues to highlight values \\(based on existing definitions in sys\\_highlighted\\_value\\). Admins can configure conditional formatting rules on alert columns \\(e.g., severity, priority\\) so that critical items are immediately visible through colored indicators and icons - no more scanning through uniform rows.\n\n Azure Monitor Issues now surface related alerts in context. A new 'Related Records' tab appears directly in the alert view for Azure Monitor Issues, letting operators drill into associated alerts without leaving their current workflow.\n\n Azure Monitor Issues are now bi-directionally synchronized with ServiceNow. The integration supports real-time ingestion of Azure Monitor Issues via webhook and polling, with two-way synchronization of status, severity, title, description, and AI-generated insights. OAuth 2.0 and multi-tenant Azure environments are supported.\n\n - Incident fields in response automations now support free text and static values. When creating incidents through automated alert responses, teams can now enter static text or map custom values to incident fields - restoring flexibility that was previously limited.\n- Integration setup instructions are now inline and on-page. Connector setup pages now include a collapsible instructions section covering source system configuration and credentials, eliminating the need to navigate away for documentation.\n\n Dynatrace Grail problem events are now fully supported. The new connector ingests Dynatrace Grail problem events and automatically binds alerts to the correct configuration item using root cause entity or CMDB tags. Davis AI context, severity mapping, and full event lifecycle \\(updates, reopens, merges\\) are supported - including predictive, RUM, synthetic, vulnerability, and business process anomaly events.\n\n Dynatrace Gen3 event payloads are now supported in the event push connector, alongside legacy formats - no migration required.\n\n - Admins can now limit the volume of related alerts retrieved per connector, giving control over data load in high-volume environments.\n- Alert Automation - Multiline text support in compose actions - On the Enrich page's compose action, the text field now supports multiple lines - the box resizes and preserves line breaks and spacing instead of collapsing everything into a single line. This fixes formatted alert descriptions rendering incorrectly downstream.\n- Alert Automation - Static values for incident fields in response automations - In the 'Create Incident Advanced' response automation action, users can now enter static text values for fields like urgency and priority \\(in addition to alert-field references\\) .\n\n Changed\n\n - Express List now fully supports right-to-left languages, including Arabic and Hebrew, with correct mirroring of layout, icons, and spacing.\n- All 'Now Assist' references across Service Operations Workspace, Express List, Integration Launchpad, and the AIOps AI Specialist onboarding have been rebranded to ServiceNow Otto.\n- The Probable Cause tab in the Alerts Preview panel is now called 'Related Records' and includes Azure Monitor Issues.\n- The Dynatrace Gen3 payload processor now handles both workflow-wrapped and raw Davis Gen3 payloads consistently, with improved severity mapping and entity tag preservation.\n\n Fixed\n\n - Alert automation no longer hangs when the interface language is set to Portuguese.\n- The AIOps Supervisor Homepage remains responsive when managing a large number of teammates.\n- Express List no longer fails to load when a system property record has a missing type value.\n\n |
| \n\nAI Platform skills\n\n | \n\n3.1.4\n\n | \n\nChanges made as part of Otto rebranding.\n\n Plugin name changes and source display updates.\n\n |
| \n\nAI Security and Privacy\n\n | \n\n6.0.10\n\n | \n\nThis is a major release of the AI Control Tower Security pillar, delivering the following capabilities.\n\n New\n\n - AI agent containment with kill switch protocol \\(phase 1\\): Revoke AI agent session tokens through Okta, deactivate and reinstate AI agents running in AWS Bedrock, AWS Bedrock AgentCore, GCP Vertex AI \\(limited support\\), and ServiceNow agents.\n- Extended agent map schema: On the map, you can see nodes for LLMs and MCP servers for complete resource visibility across your enterprise. Previously, the map only showed agentic workflows, AI agents, tools, and providers.\n- System prompt leakage, threat monitoring, and sensitive data disclosure post-runtime metrics are now configured and active by default. Previously, you had to enable them manually.\n\n Changed\n\n - Veza access intelligence usability: Improved messaging in Access Intelligence tab of AI assets in agent map.\n- Overview and Runtime metric quality: Improved accuracy of AI threat metrics and evaluation datasets that use Traceloop for continuous monitoring.\n- Now Assist was renamed to ServiceNow Otto.\n\n Removed\n\n - Number of clients connecting to MCP servers metrics in Overview metrics.\n- Ability to create security incidents from dormant agents using conversational prompts.\n\n |
| \n\nAI Skill Kit\n\n | \n\n9.2.4\n\n | \n\n- Now Assist Skill Kit is now renamed to AI Skill Kit.\n- The default model provider for skills is now Azure \\(from NowLLM\\). Newly created skills will use Azure as the default provider unless explicitly changed.\n\n |
| \n\nAI slot-filling for catalog items\n\n | \n\n1.4.5\n\n | \n\nNew: Minor enhancements.\n\n Fixed: Minor defects.\n\n |
| \n\nAI Troubleshooting\n\n | \n\n4.1.4\n\n | \n\n- Troubleshoot setup issues for Now Assist in Virtual Agent, AI Search, and Now Assist skills in the Now Assist Admin console.\n- Set up proactive error monitoring to automate checks for execution errors and alert when acceptable threshold is crossed.\n- View actionable list of identified underlying issues for quick problem resolution.\n\n |
| \n\nAlert Assist\n\n | \n\n3.11.3\n\n | \n\nChanged\n\n All 'Now Assist' references across the application have been updated to ServiceNow Otto.\n\n |
| \n\nAlert Rules Management\n\n | \n\n18.16.1\n\n | \n\n--- AI Generated Release Notes ---.\n\n Changed\n\n All references to 'Now Assist' have been updated to 'ServiceNow Otto' across IT Operations Management \\(ITOM\\) features. UI labels, flow descriptions, action descriptions, and rule labels now consistently use the 'ServiceNow Otto' name, replacing the previous 'Now Assist' terminology.\n\n |
| \n\nAmazon Bedrock Spoke\n\n | \n\n1.5.1\n\n | \n\nFixed an issue in Amazon Bedrock Spoke OEM actions where additional headers were not being sent correctly.\n\n Fixed an issue in Amazon Bedrock Spoke where the Generative AI Controller streaming done-chunk double-encoded non-ASCII model output \\(em dash, curly quotes, accents\\) as ISO-8859-1, causing garbled thinking and tool\\_use inputs due to VAStreamConsumer not enforcing UTF-8.\n\n |
| \n\nAPO - Foundation\n\n | \n\n1.3.3\n\n | \n\nThe application captures dependencies, updated the plugin dependencies for this release.\n\n |
| \n\nAPO - Prime\n\n | \n\n1.3.3\n\n | \n\nThe application captures dependencies, updated the plugin dependencies for this release.\n\n |
| \n\nApp Engine Notifications\n\n | \n\n29.2.6\n\n | \n\nApp is a dependency of App Engine Studio. Please see App Engine Studio for release notes.\n\n |
| \n\nApp Engine - Prime\n\n | \n\n29.1.8\n\n | \n\nChanged\n\n Updated to support the ServiceNow Otto brand.\n\n |
| \n\nApp Life Cycle AI Agents\n\n | \n\n29.5.2\n\n | \n\nChanged\n\n Updated to support the ServiceNow Otto brand.\n\n |
| \n\nApp Studio Commons\n\n | \n\n29.2.8\n\n | \n\nMaintenance release.\n\n |
| \n\nAsset Management Common\n\n | \n\n15.1.4\n\n | \n\nRelated-list visibility is restored in Hardware Asset Management, Agentic Process sidebar availability is improved, and security hardening strengthens access-control enforcement across asset management workflows.\n\n - Stockroom-related lists are now visible in Hardware Asset Workspace.\n- The Agentic Process sidebar availability has been improved.\n- Security enhancements strengthen access-control enforcement within asset management workflows.\n\n |
| \n\nAutomation Center\n\n | \n\n15.1.1\n\n | \n\nSn\\_ac.auto\\_onboarding\\_catalog\\_items - Use this system property to control how catalog items are onboarded as automations. Users with the sn\\_ac.automation\\_admin role can edit the system property.\n\n - True \\(default\\): New catalog items are onboarded automatically and appear on the automation dashboard immediately, without time and cost savings for each catalog item.\n- False: New catalog items are onboarded manually. Generating this data takes longer, but the dashboard shows an expanded summary with time and cost savings for each catalog item.\n\n |
| \n\nBuild Agent \\(Trial\\)\n\n | \n\n2.5.8\n\n | \n\nNew\n\n - New Build Agent model integrations, including GPT-5.5, Gemini 3.5 Flash, and Opus 4.8.\n- Ability to select model versions directly from the Build Agent chat panel within ServiceNow Studio.\n- Ability to create new custom skills and rules at instance-wide, application, and user levels to tailor Build Agent's behavior.\n- Run background scripts securely within app-build flows, with rollback, scope-restriction, and dry-run containment paths.\n- Ability to handoff ServiceNow Otto conversations to Build Agent in ServiceNow Studio.\n- Ability to run Build Agent in Developer Sandboxes, allowing for better collaboration and isolation.\n- Automatically keep all the ATF tests in sync as your Build Agent written code evolves over time, toggled on via the 'Sync ATF tests with app' setting for Build Agent.\n- Automatically keep all the UI tests in sync as your Build Agent written code evolves over time, toggled via the 'Run UI ATF Tests' setting for Build Agent.\n- Get prompted to generate ATF tests anytime you invoke Build Agent, enabled via Build Agent settings.\n- Execute and troubleshoot ATF tests directly from the ServiceNow SDK.\n- Support for new knowledge base access metadata type.\n- More granular overview of tools per connected MCP server in Build Agent settings.\n- Expanded MCP Server support, including AWS DevOps, Box, Postman, and Sentry.\n\n Fixed\n\n - Context compaction enhancements.\n- Sub Agent memory improvements.\n\n |
| \n\nBuild Agent Premium\n\n | \n\n1.5.5\n\n | \n\nNew\n\n - New Build Agent model integrations, including GPT-5.5, Gemini 3.5 Flash, and Opus 4.8.\n- Ability to select model versions directly from the Build Agent chat panel within ServiceNow Studio.\n- Ability to create new custom skills and rules at instance-wide, application, and user levels to tailor Build Agent's behavior.\n- Run background scripts securely within app-build flows, with rollback, scope-restriction, and dry-run containment paths.\n- Ability to handoff ServiceNow Otto conversations to Build Agent in Studio.\n- Ability to run Build Agent in Developer Sandboxes, allowing for better collaboration and isolation.\n- Automatically keep all the ATF tests in sync as your Build Agent written code evolves over time, toggled via the 'Sync ATF tests with app' setting for Build Agent.\n- Automatically keep all the UI tests in sync as your Build Agent written code evolves over time, toggled via the 'Run UI ATF Tests' setting for Build Agent.\n- Get prompted to generate ATF tests anytime you invoke Build Agent, enabled via Build Agent settings.\n- Execute and troubleshoot ATF tests directly from the ServiceNow SDK.\n- Support for new knowledge base access metadata type.\n- More granular overview of tools per connected MCP server in Build Agent settings.\n- Expanded MCP Server support, including AWS DevOps, Box, Postman, and Sentry.\n\n Fixed\n\n - Context compaction enhancements.\n- Sub Agent memory improvements.\n\n |
| \n\nCareer Conversations\n\n | \n\n3.11.2\n\n | \n\nNow Assist introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.Growth Conversation Preparation AI agent has been updated to follow the Otto guidelines.\n\n |
| \n\nCare Team Operations AI agent collection\n\n | \n\n2.0.4\n\n | \n\nFixed\n\n Dependency and branding fixes.\n\n |
| \n\nCatalog Conversational Coverage\n\n | \n\n6.1.4\n\n | \n\nNew\n\n Minor enhancements.\n\n |
| \n\nCertificate Inventory and Management\n\n | \n\n4.3.0\n\n | \n\nFixed: Refined the access control list \\(ACL\\) role permissions required to access certificate inventory and management records.\n\n |
| \n\nChange Management for Service Operations Workspace\n\n | \n\n9.3.2\n\n | \n\nUpdated plugin dependencies to ensure compatibility with the ServiceNow latest release.\n\n |
| \n\nChat Summarization for Virtual Agent\n\n | \n\n1.12.1\n\n | \n\nChanges related to Otto Rebranding Directive.\n\n |
| \n\nClone Admin Console\n\n | \n\n2.3.0\n\n | \n\n- Enhanced authentication: Clone Admin Console now uses OAuth-based authentication. When you place your next clone, a guided experience automatically prompts you to set up the new mechanism between your instances.\n- Cleanup Script status: You can now view the status of your cleanup scripts. With Multi-Instance View enabled, the status appears on the clone status page of the source instance.\n\n Clone Request page: The page now warns you if a clone profile overrides the target instance selection.\n\n |
| \n\nCMDB Workspace\n\n | \n\n9.3.0\n\n | \n\nNew\n\n - Welcome to ServiceNow Otto, the new name for Now Assist!.\n- Support for 400% zoom in web browsers.\n\n Changed\n\n Show dependency maps in Unified Map for specific Service Instance CI classes, instead of using service maps.\n\n Fixed\n\n - Various CMDB Data Manager performance and quality issues.\n- Various Data Certification quality issues.\n- CMDB Workspace and CI Form quality issues.\n- Various internationalization issues.\n\n |
| \n\nCollaborative Work Management\n\n | \n\n10.2.3\n\n | \n\nNew\n\n SPM's Project Workspace now has an integration with Collaborative Work Management\n\n - Team Members can create new CWM tasks/stories under an assigned project task.\n- Users can move or break a CWM task's connection to a different project task.\n- Project Managers will see CWM tasks/stories connected to their project tasks directly inline in the Planning page of the Project in Project Workspace.\n- Team Members in CWM see their connected project and project tasks as columns in CWM list view, and in 'My Work'.\n\n Changed\n\n Relationships for any task types can added now using Task number/id instead of just Task description.\n\n |
| \n\nCollaborative Work Management - Advanced\n\n | \n\n2.0.9\n\n | \n\nNew\n\n SPM's Project Workspace now has an integration with Collaborative Work Management\n\n - Team Members can create new CWM tasks/stories under an assigned project task.\n- Users can move or break a CWM task's connection to a different project task.\n- Project Managers will see CWM tasks/stories connected to their project tasks directly inline in the Planning page of the Project in Project Workspace.\n- Team Members in CWM see their connected project and project tasks as columns in CWM list view, and in 'My Work'.\n\n Changed\n\n - Relationships for any task types can added now using Task number/id instead of just Task description.\n- Now Assist is now ServiceNow Otto.\n\n |
| \n\nCommon AI Framework\n\n | \n\n2.0.2\n\n | \n\nEnhancements to support the ServiceNow Otto brand.\n\n |
| \n\nCommon Service Delivery\n\n | \n\n14.1.2\n\n | \n\nNew\n\n Added indexed finance case data as a search source for Finance Knowledge article generation in Knowledge Center.\n\n |
| \n\nConfiguration Hub\n\n | \n\n1.0.11\n\n | \n\n- Internal Code Fixes.\n\n |
| \n\nContent Pack for CMDB\n\n | \n\n2.1.1\n\n | \n\nFixed\n\n - Allow specific CI Classes to be excluded from Service Graph Connector recommendations. For example cmdb\\_ci\\_ot to be excluded for Hardware Asset Management use cases.\n- Updated logic to retrieve Service Graph Connector recommendations only if mappings exist to the specific CI Class, not to its base classes.\n\n |
| \n\nContent Publishing\n\n | \n\n37.3.3\n\n | \n\nUpdated to support the latest version of the dependent apps.\n\n |
| \n\nContract Management Pro - Prime\n\n | \n\n1.0.16\n\n | \n\nNew\n\n Conversational search results can be exported in multiple file formats.\n\n Changed\n\n ServiceNow Otto is the new AI experience brand. Now Assist in Contract Management is now ServiceNow Otto for Contract Management Pro.\n\n Fixed\n\n Contract fulfillers can trigger AI review for contracts stored in external storage.\n\n |
| \n\nConversational Catalog Requests\n\n | \n\n7.2.4\n\n | \n\nNew: Minor enhancements.\n\n Fixed: Minor defects.\n\n |
| \n\nConversational Studio\n\n | \n\n11.0.4\n\n | \n\nNew\n\n - Bulk migration of Topics to AI Agents is now supported. Admins can select and migrate batches of 100+ Topics to AI Agents at once using the Topics-to-AI Agents tool.\n- Auto Evaluation integration for migrated AI Agents. The Topics-to-AI Agents tool now integrates with Auto Evaluation, allowing users to review the quality of migrated AI Agents.\n- Dataset creation and evaluation for migrated Topics. Users can create datasets and run automated evaluations comparing migrated Topics and AI Agents, with comparison metrics displayed upon completion.\n- NLU deprecation banner in Asset Library. A legal-approved banner now displays in the Assistant Designer Asset Library when NLU assets are present or the NLU/Keyword filter is active. The banner includes a 'Learn More' link to deprecation documentation and is dismissible per user session.\n- Assignment of active Assets to inactive Assistants. Users can assign active Assets-including Topics, Subflows, Actions, AI Agents, Agentic Workflows, and Custom Skills-to inactive Assistants via Asset and gt; Conversational Settings, with clear differentiation between active and inactive Assistants in the UI.\n\n Changed\n\n - Test assistant button availability. The 'Test assistant' button in Assistant Designer is now disabled when the Voice assistant is not active or prerequisites are incomplete.\n- Asset pages and Asset Library updates. The Asset pages and Asset Library have been updated to reflect new design standards and improved usability.\n\n Fixed\n\n Migrated Topics now correctly display their migration status. The system accurately discerns the 'isMigrated' state for NLU topics, resolving previous inconsistencies.\n\n |
| \n\nConversational subflows and actions\n\n | \n\n30.0.4\n\n | \n\nChanged\n\n - Discontinued Now LLM to use third-party model for CSA Skills.\n- Renamed Now Assistant to ServiceNow Otto in CSA Side Panel.\n- Created the required Query\\_range ACLs as per Cobalt raven directive.\n\n |
| \n\nConversation Evaluator\n\n | \n\n3.1.3\n\n | \n\nAs part of our evolving model strategy, the default model for all skills is being migrated from NowLLM to a 3rd-party \\(3P\\) model. This change aligns with our ongoing efforts to enhance model capabilities, performance, and scalability across the platform.\n\n What's changing?.\n\n - The default model for all skills will transition from NowLLM to a 3P model.\n- Existing skills that rely on the default model will automatically use the new default unless explicitly configured otherwise.\n\n |
| \n\nCore Business Suite\n\n | \n\n3.3.2\n\n | \n\n- Shipped out-of-the-box knowledge bases defined at two levels: individual business unit knowledge bases \\(Human Resources, Legal, Source to Pay, Workplace Services, and Health and amp; Safety\\) and a CBS aggregate knowledge base.\n- Owners and managers can be defined by the admin in the Knowledge module for each knowledge base to ensure proper governance and content tracking.\n- Shipped new AI skills module under the Platform module on Configuration console enables admins to activate knowledge-specific skills from simplified setup.\n- Improve article optimization in terms of content quality, identification, and merging of duplicate articles to eliminate redundant content.\n- Shipped Now Assist search sources for all the business unit for Knowledge article generation from case tables on the Knowledge center.\n- Create contextually relevant articles from case tables and drive better AI-assisted content creation by enabling Knowledge Content Recommendation skill from AI skills module.\n\n Admins can now manage access to the Core Business Suite analytics dashboard through the new Groups module under Core Business Suite module. Define which users have view and edit access by adding them to groups, providing fine-grained control over who can access reporting and metrics across your Core Business Suite implementation.\n\n |
| \n\nCore Business Suite Advanced\n\n | \n\n3.3.2\n\n | \n\nUpdated to support the latest version of the dependent apps.\n\n |
| \n\nCore Business Suite Advanced for Finance\n\n | \n\n3.3.2\n\n | \n\nUpdated to support the latest version of the dependent apps.\n\n |
| \n\nCore Business Suite Advanced for Health and Safety\n\n | \n\n3.3.2\n\n | \n\nUpdated to support the latest version of the dependent apps.\n\n |
| \n\nCore Business Suite Advanced for Human Resources\n\n | \n\n3.3.2\n\n | \n\nUpdated to support the latest version of the dependent apps.\n\n |
| \n\nCore Business Suite Advanced for Legal\n\n | \n\n3.3.2\n\n | \n\nUpdated to support the latest version of the dependent apps.\n\n |
| \n\nCore Business Suite Advanced for Source to Pay\n\n | \n\n3.3.2\n\n | \n\nUpdated to support the latest version of the dependent apps.\n\n |
| \n\nCore Business Suite Advanced for Workplace Services\n\n | \n\n3.3.3\n\n | \n\nUpdated to support the latest version of the dependent apps.\n\n |
| \n\nCore Business Suite Analytics\n\n | \n\n3.3.1\n\n | \n\n- Introduced Goups under the Core Business Suite module in the Configuration Console.\n- Admins can now manage access to the Core Business Suite analytics dashboard through the new Groups module under Core Business Suite module.\n- Define which users have view and edit access by adding them to the groups, providing granular control over who can access reporting and metrics across your Core Business Suite implementation.\n\n |
| \n\nCore Business Suite for Finance\n\n | \n\n3.3.2\n\n | \n\nShipped Now Assist search sources for Finance for Knowledge article generation from finance case table on Knowledge center.\n\n Create contextually relevant articles from case tables and drive better AI-assisted content creation by enabling Knowledge Content Recommendation skill from AI skills module.\n\n |
| \n\nCore Business Suite for Health and Safety\n\n | \n\n3.3.2\n\n | \n\n- Shipped out-of-the-box Safety knowledge base.\n- Owners and managers can be defined by the admin for the knowledge base in the Core Business Suite configuration console to ensure proper governance and content tracking.\n- Shipped user criteria for Health and amp; Safety knowlegde base.\n- Shipped Now Assist search sources for Health and amp; Safety for Knowledge article generation from health and safety case table on the Knowledge center.\n- Create contextually relevant articles from case tables and drive better AI-assisted content creation by enabling Knowledge Content Recommendation skill from AI skills module.\n\n |
| \n\nCore Business Suite for Human Resources\n\n | \n\n3.3.2\n\n | \n\n- Shipped out-of-the-box Human Resources knowledge base.\n- Owners and managers can be defined by the admin for the knowledge bases in the Core Business Suite configuration console to ensure proper governance and content tracking.\n- Shipped Now Assist search sources for Human Resources for Knowledge article generation from legal case table on the Knowledge center.\n- Create contextually relevant articles from case tables and drive better AI-assisted content creation by enabling Knowledge Content Recommendation skill from AI skills module.\n\n |
| \n\nCore Business Suite for Legal\n\n | \n\n3.3.2\n\n | \n\nShipped out-of-the-box Legal knowledge base.\n\n Owners and managers can be defined by the admin for the knowledge base in the Core Business Suite configuration console to ensure proper governance and content tracking.\n\n Shipped Now Assist search sources for Legal for Knowledge article generation from legal case table on Knowledge center.\n\n Create contextually relevant articles from case tables and drive better AI-assisted content creation by enabling Knowledge Content Recommendation skill from AI skills module.\n\n |
| \n\nCore Business Suite For Source To Pay\n\n | \n\n3.3.2\n\n | \n\n- Shipped out-of-the-box Procurement and Supplier knowledge bases.\n- Owners and managers can be defined by the admin for the knowledge base in the Core Business Suite configuration console to ensure proper governance and content tracking.\n- Shipped Now Assist search sources for Source to Pay for Knowledge article generation from invoice, supplier and procurement case table on the Knowledge center.\n- Create contextually relevant articles from case tables and drive better AI-assisted content creation by enabling Knowledge Content Recommendation skill from AI skills module.\n\n |
| \n\nCore Business Suite For Workplace Service Delivery\n\n | \n\n3.3.3\n\n | \n\n- Shipped out-of-the-box Workplace Services knowledge base.\n- Owners and managers can be defined by the admin for the knowledge base in the Core Business Suite configuration console to ensure proper governance and content tracking.\n- Shipped Now Assist search sources for Workplace Services for Knowledge article generation from workplace case table on the Knowledge center.\n- Create contextually relevant articles from case tables and drive better AI-assisted content creation by enabling Knowledge Content Recommendation skill from AI skills module.\n\n |
| \n\nCore Business Suite Foundation\n\n | \n\n3.3.2\n\n | \n\n- Shipped out-of-the-box knowledge bases defined at two levels: individual business unit knowledge bases \\(Human Resources, Legal, Source to Pay, Workplace Services, and Health and amp; Safety\\) and a CBS aggregate knowledge base.\n- Owners and managers can be defined by the admin in the Knowledge module for each knowledge base to ensure proper governance and content tracking.\n- Added new AI skills module under the Platform module on Configuration console enables admins to activate knowledge-specific skills from simplified setup.\n- Improve article optimization in terms of content quality, identification, and merging of duplicate articles to eliminate redundant content.\n- Shipped Now Assist search sources for all the business unit for Knowledge article generation from case tables on Knowledge center.\n- Create contextually relevant articles from case tables and drive better AI-assisted content creation by enabling Knowledge Content Recommendation skill from AI skills module.\n\n Admins can now manage access to the Core Business Suite analytics dashboard through the new Groups module under Core Business Suite module. Define which users have view and edit access by adding them to groups, providing fine-grained control over who can access reporting and metrics across your Core Business Suite implementation.\n\n |
| \n\nCore Business Suite Foundation for Finance\n\n | \n\n3.3.2\n\n | \n\nShipped Now Assist search sources for Finance for Knowledge article generation from finance case table on Knowledge center.\n\n Create contextually relevant articles from case tables and drive better AI-assisted content creation by enabling Knowledge Content Recommendation skill from AI skills module.\n\n |
| \n\nCore Business Suite Foundation for Health and Safety\n\n | \n\n3.3.2\n\n | \n\n- Shipped out-of-the-box Safety knowledge base.\n- Owners and managers can be defined by the admin for the knowledge base in the Core Business Suite configuration console to ensure proper governance and content tracking.\n- Shipped user criteria for Health and amp; Safety knowlegde base.\n- Shipped Now Assist search sources for Health and amp; Safety for Knowledge article generation from health and safety case table on the Knowledge center.\n- Create contextually relevant articles from case tables and drive better AI-assisted content creation by enabling Knowledge Content Recommendation skill from AI skills module.\n\n |
| \n\nCore Business Suite Foundation for Human Resources\n\n | \n\n3.3.2\n\n | \n\nShipped out-of-the-box Human Resources knowledge base.\n\n Owners and managers can be defined by the admin for the knowledge base in the Core Business Suite configuration console to ensure proper governance and content tracking.\n\n Shipped Now Assist search sources for Human Resources for Knowledge article generation from legal case table on Knowledge center.\n\n Create contextually relevant articles from case tables and drive better AI-assisted content creation by enabling Knowledge Content Recommendation skill from AI skills module.\n\n |
| \n\nCore Business Suite Foundation for Legal\n\n | \n\n3.3.2\n\n | \n\nShipped out-of-the-box Legal knowledge base.\n\n Owners and managers can be defined by the admin for the knowledge base in the Core Business Suite configuration console to ensure proper governance and content tracking.\n\n Shipped Now Assist search sources for Legal for Knowledge article generation from legal case table on Knowledge center.\n\n Create contextually relevant articles from case tables and drive better AI-assisted content creation by enabling Knowledge Content Recommendation skill from AI skills module.\n\n |
| \n\nCore Business Suite Foundation for Source to Pay\n\n | \n\n3.3.2\n\n | \n\n- Shipped out-of-the-box Procurement and Supplier knowledge bases.\n- Owners and managers can be defined by the admin for the knowledge base in the Core Business Suite configuration console to ensure proper governance and content tracking.\n- Shipped Now Assist search sources for Source to Pay for Knowledge article generation from invoice, supplier and procurement case table on the Knowledge center.\n- Create contextually relevant articles from case tables and drive better AI-assisted content creation by enabling Knowledge Content Recommendation skill from AI skills module.\n\n |
| \n\nCore Business Suite Foundation for Workplace Services\n\n | \n\n3.3.3\n\n | \n\nShipped out-of-the-box Workplace Services knowledge base.\n\n Owners and managers can be defined by the admin for the knowledge base in the Core Business Suite configuration console to ensure proper governance and content tracking.\n\n Shipped Now Assist search sources for Workplace Services for Knowledge article generation from workplace case table on the Knowledge center.\n\n Create contextually relevant articles from case tables and drive better AI-assisted content creation by enabling Knowledge Content Recommendation skill from AI skills module.\n\n |
| \n\nCore Business Suite Prime\n\n | \n\n3.3.2\n\n | \n\nUpdated to support the latest version of the dependent apps.\n\n |
| \n\nCore Business Suite Prime for Finance\n\n | \n\n3.3.2\n\n | \n\nUpdated to support the latest version of the dependent apps.\n\n |
| \n\nCore Business Suite Prime for Health and Safety\n\n | \n\n3.3.2\n\n | \n\nUpdated to support the latest version of the dependent apps.\n\n |
| \n\nCore Business Suite Prime for Human Resources\n\n | \n\n3.3.2\n\n | \n\nUpdated to support the latest version of the dependent apps.\n\n |
| \n\nCore Business Suite Prime for Legal\n\n | \n\n3.3.2\n\n | \n\nUpdated to support the latest version of the dependent apps.\n\n |
| \n\nCore Business Suite Prime for Source to Pay\n\n | \n\n3.3.2\n\n | \n\nUpdated to support the latest version of the dependent apps.\n\n |
| \n\nCore Business Suite Prime for Workplace Services\n\n | \n\n3.3.3\n\n | \n\nUpdated to support the latest version of the dependent apps.\n\n |
| \n\nCPQ for Manufacturing Advanced\n\n | \n\n2.0.0\n\n | \n\nHttps://www.servicenow.com/docs/r/release-notes/manufacturing-commercial-operations-rn.html.\n\n |
| \n\nCPQ for Manufacturing Foundation\n\n | \n\n2.0.0\n\n | \n\nHttps://www.servicenow.com/docs/r/release-notes/manufacturing-commercial-operations-rn.html.\n\n |
| \n\nCRM Touchpoint\n\n | \n\n1.5.2\n\n | \n\nNew\n\n Admins can now assign granular read and write roles for CRM Touchpoints. The new roles provide fine-grained access control to CRM Touchpoint records, enabling separate assignment of read and write permissions through the Responsibility Framework. Access Control Lists \\(ACLs\\) have been updated to enforce these granular permissions.\n\n |
| \n\nCryptographic Asset Compliance\n\n | \n\n1.0.2\n\n | \n\nNew\n\n - Centralized cryptographic asset visibilityAssess the quantum safety of your certificates and cloud keys \\(AWS KMS and Azure Key Vault\\) discovered across on-premises and cloud environments from a centralized inventory, giving you a unified view of your organization's quantum safety posture.\n- Policy-based risk indicatorsIdentify at-risk cryptographic assets, including risks like outdated algorithms, untrusted certificate authorities, and expiring certificates, helping you focus remediation efforts where they matter most.\n- Post-quantum cryptography \\(PQC\\) compliance and quantum vulnerability dashboardsTrack PQC compliance status and quantum vulnerability through purpose-built dashboards. For example, certificates using RSA are automatically tagged as quantum-vulnerable, enabling data-driven migration planning toward quantum-resistant algorithms.\n- Dependency graph for impact analysisVisualize where each cryptographic asset is used across your environment with an interactive dependency graph and assess downstream impact before initiating migration, reducing the risk of service disruption.\n- AI-driven analysis and recommendationsGet AI-generated insights for each identified cryptographic asset, including recommended next steps to guide remediation and migration planning.\n\n |
| \n\nCSM - Advanced\n\n | \n\n2.1.2\n\n | \n\nUpdated with the latest version of ServiceNow Otto Customer Service Management \\(CSM\\).\n\n |
| \n\nCSM - Foundation\n\n | \n\n2.1.2\n\n | \n\nUpdated with the latest version of ServiceNow Otto Customer Service Management \\(CSM\\).\n\n |
| \n\nCSM MCP Server\n\n | \n\n1.2.0\n\n | \n\nNew: Sentiment Analysis and amp; Activity Response Generation.\n\n Two new GenAI skills for CSM MCP Server, with full enterprise security and intelligent plugin gating. Tools deploy only on instances where the com.sn.csm.gen.ai plugin is active-no setup errors, no unnecessary dependencies.\n\n |
| \n\nCSM - Prime\n\n | \n\n2.1.2\n\n | \n\nUpdated with the latest version of ServiceNow Otto Customer Service Management \\(CSM\\).\n\n |
| \n\nCTO Voice AI Agents\n\n | \n\n2.0.7\n\n | \n\nChanged\n\n Dependency version fixes and branding fixes.\n\n |
| \n\nCustom App Record Summarization\n\n | \n\n29.2.6\n\n | \n\nChanged\n\n Updated to support the ServiceNow Otto brand.\n\n |
| \n\nCustomer Service Management AI agent collection\n\n | \n\n6.2.0\n\n | \n\nCustomer 360 query routing to improve performance for lookups and KB-related queries.\n\n |
| \n\nData Discovery\n\n | \n\n8.1.3\n\n | \n\nService now Otto Directive Changes.\n\n |
| \n\nData Foundation Model\n\n | \n\n1.12.0\n\n | \n\nAdded the 'Agentic Client' model category to the cmdb\\_model\\_category table. The category groups AI client software such as Arc ServiceNow clients, Claude Coworker clients, and so on.\n\n |
| \n\nData Privacy\n\n | \n\n8.1.4\n\n | \n\n\\*RTA not supporting selection of child tables from different scopes other than the scope of the policy\\*All columns selected from parent automatically apply to children \\(Need to add support for handling inherited child table field separately\\).\n\n |
| \n\nDCNAM - Advanced\n\n | \n\n2.2.0\n\n | \n\nMaintenance release - dependency updates only; no new customer-facing functionality in this version.\n\n |
| \n\nDeployment Pipeline\n\n | \n\n29.2.6\n\n | \n\nApp is a dependency of App Engine Studio. Please see App Engine Studio for release notes.\n\n |
| \n\nDEX Application and Device Health\n\n | \n\n5.1.3\n\n | \n\nFixed\n\n - Offline Monitoring: Continue collecting endpoint telemetry during network outages and automatically sync queued metrics when connectivity is restored.\n- Incident Work Notes Integration: Automatically add DEX work note to incident with deep links to DEX device health, DEX application health, when any of the following fields are updated \\(Configuration Item, Service, Service Offering\\).\n- CMDB population with enhanced discovery: Running processes are now reconciled directly into the cmdb\\_running\\_process table without creating unnecessary Application CIs. Running process data no longer creates Application Shell CIs in cmdb\\_ci\\_appl, and the system uses targeted reconciliation instead of the full ADM pipeline to keep your application inventory focused on actual software installations. This results in a cleaner CMDB with less clutter, better performance for instances with high process activity, and clearer separation between process telemetry and installed software inventory.\n- Updated remedial action: Perform disk clean up remedial action has been renamed to Disk cleanup for low disk space on device health page.\n- DEX policies for Windows and mac OS: These DEX policies are now split into multiple policies to optimise the performance of the device or the application that is monitored.\n\n |
| \n\nDEX Content Playbook\n\n | \n\n5.1.2\n\n | \n\nSee DEX Application and Device Health product for release notes. This app is a dependency of DEX Application and Device Health.\n\n |
| \n\nDEX Desktop Assistant\n\n | \n\n5.1.1\n\n | \n\nSee DEX Application and Device Health product for release notes. This app is a dependency of DEX Application and Device Health.\n\n |
| \n\nDEX Self Service\n\n | \n\n5.1.1\n\n | \n\nSee DEX Application and Device Health product for release notes. This app is a dependency of DEX Application and Device Health.\n\n |
| \n\nDigital Experience Score\n\n | \n\n5.1.1\n\n | \n\nSee DEX Application and Device Health product for release notes. This app is a dependency of DEX Application and Device Health.\n\n |
| \n\nDigital Integration Management\n\n | \n\n1.6.4\n\n | \n\nRemoved a hardcoded platform\\_host system ID from the EA credential-field UI policy condition. Credential fields on sn\\_apm\\_di\\_credential now enforce read-only consistently across all customer instances, regardless of platform host.\n\n |
| \n\nDocument Intelligence\n\n | \n\n8.0.9\n\n | \n\nMinor UI content updates.\n\n |
| \n\nDynamic Guidance\n\n | \n\n28.4.3\n\n | \n\nFixed\n\n - Integrated oneextend-gen-ai APIs to handle transcript storage, knowledge base retrieval, and connection initialization.\n- This update ensures all three core operations now use the consolidated API layer for consistency and maintainability.\n\n |
| \n\nEmployee Center\n\n | \n\n44.2.2\n\n | \n\nUpdated to support the latest version of the dependent apps.\n\n |
| \n\nEmployee Goals\n\n | \n\n1.4.3\n\n | \n\nNo customer facing changes were shipped in this version.\n\n |
| \n\nEmployee Profile\n\n | \n\n14.1.0\n\n | \n\nUpdated to support the latest version of the dependent apps.\n\n |
| \n\nEmployee Slate \\(built for Now Assist\\)\n\n | \n\n1.3.3\n\n | \n\n- Introduced topic-based content discovery with category-based navigation in Employee Slate, updating the browse experience.\n- Enhanced org charts with responsive layouts, profile cards redesign, and team visualization.\n- Provided field visibility controls on knowledge articles.\n- Introduced configuration scope controls so task configs and Lit-based action widgets can independently target Employee Center or Employee Slate, enabling teams to ship new configs with existing mappings.\n- Introduced task record preprocessing for skills to fetch context, enrich records, and format output before skill invocation.\n- Rebranded Now Assist, Moveworks, and AI Experience to Otto for consistency.\n\n |
| \n\nEmployee Slate Core\n\n | \n\n2.2.3\n\n | \n\n- Introduced topic-based content discovery with category-based navigation in Employee Slate, updating the browse experience.\n- Enhanced org charts with responsive layouts, profile cards redesign, and team visualization.\n- Provided field visibility controls on knowledge articles.\n- Introduced configuration scope controls so task configs and Lit-based action widgets can independently target Employee Center or Employee Slate, enabling teams to ship new configs with existing mappings.\n- Introduced task record preprocessing for skills to fetch context, enrich records, and format output before skill invocation.\n- Rebranded Now Assist, Moveworks, and AI Experience to Otto for consistency.\n\n |
| \n\nEnhanced Features for IRM Enterprise\n\n | \n\n22.5.0\n\n | \n\n \n\n |
| \n\nEnhanced Features for IRM Professional\n\n | \n\n22.5.0\n\n | \n\n \n\n |
| \n\nEnterprise Architecture Workspace\n\n | \n\n9.2.1\n\n | \n\nNew\n\n - Added four new entity types - Business Actor, Business Role, Stakeholder, and Driver to the Business Architecture section of the Portfolio page.\n- Added business capabilities and business process as related lists on the Goals page in the Business Architecture section of the Portfolio page.\n- Added business capabilities and business process as related list on the Business Unit page in the Business Architecture section of the Portfolio page.\n- Added goals as related list on the Business Processes and Business Capabilities page in the Business Architecture section of the Portfolio page.\n- Added business units as related list on the Business Processes and Business Capabilities page in the Business Architecture section of the Portfolio page.\n\n Changed\n\n Renamed Now Assist to ServiceNow Otto. All Enterprise Architecture Workspace screens, icons, and generative AI skill names now reflect the ServiceNow Otto brand.\n\n Fixed\n\n - Corrected the French translation of Retire in the bubble chart labels and captions.\n- Out-of-the-box business application certification policies now ship inactive by default, preventing unintended task creation.\n- Sorting by hierarchy ID in the Business Portfolio now uses natural numeric ordering, so capabilities sequence correctly \\(1.1 and rarr; 1.2 and rarr; ... and rarr; 1.9 and rarr; 1.10 and rarr; 1.11\\) instead of being sorted as text.\n- The Save button now displays for Business Applications in CMDB Workspace, matching the classic UI.\n\n |
| \n\nERP Rapid Deployment Packs\n\n | \n\n33.0.0\n\n | \n\n- Manage the full life cycle of data records across business domains through the MDM Orchestrator.\n- Review and act on transactions, data records, and month-end journal entries from a single location through the centralized Approvals Hub.\n- Validate and authorize manual journal entries before they post to the general ledger through the Journal Entry Approval Portal.\n\n |
| \n\nEvent Management Connectors\n\n | \n\n2.20.2\n\n | \n\nChanged\n\n - Enhanced Dynatrace Event Connector to support Dynatrace Grail 3rd Gen APIs.\n- Enhanced Azure Event connector to support Azure issues from Azure monitor.\n\n |
| \n\nEvent Management Core\n\n | \n\n23.17.3\n\n | \n\n--- AI Generated Release Notes ---.\n\n Changed\n\n All references to 'Now Assist' have been updated to 'ServiceNow Otto' across the em-scoped-app and em-arm modules. UI labels, flow descriptions, hint texts, and rule labels now consistently use the new product name to align with branding changes. Commit: Renaming of now assist to ServiceNow Otto - em-scoped-app; Updates according to the revised guideline.\n\n |
| \n\nExternal content connectors - ServiceNow Otto agent\n\n | \n\n1.2.0\n\n | \n\nChanged\n\n Name of AI agent to configure External Content Connector has been updated to External content connectors - ServiceNow Otto agent.\n\n |
| \n\nField Service Management AI agent collection\n\n | \n\n4.0.5\n\n | \n\nNew\n\n Fluent based development support added.\n\n Changed\n\n ServiceNow Otto is the new Al experience brand. This change is reflected in the name of ServiceNow products, including Field Service Management. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features.\n\n Fixed\n\n Removed\n\n |
| \n\nField Service Mobile\n\n | \n\n29.2.3\n\n | \n\nSecurity patch.\n\n |
| \n\nFinance and Procurement - Foundation\n\n | \n\n1.4.3\n\n | \n\nChanged\n\n Updated the plugin name and details to Finance and Procurement - Foundation.\n\n |
| \n\nFinance and Procurement - Prime\n\n | \n\n1.4.3\n\n | \n\nChanged\n\n Updated the plugin name and details to Finance and Procurement - Prime.\n\n |
| \n\nFinance Common Architecture\n\n | \n\n14.0.2\n\n | \n\nNew\n\n Introduced the Jurisdiction table to store jurisdiction names, codes, types, and associated tax authority.\n\n Changed\n\n - Enhanced the Tax Type table to associate tax types with jurisdictions.\n- Updated the Tax Type list view to display jurisdiction type and tax authority.\n- When adding a tax line, jurisdiction type and tax authority now populate automatically based on the selected tax type. These fields are hidden by default and can be enabled as needed.\n\n |
| \n\nFinancials Core\n\n | \n\n6.2.5\n\n | \n\nFixed\n\n - Fixed an issue where financial plans didn't support negative budget values.\n- Fixed an issue where a script naming conflict caused actuals to aggregate incorrectly after upgrade.\n- Fixed an issue where customized access control rules on cost plan breakdowns weren't applied on the Financials tab of Project Workspace.\n- Fixed an issue where long text strings caused overflow in Financial Dashboard widgets.\n\n |
| \n\nFinancial Services Operations AI agent collection\n\n | \n\n4.3.1\n\n | \n\nFixed\n\n Fixed multilingual output in Friendly fraud AI Agent.\n\n |
| \n\nFinancial Services Operations Core\n\n | \n\n12.4.2\n\n | \n\nChanged\n\n Centralized currency rounding precision logic into a shared utility, ensuring consistent handling of the platform's currency fraction digits setting across all consumers.\n\n |
| \n\nFlow Designer - Designer\n\n | \n\n29.5.2\n\n | \n\nRebranded UI for ServiceNow Otto.\n\n |
| \n\nFlow Designer GenAI\n\n | \n\n30.0.6\n\n | \n\nNew\n\n - All references to Now Assist, Moveworks, and AI Experience have been renamed to ServiceNow Otto. Applications, features, plugins, packages, in-product strings, images, and documentation now consistently use ServiceNow Otto branding.\n- Admins can now configure Flow Designer GenAI skills and agents to use optimal small third-party models as the default. Google Gemini 3.5 Flash, OpenAI GPT 5.1, and OpenAI GPT 5.4 mini are validated and available for use.\n- Context Memory input is now available in the Use an AI Agent action. Users can provide context memory to enhance agent interactions.\n\n Changed\n\n - TinyMCE editor library has been upgraded to version 8 across Flow Designer GenAI products. Editor functionality, including hashtag and prompt editing, has been validated with no regressions.\n- Default model provider for Flow Designer GenAI skills and agents is now a third-party model. Now LLM is no longer the default; optimal small models are set as default, with exception handling for large models.\n- Prompt Analyzer findings for Flow Generation prompts have been reviewed and addressed. All active prompts now comply with prompt standards and best practices.\n- Call Now Assist Skill step now supports a data pill value. Data pill values can be used directly in skill calls.\n- Invalid roles in ACL definitions have been audited and remediated across Flow Designer GenAI products. Access control behavior is validated and confirmed compliant.\n- Implementation Agent integration for AI Approvals has been updated and validated. End-to-end sanity testing confirms no regressions in MCP and Decision Tables.\n- GetRefRecord scoping bypass fix has been validated. No direct references found and sanity testing confirms no scoping bypass issues.\n- Project Greenlight test automation and stabilization improvements delivered. Manual test backlog analyzed, prioritized automation plan executed, pre-merge automation expectations defined, and test stability improved for MCP, Decision Tables, and AI Approvals.\n- Java 21 compile upgrade validated across Flow Designer GenAI products. MCP, Decision Tables, and AI Approvals tested with no regressions.\n- Non-Glide Cobalt Raven ACLs merged and validated in product code. Sanity testing confirms no regressions in ACL behavior.\n- User-supplied JavaScript execution is now disabled in the Guest Sandbox environment. Flow Generation, Flow Summarization, MCP, Decision Tables, and AI Approvals are unaffected and validated for correct operation.\n- CSRF remediation implemented and validated across platform APIs. MCP, Decision Tables, and AI Approvals API endpoints confirmed compliant with CSRF protection.\n\n |
| \n\nFlow Diagramming\n\n | \n\n29.1.1\n\n | \n\nChanged\n\n Rebranded UI for ServiceNow Otto.\n\n |
| \n\nFlow Generation\n\n | \n\n29.4.4\n\n | \n\nFlow Generation skills and agents now default to optimal small third-party models. All skills and agents previously using Now LLM have been updated to use Google Gemini 3.5 Flash, OpenAI GPT 5.1, or OpenAI GPT 5.4 mini as default model providers. Large model selections require documented exception approval.\n\n Changed\n\n ServiceNow Otto branding is now applied throughout Flow Generation interfaces. All UI strings, labels, and icons referencing 'Now Assist' have been replaced with ServiceNow Otto naming and marks according to Otto Naming Guidelines. Interactive and background surfaces display the correct Otto mark variant. UX review has been completed prior to merge.\n\n Prompt Analyzer findings for Flow Generation prompts have been reviewed and addressed. All prompt standards and best practices have been validated for skills, and any issues have been triaged or resolved.\n\n |
| \n\nFlow Summarization\n\n | \n\n29.4.4\n\n | \n\nFlow Summarization now defaults to optimal small third-party models for skills and agents. All skills and agents previously using Now LLM have been updated to use Google Gemini 3.5 Flash, OpenAI GPT 5.1, or OpenAI GPT 5.4 mini as the default model provider. These models have been tested and validated for the AP5/Australia release.\n\n Changed\n\n ServiceNow Otto branding is now applied throughout Flow Summarization. All UI strings, labels, and icons referencing 'Now Assist' have been replaced with ServiceNow Otto naming and marks per Otto Naming Guidelines. Interactive surfaces now display the Otto mark, and background AI processes use the black Otto mark. Loading animations and field-level sparkles are flagged for PM review before updating. UX review has been completed prior to merge.\n\n Prompt Analyzer findings for Flow Summarization prompts have been reviewed and addressed. All prompt standards and best practice issues identified by Prompt Analyzer have been triaged or resolved for skills within Flow Summarization.\n\n |
| \n\nForm data collector\n\n | \n\n2.3.1\n\n | \n\nChanged\n\n Updated internal config properties.\n\n |
| \n\nFSM - Advanced\n\n | \n\n2.0.9\n\n | \n\nNew\n\n Fluent based development support added.\n\n Changed\n\n ServiceNow Otto is the new Al experience brand. This change is reflected in the name of ServiceNow products, including Field Service Management. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features.\n\n Fixed\n\n Removed\n\n |
| \n\nFSM - Foundation\n\n | \n\n2.0.9\n\n | \n\nNew\n\n Fluent based development support added.\n\n Changed\n\n ServiceNow Otto is the new Al experience brand. This change is reflected in the name of ServiceNow products, including Field Service Management. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features.\n\n Fixed\n\n Removed\n\n |
| \n\nGenerative AI Controller\n\n | \n\n14.2.2\n\n | \n\nNew: Added support for capabilities provided by newest AI models \\(Latest Azure OpenAI, Gemini, and Claude models\\).\n\n |
| \n\nGoogle Gemini Spoke\n\n | \n\n1.6.2\n\n | \n\nFixed an issue in Google Gemini Spoke OEM actions where additional headers were not being sent correctly.\n\n |
| \n\nGRC: Approver Configurator\n\n | \n\n22.5.1\n\n | \n\n \n\n |
| \n\nGRC: Common Workspace Elements\n\n | \n\n22.5.1\n\n | \n\n \n\n |
| \n\nGRC: Metrics\n\n | \n\n22.5.2\n\n | \n\nNew\n\n - Campaigns support metric bundling and unified workflow managementMetric Campaigns bundles metrics by group, entity, frequency, and calendar into a single coordinated workflow, ensuring all metric types move through data collection, submission, and approval together as one transaction. Campaign cycles are automatically generated periodically based on the frequency configured at the campaign level.\n- Streamlined campaign UI and bulk actionsThe campaign workspace provides a scalable interface for managing up to 30 metrics across 17 entities, with dropdown filters and minimized scrolling. Users can bulk submit and approve metric data tasks, and tick marks indicate completion status for campaign setup steps.\n- Configurable data owner and approval workflowsAdmins can assign data owners and configure single-level or multi-level approval workflows for campaigns, with validation to prevent conflicts between data owners and approvers.\n- Enhanced metric data task \\(MDT\\) lifecycle and UIMetric data tasks now support campaign-driven scheduling, custom due dates, and read-only data fields for calculated metrics. The MDT UI includes new filters for project and task, project details on the ribbon, and approval page updates for bulk actions.\n- Threshold variance calculation and configurationMetric definitions now support configurable variance base values and improved variance calculation logic, including handling of missing or overridden data and immediate client-side updates.\n- Support for calculated metric definition \\(CMD\\) task creation and approvalTasks are now generated for calculated metrics, enabling review and approval before data is used in disclosures or reporting. CMD recalculation occurs in real time when source data changes, and approval flows are fully supported.\n- Naming conventions for campaign cyclesCampaign cycles are named according to frequency \\(daily, weekly, monthly, quarterly, semi-annually, annually\\) for clarity and consistency.\n\n Changed\n\n - Campaign and metric data task logic updated for campaign-driven schedulingWhen a metric is part of an active, published campaign, its data collection schedule, due date, and lifecycle are governed by the campaign rather than the individual metric definition. Updates to campaign cycles or due dates are reflected across all associated tasks.\n- Bulk state updates for campaign cyclesCampaign cycles automatically transition to 'Approval' or 'Closed' states based on the status of underlying tasks, eliminating manual intervention.\n- Validation and filtering improvements for campaign setupEntity selection now prevents duplicates, and the system shows an error message when a user attempts to add an entity already present in another campaign with matching group, frequency, and calendar. Bulk submission is disabled by default for new campaigns.\n- Metric data logic refined for task state and value propagationMetric data values populate immediately when child tasks complete, but the state remains 'in-progress' if tasks are enabled. CMD recalculation and approval flows are updated so task states and value propagation stay correct.\n- Approval configuration UI updatedThe data owner and approval configuration page now supports adding multiple approval levels, error handling for empty or conflicting values, and automatic clearing of multi-level settings when switching to single-level approval.\n- Field-level access controls and UI policies updatedData owner and approver fields are now managed at the campaign level, with updated ACLs and UI policies to enforce correct permissions and field behaviors.\n\n |
| \n\nGRC: Policy and Compliance Management\n\n | \n\n22.5.0\n\n | \n\nChanges.\n\n Multiple record association \\(MRA\\) security enhancements: Authorization validation has been strengthened within MRA workflows to consistently enforce access checks during record association operations.\n\n |
| \n\nGRC: Profiles\n\n | \n\n22.5.1\n\n | \n\n\\*\\*New\\*\\* None \\*\\*Changed\\*\\* None \\*\\*Fixed\\*\\* Fixed Cobalt Pegasus vulnerability by enforcing Glide Record Secure while querying/saving data through MRA components. \\*\\*Removed\\*\\* None.\n\n |
| \n\nGRC: Vendor Risk Management Workspace\n\n | \n\n22.5.0\n\n | \n\nChanged\n\n - Rebranded to ServiceNow Otto, replacing Now Assist references for a consistent AI experience.\n- Enhanced MRA authorization validation to ensure access checks are consistently enforced during record association.\n\n |
| \n\nGRC Common GenAI\n\n | \n\n22.5.1\n\n | \n\n\\*\\*New\\*\\* None \\*\\*Changed\\*\\* ServiceNow Otto for Integrated Risk Management branding is now applied across relevant products.All references to 'Now Assist for IRM' have been updated to 'ServiceNow Otto for Integrated Risk Management' in the Australia Patch5 and Zurich latest patch releases. \\*\\*Fixed\\*\\* None \\*\\*Removed\\*\\* None.\n\n |
| \n\nGRC Shared GenAI\n\n | \n\n22.5.1\n\n | \n\nChanges.\n\n - Multiple record association \\(MRA\\) security enhancements: Authorization validation has been strengthened within MRA workflows to consistently enforce access checks during record association operations.\n- Query Range ACL enhancements: Improved application security by adding query range access controls and strengthening authorization checks across supported data models. This helps ensure users can access only the data they are authorized to view.\n\n |
| \n\nGroup-Action Framework\n\n | \n\n7.2.1\n\n | \n\n--- AI Generated Release Notes ---.\n\n New\n\n - Admins can now grant report-view access to additional data tables for users with the data report viewer role, enabling broader visibility in dashboard visualizations.\n- Incremental clustering capabilities have been introduced for apps like Agent Advisor, Suggested steps allowing the system to process and group data as they come in.\n- GPT SMALL will now be the default model for GAF skills, enabling enhanced skill processing and evaluation.\n\n Changed\n\n Incremental clustering handler logic has been updated to improve prediction accuracy and workflow processing for Agent Advisor features.\n\n |
| \n\nHardware Asset Management\n\n | \n\n15.2.0\n\n | \n\nFixed an issue with PLANNED\\_ASSETS\\_EXTENSION\\_POINT API to ensure ACL rules are respected during planned asset candidate filtering on disposal orders.\n\n |
| \n\nHardware Asset Management - Advanced\n\n | \n\n1.0.4\n\n | \n\nThis app extends ServiceNow Otto capabilities for Hardware Asset Management through a subscription model. This release updates app dependencies to the latest versions while maintaining compatibility with the Hardware Asset Management - Advanced app.\n\n |
| \n\nHCLS - Advanced\n\n | \n\n3.0.3\n\n | \n\nMinor typo correction.\n\n |
| \n\nHCLS - Foundation\n\n | \n\n3.0.3\n\n | \n\nNew\n\n Dependency version fixes and branding fixes.\n\n |
| \n\nHCLS - Prime\n\n | \n\n3.0.4\n\n | \n\nChanged\n\n Dependency version fixes and branding fixes.\n\n |
| \n\nHealth and Safety Case Management\n\n | \n\n6.3.1\n\n | \n\nSafety Knowledge Base access controls for managers and requestors. Health and amp; Safety managers and agents can now contribute to Safety Knowledge Base articles, while case requestors have read-only access to articles within the Knowledge Base.\n\n |
| \n\nHealth and Safety Contractor Management\n\n | \n\n5.3.1\n\n | \n\nVersion bump only, because the hs-core version was updated. No new features delivered. Fixed one defect related to adding a worker in Brazil.\n\n |
| \n\nHealth and Safety Core\n\n | \n\n13.3.1\n\n | \n\nFixed\n\n The Assets involved list on the Incident Overview tab now displays correctly when the system property for invalid queries is set to return no rows. The previous hardcoded filter requiring an 'active' field has been corrected to support tables without an 'active' field.\n\n |
| \n\nHealth and Safety Incident Management\n\n | \n\n13.3.1\n\n | \n\nRole-based access to Safety Knowledge Base articles. Health and Safety managers and agents can now contribute to knowledge articles in the Safety Knowledge Base, while case requestors have read-only access.\n\n Fixed\n\n The active status of Health and Safety incident records now updates correctly when the state changes from Closed to Work in Progress.\n\n |
| \n\nHealth and Safety Risk Management\n\n | \n\n9.3.1\n\n | \n\nChanged\n\n - Date of birth and Date of hire fields now populate correctly in the exported OSHA 301 PDF forms.\n- Work notes on Health and Safety incidents are now restricted from being visible to end users.\n- Risk Management ACLs no longer override involved party access to Health and Safety incidents.\n- The body part picker now correctly selects the back of the hand instead of the palm when clicked.\n- ACL checks are now enforced on Health and Safety incident records for all applicable extension points.\n\n Fixed\n\n - Hardcoded strings and date and time formats in the Health and Safety Workspace now adapt to non-English locales.\n- 'Link Documents' and 'Select Documents' action labels appear translated on initial page load.\n- Users are prevented from creating and linking Health and Safety actions to restricted incidents without the required access permissions.\n- An intermittent issue that prevented incident playbook triggers from firing has been resolved.\n- A scrolling issue in the Injury Details section that prevented the delete option for the last added injury from being reachable has been fixed.\n- A cross-scope access violation in the Attach Health and Safety Case primary record to universal request business rule that prevented the Transfer and Create Associated Ticket buttons from appearing has been resolved.\n- The Approval Task Creator tool now reads manager details correctly when the application is installed.\n- The Health and Safety Ask attachment field now renders as mandatory when configured as required on a Smart Assessment template question.\n- A time zone issue that caused the Inspection Schedule flow to run incorrectly for daily frequency schedules has been resolved.\n- Scheduling an audit no longer returns a 'Component not configured' error.\n\n |
| \n\nHRSD - Advanced\n\n | \n\n2.2.2\n\n | \n\nNew\n\n Otto skills and a refreshed user interface for Otto.\n\n |
| \n\nHRSD - Foundation\n\n | \n\n2.2.1\n\n | \n\nNew\n\n Otto skills and a refreshed user interface for Otto.\n\n |
| \n\nHRSD - Prime\n\n | \n\n2.2.2\n\n | \n\nNew\n\n Otto skills and a refreshed user interface for Otto.\n\n |
| \n\nHR Voice AI Agents\n\n | \n\n2.3.11\n\n | \n\nFixed\n\n - Fixed issue retrieving expenses for Zoho agent fails.\n- Fixed issue with HR case creation agent needing an HR role.\n\n |
| \n\nHuman Resources: Service Portal\n\n | \n\n44.2.1\n\n | \n\nUpdated to support the latest version of the dependent apps.\n\n |
| \n\nImpact\n\n | \n\n10.0.5\n\n | \n\nImpact Store App - August Release.\n\n 1. Scan Engine Definition Enhancements - Restored sys\\_properties Scanning.\n\n Customers can once again add sys\\_properties directly as an Applicable Table target in Scan Engine Definitions, using any conditions they choose.\n\n This capability was temporarily removed one release ago, which required customers to use a dedicated 'Sys Property' definition type \\(system property name + condition\\) to check properties. Based on customer feedback, the August release restores the original free-form scanning approach for sys\\_properties - customers now have both options available:\n\n - Direct table scanning of sys\\_properties with custom conditions \\(restored\\).\n- The 'Sys Property' definition type \\(system property name + condition\\).\n\n 2. On-Demand Accelerators - Defects and Enhancements.\n\n This release includes a set of defect fixes and enhancements for On-Demand Accelerators, improving reliability and overall performance of the accelerator experience.\n\n |
| \n\nImpact Common\n\n | \n\n10.0.2\n\n | \n\nImpact Store App - August Release.\n\n 1. Scan Engine Definition Enhancements - Restored sys\\_properties Scanning.\n\n Customers can once again add sys\\_properties directly as an Applicable Table target in Scan Engine Definitions, using any conditions they choose.\n\n This capability was temporarily removed one release ago, which required customers to use a dedicated 'Sys Property' definition type \\(system property name + condition\\) to check properties. Based on customer feedback, the August release restores the original free-form scanning approach for sys\\_properties - customers now have both options available:\n\n - Direct table scanning of sys\\_properties with custom conditions \\(restored\\).\n- The 'Sys Property' definition type \\(system property name + condition\\).\n\n 2. On-Demand Accelerators - Defects and Enhancements.\n\n This release includes a set of defect fixes and enhancements for On-Demand Accelerators, improving reliability and overall performance of the accelerator experience.\n\n |
| \n\nImpact Content\n\n | \n\n10.0.4\n\n | \n\nImpact Store App - August Release.\n\n 1. Scan Engine Definition Enhancements - Restored sys\\_properties Scanning.\n\n Customers can once again add sys\\_properties directly as an Applicable Table target in Scan Engine Definitions, using any conditions they choose.\n\n This capability was temporarily removed one release ago, which required customers to use a dedicated 'Sys Property' definition type \\(system property name + condition\\) to check properties. Based on customer feedback, the August release restores the original free-form scanning approach for sys\\_properties - customers now have both options available:\n\n - Direct table scanning of sys\\_properties with custom conditions \\(restored\\).\n- The 'Sys Property' definition type \\(system property name + condition\\).\n\n 2. On-Demand Accelerators - Defects and Enhancements.\n\n This release includes a set of defect fixes and enhancements for On-Demand Accelerators, improving reliability and overall performance of the accelerator experience.\n\n |
| \n\nImpact Health Content\n\n | \n\n5.0.2\n\n | \n\n \n\n |
| \n\nImpact Value Management - ITSM\n\n | \n\n5.0.0\n\n | \n\nThis release upgrades the Data Collection App for ITSM with an expanded set of value-measurement metrics.\n\n All existing metrics remain unchanged. No modifications have been made to current functionality. This release only adds net-new metrics that extend value-measurement capabilities across the supported products.\n\n For the complete list of new metrics, please refer to the Supporting Document.\n\n Enhanced Metrics\n\n Any new metric introduced with this release is classified as an Enhanced Metric. Enhanced Metrics can be collected, and their data will be visible on the data dashboard included with the Data Collection App.\n\n Important: Automatic data transfer of Enhanced Metrics to ServiceNow's centralized Impact Delivery Instance is not supported.\n\n To make Enhanced Metric data available on the Impact Delivery Instance, customers must:\n\n - Install the Impact In-Platform App, and.\n- Enable ServiceBridge.\n\n Both steps are mandatory for Enhanced Metric data to appear on the Impact Delivery Instance.\n\n |
| \n\nIncident Communications Management for Service Operations Workspace\n\n | \n\n9.3.1\n\n | \n\nUpdated plugin dependencies to ensure compatibility with the ServiceNow latest release.\n\n |
| \n\nIncident Management for Service Operations Workspace\n\n | \n\n9.3.1\n\n | \n\nUpdated plugin dependencies to ensure compatibility with the ServiceNow latest release.\n\n |
| \n\nInsights Clustering Utils\n\n | \n\n3.3.1\n\n | \n\nNo major changes.\n\n |
| \n\nInsurance Claims Core\n\n | \n\n3.6.2\n\n | \n\nChanged\n\n Updated internal application components to support ongoing platform enhancements.\n\n |
| \n\nIntegrated Risk Management Advanced\n\n | \n\n22.5.0\n\n | \n\n \n\n |
| \n\nIntegrated Risk Management Foundation\n\n | \n\n22.5.1\n\n | \n\n \n\n |
| \n\nIntegrated Risk Management Prime\n\n | \n\n22.5.0\n\n | \n\n \n\n |
| \n\nInteraction Management for Service Operations Workspace\n\n | \n\n9.3.1\n\n | \n\nUpdated plugin dependencies to ensure compatibility with the ServiceNow latest release.\n\n |
| \n\nInvoice Case Management\n\n | \n\n13.1.4\n\n | \n\nThis release includes fixes for reported defects to improve product stability.\n\n |
| \n\nIRM Compliance GenAI\n\n | \n\n22.5.3\n\n | \n\nChanged\n\n ServiceNow OTTO Branding Updates: The IRM Compliance GenAI user interface now reflects ServiceNow's OTTO branding. All references to 'Now Assist' have been updated to 'OTTO' in UI labels, navigation, and help text.\n\n |
| \n\nIRM Risk GenAI\n\n | \n\n22.5.1\n\n | \n\nChanged\n\n - Updated the application to reflect the new ServiceNow OTTO branding, replacing Now Assist references and providing a more consistent AI experience across the platform.\n- Note: These branding updates are fully supported on AP5. Customers using AP4 will continue to see legacy branding elements and could notice missing icons on a few buttons until they upgrade to AP5.\n\n |
| \n\nITOM - Advanced\n\n | \n\n1.1.3\n\n | \n\nNew\n\n Cryptographic Asset Compliance\n\n - Centralized cryptographic asset visibilityAssess the quantum safety of your certificates and cloud keys \\(AWS KMS and Azure Key Vault\\) discovered across on-premises and cloud environments from a centralized inventory, giving you a unified view of your organization's quantum safety posture.\n- Policy-based risk indicatorsIdentify at-risk cryptographic assets, including risks like outdated algorithms, untrusted certificate authorities, and expiring certificates, helping you focus remediation efforts where they matter most.\n- Post-quantum cryptography \\(PQC\\) compliance and quantum vulnerability dashboardsTrack PQC compliance status and quantum vulnerability through purpose-built dashboards. For example, certificates using RSA are automatically tagged as quantum-vulnerable, enabling data-driven migration planning toward quantum-resistant algorithms.\n- Dependency graph for impact analysisVisualize where each cryptographic asset is used across your environment with an interactive dependency graph and assess downstream impact before initiating migration, reducing the risk of service disruption.\n- AI-driven analysis and recommendationsGet AI-generated insights for each identified cryptographic asset, including recommended next steps to guide remediation and migration planning.\n\n AI Agents for Observability\n\n Extend alert analysis capabilities with the Azure Monitor MCP Agent and Gemini Cloud Assist A2A Investigation Agent in the analyze alert impact agentic workflow.\n\n Changed\n\n AI Agents for Service Level Objective\n\n ServiceNow Otto is the new AI experience brand. This change is reflected in the name of ServiceNow products, including AI agents for SLO. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features.\n\n ITOM AI Agents for Service Mapping\n\n - ServiceNow Otto is the new AI experience brand. This name change is reflected in ServiceNow products, including ITOM AI Agents For Service Mapping. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features.\n- The Now LLM Service is no longer the default model provider for new or inactive AI assets. A third-party LLM is now selected by default, while existing configurations using the Now LLM Service continue unchanged. The Now LLM Service is still available for manual selection.\n\n AI Agents for Observability\n\n ServiceNow Otto is the new AI experience brand. This change is reflected in the name of ServiceNow products, including AI agents for Observability. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features.\n\n LEAP\n\n Now Assist is renamed to ServiceNow Otto. All references to Now Assist are renamed and relevant images updated.\n\n Fixed\n\n ITOM URL Discovery\n\n You can now add one or more URLs to targeted discovery from the Other URLs tab and the domain details page in the ITOM URL Discovery for SAM dashboard without receiving an error.\n\n |
| \n\nITOM AI Agents For Service Mapping\n\n | \n\n1.4.1\n\n | \n\nChanged\n\n - ServiceNow Otto is the new AI experience brand. This name change is reflected in ServiceNow products, including ITOM AI Agents For Service Mapping. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features.\n- The Now LLM Service is no longer the default model provider for new or inactive AI assets. A third-party LLM is now selected by default, while existing configurations using the Now LLM Service continue unchanged. The Now LLM Service is still available for manual selection.\n\n |
| \n\nITOM Cloud Services Core\n\n | \n\n4.3.0\n\n | \n\nNew\n\n - Detect and automatically remediate common ICS configuration issues directly from the Diagnostics page.\n- Added ADCv2 and mTLS prerequisite checks to the System Property card, flagged in red when either is missing.\n\n Fixed\n\n - Improved alerting reliability for CnC keepalive REST request error monitoring.\n- Corrected ICS integration user setup so service accounts are provisioned with the right access by default.\n- Updated underlying platform components for improved stability and forward compatibility.\n\n |
| \n\nITOM Configuration Console\n\n | \n\n28.3.1\n\n | \n\nNew\n\n - Best practices for Discovery setup.\n- Assign a NOC Manager.\n- Remediation Actions - show response automations that do not contain 'incident'.\n\n Changed\n\n - Change the 'Assign Event Management Admin' item from direct assignment to group assignment \\(similar to the operator item\\).\n- Update the operator training step to link to ServiceNow University.\n\n |
| \n\nITOM Guided Setup - New\n\n | \n\n27.5.1\n\n | \n\nNow Assist and gt; ServiceNow Otto announcement.\n\n Now Assist introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n |
| \n\nIT Service Management\n\n | \n\n3.2.5\n\n | \n\nNew\n\n - Simplified request experience for order guides on Employee Center: For requests submitted through order guides, employees see the parent Request \\(REQ\\) as the primary entity in the order confirmation page, My Requests list, and activity filtering. Approval workflows for these order guide requests and email notifications operate at the REQ level, providing a unified view of multi-item requests.\n- Simplified Request on Employee Slate: Initial support for the simplified request experience on Employee Slate, enabling request simplification for both new and upgrade customer paths.\n\n |
| \n\nIT Service Management Advanced\n\n | \n\n3.2.6\n\n | \n\nNo changes.\n\n |
| \n\nIT Service Management AI agent collection\n\n | \n\n11.0.5\n\n | \n\nNew\n\n - AI can now automatically complete Change Risk Assessment and Dynamic Schema questions based on the change record's context, showing its reasoning for each answer so admins and change managers can verify or correct it. Answers that identify compliance exposure \\(for example SOX, PCI-DSS, or HIPAA\\) automatically populate the matching Dynamic Schema fields.\n- A new AI agent can diagnose and resolve common Okta account lockouts and MFA failures reported through an incident or self-service, checking live account status and submitting the correct unlock or reset request automatically.\n- A new Teams-native AI agent lets shift agents manage on-call coverage directly in chat - requesting coverage or leave, and asking questions like 'who is on call' or 'when is my next shift.'.\n\n Changed\n\n The DEX Diagnosis AI agent now factors in event monitoring logs and statistical anomaly signals alongside existing telemetry for more accurate root-cause diagnoses, and now surfaces the specific evidence behind each conclusion.\n\n Fixed\n\n - Fixed an issue where several AI agents \\(including Zscaler, Installed Apps, and Modern Change agents\\) had read-only configuration, preventing customers from disabling them.\n- Fixed an issue where the Zscaler and Installed Apps agents' action engagement tools showed an empty timeout field.\n- Fixed a date-formatting issue in the Change Outage Assistant AI agent.\n- Fixed a security issue that allowed any authenticated user, regardless of role, to invoke ITSM AI agents and skills that should have been role-restricted.\n- Fixed an issue where the incident investigation and resolution workflow could fail with an 'incident search/read service unavailable' error.\n- Fixed an issue where the knowledge-article search filters used by the Create Incident AI agent were not being applied correctly.\n- Reduced processing time for the Generate Change Request Plans AI flow, which had been taking an unusually long time to complete.\n- Fixed an issue where built-in ITSM AI agents were unintentionally discoverable and visible within the Now Assist Platform.\n- Fixed an issue where a required role was missing from the Link Major Incident agent's flow, which could prevent the agent from working as expected for some users.\n- Fixed an issue where the Triage and Categorize AI agent could assign an irrelevant, caller-owned device as the configuration item when the matched service offering had no related configuration items of its own.\n\n Removed\n\n No items removed in this release.\n\n |
| \n\nITSM Admin Experience\n\n | \n\n3.2.3\n\n | \n\nNew\n\n The Configuration Console honours ITSM granular roles on a per-step basis for the Employee Experience and ITSM Fulfiller Experience steps. The Console evaluates the invoking user's granular role for each step, gates visibility and actions accordingly, and surfaces consistent messaging on which role to request.\n\n - To delegate Incident Management setup tasks, provide sn\\_incident\\_admin role.\n- To delegate Request Management setup tasks, provide sn\\_request\\_admin role.\n\n |
| \n\nITSM Admin Experience Components\n\n | \n\n3.2.0\n\n | \n\nNo changes.\n\n |
| \n\nITSM - Advanced\n\n | \n\n2.3.3\n\n | \n\nNew\n\n - AI can now automatically complete Change Risk Assessment and Dynamic Schema questions based on the change record's context, showing its reasoning for each answer so admins and change managers can verify or correct it. Answers that identify compliance exposure \\(for example SOX, PCI-DSS, or HIPAA\\) automatically populate the matching Dynamic Schema fields.\n- A new Teams-native AI agent lets shift agents manage on-call coverage directly in chat - requesting coverage or leave, and asking questions like 'who is on call' or 'when is my next shift.'.\n- Employees creating a ticket in Service Portal now see an AI-generated suggestion - drawn from relevant knowledge articles and catalog items - before they submit, based on the ticket description and their hardware, location, and department.\n\n Changed\n\n - Now Assist, Moveworks, and 'AI Experience' branding has been renamed to ServiceNow Otto across in-product labels, icons, tooltips, and documentation.\n- Incident Managers can now drill from any indicator on the Insights and Opportunities dashboard directly into the underlying incident records without losing their place on the dashboard.\n- The employee consent experience for remedial actions is more consistent and accurate: duplicate requests are no longer triggered for already-approved or declined actions, and messaging now notes when a device needs to stay online.\n- The DEX Diagnosis AI agent now factors in event monitoring logs and statistical anomaly signals alongside existing telemetry for more accurate root-cause diagnoses, and now surfaces the specific evidence behind each conclusion.\n\n Fixed\n\n - Fixed an issue where the summarize capability could produce an irrelevant summary on requested items with many related records.\n- Corrected a remaining reference to the previous Now Assist branding that had been missed during the ServiceNow Otto rename.\n- Fixed an issue on the Insights and Opportunities dashboard where assigning an incident to a cluster could fail and prevent clustering from completing.\n- Fixed a date-formatting issue in the Change Outage Assistant AI agent.\n- Fixed an issue where the incident investigation and resolution workflow could fail with an 'incident search/read service unavailable' error.\n- Fixed an issue where the knowledge-article search filters used by the Create Incident AI agent were not being applied correctly.\n- Improved the error message shown for the Resolution Notes generation skill when the 'display in product desktop' setting is turned off.\n- Reduced processing time for the Generate Change Request Plans AI flow, which had been taking an unusually long time to complete.\n- Fixed an issue where built-in ITSM AI agents were unintentionally discoverable and visible within the Now Assist Platform.\n- Fixed an issue where a required role was missing from the Link Major Incident agent's flow, which could prevent the agent from working as expected for some users.\n- Fixed an issue where the Triage and Categorize AI agent could assign an irrelevant, caller-owned device as the configuration item when the matched service offering had no related configuration items of its own.\n\n Removed\n\n No items removed in this release.\n\n |
| \n\nITSM Advanced Admin Experience\n\n | \n\n3.2.1\n\n | \n\nNo changes.\n\n |
| \n\nITSM Change Admin Experience\n\n | \n\n1.2.2\n\n | \n\nNew\n\n Forms module in Configuration Console.\n\n Review and configure change forms that IT fulfiller staff use to create and manage changes. Use the Form Builder to customize form layouts, fields, and sections to match your organization's change processes.\n\n Lists module in Configuration Console\n\n Configure which columns appear in the change lists for your IT fulfiller staff.\n\n Changed\n\n Enhanced AI agents\n\n Use a document upload flow as an alternative to the traditional form-based approach to configure team roles and the Change Advisory Board \\(CAB\\) using AI agents, with support for PDF, DOCX, XLSX, and CSV file formats.\n\n |
| \n\nITSM Employee Experience\n\n | \n\n3.2.1\n\n | \n\nNew\n\n - Simplified request experience for order guides on Employee Center: For requests submitted through order guides, employees see the parent Request \\(REQ\\) as the primary entity in the order confirmation page, My Requests list, and activity filtering. Approval workflows for these order guide requests and email notifications operate at the REQ level, providing a unified view of multi-item requests.\n- Simplified Request on Employee Slate: Initial support for the simplified request experience on Employee Slate, enabling request simplification for both new and upgrade customer paths.\n\n The Configuration Console now honours ITSM granular roles on a per-step basis for the Employee Experience and ITSM Fulfiller Experience steps. The Console evaluates the invoking user's granular role for each step, gates visibility and actions accordingly, and surfaces consistent messaging on which role to request.\n\n - To delegate Incident Management setup tasks, provide sn\\_incident\\_admin role.\n- To delegate Request Management setup tasks, provide sn\\_request\\_admin role.\n\n |
| \n\nITSM - Foundation\n\n | \n\n2.3.3\n\n | \n\nNew\n\n Employees creating a ticket in Service Portal now see an AI-generated suggestion - drawn from relevant knowledge articles and catalog items - before they submit, based on the ticket description and their hardware, location, and department.\n\n Changed\n\n - Now Assist, Moveworks, and 'AI Experience' branding has been renamed to ServiceNow Otto across in-product labels, icons, tooltips, and documentation.\n- Incident Managers can now drill from any indicator on the Insights and Opportunities dashboard directly into the underlying incident records without losing their place on the dashboard.\n- The employee consent experience for remedial actions is more consistent and accurate: duplicate requests are no longer triggered for already-approved or declined actions, and messaging now notes when a device needs to stay online.\n\n Fixed\n\n - Fixed an issue where the summarize capability could produce an irrelevant summary on requested items with many related records.\n- Corrected a remaining reference to the previous Now Assist branding that had been missed during the ServiceNow Otto rename.\n- Fixed an issue on the Insights and Opportunities dashboard where assigning an incident to a cluster could fail and prevent clustering from completing.\n- Fixed an issue where the incident investigation and resolution workflow could fail with an 'incident search/read service unavailable' error.\n- Fixed an issue where the knowledge-article search filters used by the Create Incident AI agent were not being applied correctly.\n- Improved the error message shown for the Resolution Notes generation skill when the 'display in product desktop' setting is turned off.\n- Fixed an issue where built-in ITSM AI agents were unintentionally discoverable and visible within the Now Assist Platform.\n- Fixed an issue where a required role was missing from the Link Major Incident agent's flow, which could prevent the agent from working as expected for some users.\n- Fixed an issue where the Triage and Categorize AI agent could assign an irrelevant, caller-owned device as the configuration item when the matched service offering had no related configuration items of its own.\n\n Removed\n\n No items removed in this release.\n\n |
| \n\nITSM Fulfiller Experience\n\n | \n\n3.2.1\n\n | \n\nNo changes.\n\n |
| \n\nITSM - Prime\n\n | \n\n2.3.3\n\n | \n\nNew\n\n - AI can now automatically complete Change Risk Assessment and Dynamic Schema questions based on the change record's context, showing its reasoning for each answer so admins and change managers can verify or correct it. Answers that identify compliance exposure \\(for example SOX, PCI-DSS, or HIPAA\\) automatically populate the matching Dynamic Schema fields.\n- A new AI agent can diagnose and resolve common Okta account lockouts and MFA failures reported through an incident or self-service, checking live account status and submitting the correct unlock or reset request automatically.\n- A new Teams-native AI agent lets shift agents manage on-call coverage directly in chat - requesting coverage or leave, and asking questions like 'who is on call' or 'when is my next shift.'.\n- Employees creating a ticket in Service Portal now see an AI-generated suggestion - drawn from relevant knowledge articles and catalog items - before they submit, based on the ticket description and their hardware, location, and department.\n\n Changed\n\n - Now Assist, Moveworks, and 'AI Experience' branding has been renamed to ServiceNow Otto across in-product labels, icons, tooltips, and documentation.\n- Incident Managers can now drill from any indicator on the Insights and Opportunities dashboard directly into the underlying incident records without losing their place on the dashboard.\n- A new dashboard section shows how closely AI-proposed solutions in Copilot \\(supervised\\) mode matched what human agents ultimately implemented.\n- The employee consent experience for remedial actions is more consistent and accurate: duplicate requests are no longer triggered for already-approved or declined actions, and messaging now notes when a device needs to stay online.\n- The DEX Diagnosis AI agent now factors in event monitoring logs and statistical anomaly signals alongside existing telemetry for more accurate root-cause diagnoses, and now surfaces the specific evidence behind each conclusion.\n\n Fixed\n\n - Fixed an issue where the summarize capability could produce an irrelevant summary on requested items with many related records.\n- Fixed an issue where several AI agents \\(including Zscaler, Installed Apps, and Modern Change agents\\) had read-only configuration, preventing customers from disabling them.\n- Fixed an issue where the Zscaler and Installed Apps agents' action engagement tools showed an empty timeout field.\n- Corrected a remaining reference to the previous Now Assist branding that had been missed during the ServiceNow Otto rename.\n- Fixed an issue on the Insights and Opportunities dashboard where assigning an incident to a cluster could fail and prevent clustering from completing.\n- Fixed a date-formatting issue in the Change Outage Assistant AI agent.\n- Fixed an issue where the incident investigation and resolution workflow could fail with an 'incident search/read service unavailable' error.\n- Fixed an issue where the knowledge-article search filters used by the Create Incident AI agent were not being applied correctly.\n- Reordered the metrics on the Copilot Performance dashboard so the '80% or higher similarity' metric appears first.\n- Improved the error message shown for the Resolution Notes generation skill when the 'display in product desktop' setting is turned off.\n- Reduced processing time for the Generate Change Request Plans AI flow, which had been taking an unusually long time to complete.\n- Fixed an issue where built-in ITSM AI agents were unintentionally discoverable and visible within the Now Assist Platform.\n- Fixed an issue where a required role was missing from the Link Major Incident agent's flow, which could prevent the agent from working as expected for some users.\n- Fixed an issue where the Triage and Categorize AI agent could assign an irrelevant, caller-owned device as the configuration item when the matched service offering had no related configuration items of its own.\n\n Removed\n\n No items removed in this release.\n\n |
| \n\nJourney designer\n\n | \n\n7.6.5\n\n | \n\nNow Assist introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n - Updated agentic workflows in Journey Designer to align with the Otto rebranding initiative.\n- Replaced legacy product terminology, labels, visual references and user-facing text with Otto branding.\n\n |
| \n\nKeyboard Shortcuts AI Skills\n\n | \n\n1.0.4\n\n | \n\nGenerally Available Compatibility: Support for Next Experience interfaces where keyboard shortcuts are configurable.\n\n |
| \n\nKnowledge Capabilities in UI Builder\n\n | \n\n30.5.4\n\n | \n\nAuto-update, auto-merge and otto branding updates.\n\n |
| \n\nKnowledge Graph\n\n | \n\n8.2.1\n\n | \n\nGraph query builder to traverse through Knowledge Graph.\n\n |
| \n\nLead to Cash Core\n\n | \n\n1.9.6\n\n | \n\nRelease Notes \\*\\*New\\*\\* None \\*\\*Changed\\*\\* Enhanced support to provide custom mapping in DeltaService API. \\*\\*Fixed\\*\\* None \\*\\*Removed\\*\\* None.\n\n |
| \n\nLEAP\n\n | \n\n4.2.1\n\n | \n\nChanged\n\n Now Assist is renamed to 'ServiceNow Otto'.\n\n |
| \n\nLegal Counsel Center\n\n | \n\n2.4.0\n\n | \n\nChanged\n\n ServiceNow Otto is the new AI experience brand. Now Assist for Legal Service Delivery is ServiceNow Otto for Legal Service Delivery.\n\n Fixed\n\n - Cancelling an edit to a Quick Link on Legal Counsel Center Home page now correctly restores the original display name and URL instead of retaining the unsaved changes.\n- Security fixes.\n\n |
| \n\nLegal Request Management\n\n | \n\n10.3.0\n\n | \n\nChanged\n\n ServiceNow Otto is the new AI experience brand. Now Assist for Legal Service Delivery is ServiceNow Otto for Legal Service Delivery.\n\n Fixed\n\n Security fixes.\n\n |
| \n\nLegal Service Delivery - Prime\n\n | \n\n1.0.14\n\n | \n\nChanged\n\n ServiceNow Otto is the new AI experience brand. Now Assist for Legal Service Delivery is ServiceNow Otto for Legal Service Delivery.\n\n |
| \n\nList AI Experience\n\n | \n\n3.1.4\n\n | \n\nChanged\n\n - Updated logos to new Otto logos and removed any references to Now Assist for AI filter assist, Track record list change, and multi record actions.\n- Replaced NowLLM with Gemini for Track record list changes.\n\n |
| \n\nMajor Incident Management for Service Operations Workspace\n\n | \n\n9.3.1\n\n | \n\nUpdated plugin dependencies to ensure compatibility with the ServiceNow latest release.\n\n |
| \n\nManufacturing Commercial Operations Advanced\n\n | \n\n2.0.3\n\n | \n\nHttps://www.servicenow.com/docs/r/release-notes/manufacturing-commercial-operations-rn.html.\n\n |
| \n\nManufacturing Commercial Operations AI agents collection\n\n | \n\n3.3.0\n\n | \n\nHttps://docs-preview.corp.service-now.com/bundle/australia-release-notes/page/release-notes/manufacturing-commercial-operations-rn.html.\n\n |
| \n\nManufacturing Commercial Operations Foundation\n\n | \n\n2.0.3\n\n | \n\nHttps://www.servicenow.com/docs/r/release-notes/manufacturing-commercial-operations-rn.html.\n\n |
| \n\nManufacturing Commercial Operations Prime\n\n | \n\n2.0.3\n\n | \n\nHttps://www.servicenow.com/docs/r/release-notes/manufacturing-commercial-operations-rn.html.\n\n |
| \n\nMentoring\n\n | \n\n2.4.3\n\n | \n\nAddressed UI Defects \\(Hide the Now Assist FAB when Mentoring modals/flyouts open to prevent it from overlapping the UI\\).\n\n |
| \n\nMetric data table\n\n | \n\n22.5.0\n\n | \n\nAll subgroup sections are now displayed in the Metric Data Grid, allowing users to view and select metric data tasks across multiple subgroups.\n\n |
| \n\nMicrosoft Azure OpenAI Generative AI Spoke\n\n | \n\n3.12.3\n\n | \n\nFixed an issue in Azure OpenAI Spoke where multi-turn GPT conversations failed due to message input not being passed as JSON type.\n\n Fixed an issue in Azure OpenAI Spoke where Tool Calling was not supported in Streaming \\(SSE\\) mode for GPT-5.4 in GAIC.\n\n |
| \n\nMIF Customer Instance\n\n | \n\n4.1.3\n\n | \n\nNew\n\n - A new column, retirement date, is now available in the sn\\_mif\\_instance table for licensing to consume and use to manage entitlements.\n- Clone exclusion and preserver are available in the sn\\_mif\\_vtable\\_operation\\_context table.\n\n |
| \n\nModel Context Protocol Client\n\n | \n\n2.3.2\n\n | \n\n- Added description field to the MCP server for a better discovery.\n\n - Pre-work for supporting MCP servers to assistants.\n\n |
| \n\nModel Context Protocol Server\n\n | \n\n1.7.2\n\n | \n\nNew: OAuth Client Registration wizard: register an inbound OAuth client for your MCP server using a guided setup \\(name and redirect URL\\) instead of configuring it manually.- In-console tool testing: list and run any tool directly from the MCP Server Console to validate it before making it available to clients.- Tool visibility controls: choose which tools are visible in the console and to connected MCP clients.- Tool annotations: tools now indicate whether they are read-only, destructive, or display a friendly title, so AI clients like Claude can skip confirmation prompts for safe, read-only actions.- Improved separation between production and sub-production traffic, so testing and development activity no longer competes with production usage.\n\n Changed: Expanded request tracing, so administrators can follow a single tool call from start to finish.- Improved throughput and scaling, supporting significantly more concurrent users without performance degradation.- Enhanced monitoring for rate limits and platform guardrails to help administrators stay ahead of usage issues.\n\n Fixed: Performance and scaling fixes that address slowdowns under higher concurrent usage.\n\n |
| \n\nNow Assist for Digital End-user Experience \\(DEX\\)\n\n | \n\n5.1.2\n\n | \n\nA new AI agent can diagnose and resolve slow computer issues reported through an incident or self-service, checking live device health across disk, CPU, memory, and network, and automatically applying the right fix - from killing resource-heavy processes to freeing up disk space.This change integrates with ZTS so will not be published until ZTS is GA.\n\n |
| \n\nobserv-ai-agents-app\n\n | \n\n6.2.3\n\n | \n\nNew\n\n Added the following agents to the Analyze alert impact agentic workflow:\n\n - Gemini Cloud Assist A2A Investigation Agent.\n- Azure Monitor MCP Agent.\n\n Changed\n\n ServiceNow Otto is the new AI experience brand. This change is reflected in the name of ServiceNow products, including AI Agents for Observability. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features.\n\n |
| \n\nOn Call Scheduling for Service Operations Workspace\n\n | \n\n9.3.1\n\n | \n\nUpdated plugin dependencies to ensure compatibility with the ServiceNow latest release.\n\n |
| \n\nOperational Sustainability Management\n\n | \n\n22.5.3\n\n | \n\nNew\n\n - Product roles and functional domain separation. Product roles have been restructured with updated role inheritance and licensing exclusions, enabling clearer role management and functional domain separation in ESG.\n- Unified Document Designer add-in. The Office 365 reporting and Document Designer add-ins have been consolidated into a single unified Document Designer plugin with updated manifest and business domain support.\n\n Changed\n\n - Read access to emission calculation guidelines is now restricted to the cmdagentuser role only.\n- The read access of the GRC confidentiality user role on the Portfolio Management Goal Framework table has been reviewed and updated.\n- Business domain references for uptaking teams are now updated automatically via a new script.\n- Demo data has been corrected to align with updated role and domain separation changes.\n\n Fixed\n\n - The metric picker now loads quickly when adding Metric to Target relationships via related lists.\n- Metric data task values are no longer set to null when edited with multibyte characters.\n- Related list UX form values sourced from the main form are now retained when reloading in the ESG workspace.\n- The Document ID field is now read-only and is populated automatically.\n- Accessibility issues across the application have been resolved.\n- List type data visualization is now available for selection in Reporting configuration.\n- The record-vertical child page now correctly sets values when using the Form controller.\n\n |
| \n\nOperational Sustainability Management Advanced\n\n | \n\n22.5.1\n\n | \n\nServiceNow Otto Branding Updates Updated the application to reflect the new ServiceNow Otto branding, replacing Now Assist references and providing a more consistent AI experience across the platform.\n\n |
| \n\nOpportunity Management Application\n\n | \n\n13.1.0\n\n | \n\nNew\n\n - Added support for Opportunity records in global search.\n- UI refinements on the Opportunity page - padding fixes and rebranding updates.\n- Quote tasks for primary quotes now appear in the To-Do section of the Opportunity Overview page.\n- Added configurable dependency between Won/Lost stage and Won/Lost reason fields, controlled via system properties.\n\n Fixed\n\n - Resolved UX defects on the Opportunity Overview page and Guided Selling experience.\n- Fixed semantic search results for Opportunity records.\n- Corrected inconsistencies in Contract End Date and Term \\(months\\) calculations within Opportunity Management.\n- Price list on Opportunity now updates correctly when currency is changed.\n- Resolved intermittent 'One or more property values are invalid' error in Manage Allocations when saving allocation splits.\n- Addressed performance issues on the Opportunity page.\n\n |
| \n\nOpportunity Management Data Model\n\n | \n\n13.1.0\n\n | \n\nNew\n\n - Added support for Opportunity records in global search.\n- UI refinements on the Opportunity page - padding fixes and rebranding updates.\n- Quote tasks for primary quotes now appear in the To-Do section of the Opportunity Overview page.\n- Added configurable dependency between Won/Lost stage and Won/Lost reason fields, controlled via system properties.\n\n Fixed\n\n - Resolved UX defects on the Opportunity Overview page and Guided Selling experience.\n- Fixed semantic search results for Opportunity records.\n- Corrected inconsistencies in Contract End Date and Term \\(months\\) calculations within Opportunity Management.\n- Price list on Opportunity now updates correctly when currency is changed.\n- Resolved intermittent 'One or more property values are invalid' error in Manage Allocations when saving allocation splits.\n- Addressed performance issues on the Opportunity page.\n\n |
| \n\nPayment Card\n\n | \n\n1.5.1\n\n | \n\nChanged\n\n Updated internal application components to support ongoing platform enhancements.\n\n |
| \n\nPipeline\n\n | \n\n29.2.6\n\n | \n\nApp is a dependency of App Engine Studio. Please see App Engine Studio for release notes.\n\n |
| \n\nPlatform AI Agents and Skills\n\n | \n\n13.2.5\n\n | \n\nNew\n\n Identify Escalation Signals agentic workflow now includes suggested actions, to help fulfillers take action on potential escalations.\n\n Changed\n\n - Updated the Generate my work plan agentic workflow summary and reasoning to make it more understandable and relevant to end users.\n- Enabled citations for resolution notes. Users can directly reference which work note/comment/KB section the resolution note came from and navigate there.\n- Agentic workflows can now be triggered using survey record number in the utterance.\n- Updated branding of Now Assist to Otto, inline with the Otto directive.\n- Performance improvements to the Analyze task trends agentic workflow.\n\n Fixed\n\n - Added 'Show Citations' toggle in the NAA guided-setup wizard for Record Resolution Notes.\n- Fixed greetings appearing in the Branded Email response generated by LLM.\n- Added 3P model support for replan skill as part of Generate my work plan agentic workflow.\n\n |
| \n\nPlaybook Experience\n\n | \n\n29.5.4\n\n | \n\nChanged\n\n Rebranding: Updated branding in Hybrid agentic activity and Use an AI agent from NowAssist to ServiceNow Otto.\n\n |
| \n\nPlaybook Experience Components\n\n | \n\n29.5.2\n\n | \n\nChanged\n\n Rebranding: Updated branding in Hybrid agentic activity and Use an AI agent from NowAssist to ServiceNow Otto.\n\n |
| \n\nPluralsight Spoke\n\n | \n\n1.3.0\n\n | \n\nFixed\n\n Resolved an issue where Pluralsight Spoke actions and datastreams stopped working as expected following Pluralsight's 2025 API deprecations. The spoke has been updated to use Pluralsight's current API endpoints, restoring end-to-end functionality for course and content synchronization, user activity ingestion, and the associated spoke actions used in HR learning workflows.\n\n |
| \n\nPOM - Prime\n\n | \n\n1.2.5\n\n | \n\nNow Assist has been renamed to ServiceNow Otto, ServiceNow's AI experience brand. As a result, references to Now Assist have been replaced with ServiceNow Otto.\n\n |
| \n\nPortfolio Planning\n\n | \n\n8.17.0\n\n | \n\nNew\n\n - View the demand summary card on the AI Overview tab of the demand record page when the demand summarization skill is active and accessible.\n- View and filter demand data using the Overview, Financials, and Data Quality tabs in Demands Dashboard.\n- View and manage cost plans, benefit plans, and baselines from the Financials grid in Demands.\n- Switch between the Dashboard and List views in Demands using the breadcrumb navigation.\n- View a related list of similar demands on the demand record page for quick access to system-identified matches.\n- Explore detailed data directly from the Demands Dashboard widgets using the widget drill-down capability.\n- Track Risks, Issues, Decisions, Actions, and Changes \\(RIDAC\\) for planning items directly within the workspace using related lists and configurable views on record pages, with role-based access for viewing and editing.\n- Use the L2 RIDAC menu to view all RIDAC items, project-specific RIDAC, portfolio risks, and program risks. Note that certain fields are read-only during and after creation.\n\n Changed\n\n The portfolio financials page now displays a budget value of 0 for planning items without an approved budget, ensuring accurate variance calculations and eliminating blank values.\n\n Fixed\n\n - Resolved an accessibility issue where the screen reader announced the value of the Rows Per Page dropdown more than once in Portfolio Planning.\n- Resolved an accessibility issue where roadmap keyboard shortcuts appeared as a one-time popup when tabbing through the interface. Shortcuts are now persistently accessible from the side panel.\n\n Removed\n\n - Removed the % Complete label from demand bars in the Roadmap tab, demand cards in the Kanban tab, and the % Complete column for demand rows in grid and list views, as demands do not support percent complete calculations.\n- Removed the standalone demand summarization component from the demand record page in Next Experience for Demand Management. The summary now appears only within the AI Overview tab.\n\n |
| \n\nPortfolio Planning Core\n\n | \n\n5.13.2\n\n | \n\nFixed\n\n Resolved an issue where execution URL and demand menu links from the portfolio plan grid, Kanban, and roadmap were broken due to a URL change introduced with the new L2 navigation.\n\n |
| \n\nPortfolio Planning integrations for Shared Infrastructure\n\n | \n\n3.12.2\n\n | \n\nFixed\n\n Resolved an issue where execution URL and demand menu links from the portfolio plan grid, Kanban, and roadmap were broken due to a URL change introduced with the new L2 navigation.\n\n |
| \n\nPortfolio Planning with PPM, Agile 2.0, and SAFe\n\n | \n\n4.7.2\n\n | \n\nFixed an L10 Warning and can now read property 'isValid' from undefined from 'Sync Data from execution to alignment' flow.\n\n |
| \n\nPrivacy Management Advanced\n\n | \n\n22.5.0\n\n | \n\nChanged\n\n ServiceNow OTTO Branding Updates\n\n Updated the application to reflect ServiceNow's new OTTO branding, replacing Now Assist references for a consistent AI experience across the platform.\n\n |
| \n\nProactive Engagement\n\n | \n\n5.1.1\n\n | \n\nSee DEX Application and Device Health product for release notes. This app is a dependency of DEX Application and Device Health.\n\n |
| \n\nProblem Management for Service Operations Workspace\n\n | \n\n9.3.1\n\n | \n\nUpdated plugin dependencies to ensure compatibility with the ServiceNow latest release.\n\n |
| \n\nProcess Automation Designer\n\n | \n\n29.5.6\n\n | \n\nNew\n\n - Playbooks as MCP tools: Access and run your Playbooks directly from your favorite MCP client.\n- New 'run as' option: The Hybrid Agentic Activity and Use an AI Agent activity now support running as the user who completed the previous activity.\n- Expanded autonomous mode: Hybrid Agentic Activity autonomous mode now supports custom form-based activities, with operations configurable in the activity definition.\n\n Changed\n\n Updated default model: Playbook generation skills now default to Azure OpenAI instead of NowLLM.\n\n |
| \n\nProcurement Case Management\n\n | \n\n19.0.7\n\n | \n\nFixed\n\n - Restricted purchase modification request access to a user's own records.\n- Applied security hardening to address CVE-2025-3648.\n\n |
| \n\nProduct Catalog Advanced\n\n | \n\n10.4.0\n\n | \n\nSupport multilanguage filtering for TMF-620 API.\n\n |
| \n\nProduct Catalog Management Core\n\n | \n\n19.2.0\n\n | \n\nNew\n\n Enable external integrations and in-platform applications to retrieve the eligible catalog-category tree hierarchy by using a REST endpoint.\n\n |
| \n\nProject Workspace\n\n | \n\n7.5.0\n\n | \n\nNew\n\n - Users can now customize L2 menu items in Project Workspace. Users are able to personalize the L2 menu without system issues, and their customization settings persist across sessions. When enabled by an administrator, the legacy RIDAC page is hidden to streamline navigation. Customization applies consistently for all users with appropriate permissions.\n- Project managers can view connected tasks and stories inline in the Planner tab. Connected CWM tasks and stories now display as child rows under each project task in the Planner, with standard columns shown and collapsible rows. Inline editing is disabled for these child tasks; edits can be made in the form view as permitted.\n- A toggle button is now available in Project Workspace settings to show or hide connected tasks. By default, the toggle is turned on, displaying all CWM and Project Workspace tasks. Turning it off hides connected tasks from view.\n\n Changed\n\n - Performance improvements have been made to AI-generated status reports. Status report generation now runs asynchronously, resulting in faster performance for the health widget and executive summary widget in In-App insights.\n- All customer-facing SPM product documentation now uses the 'ServiceNow Otto' name. References to 'Now Assist,' 'Moveworks,' and 'AI Experience' have been updated to 'ServiceNow Otto' in documentation, following the Otto Naming Guidelines.\n\n Fixed\n\n - Changes made in the Project Workspace Planning tab are now retained after refreshing the page. Previously, updates could be lost due to errors in handling planning attributes; this has been resolved.\n- The Status Report UI Action now opens the correct page without errors. The routing logic has been updated to ensure the status report page loads as expected.\n- Export logs from the Project Workspace now correctly indicate whether the export was performed from the Planning or Financials page, improving traceability.\n\n |
| \n\nPublic Sector Digital Services AI Agent Collection\n\n | \n\n1.6.0\n\n | \n\nServiceNow Otto Rebranding.\n\n |
| \n\nPurchase Order Management\n\n | \n\n2.2.7\n\n | \n\nChanged: Now Assist has been renamed to ServiceNow Otto, ServiceNow's AI experience brand. As a result, references to Now Assist have been replaced with ServiceNow Otto.\n\n |
| \n\nQuery Generation\n\n | \n\n6.2.2\n\n | \n\nIndicator Configuration - Allows users to promote indicators manually in AI Search results.\n\n |
| \n\nQuery Orchestrator\n\n | \n\n1.3.1\n\n | \n\nChanged\n\n Updated internal application components to support ongoing platform enhancements.\n\n |
| \n\nRecommendation template\n\n | \n\n22.5.1\n\n | \n\nChanged\n\n ServiceNow OTTO Branding Updates\n\n Updated the application to reflect ServiceNow's new OTTO branding, replacing Now Assist references for a consistent AI experience across the platform.\n\n |
| \n\nRecommended Actions for ITSM\n\n | \n\n3.4.1\n\n | \n\nChanged\n\n Now Assist Multi-Content Response Genius Results support.\n\n |
| \n\nRecommended Actions for Security Operations\n\n | \n\n2.3.3\n\n | \n\nChanged\n\n Now Assist has been rebranded as ServiceNow Otto.\n\n |
| \n\nRecord Page for Service Operations Workspace\n\n | \n\n9.3.2\n\n | \n\nUpdated plugin dependencies to ensure compatibility with the ServiceNow latest release.\n\n |
| \n\nRecord - vertical\n\n | \n\n22.5.2\n\n | \n\nChanged\n\n - Updated the application to reflect the new ServiceNow Otto branding, replacing Now Assist references and providing a more consistent AI experience across the platform.\n- The record page on Operational Sustainability management workspace for Campaigns now shows a tick mark when the actions in its related lists are completed.\n- It also groups the records within the related list based on the group field configured.\n\n |
| \n\nRemedial Actions Framework\n\n | \n\n9.3.3\n\n | \n\n- Admins can now configure remedial actions for both device and non-device scenarios. The system supports defining remedial actions with an action type \\(device or non-device\\), consent requirements, and applicability for specific roles such as AI Specialist.\n- API consumers can now retrieve remedial actions by applicability. An API endpoint is available to fetch a list of remedial actions relevant to a specified applicability, including action identifiers, names, and consent requirements.\n\n |
| \n\nRequest Management for Service Operations Workspace\n\n | \n\n9.3.1\n\n | \n\nUpdated plugin dependencies to ensure compatibility with the ServiceNow latest release.\n\n |
| \n\nResource Management Workspace\n\n | \n\n5.9.3\n\n | \n\nFixed\n\n - Filtering for unassigned tasks in Resource Management Workspace no longer creates blank resource cards; the filter now shows only relevant cards.\n- The Resource Management Workspace tooltip now correctly shows 'Pending' status instead of a null value after updates.\n- Resource Management Workspace no longer generates additional assignments with zero person days; assignments are created only when resources are available and effort is sufficient.\n- The Unassigned Assignment Requests dashboard in Resource Management Workspace now filters correctly by unassigned task start date.\n- The new resource assignment modal in Resource Management Workspace now loads correctly when domain determination is enabled.\n- Notes no longer duplicate when you assign an unassigned assignment from Resource Management Workspace.\n- Expand All now calculates correctly when grouping by primary resource group.\n- Resource realign calls and realign buttons now disable correctly when the auto-realign property is configured.\n- Color coding now displays correctly when grouping by owner using resource manager impersonation.\n\n |
| \n\nRetail Core\n\n | \n\n7.5.0\n\n | \n\nChanged: Added a plugin-gated 'In-Store Ops Tasks' tab to the RSM portal Home page and Cases and amp; Tasks page.\n\n |
| \n\nRoadmap UI Builder Component\n\n | \n\n22.14.0\n\n | \n\nNew\n\n Access the Roadmap Component shortcuts modal from the side panel for a more consistent experience when viewing and managing roadmap shortcuts.\n\n Fixed\n\n - Resolved an accessibility issue where the close button on roadmap item popovers incorrectly included the aria-pressed attribute and was presented as a toggle button.\n- Resolved an accessibility issue where the No Roadmap Milestones tooltip help button was not included in the tab order and did not respond to the Enter key.\n\n |
| \n\nRPA Hub\n\n | \n\n18.1.2\n\n | \n\nChanged\n\n - Improved the ability to map credential records to automation processes, enhancing configuration flexibility for RPA administrators.\n- Enhanced the functionality for organizing and grouping robots to improve automation distribution and workload management.\n- Security enhancements to strengthen authorization controls and data protection across the application.\n\n |
| \n\nRPA Plugin Bundle\n\n | \n\n18.0.4\n\n | \n\nChanged\n\n - Improved the ability to map credential records to automation processes, enhancing configuration flexibility for RPA administrators.\n- Enhanced the functionality for organizing and grouping robots to improve automation distribution and workload management.\n- Security enhancements to strengthen authorization controls and data protection across the application.\n\n |
| \n\nRSM - Advanced\n\n | \n\n1.1.1\n\n | \n\nNow Assist is becoming ServiceNow Otto. Otto is the unified AI experience through which people interact with ServiceNow's intelligence in natural language to get work done.\n\n |
| \n\nRSM - Foundation\n\n | \n\n1.1.1\n\n | \n\nNow Assist is becoming ServiceNow Otto. Otto is the unified AI experience through which people interact with ServiceNow's intelligence in natural language to get work done.\n\n |
| \n\nRSM - Prime\n\n | \n\n1.1.1\n\n | \n\nNow Assist is becoming ServiceNow Otto. Otto is the unified AI experience through which people interact with ServiceNow's intelligence in natural language to get work done.\n\n |
| \n\nSales and Order Management for Technology Provider - Advanced\n\n | \n\n1.0.7\n\n | \n\nUnderline application released.\n\n |
| \n\nSales and Order Management for Technology Provider - Prime\n\n | \n\n1.0.6\n\n | \n\nSKU plugin.\n\n |
| \n\nSales and Order Management for Telecommunications, Media and Technology - Advanced\n\n | \n\n1.0.6\n\n | \n\nSKU plugin.\n\n |
| \n\nSales and Order Management for Telecommunications, Media and Technology - Prime\n\n | \n\n1.0.8\n\n | \n\nSKU Application Container.\n\n |
| \n\nSales and Order Management for Telecommunications - Advanced\n\n | \n\n2.2.2\n\n | \n\nChangedMaintenance release - dependency updates only; no new customer-facing functionality in this version.\n\n |
| \n\nSales and Order Management for Telecommunications - Prime\n\n | \n\n2.2.1\n\n | \n\nChangedMaintenance release - dependency updates only; no new customer-facing functionality in this version.\n\n |
| \n\nSales and Service API Core\n\n | \n\n7.3.5\n\n | \n\nNew: Not applicable.\n\n Change: Performance improvements.\n\n |
| \n\nSales Common\n\n | \n\n8.0.2\n\n | \n\nMinor performance improvements and defect fixes.\n\n |
| \n\nSales Development AI Agents\n\n | \n\n1.0.10\n\n | \n\nFluent based development support added.\n\n |
| \n\nScan Engine\n\n | \n\n5.0.2\n\n | \n\nNew\n\n - Scan-time completion warnings - Added warnings during scan execution when the selected Suite Scan may not meet the requirements needed to complete an Update Set or application workflow.\n- New statistical rule detection type - Added support for a new statistic detection type for Scan Engine statistical rules, including schema validation and compile/decompile support.\n\n Changed\n\n Clearer Suite Scan messaging - Improved labels, descriptions, and enforcement messaging for Update Set and Application Suite Scan settings. Users now receive clearer guidance when Suite Scan is unavailable, including restricted actions and recommended next steps.\n\n Fixed\n\n - Full-table custom definition scanning restored - Restored support for custom Scan Engine definitions that scan entire tables. Additional warning guidance is now provided when targeting the System Properties table.\n- Improved Platform Health Analytics dashboard performance to reduce load times.\n- Corrected findings count inconsistencies in Platform Owner dashboard views.\n- Fixed Update Set enforcement issues when complex AND/OR conditions are configured.\n- Resolved exception-handling issues affecting findings during rescans.\n- Corrected clone behaviour for resolved finding history records.\n- Fixed localisation issues in My Resolved Findings.\n- Resolved UI branding and consistency issues across Health Findings, and AI Code Review pages.\n\n |
| \n\nSchedule Optimization\n\n | \n\n29.0.22\n\n | \n\nMade Security enhancements on Schedule Optimization store app compatible to Australia release.\n\n No Actions needed from customer while upgrading to this version.\n\n |
| \n\nScreen Summarization\n\n | \n\n1.2.6\n\n | \n\nUpdated icon and wording to align with ServiceNow's latest AI visual experience.\n\n |
| \n\nSecurity Incident Response\n\n | \n\n14.1.5\n\n | \n\nFixed\n\n - Fixed an issue where analysts could not interact with Overview tab widgets or closure modal links in the Security Incident Response Workspace.\n- Fixed an issue where the Configure button on the Post Incident Review Assessments Setup page did not respond due to a client-script error.\n- Improved accessibility by ensuring screen reader users are notified when a quick link is added on the Security Incident Response Workspace home page \\(WCAG 3.2.2 compliance\\).\n- Fixed an issue in the Security Operations Integration - Publish to Watchlist V1 integration flow where a single Capability Implementation input incorrectly triggered execution of all active implementations.\n\n |
| \n\nSecurity Incident Response Workspace\n\n | \n\n1.9.9\n\n | \n\nUsers can now preview attachments in a configurable upload modal before completing the upload process.\n\n - Translations now display correctly on Quick filters in Security Incident Workspace.\n- Heading levels in Security Incident Response are now sequential, improving accessibility and screen reader compatibility.\n- The relationship graph in Security Incident Workspace now supports localization and displays translated content.\n- Users can now close security incidents from the closure modal, even when the active tab is not the details tab.\n\n |
| \n\nSecurity Support Common\n\n | \n\n30.5.5\n\n | \n\nFixed\n\n - Security tags are now correctly applied to Security Incident Response records when hierarchical conditions are used in filter groups.\n- URLs are now correctly recognized as observable data types.\n- Resolved an issue where duplicate assignment records were being loaded.\n\n |
| \n\nService Level Management Experience for Workspace\n\n | \n\n9.3.1\n\n | \n\nUpdated plugin dependencies to ensure compatibility with the ServiceNow latest release.\n\n |
| \n\nServiceNow AI Lens\n\n | \n\n8.0.1\n\n | \n\nNew\n\n - Use ServiceNow AI Lens from your browser to upload one or more files for AI Lens to analyze and auto-fill form fields - no installation required.\n- Use Lens as a Service to map the data from multiple related Excel column headers and values to a single ServiceNow table field.\n- Use Lens as a Service to auto-map an Excel column header and its values from a single Excel sheet to multiple ServiceNow table fields simultaneously.\n- Choose how AI Lens opens when you start a session - from your browser or the desktop application. You can update this preference at any time.\n\n Changed\n\n Updated the AI experience branding in AI Lens to align with ServiceNow Otto naming and visual guidelines.\n\n |
| \n\nServiceNow AI Lens Core\n\n | \n\n8.0.1\n\n | \n\nNew\n\n - Use ServiceNow AI Lens from your browser to upload one or more files for AI Lens to analyze and auto-fill form fields - no installation required.\n- Use Lens as a Service to map the data from multiple related Excel column headers and values to a single ServiceNow table field.\n- Use Lens as a Service to auto-map an Excel column header and its values from a single Excel sheet to multiple ServiceNow table fields simultaneously.\n- Choose how AI Lens opens when you start a session - from your browser or the desktop application. You can update this preference at any time.\n\n Changed\n\n Updated the AI experience branding in AI Lens to align with ServiceNow Otto naming and visual guidelines.\n\n |
| \n\nServiceNow IDE\n\n | \n\n4.4.4\n\n | \n\nNew\n\n - Use ServiceNow IDE capabilities within ServiceNow Studio to create apps in source code. Use the new Explorer tab to open Fluent files and see underlying Fluent source code.\n- Upgrade to the new version of source control in ServiceNow Studio to access more features, such as additional Git commands.\n\n Changed\n\n ServiceNow Otto is the new AI experience brand. This change is reflected in the name of ServiceNow products, including ServiceNow Studio. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features.\n\n |
| \n\nServiceNow Otto Agents for requestor\n\n | \n\n3.7.2\n\n | \n\nApproval checklist generation skill now supports passing the request body in place of the Approval ID.\n\n Now Assist introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n |
| \n\nServiceNow Otto AI web agent\n\n | \n\n32.0.6\n\n | \n\nNew\n\n Preserve context across long-running sessions by summarizing older step history instead of discarding it. When history exceeds the configured window, older steps are automatically summarized instead of being discarded. They preserve context about earlier actions, failed approaches, and application state.\n\n Three new system properties let you configure how adaptive desktop actions step history is compacted:\n\n - Sn\\_naa.web\\_agent.compaction\\_enabled.\n- Sn\\_naa.web\\_agent.compaction\\_history\\_limit.\n- Sn\\_naa.web\\_agent.summarization\\_batch\\_size.\n\n Changed\n\n - Adaptive desktop actions are now batched for better performance. Multiple actions execute per LLM call instead of one call per action that reduces the round-trip latency that previously limited production readiness.\n- ServiceNow Otto is the new AI experience brand. This change is reflected in the name of ServiceNow products, including AI Desktop Actions. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features.\n\n |
| \n\nServiceNow Otto context menu\n\n | \n\n3.8.3\n\n | \n\n- \\[Otto Directive\\]: Renaming of Now assist to ServiceNow Otto.\n- Defect fixes and minor performance enhancements.\n\n |
| \n\nServiceNow Otto Conversational Data Collection\n\n | \n\n10.2.8\n\n | \n\n- Custom skills display line breaks incorrectly in Now Assist Panel.\n- Data Collector doesn't trigger search after 3 retries.\n- Skill name is incorrectly extracted during slot filling.\n- User responses aren't translated back during dynamic translation.\n\n |
| \n\nServiceNow Otto for Accounts Payable Operations \\(APO\\)\n\n | \n\n8.1.0\n\n | \n\nNow Assist has been renamed to ServiceNow Otto, ServiceNow's AI experience brand. As a result, references to Now Assist have been replaced with ServiceNow Otto.\n\n |
| \n\nServiceNow Otto for AIRC\n\n | \n\n22.5.1\n\n | \n\nChanged\n\n ServiceNow OTTO Branding Updates\n\n Updated the application to reflect the new ServiceNow OTTO branding, replacing Now Assist references and providing a more consistent AI experience across the platform.\n\n |
| \n\nServiceNow Otto for AI Search\n\n | \n\n17.2.7\n\n | \n\nChanged\n\n Now Assist in AI Search has been renamed to ServiceNow Otto for AI Search, reflecting ServiceNow's broader AI product branding. References throughout the product experience have been updated accordingly.\n\n Fixed\n\n - Synthesized Answer consistency for Gemini and Anthropic models. Addressed inconsistent prompt instructions that resulted in and lt;response and gt; field to sometimes appear under and lt;thinking and gt; and sometimes be missing altogether, causing streaming issues.\n- Added sys\\_property gate to skip catalog price field in GR citation builder to avoid performance degradation.\n\n |
| \n\nServiceNow Otto for App Engine\n\n | \n\n29.2.7\n\n | \n\nChanged\n\n Updated to support the ServiceNow Otto brand.\n\n |
| \n\nServiceNow Otto for Automation Center\n\n | \n\n1.3.0\n\n | \n\n- ServiceNow Otto is the new AI experience brand. This change is reflected in the name of ServiceNow products, including Automation Center. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features.\n- The Now Assist for Automation Center plugin is now renamed to ServiceNow Otto for Automation Center.\n\n |
| \n\nServiceNow Otto for Care Team Operations\n\n | \n\n2.0.6\n\n | \n\nNow Assist for Care Team Operations has been renamed to ServiceNow Otto for Care Team Operations.\n\n |
| \n\nServiceNow Otto for Code\n\n | \n\n28.5.28\n\n | \n\nChanged\n\n Name change from Now assist to ServiceNow Otto.\n\n Fixed\n\n General fixes and enhancements.\n\n |
| \n\nServiceNow Otto for Collaborative Work Management \\(CWM\\)\n\n | \n\n6.2.3\n\n | \n\nNew\n\n SPM's Project Workspace now has an integration with Collaborative Work Management\n\n - Team Members can create new CWM tasks/stories under an assigned project task.\n- Users can move or break a CWM task's connection to a different project task.\n- Project Managers will see CWM tasks/stories connected to their project tasks directly inline in the Planning page of the Project in Project Workspace.\n- Team Members in CWM see their connected project and project tasks as columns in CWM list view, and in 'My Work'.\n\n Changed\n\n - Relationships for any task types can added now using Task number/id instead of just Task description.\n- Now Assist is now rebranded as ServiceNow Otto.\n\n |
| \n\nServiceNow Otto for Configuration Management Database \\(CMDB\\)\n\n | \n\n4.2.0\n\n | \n\nNew\n\n - Added summarization to the CMDB success advisor for HAM dashboard.\n- Added summarization to the CMDB success advisor for Data Foundations dashboard.\n\n Fixed\n\n Security fixes.\n\n |
| \n\nServiceNow Otto for Contract Analysis\n\n | \n\n1.0.15\n\n | \n\nStarting with v1.0.15, Now Assist for Software Asset Management is now ServiceNow Otto for Software Asset Management.\n\n |
| \n\nServiceNow Otto for Contract Management Pro\n\n | \n\n2.4.6\n\n | \n\nChanged\n\n ServiceNow Otto is the new AI experience brand. Now Assist in Contract Management is now ServiceNow Otto for Contract Management Pro.\n\n |
| \n\nServiceNow Otto for Conversational Spokes\n\n | \n\n1.1.2\n\n | \n\nRebranding from Now Assist to ServiceNow Otto.\n\n |
| \n\nServiceNow Otto for Core Business Suite\n\n | \n\n3.3.2\n\n | \n\n- Added new AI skills module under the Platform module on Configuration console. It enables admins to activate knowledge-specific skills from simplified setup.\n- Improve article optimization in terms of content quality, identification, and merging duplicate articles to eliminate redundant content.\n- Shipped Now Assist search sources for all the business units to generate knowledge article from the BU case tables on the Knowledge center.\n- Create contextually relevant articles from case tables and drive better AI-assisted content creation by enabling Knowledge Content Recommendation skill from AI skills module.\n\n |
| \n\nServiceNow Otto for CPQ\n\n | \n\n1.1.4\n\n | \n\n1. App dependency for sn\\_cpq\\_cfg\\_ai\\_a2a2. Support enforced for min glide version of Australia Patch 2 and Zurich Patch 10 respectively.\n\n |
| \n\nServiceNow Otto for Creator\n\n | \n\n29.5.6\n\n | \n\nChanged\n\n - ServiceNow Otto branding.\n- Please click on the individual dependent apps included with this package for detailed release note information.\n\n |
| \n\nServiceNow Otto for CSM Complaint Case\n\n | \n\n2.2.1\n\n | \n\nApp renamed to ServiceNow Otto for CSM Complaint Case.\n\n |
| \n\nServiceNow Otto for CSM Major Issue Management\n\n | \n\n1.2.4\n\n | \n\nRename the app to Now Assist for CSM Major Issue Management.\n\n |
| \n\nServiceNow Otto for Customer Service Management \\(CSM\\)\n\n | \n\n14.2.0\n\n | \n\nServiceNow Otto is the new Al experience brand. This change is reflected in the name of ServiceNow products, including Customer Service Management. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features.\n\n |
| \n\nServiceNow Otto for Document Voice\n\n | \n\n2.0.9\n\n | \n\nChanged\n\n Enhanced the voice Q and amp;A experience.\n\n Fixed\n\n Fixed a few UI issues that occurred when closing voice Q and amp;A sessions.\n\n |
| \n\nServiceNow Otto for Employee Center Pro\n\n | \n\n1.2.4\n\n | \n\nUpdated to support the latest version of the dependent apps.\n\n |
| \n\nServiceNow Otto for Employee Experience\n\n | \n\n4.4.3\n\n | \n\nOtto rebranding: All references to AIA, Moveworks, or Now Assist are replaced with Otto throughout. You can see Otto as the assistant in all relevant interfaces and documentation.\n\n |
| \n\nServiceNow Otto for Enterprise Architecture \\(EA\\)\n\n | \n\n7.5.2\n\n | \n\nAdded support for linked text in Enterprise Architecture query agent responses. Selecting a linked record opens that record directly in Enterprise Architecture Workspace.\n\n Changed\n\n Rebranded Now Assist to ServiceNow Otto. The product name Now Assist for Enterprise Architecture is updated to ServiceNow Otto for Enterprise Architecture as part of the rebranding initiative.\n\n |
| \n\nServiceNow Otto for Enterprise Asset Management\n\n | \n\n1.1.2\n\n | \n\nChanged\n\n All visible references to 'Now Assist' have been updated to 'ServiceNow Otto' to ensure consistent branding.\n\n |
| \n\nServiceNow Otto for Error Framework\n\n | \n\n1.1.9\n\n | \n\nChanged: AMB Insights introduced.\n\n |
| \n\nServiceNow Otto for Field Service Management\n\n | \n\n11.0.6\n\n | \n\nNew\n\n Fluent based development support added.\n\n Changed\n\n ServiceNow Otto is the new Al experience brand. This change is reflected in the name of ServiceNow products, including Field Service Management. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features.\n\n Fixed\n\n Removed\n\n |
| \n\nServiceNow Otto for Finance and Procurement\n\n | \n\n7.1.0\n\n | \n\nNow Assist has been renamed to ServiceNow Otto, ServiceNow's AI experience brand. As a result, Now Assist for FSC Common is now ServiceNow Otto for Finance and Procurement.\n\n |
| \n\nServiceNow Otto for Financial Services Operations \\(FSO\\)\n\n | \n\n3.4.2\n\n | \n\nChanged\n\n - Updated internal application components to support ongoing platform enhancements.\n- Updated 'ServiceNow Otto' branding for ServiceNow Otto for Financial Services Operations \\(FSO\\).\n\n |
| \n\nServiceNow Otto for Hardware Asset Management\n\n | \n\n4.7.0\n\n | \n\nThis release rebrands Now Assist to ServiceNow Otto. Previous references to Now Assist inside Hardware Asset Workspace have been replaced with new verbiage.\n\n |
| \n\nServiceNow Otto for Health and Safety\n\n | \n\n1.5.1\n\n | \n\nUnified AI branding across Health and Safety interfaces. All customer-facing references to 'Now Assist,' 'Moveworks,' and 'AI Experience' have been replaced with 'ServiceNow Otto' in Health and Safety. Design review has confirmed consistency across UI elements, tooltips, images, and documentation.\n\n Changed\n\n GenAI capabilities now default to third-party model providers. Four Health and Safety GenAI features have updated their default model provider from Now LLM to the best-performing third-party provider \\(Azure OpenAI, Google Gemini, or AWS Claude\\) per capability. No Now LLM defaults remain in GenAI workflows.\n\n |
| \n\nServiceNow Otto for HR Service Delivery \\(HRSD\\)\n\n | \n\n13.4.1\n\n | \n\nNow Assist introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n New Skills released:Activity Response Generation skill:\n\n - Actions surface in case record: Suggest response, Post response, Refine.\n- 'Suggest a response' generates a relevant, non-empty AI response for an HR case with sufficient activity context.\n\n |
| \n\nServiceNow Otto for ICW\n\n | \n\n1.1.0\n\n | \n\nChanged in this release: ServiceNow Otto for Industrial Connected Workforce is the new name for Now Assist for ICW.\n\n |
| \n\nServiceNow Otto for Impact\n\n | \n\n5.0.2\n\n | \n\nWhat's changing.\n\n As part of ServiceNow's broader move to unify its AI capabilities under one brand, ServiceNow Otto, several Now Assist-powered skills within Impact have been renamed. This is a branding update only - the underlying functionality, workflows, and outputs you rely on today are unchanged.\n\n What this means for you.\n\n - Any menu labels, skill names, or references to 'Now Assist' for these two capabilities will now show as 'Otto' across the Impact UI.\n- How you invoke these skills, the outputs they generate, or your entitlements/licensing remains the same.\n\n |
| \n\nServiceNow Otto for Integrated Risk Management\n\n | \n\n22.5.0\n\n | \n\n\\*\\*New\\*\\*.\n\n \\*\\*Changed\\*\\*All references to 'Now Assist for IRM' have been renamed to 'ServiceNow Otto for Integrated Risk Management' in the Australia Patch4 and Zurich latest patch versions.\n\n \\*\\*Fixed\\*\\*.\n\n - The display properties for ServiceNow Otto for Integrated Risk Management plug-in updated, so that System Admins can install this plug-in.\n- Install-as-dependency settings also have been updated to ensure correct application visibility and dependency management.\n\n \\*\\*Removed\\*\\*.\n\n |
| \n\nServiceNow Otto for Integration Hub\n\n | \n\n2.3.2\n\n | \n\nChanged: Name change from Now assist to ServiceNow Otto.\n\n |
| \n\nServiceNow Otto for IT Operations Management \\(ITOM\\)\n\n | \n\n2.9.2\n\n | \n\nNew\n\n AIOps AI Specialist:\n\n - Operator-reopened alerts get full AI investigation automatically. When a human operator reopens an alert that the AI previously closed as noise, the system bypasses noise classification for the rest of that alert's lifecycle and runs a complete investigation - ensuring human overrides are respected and learned from.\n- AI-handled alerts are automatically returned to the original operator. After the AIOps AI Specialist completes its analysis or remediation, the alert is reassigned back to the human who originally owned it, preserving all AI-generated context and notes.\n- AWS Claude is now supported as an AI agent provider, expanding the choice of underlying AI models for automated workflows.\n\n Changed\n\n All Now Assist references changed to ServiceNow Otto.\n\n AIOps AI Specialist:\n\n - AIOps AI Specialist auto-assignment no longer overrides human ownership. The AIOps AI Specialist will not automatically take over alerts already assigned to a human operator, reducing unwanted reassignments and keeping accountability clear.\n- When the AIOps AI Specialist is manually triggered on a human-assigned alert, the alert returns to its original owner after AI processing - with configuration options to control behavior for noisy or previously assigned alerts.\n\n Fixed\n\n AIOps AI Specialist\n\n Fixes and improvements.\n\n |
| \n\nServiceNow Otto for IT Service Management \\(ITSM\\)\n\n | \n\n17.0.5\n\n | \n\nNew\n\n - AI can now automatically complete Change Risk Assessment and Dynamic Schema questions based on the change record's context, showing its reasoning for each answer so admins and change managers can verify or correct it. Answers that identify compliance exposure \\(for example SOX, PCI-DSS, or HIPAA\\) automatically populate the matching Dynamic Schema fields.\n- A new AI agent can diagnose and resolve common Okta account lockouts and MFA failures reported through an incident or self-service, checking live account status and submitting the correct unlock or reset request automatically.\n- A new Teams-native AI agent lets shift agents manage on-call coverage directly in chat - requesting coverage or leave, and asking questions like 'who is on call' or 'when is my next shift.'.\n- Employees creating a ticket in Service Portal now see an AI-generated suggestion - drawn from relevant knowledge articles and catalog items - before they submit, based on the ticket description and their hardware, location, and department.\n\n Changed\n\n - ServiceNow Otto, Moveworks, and 'AI Experience' branding has been renamed to ServiceNow Otto across in-product labels, icons, tooltips, and documentation.\n- Incident Managers can now drill from any indicator on the Insights and Opportunities dashboard directly into the underlying incident records without losing their place on the dashboard.\n- A new dashboard section shows how closely AI-proposed solutions in Copilot \\(supervised\\) mode matched what human agents ultimately implemented.\n- The employee consent experience for remedial actions is more consistent and accurate: duplicate requests are no longer triggered for already-approved or declined actions, and messaging now notes when a device needs to stay online.\n- The DEX Diagnosis AI agent now factors in event monitoring logs and statistical anomaly signals alongside existing telemetry for more accurate root-cause diagnoses, and now surfaces the specific evidence behind each conclusion.\n\n Fixed\n\n - Fixed an issue where the summarize capability could produce an irrelevant summary on requested items with many related records.\n- Fixed an issue where several AI agents \\(including Zscaler, Installed Apps, and Modern Change agents\\) had read-only configuration, preventing customers from disabling them.\n- Fixed an issue where the Zscaler and Installed Apps agents' action engagement tools showed an empty timeout field.\n- Corrected a remaining reference to the previous Now Assist branding that had been missed during the ServiceNow Otto rename.\n- Fixed an issue on the Insights and Opportunities dashboard where assigning an incident to a cluster could fail and prevent clustering from completing.\n- Fixed a date-formatting issue in the Change Outage Assistant AI agent.\n- Fixed a security issue that allowed any authenticated user, regardless of role, to invoke ITSM AI agents and skills that should have been role-restricted.\n- Fixed an issue where the incident investigation and resolution workflow could fail with an 'incident search/read service unavailable' error.\n- Fixed an issue where the knowledge-article search filters used by the Create Incident AI agent were not being applied correctly.\n- Reordered the metrics on the Copilot Performance dashboard so the '80% or higher similarity' metric appears first.\n- Improved the error message shown for the Resolution Notes generation skill when the 'display in product desktop' setting is turned off.\n- Reduced processing time for the Generate Change Request Plans AI flow, which had been taking an unusually long time to complete.\n- Fixed an issue where built-in ITSM AI agents were unintentionally discoverable and visible within the Now Assist Platform.\n- Fixed an issue where a required role was missing from the Link Major Incident agent's flow, which could prevent the agent from working as expected for some users.\n- Fixed an issue where the Triage and Categorize AI agent could assign an irrelevant, caller-owned device as the configuration item when the matched service offering had no related configuration items of its own.\n\n Removed\n\n No items removed in this release.\n\n |
| \n\nServiceNow Otto for Knowledge Management\n\n | \n\n30.12.12\n\n | \n\nAuto-update, auto-merge and otto branding updates.\n\n |
| \n\nServiceNow Otto for Legal Service Delivery\n\n | \n\n1.9.4\n\n | \n\nChanged\n\n ServiceNow Otto is the new AI experience brand. Now Assist for Legal Service Delivery is ServiceNow Otto for Legal Service Delivery.\n\n Fixed\n\n The ServiceNow Otto panel now starts a single chat session for a legal request record instead of opening multiple concurrent sessions.\n\n |
| \n\nServiceNow Otto for Manufacturing Commercial Operations \\(MCO\\)\n\n | \n\n3.3.0\n\n | \n\nHttps://docs-preview.corp.service-now.com/bundle/australia-release-notes/page/release-notes/manufacturing-commercial-operations-rn.html.\n\n |
| \n\nServiceNow Otto for Operational Sustainability\n\n | \n\n22.5.1\n\n | \n\nServiceNow Otto Branding Updates Updated the application to reflect the new ServiceNow Otto branding, replacing Now Assist references and providing a more consistent AI experience across the platform.\n\n |
| \n\nServiceNow Otto for Opportunity Management\n\n | \n\n1.1.8\n\n | \n\nRenamed the plugin from Opportunity management AI feature' to 'ServiceNow Otto for Opportunity Management.\n\n Provides more clear Error messages on Claude for a few scenarios.\n\n |
| \n\nServiceNow Otto for Order Management\n\n | \n\n2.3.2\n\n | \n\nServiceNow Otto is the new AI experience brand. This change is reflected in the name of ServiceNow products, including Now Assist for Order Management. Your product entitlements remain unchanged. There is no change to functionality or existing customer configurations.\n\n |
| \n\nServiceNow Otto for OT Service Management\n\n | \n\n3.1.5\n\n | \n\nNew\n\n Updated to support the ServiceNow Otto brand.\n\n |
| \n\nServiceNow Otto for Platform\n\n | \n\n12.2.0\n\n | \n\nThe application captures dependencies, updated the plugin dependencies for this release.\n\n |
| \n\nServiceNow Otto for Platform Advanced\n\n | \n\n2.2.0\n\n | \n\nThe application captures dependencies, updated the plugin dependencies for this release.\n\n |
| \n\nServiceNow Otto for Platform Foundation\n\n | \n\n2.2.0\n\n | \n\nThe application captures dependencies, updated the plugin dependencies for this release.\n\n |
| \n\nServiceNow Otto for Platform Prime\n\n | \n\n2.2.0\n\n | \n\nThe application captures dependencies, updated the plugin dependencies for this release.\n\n |
| \n\nServiceNow Otto for Privacy Management\n\n | \n\n22.5.0\n\n | \n\nChanged\n\n ServiceNow OTTO Branding Updates\n\n Updated the application to reflect ServiceNow's new OTTO branding, replacing Now Assist references for a consistent AI experience across the platform.\n\n |
| \n\nServiceNow Otto for Process Mining\n\n | \n\n3.2.0\n\n | \n\nChanged: the default NowLLM provider to a 3p model provider\\(Amazon bedrock\\)- Unable to Edit without creator role issue- Made GenAI Skill access rules customizable- Move GenAI skills to platform.\n\n |
| \n\nServiceNow Otto for Public Sector Digital Services \\(PSDS\\)\n\n | \n\n2.5.0\n\n | \n\nServiceNow Otto Rebranding.\n\n |
| \n\nServiceNow Otto for Purchase Order Management \\(POM\\)\n\n | \n\n1.3.4\n\n | \n\nChanged: Now Assist has been renamed to ServiceNow Otto, ServiceNow's AI experience brand. As a result, references to Now Assist have been replaced with ServiceNow Otto.\n\n |
| \n\nServiceNow Otto for Retail Service Management\n\n | \n\n1.5.1\n\n | \n\nNow Assist is becoming ServiceNow Otto. Otto is the unified AI experience through which people interact with ServiceNow's intelligence in natural language to get work done.\n\n |
| \n\nServiceNow Otto for RPA Hub\n\n | \n\n5.1.1\n\n | \n\nChanged\n\n Updated the AI experience branding in RPA Desktop Design Studio to align with ServiceNow Otto naming and visual guidelines.\n\n |
| \n\nServiceNow Otto for Sales and Order Management for Telecommunications\n\n | \n\n4.2.2\n\n | \n\nChangedMaintenance release - dependency updates only; no new customer-facing functionality in this version.\n\n |
| \n\nServiceNow Otto for Sales Automation\n\n | \n\n1.1.6\n\n | \n\nNew\n\n Fluent-based development support has been added.\n\n Changed\n\n The app has been renamed from 'Now Assist for Sales Force Automation \\(SFA\\)' to 'ServiceNow Otto for Sales Automation'.\n\n |
| \n\nServiceNow Otto for Security Incident Response \\(SIR\\)\n\n | \n\n6.4.5\n\n | \n\nChanged\n\n Now Assist has been renamed to ServiceNow Otto, ServiceNow's AI experience brand.\n\n Fixed\n\n Correlation Insight skill now supports optional security incident ID for MCP.\n\n |
| \n\nServiceNow Otto for Security Incident Response Integration Toolkit\n\n | \n\n1.2.5\n\n | \n\nFixed\n\n Rebranded 'Now Assist' to 'ServiceNow Otto' across the application.\n\n |
| \n\nServiceNow Otto for Service Quality\n\n | \n\n2.1.2\n\n | \n\n- New: ServiceNow Otto is the new AI Experience brand. This change is reflected in the name of ServiceNow products, including Now Assist for Service Quality. Your product entitlements remain unchanged.\n- Changed: The engine that evaluates a case when it's closed now runs as a single streamlined step instead of a longer chain of internal steps to minimize failures points.- The loading time of the Automated Quality Assurance dashboard is optimized to handle large number for records.\n\n |
| \n\nServiceNow Otto for Smart Assessment Engine\n\n | \n\n22.5.6\n\n | \n\nChanged\n\n ServiceNow Otto branding is now implemented across the Smart Assessment Engine \\(SAE\\) AI user interface. All customer-facing references to 'Now Assist' in SAE AI UI elements, labels, tooltips and images have been replaced with 'ServiceNow Otto'.\n\n |
| \n\nServiceNow Otto for Software Asset Management \\(SAM\\)\n\n | \n\n10.4.0\n\n | \n\nStarting with v10.4.0, Now Assist for Software Asset Management is now ServiceNow Otto for Software Asset Management.\n\n |
| \n\nServiceNow Otto for Sourcing and Procurement Operations \\(SPO\\)\n\n | \n\n10.1.0\n\n | \n\nChanged\n\n Now Assist has been renamed to ServiceNow Otto, ServiceNow's AI experience brand. As a result, Now Assist for Sourcing and Procurement Operations is now ServiceNow Otto for Sourcing and Procurement Operations.\n\n |
| \n\nServiceNow Otto for Spoke Generation\n\n | \n\n2.0.1\n\n | \n\nChanged: Servicenow Otto rename changes.\n\n |
| \n\nServiceNow Otto for Strategic Portfolio Management\n\n | \n\n9.8.0\n\n | \n\nNew\n\n - Use the Budget Overrun insight card in Portfolio AI Insights to view real-time analysis of planning items with forecasts over budget, including impact assessment, root cause analysis, and recommended next steps to proactively manage budget overruns and allocation decisions.\n- Updated all customer-facing references from 'Now Assist' to 'ServiceNow Otto' across SPM products and UI components.\n- Access a dedicated AI Overview tab for demand summarization on the demand record page.\n\n Changed\n\n - Project Q and amp;A now supports questions about work notes and dependencies on a project.\n- Improved the performance of AI project status report generation to create draft reports faster.\n- Improved the output quality and performance of goal insights generation.\n- Improved AI-identified risk generation with minor functional enhancements.\n\n |
| \n\nServiceNow Otto for Supplier Lifecycle Operations \\(SLO\\)\n\n | \n\n8.1.0\n\n | \n\nNow Assist has been renamed to ServiceNow Otto, ServiceNow's AI experience brand. As a result, references to Now Assist have been replaced with ServiceNow Otto.\n\n |
| \n\nServiceNow Otto for Talent\n\n | \n\n1.9.2\n\n | \n\nNow Assist introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n In this version, Now Assist for Talent app has been renamed to ServiceNow Otto for Talent.\n\n |
| \n\nServiceNow Otto for Telecommunications, Media and Technology \\(TMT\\)\n\n | \n\n6.0.13\n\n | \n\nMeeting V2 Agent is getting shipped.\n\n |
| \n\nServiceNow Otto for Telecommunications Service Management\n\n | \n\n2.2.1\n\n | \n\nOtto Rebranding.\n\n |
| \n\nServiceNow Otto for Third-Party Risk Management\n\n | \n\n22.5.0\n\n | \n\nUpdated.\n\n - Rebranded to ServiceNow Otto, replacing Now Assist references for a consistent AI experience.\n- Enhanced MRA authorization validation to ensure access checks are consistently enforced during record association.\n\n |
| \n\nServiceNow Otto for Threat Intelligence Security Center\n\n | \n\n2.4.0\n\n | \n\nNew\n\n Added support for Google Gemini 3.5 Flash and OpenAI GPT 5.4 mini models for Case summarization.\n\n Changed\n\n Now Assist has been renamed to ServiceNow Otto, ServiceNow's AI experience brand.\n\n |
| \n\nServiceNow Otto for Unified Security Exposure Management\n\n | \n\n5.2.3\n\n | \n\nEnhancements to the Security Exposure 360 feature:\n\n - Clickable Links to Records: Counts and findings in the Security Exposure 360 output are now directly clickable, linking you to the underlying vulnerable item \\(VITs\\)/records in your ServiceNow AI Platform instance.\n- Suggested follow-up questions: Suggested follow-up questions are provided that help you drill down.\n\n Changed\n\n Enhancements to support the ServiceNow Otto brand.\n\n |
| \n\nServiceNow Otto for Vault\n\n | \n\n2.2.2\n\n | \n\nChanged\n\n - Starting with Australia Patch 5, Now Assist for Vault is now ServiceNow Otto for Vault. This name change reflects the evolution of AI assistance on the platform into a conversational, agentic AI experience. All existing functionality, configurations, and AI-powered security capabilities are unchanged.\n- Azure OpenAI is now the default model for all AI assets in ServiceNow Otto for Vault, including the Discovery data pattern grouping skill and the Data Discovery Job Summarization skill. Existing configurations that use the Now LLM Service continue to work as before, and you can still select the Now LLM Service manually.\n\n |
| \n\nServiceNow Otto for Virtual Agent\n\n | \n\n21.0.8\n\n | \n\n--- AI Generated Release Notes ---.\n\n New\n\n Admins can now configure document upload at the assistant level. Admins can enable or disable document upload for each assistant, ensuring consistent behavior across all user interactions.\n\n Admins can create and assign MCP Server connections to assistants. Admins can set up MCP Server connections in AI Agent Studio, assign them to assistants, and configure role-based access for premium chat experiences.\n\n Admins can enable or disable estimated wait time display for Live Agent in Chat menu items. The option to show or hide estimated wait time is now available for Chat menu items of type 'Chat.'.\n\n System prevents creation of duplicate Chat menu items of type 'Chat' within an assistant. Only one Chat menu item of type 'Chat' can exist per assistant.\n\n Playbook skills are now supported in AI search sources for premium chat. The system returns playbook skills in applicable searches, enhancing Playbook visibility for ServiceNow Otto panel assistants.\n\n Admins can define custom persona policies, including parametric memory settings. A new Policy persona detail type is available, allowing admins to specify custom instructions such as disabling parametric memory.\n\n Admins can disable the test assistant button when prerequisites are not met. The test assistant button is disabled unless the assistant is active and required configurations are complete.\n\n Changed\n\n Product branding and assistant names updated from 'Now Assist' to 'ServiceNow Otto.' All UI components, pages, and customer-facing materials now reference 'ServiceNow Otto' instead of 'Now Assist,' including Assistant Designer, chat headers, and default assistant names.\n\n Search source names and topic names updated to be more customer-friendly. Multiple search sources and topics have been renamed to descriptive, user-focused labels.\n\n Enhanced Chat branding UI now clarifies dependency on selected branding profile. The branding configuration page clearly indicates that Enhanced Chat's branding relies on the selected profile.\n\n Basic details tab and AI agents tab enhancements. UI improvements include updated naming conventions, optional description fields, and clearer organization of assistant details.\n\n Welcome message management and AI prompt guidance improved for admins. Admins can select and manage localized welcome messages, update Voice AI agent content, and access in-product guidance for crafting effective AI prompts.\n\n Keyterm and pronunciation dictionaries added to the UI. Admins can manage keyterm and pronunciation dictionaries directly from the interface.\n\n Primary language configuration moved into the language config table. The system now inserts primary language records into the language table during deployment creation and updates logic for secondary language handling.\n\n Inactivity default timeout updated to 30 seconds. The system now uses a 30-second timeout for inactivity, replacing the previous 60-second default.\n\n Analysis tab now displays latency for all bot responses in voice mode. Latency values are shown next to timestamps for voice responses; chat mode displays a text flag.\n\n Secondary language edit functionality removed from the UI. The option to edit secondary language has been eliminated.\n\n Branding preview and disclaimers updated to reflect ServiceNow Otto branding. UI elements now show ServiceNow Otto branding in previews and disclaimers.\n\n Noise cancellation content updated for low, medium, and high categories. UI content for noise cancellation settings is revised for clarity and consistency.\n\n Fixed\n\n Error in setting the Assistant nickname and specialization through the Personalization page has been resolved. Assistant personalization now works as expected.\n\n |
| \n\nServiceNow Otto for Virtual Agent Configurations\n\n | \n\n16.0.3\n\n | \n\nChanged\n\n Otto renaming changes.\n\n |
| \n\nServiceNow Otto for Voice Agents\n\n | \n\n5.2.4\n\n | \n\nNew\n\n - STT Key Term Dictionary - Administrators can now configure custom key terms within language settings to improve speech-to-text recognition accuracy for domain-specific vocabulary.\n- Conversational Quality Controls - Voice pacing and readability settings are now configurable via the Agents API, enabling more natural and controlled interactions.\n- Expanded Language and amp; Voice Support - Added support for the following languages: Finnish, Czech, Slovakian, and Ukrainian.\n\n Fixed\n\n - Resolved an issue where the Test Assistant UI displayed empty message bubbles when a secondary language was enabled.\n- Fixed a plan handler error that prevented incoming plan IDs from being accepted correctly.\n- Updated default values on out-of-box deployments to reflect current configuration requirements.\n\n Changed\n\n Rebranding to ServiceNow Otto - ServiceNow Otto is the AI experience brand going forward. All product references to Now Assist have been updated to the ServiceNow Otto naming convention.\n\n |
| \n\nServiceNow Otto for WDF\n\n | \n\n2.3.4\n\n | \n\nNow Assist for Workflow Data Fabrics \\(WDF\\) has been renamed to ServiceNow Otto for Workflow Data Fabrics \\(WDF\\).\n\n |
| \n\nServiceNow Otto for Workplace Service Delivery \\(WSD\\)\n\n | \n\n1.1.20\n\n | \n\nNew\n\n Changed\n\n ServiceNow Otto is the new AI experience brand. This change is reflected in the name of ServiceNow products. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features.\n\n Fixed\n\n Removed\n\n |
| \n\nServiceNow Otto for Wrap Up\n\n | \n\n1.0.4\n\n | \n\nName updated to ServiceNow Otto for Wrap Up.\n\n |
| \n\nServiceNow Otto for Zero Copy Connector\n\n | \n\n2.0.6\n\n | \n\nName changes from Now Assist to Otto for Zero Copy Connector.\n\n Defect fixing.\n\n |
| \n\nServiceNow Studio\n\n | \n\n29.2.11\n\n | \n\nThis app is a dependency of ServiceNow Studio + ServiceNow IDE. Please see release notes for parent app.\n\n |
| \n\nService Operations Workspace Alert Automation\n\n | \n\n25.17.1\n\n | \n\nAdded.\n\n - Support multi-line text in enrich automation compose actions using a and lt;br and gt; tag.\n- When creating incidents in response automations, you can now set an incident field to a static value.\n\n Changed\n\n Now Assist has been renamed to ServiceNow Otto.\n\n |
| \n\nService Operations Workspace Alert Automation API\n\n | \n\n25.17.2\n\n | \n\nAdded.\n\n - Support multi-line text in enrich automation compose actions using a and lt;br and gt; tag.\n- When creating incidents in response automations, you can now set an incident field to a static value.\n\n Changed\n\n Now Assist has been renamed to ServiceNow Otto.\n\n |
| \n\nService Operations Workspace Alert Automation UI\n\n | \n\n25.17.1\n\n | \n\nAdded.\n\n - Support multi-line text in enrich automation compose actions using a and lt;br and gt; tag.\n- When creating incidents in response automations, you can now set an incident field to a static value.\n\n Changed\n\n Now Assist has been renamed to ServiceNow Otto.\n\n |
| \n\nService Operations Workspace Alert Mngmt\n\n | \n\n27.3.4\n\n | \n\nNew\n\n - Admins can set static values for incident fields in Event Management response automations. When creating incidents via advanced response automation, users can now assign fixed values or map alert fields to incident fields, restoring and extending previous functionality.\n- Admins can enter free text in the Create Incident Advanced subflow. The UI now supports free text input for incident field customization during incident creation in response automations.\n- Migration script updates the JSON formats for custom fields used in incident creation automations. A fix script migrates legacy data in incident field mapping to the new JSON format, ensuring compatibility and data integrity.\n- Compose actions now support multiline text. Users can enter, view, and edit structured, multi-line content in Alert Automation compose fields, with line breaks preserved and bidirectional compatibility with UI16.\n\n Fixed\n\n Alert automation in the Service Operations Workspace no longer hangs when changing the language to Portuguese.\n\n |
| \n\nService Operations Workspace Core\n\n | \n\n9.3.1\n\n | \n\nUpdated plugin dependencies to ensure compatibility with the ServiceNow latest release.\n\n |
| \n\nService Operations Workspace Express List\n\n | \n\n27.4.5\n\n | \n\nNew\n\n - Express list now supports color-coded visual cues to highlight values \\(based on existing definitions in sys\\_highlighted\\_value\\). Admins can configure conditional formatting rules on alert columns \\(e.g., severity, priority\\) so that critical items are immediately visible through colored indicators and icons - no more scanning through uniform rows.\n- Azure Monitor Issues now surface related alerts in context. A new 'Related Records' tab appears directly in the alert view for Azure Monitor Issues, letting operators drill into associated alerts without leaving their current workflow.\n\n Changed\n\n - Express List now fully supports right-to-left languages, including Arabic and Hebrew, with correct mirroring of layout, icons, and spacing.\n- All 'Now Assist' references across Service Operations Workspace, Express List, etc. have been rebranded to ServiceNow Otto.\n- The 'Probable Cause' tab in the Alerts Preview panel is now called 'Related Records' and includes Azure Monitor Issues.\n\n Fixed\n\n Express List no longer fails to load when a system property record has a missing type value.\n\n |
| \n\nService Operations Workspace Express List App\n\n | \n\n27.2.2\n\n | \n\nNew\n\n - Express list now supports color-coded visual cues to highlight values \\(based on existing definitions in sys\\_highlighted\\_value\\). Admins can configure conditional formatting rules on alert columns \\(e.g., severity, priority\\) so that critical items are immediately visible through colored indicators and icons - no more scanning through uniform rows.\n- Azure Monitor Issues now surface related alerts in context. A new 'Related Records' tab appears directly in the alert view for Azure Monitor Issues, letting operators drill into associated alerts without leaving their current workflow.\n\n Changed\n\n - Express List now fully supports right-to-left languages, including Arabic and Hebrew, with correct mirroring of layout, icons, and spacing.\n- All 'Now Assist' references across Service Operations Workspace, Express List, etc. have been rebranded to ServiceNow Otto.\n- The 'Probable Cause' tab in the Alerts Preview panel is now called 'Related Records' and includes Azure Monitor Issues.\n\n Fixed\n\n Express List no longer fails to load when a system property record has a missing type value.\n\n |
| \n\nService Operations Workspace Integrations launchpad\n\n | \n\n27.2.3\n\n | \n\nChanged\n\n Updated ServiceNow Otto branding for HLA data inputs integrations.\n\n |
| \n\nService Operations Workspace Integrations launchpad UI\n\n | \n\n27.2.3\n\n | \n\nChanged\n\n Updated ServiceNow Otto branding for HLA data inputs integrations.\n\n |
| \n\nService Operations Workspace ITOM Apps\n\n | \n\n27.2.17\n\n | \n\nNew\n\n - AI value is now visible on the AIOps 360 dashboard. A new widget shows estimated time saved based on how many alerts were resolved and analyzed by AI, giving operations teams a real-time view of AI's impact on their workload.\n- Alerts Express List now supports color-coded visual cues to highlight values \\(based on existing definitions in sys\\_highlighted\\_value\\). Admins can configure conditional formatting rules on alert columns \\(e.g., severity, priority\\) so that critical items are immediately visible through colored indicators and icons - no more scanning through uniform rows.\n\n Azure Monitor Issues now surface related alerts in context. A new 'Related Records' tab appears directly in the alert view for Azure Monitor Issues, letting operators drill into associated alerts without leaving their current workflow.\n\n Azure Monitor Issues are now bi-directionally synchronized with ServiceNow. The integration supports real-time ingestion of Azure Monitor Issues via webhook and polling, with two-way synchronization of status, severity, title, description, and AI-generated insights. OAuth 2.0 and multi-tenant Azure environments are supported.\n\n - Incident fields in response automations now support free text and static values. When creating incidents through automated alert responses, teams can now enter static text or map custom values to incident fields - restoring flexibility that was previously limited.\n- Integration setup instructions are now inline and on-page. Connector setup pages now include a collapsible instructions section covering source system configuration and credentials, eliminating the need to navigate away for documentation.\n\n Dynatrace Grail problem events are now fully supported. The new connector ingests Dynatrace Grail problem events and automatically binds alerts to the correct configuration item using root cause entity or CMDB tags. Davis AI context, severity mapping, and full event lifecycle \\(updates, reopens, merges\\) are supported - including predictive, RUM, synthetic, vulnerability, and business process anomaly events.\n\n Dynatrace Gen3 event payloads are now supported in the event push connector, alongside legacy formats - no migration required.\n\n - Admins can now limit the volume of related alerts retrieved per connector, giving control over data load in high-volume environments.\n- Alert Automation - Multiline text support in compose actions - On the Enrich page's compose action, the text field now supports multiple lines - the box resizes and preserves line breaks and spacing instead of collapsing everything into a single line. This fixes formatted alert descriptions rendering incorrectly downstream.\n- Alert Automation - Static values for incident fields in response automations - In the 'Create Incident Advanced' response automation action, users can now enter static text values for fields like urgency and priority \\(in addition to alert-field references\\) .\n\n Changed\n\n - Express List now fully supports right-to-left languages, including Arabic and Hebrew, with correct mirroring of layout, icons, and spacing.\n- All 'Now Assist' references across Service Operations Workspace, Express List, Integration Launchpad, and the AIOps AI Specialist onboarding have been rebranded to ServiceNow Otto.\n- The Probable Cause tab in the Alerts Preview panel is now called 'Related Records' and includes Azure Monitor Issues.\n- The Dynatrace Gen3 payload processor now handles both workflow-wrapped and raw Davis Gen3 payloads consistently, with improved severity mapping and entity tag preservation.\n\n Fixed\n\n - Alert automation no longer hangs when the interface language is set to Portuguese.\n- The AIOps Supervisor Homepage remains responsive when managing a large number of teammates.\n- Express List no longer fails to load when a system property record has a missing type value.\n\n |
| \n\nService Operations Workspace ITSM Admin Center\n\n | \n\n9.3.1\n\n | \n\nUpdated plugin dependencies to ensure compatibility with the ServiceNow latest release.\n\n |
| \n\nService Operations Workspace ITSM Advanced Applications\n\n | \n\n9.3.1\n\n | \n\nUpdated plugin dependencies to ensure compatibility with the ServiceNow latest release.\n\n |
| \n\nService Operations Workspace ITSM Applications\n\n | \n\n9.3.1\n\n | \n\nUpdated plugin dependencies to ensure compatibility with the ServiceNow latest release.\n\n |
| \n\nService Operations Workspace ITSM Common\n\n | \n\n9.3.1\n\n | \n\nUpdated plugin dependencies to ensure compatibility with the ServiceNow latest release.\n\n |
| \n\nService Operations Workspace Log Analytics\n\n | \n\n26.7.2\n\n | \n\nHidden app.\n\n |
| \n\nService Operations Workspace Supervisor Dashboard\n\n | \n\n1.3.3\n\n | \n\nChanged\n\n AIOps Supervisor Homepage updated for Otto branding. All text and icon references to 'Now Assist' are replaced with 'Otto' for brand consistency. No functional changes are introduced.\n\n Fixed\n\n The AIOps Supervisor Homepage now remains responsive even with a large number of teammates.\n\n |
| \n\nService Operations Workspace UI Components\n\n | \n\n27.3.4\n\n | \n\nChanged\n\n Otto rebranding changes.\n\n |
| \n\nSLO - Foundation\n\n | \n\n1.3.3\n\n | \n\nNow Assist has been renamed to ServiceNow Otto, ServiceNow's AI experience brand. As a result, references to Now Assist have been replaced with ServiceNow Otto.\n\n |
| \n\nSLO - Prime\n\n | \n\n1.3.3\n\n | \n\nNow Assist has been renamed to ServiceNow Otto, ServiceNow's AI experience brand. As a result, references to Now Assist have been replaced with ServiceNow Otto.\n\n |
| \n\nsn-actionable-insights\n\n | \n\n1.2.1\n\n | \n\nChanged\n\n Now Assist has been renamed to ServiceNow Otto, ServiceNow's AI experience brand.\n\n |
| \n\nsn-docs\n\n | \n\n7.8.0\n\n | \n\n- All references to Now Assist, Moveworks, and AI Experience in Docs have been renamed to ServiceNow Otto. The full name, ServiceNow Otto, is used in all customer-facing contexts except where UX character limits require shortening.\n- Artifact versions now render all content correctly, without requiring users to download or zoom out to view the full content.\n- Project Status Report in Project Workspace now maintains table width as expected.\n- Exported PDF documents in Project Workspace no longer truncate issues in portrait orientation.\n\n |
| \n\nsn-formula-kit\n\n | \n\n1.2.0\n\n | \n\nChanged: System administrators can decide the list of functions that display in the Formula columns.\n\n |
| \n\nsn-ia-summary-card\n\n | \n\n1.1.0\n\n | \n\nChanged\n\n Now Assist has been renamed to ServiceNow Otto, ServiceNow's AI experience brand.\n\n |
| \n\nsn-itom-ui-internal\n\n | \n\n27.5.3\n\n | \n\nChanged\n\n Otto rebranding changes.\n\n |
| \n\nsn-task-planner\n\n | \n\n22.13.0\n\n | \n\nNew\n\n - View and manage connected tasks and stories inline in the Planner tab. Connected CWM tasks and stories display as child rows under each project task with standard fields, and are collapsible per project task. Inline editing is disabled for child tasks - edits can be made in the form view based on user permissions.\n- Use the toggle in PWS settings to show or hide connected tasks. The toggle is enabled by default, displaying all CWM and PWS tasks. Disable the toggle to hide connected tasks.\n\n Changed\n\n A red indicator now appears on a project task row when a connected CWM child task's start or end date falls outside the parent task's date range, with a tooltip explaining the conflict. The indicator clears automatically when the dates are corrected.\n\n |
| \n\nSoftware Asset Management\n\n | \n\n4.1.5\n\n | \n\nIn this version, minor defects affecting reconciliation flow performance and lifecycle report have been resolved. System behavior is now consistent and reliable in these areas.\n\n |
| \n\nSoftware Asset Management AI Advanced\n\n | \n\n2.4.3\n\n | \n\nStarting with v2.4.3, Now Assist for Software Asset Management is now ServiceNow Otto for Software Asset Management.\n\n |
| \n\nSoftware Asset Management AI Prime\n\n | \n\n2.4.2\n\n | \n\nStarting with v2.4.2, Now Assist for Software Asset Management is now ServiceNow Otto for Software Asset Management.\n\n |
| \n\nSOM for Manufacturing Advanced\n\n | \n\n2.0.0\n\n | \n\nHttps://www.servicenow.com/docs/r/release-notes/manufacturing-commercial-operations-rn.html.\n\n |
| \n\nSOM for Manufacturing Prime\n\n | \n\n2.0.0\n\n | \n\nHttps://www.servicenow.com/docs/r/release-notes/manufacturing-commercial-operations-rn.html.\n\n |
| \n\nSource-to-Pay Common Architecture\n\n | \n\n24.1.2\n\n | \n\nNew\n\n - Added the Jurisdiction field to Invoice Tax Line to capture the jurisdiction associated with a tax line.\n- Added Jurisdiction Type and Tax Authority fields to Invoice Tax Line. These fields populate automatically based on the selected jurisdiction or tax type.\n\n Changed\n\n - Enhanced the Invoice Tax Line form and list view to display jurisdiction, jurisdiction type, and tax authority.\n- Updated duplicate tax line detection to use the combination of tax type, jurisdiction, and jurisdiction type instead of tax type alone.\n- When adding or editing a tax line, jurisdiction type and tax authority now populate automatically based on the selected jurisdiction or tax type.\n\n |
| \n\nSource-to-Pay Workspace\n\n | \n\n20.0.4\n\n | \n\nChanged\n\n Updated the in-app assistant branding and messaging from Now Assist to Otto.\n\n Fixed\n\n Implemented general platform security improvements.\n\n |
| \n\nSourcing and Purchasing Automation\n\n | \n\n11.4.5\n\n | \n\nFixed\n\n - Resolved a scoping issue that could allow cross-record access under specific configurations.\n- Applied security hardening to address CVE-2025-3648.\n\n |
| \n\nSpend and Savings Management\n\n | \n\n5.0.5\n\n | \n\nApplied security hardening to address CVE-2025-3648.\n\n |
| \n\nSPM Enterprise-Wide Deployment\n\n | \n\n1.0.3\n\n | \n\nFixed\n\n Resolved security vulnerabilities and minor defects.\n\n |
| \n\nSPM Planning Attributes Core\n\n | \n\n1.17.2\n\n | \n\nNew\n\n System administrators and developers can now access Financial Management Attributes without restriction. Access is now public, enabling integration with additional applications.\n\n Fixed\n\n - Assignment realignment for demand now functions correctly.\n- Assignment date updates and realignment now work correctly when actuals are present. The system checks assignment alignment before proceeding.\n- UI actions for epic and planning items have been updated to support this alignment check.\n- Rate override and resource rate columns on the resource board now display and function correctly.\n- Task reassignments now correctly update associated dates.\n\n |
| \n\nSPO - Foundation\n\n | \n\n1.3.3\n\n | \n\nNow Assist has been renamed to ServiceNow Otto, ServiceNow's AI experience brand. As a result, references to Now Assist have been replaced with ServiceNow Otto.\n\n |
| \n\nSPO - Prime\n\n | \n\n1.3.3\n\n | \n\nNow Assist has been renamed to ServiceNow Otto, ServiceNow's AI experience brand. As a result, Now Assist references have been replaced with ServiceNow Otto.\n\n |
| \n\nStandard ticket page summarization\n\n | \n\n1.3.3\n\n | \n\nUpdated to support the ServiceNow Otto brand.\n\n |
| \n\nSummarization for Order Management\n\n | \n\n2.2.2\n\n | \n\nConverted the Summarization for Order Management Application into Fluent.\n\n |
| \n\nTag Based Alert Clustering Engine\n\n | \n\n18.24.12\n\n | \n\n--- AI Generated Release Notes ---.\n\n Fixed\n\n Query range issues on session alerts have been resolved. Session alert queries now return accurate results without errors.\n\n |
| \n\nTalent feedback\n\n | \n\n1.4.1\n\n | \n\nNow Assist introduced AI on the platform. As that experience has evolved, there's a new name for the experience. ServiceNow Otto is the conversational AI platform integrated into ServiceNow workflows. It provides agentic capabilities, supports multimodal interactions across web, mobile, and messaging channels, and enables autonomous orchestration for cross-system workflows.\n\n As part of this version, the Now Assist Icon in the 'Request feedback' button on the employee feedback page in Manager Hub was updated.\n\n |
| \n\nTechnology Advanced\n\n | \n\n1.0.11\n\n | \n\nSKU plaugin.\n\n |
| \n\nTechnology Foundation\n\n | \n\n1.0.14\n\n | \n\nSKU plugin.\n\n |
| \n\nTechnology Prime\n\n | \n\n1.0.11\n\n | \n\nSKU plugin.\n\n |
| \n\nTelecommunications, Media and Technology - Advanced\n\n | \n\n1.0.10\n\n | \n\nSKU related changes.\n\n |
| \n\nTelecommunications, Media and Technology - Foundation\n\n | \n\n1.0.12\n\n | \n\nSKU plugin.\n\n |
| \n\nTelecommunications, Media and Technology - Prime\n\n | \n\n1.0.10\n\n | \n\nSKU plugin.\n\n |
| \n\nTelecommunications Advanced\n\n | \n\n2.2.1\n\n | \n\nOtto rebranding changes.\n\n |
| \n\nTelecommunications Foundation\n\n | \n\n2.2.1\n\n | \n\nOtto Rebranding.\n\n |
| \n\nTelecommunications Prime\n\n | \n\n2.2.1\n\n | \n\nOtto rebranding changes.\n\n |
| \n\nThird-party Risk Due Diligence\n\n | \n\n22.5.0\n\n | \n\nChanged\n\n - Rebranded to ServiceNow Otto, replacing Now Assist references for a consistent AI experience.\n- Enhanced MRA authorization validation to ensure access checks are consistently enforced during record association.\n\n |
| \n\nThird-party Risk Management\n\n | \n\n22.5.1\n\n | \n\nChanged\n\n Rebranded to ServiceNow Otto, replacing Now Assist references for a consistent AI experience.\n\n Fixed\n\n Addressed Arbitrary GlideRecord read in VendorRiskAsmtAjax security issue \\[PRB1997560\\].\n\n |
| \n\nThird-party Risk Management Advanced\n\n | \n\n22.5.0\n\n | \n\nChanged\n\n - Rebranded to ServiceNow Otto, replacing Now Assist references for a consistent AI experience.\n- Enhanced MRA authorization validation to ensure access checks are consistently enforced during record association.\n\n |
| \n\nThird-party Risk Management Professional Plus\n\n | \n\n22.5.0\n\n | \n\nUpdated.\n\n - Rebranded to ServiceNow OTTO, replacing Now Assist references for a consistent AI experience.\n- Enhanced MRA authorization validation to ensure access checks are consistently enforced during record association.\n\n |
| \n\nThreat Intelligence Security Center - Advanced\n\n | \n\n3.1.0\n\n | \n\nNew\n\n Added support for Google Gemini 3.5 Flash and OpenAI GPT 5.4 mini models for Case summarization.\n\n Changed\n\n Now Assist has been renamed to ServiceNow Otto, ServiceNow's AI experience brand.\n\n |
| \n\nThreat Intelligence Support Common\n\n | \n\n13.6.8\n\n | \n\nFixed\n\n - Fixed the observable identification logic while adding an observable.\n- Fixed the translation issues for UI messages.\n\n |
| \n\nTNI - Advanced\n\n | \n\n2.2.0\n\n | \n\nMaintenance release - dependency updates only; no new customer-facing functionality in this version.\n\n |
| \n\nTNI and DCNAM AI Content Collection\n\n | \n\n2.2.0\n\n | \n\nMaintenance release - dependency updates only; no new customer-facing functionality in this version.\n\n |
| \n\nTouchpoint Meeting\n\n | \n\n3.0.7\n\n | \n\nThis application is included in the August 2026 A bundle as part of the coordinated TMT Service Management Bundle release. All existing functionality remains fully operational and consistent with the prior release.\n\n |
| \n\nTSOM - Advanced\n\n | \n\n2.2.1\n\n | \n\nMaintenance release - dependency updates only; no new customer-facing functionality in this version.\n\n |
| \n\nTSOM - Prime\n\n | \n\n2.2.1\n\n | \n\nMaintenance release - dependency updates only; no new customer-facing functionality in this version.\n\n |
| \n\nUI Components for Customer Portals\n\n | \n\n4.2.1\n\n | \n\nNew\n\n Changed\n\n Fixed\n\n Defect fixes.\n\n Removed\n\n |
| \n\nUnified Developer Core\n\n | \n\n29.2.8\n\n | \n\nMaintenance release.\n\n |
| \n\nUnified Security Exposure Management \\(USEM\\) - Advanced\n\n | \n\n2.2.3\n\n | \n\nEnhancements to the Security Exposure 360 feature:\n\n - Clickable Links to Records: Counts and findings in the Security Exposure 360 output are now directly clickable, linking you to the underlying vulnerable item \\(VITs\\)/records in your ServiceNow AI Platform instance.\n- Suggested follow-up questions: Suggested follow-up questions are provided that help you drill down.\n\n Changed\n\n Enhancements to support the ServiceNow Otto brand.\n\n |
| \n\nUnified Security Exposure Management \\(USEM\\) - Foundation\n\n | \n\n2.2.3\n\n | \n\nEnhancements to support the ServiceNow Otto brand.\n\n |
| \n\nUnified Security Exposure Management \\(USEM\\) - Prime\n\n | \n\n2.2.3\n\n | \n\nEnhancements to the Security Exposure 360 feature:\n\n - Clickable Links to Records: Counts and findings in the Security Exposure 360 output are now directly clickable, linking you to the underlying vulnerable item \\(VITs\\)/records in your ServiceNow AI Platform instance.\n- Suggested follow-up questions: Suggested follow-up questions are provided that help you drill down.\n\n Changed\n\n Enhancements to support the ServiceNow Otto brand.\n\n |
| \n\nVault Console\n\n | \n\n2.2.9\n\n | \n\n- The security\\_admin role has been removed from the roles required to elevate to and administer Vault Console. All administrative tasks including that of viewing tools metrics across the dashboard is now available to the sn\\_vault\\_console.vault\\_console\\_admin. This change was made to conform with the principle of least privilege, ensuring administrators only elevate to roles they actually need.\n- UI fixes to ensure interface elements are displayed according to entitlement settings.\n\n |
| \n\nWalk-up Experience for Service Operations Workspace\n\n | \n\n9.3.1\n\n | \n\nUpdated plugin dependencies to ensure compatibility with the ServiceNow latest release.\n\n |
| \n\nWorkflow Studio\n\n | \n\n29.2.2\n\n | \n\nChanged: Branding changes from Now Assist to Otto, the new ServiceNow AI companion.\n\n |
| \n\nWorkplace Connectors\n\n | \n\n2.3.8\n\n | \n\nNew\n\n Changed\n\n ServiceNow Otto is the new AI experience brand. This change is reflected in the name of ServiceNow products. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features.\n\n Fixed\n\n Removed\n\n |
| \n\nWorkplace Core\n\n | \n\n2.28.10\n\n | \n\nNew\n\n Changed\n\n Fixed\n\n Security fixes.\n\n Removed\n\n |
| \n\nWorkplace Reservation Management\n\n | \n\n3.6.1\n\n | \n\nNew\n\n Changed\n\n Only building or system time zones will be used when synchronizing reservations with external systems. The UTC time zone is used when no timezone can be determined.\n\n Fixed\n\n - Unable to update the visitor parking option while editing an existing reservation.\n- Unable to edit the recurring pattern after initially setting it to custom when there was no 'Max days in future' limit configured.\n- Reservation creation could fail when using abbreviated time zone formats.\n- As an admin, clicking 'View all' in the reservation email preview did not correctly display the reservation details page with all recurring reservation occurrences.\n- Fixes to support translations.\n\n Removed\n\n |
| \n\nWorkplace Space Management\n\n | \n\n1.20.13\n\n | \n\nNew\n\n Changed\n\n Fixed\n\n Security fixes.\n\n Removed\n\n |
| \n\nWorkplace Visitor Management\n\n | \n\n2.1.1\n\n | \n\nNew\n\n The introduction of new API end points to support artificial intelligence platforms.\n\n Changed\n\n Fixed\n\n Removed\n\n |