Yokohama Patch 6
The Yokohama Patch 6 release contains important problem fixes.
- Yokohama Patch 6 was released on July 31, 2025.
-
- Build date: 07-27-2025_1301
- Build tag: glide-yokohama-12-18-2024__patch6-07-17-2025
For more information about the release cycle, see the ServiceNow Release Cycle.
Overview
Yokohama Patch 6 includes 330 problem fixes in various categories. The chart below shows the top 10 problem categories included in this patch.
For a downloadable, sortable version of the fixed problems in this release, click here.
Changes in Yokohama Patch 6
- Configuration Management Database (CMDB) release notes
- Starting with Yokohama Patch 6, you can configure the sn_cmdb_admin and the sn_cmdb_editor user roles with the necessary permissions to perform some CMDB Workspace tasks by manually running a scheduled job.
- You can use Now LLM Service, Azure OpenAI, Google Gemini or Anthropic Claude on AWS as the AI model provider for Now Assist skills and AI agents. You can set skill-level preferences in the Now Assist Admin console. For more information, see Large language models on the ServiceNow AI Platform®.
- The ServiceNow® Enterprise Architecture unites strategic and operational teams, enabling organizations to achieve their business objectives. It serves as a powerful decision engine, combining robust modeling with the management of business capabilities, application portfolios, information portfolios, and technology portfolios. This product changes has for the Yokohama Patch 6 release.
- You can use Now LLM Service, Azure OpenAI, Google Gemini or Anthropic Claude on AWS as the AI model provider for Now Assist skills and AI agents. You can set skill-level preferences in the Now Assist Admin console. For more information, see Large language models on the ServiceNow AI Platform®.
- QueryRangeACLAuditor
- This patch includes the May Maintenance update script in the form of a script include (QueryRangeACLAuditor). This script is not triggered automatically and must be run after a patch upgrade. More details on running the QueryRangeACLAuditor and its functionality can be found in KB2046494.
Notable fixes
The following problems and their fixes are ordered by potential impact to customers, starting with the most significant fixes.
| Problem | Short description | Description | Steps to reproduce |
|---|---|---|---|
|
Column Level Encryption Enterprise PRB1874479 |
The security banner message 'One or more security migration jobs have failed in your instance' appears constantly and isn't dismissed after one day | As part of the Column Level Encryption (CLE) migration process from Yokohama and later, there are cases where the 'Key migration' job is failing as there's no key to migrate. As the key migration job fails, there's a security banner announcement 'One or more security migration jobs have failed in your instance', which is appearing in the instance post-migration. The red banner message for migration errors isn't dismissed. The banner message should appear only for one day and be dismissed after that. However, the banner message is displayed constantly. |
Log in to any Yokohama instance where the key migration job failed, as there is no key to migrate. Observe the banner announcement, 'One or more security migration jobs have failed in your instance', and the banner announcement is shown even after one day. |
|
Contextual Search PRB1868773 |
canWrite on GlideElement for variable sets returns a null pointer exception | There's an issue calling a canWrite on a variable set when applying form changes to be filtered. The individual variables behave correctly. | |
|
Database Persistence - Data Management PRB1810466 |
Physical Table Stats Table (sys_physical_table_stats) doesn't have a cleanup mechanism that retain the table stats records daily after Xanadu changes | A rule will be implemented similar to the one for sys_db_size_stats for sys_physical_table_stats using sample_period_start and sys_created_on, or sys_updated_on. | |
|
Database Persistence - Data Management PRB1837739 |
'Physical Table Stats Gatherer' runs long due to an influx of query with hash 2136542706 | The job runs for more than one hour. Each query takes around 239 ms but since the number of times it's being called is high, the overall job takes a longer time. | |
|
Discovery PRB1791510 |
Discovery is hanging for certain schedules due to WMI queries failing |
Run Discovery on Windows devices where the WMI queries fail in Windows OS Patterns. |
|
|
MID Server PRB1912171 |
Yokohama MID Server upgrades do not upgrade all jar files in lib | Yokohama MID Server upgrades don't upgrade all jar files in lib, causing NoClassDefFoundError for various classes, and MID Server to go down. |
Refer to the listed KB article for details. |
|
Platform Analytics Dashboard API PRB1909523 |
Changes in the dashboard only appear in the session language where they were made | Users are experiencing inconsistent behavior in Platform Analytics dashboards depending on the selected user language. When viewed in English, the dashboard reflects the latest updates. When switched to Italian, an outdated version displays, even after clearing the cache using cache.do. |
Refer to the listed KB article for details. |
All other fixes
| Problem | Short description | Description | Steps to reproduce |
|---|---|---|---|
|
Access Control List (ACL) Rules PRB1911649 |
Non-record gen_ai directive ACLs not active on zboot |
Expected behavior: All matching * ACLs should be active. Actual behavior: All matching * ACLs are active=false. |
|
|
Access Control List (ACL) Rules PRB1916144 |
gen_ai_ prefixed ACL types should use '* ACLs' for their default rule name | This is a product enhancement. | |
|
Access Control PRB1910493 |
There is slowness when loading forms with 'Table Choice' fields, even after applying a 2000 record limit | The size of CACHE_ARCHIVE_TABLE_HAS_TERMS cache needs to be higher than 2000 since many instances have > 1000 archive tables. |
Refer to the listed KB article for details. |
|
Activity Stream PRB1743672 |
Worknotes using Carriage Return aren't displaying in HR Agent Workspace when using edge encryption |
Notice that the Worknote isn't visible in the Activity Log. |
|
|
Activity Stream PRB1870524 |
If user_id is in the form of a sys_id, then the user isn't displayed correctly in the activity stream | The sys_created_by can be a user_id or a sys_id or an email, so it guesses based on the format. If the user_id is copying the sys_id format, then this process doesn't work. |
Notice this user's user_id is displayed instead of the display name. |
|
Activity Stream PRB1895624 |
Activity Stream displays sys_id instead of the display name | The user's sys_id is posted instead in the Activity Stream event. |
Notice that the user ID (sys_id format) is displayed instead of the user's display name in the Activity Stream event. |
|
Activity Stream PRB1897140 |
A workspace activity stream isn't displayed for archived records | Due to a misunderstanding of the requirements for archived records, a performance fix made it so that no workspace activity streams get generated for any archive tables, i.e. tables with an 'ar_' prefix. Instead, since archived records are read-only, all live updates for archived records should be turned off, while allowing the activity stream to be viewable. | |
|
Activity Stream PRB1914670 |
In UI16, AI Agent posts appear as the logged-in user until the page is refreshed | In UI16, the entries appear as posted by the logged-in user initially. Only after a manual refresh the name changes to AI Agent. In Workspace, the entries correctly show the AI Agent as the author, which is expected. | |
|
Advanced Work Assignment PRB1884896 |
'Capacity' displays the incorrect value in a manual 'Allocation of Work' item from the 'Queued work' tab from Workforce Optimization | The user should see a list of available agents with their capacity, but instead the user always sees zero/3. |
Notice that the capacity appears as zero/3 for the user. |
|
Advanced Work Assignment PRB1909214 |
Updating an agent's presence as an integration user via the Agent API fails | The gr.canWrite() checks aren't working as expected when the API caller is an integration user. The integration user should be allowed to update the presence state. If the API caller has the awa_integration_user role, the request should go through. If the API caller doesn't have sufficient roles, the request should fail with a 500 error. | |
|
Agile Development PRB1900463 |
Global search isn't working for certain records after upgrading to Yokohama | After upgrading to Yokohama, pre-fix for certain records, such as Release, Feature, Phase, got updated. This prevents the global search from working as expected. The new pre-fix records are searchable, but existing records created before the upgrade using the old prefix aren't searchable. |
Refer to the listed KB article for details. |
|
Agile Development PRB1909252 |
Customized story numbers are overwritten by an upgrade | A certain entry was offered in the com.snc.sdlc.scrum and com.snc.spm_agile_common packages. This entry is placed in the 'unload' folder, not the 'update' folder. Therefore, this entry becomes offending to any users who have customized it because content in the 'unload' folder is loaded during the first time activation. |
Expected behavior: The customization is retained. Actual behavior: The customization is reverted. |
|
AI Search (Glide) PRB1913666 |
There's a AisDisableSearchSignalEvent warning message: 'scope is not defined' | In the syslog table, there's an error: 'com.glide.script.RhinoEcmaError: "AisDisableSearchSignalEvent" is not defined. sys_script.a9d8af92ff602210fbf4ffffffffffa8.script ➚ ➚ ➚ : Line(3) column(0). java.lang.SecurityException: Illegal access to package_private script include AisDisableSearchSignalEvent: caller not in scope rhino.global.' | |
|
AI Search (Glide) PRB1913679 |
The ExternalContentIngestion date parsing IT test fails | AI Search seems to be unable to parse date values correctly. Expected is 2001-01-01 00:00:00, but was 2001-01-01 00:00:01. | |
|
AI Search (Glide) PRB1916149 |
Allow AI Search admin users to invalidate crawlstore and perform a full Rrcrawl for a given indexed source | This is a product enhancement. | |
|
AI Search (Glide) PRB1916150 |
Provide a Scriptable API for the External Content Connectors to get datasource-based statistics and a semantic embeddings status | This is a product enhancement. | |
|
AI Search (Glide) PRB1916188 |
Update glide AI Search external content APIs to support multiple users per indexed source | This is a product enhancement. | |
|
AI Search External User Mapping API PRB1909140 |
An API endpoint which can delete users via a GlideQuery is required for XCC | The XCC Scoped App can't delete users one at a time. It needs a way to query a subset of users. | |
|
AI Search External User Mapping API PRB1909142 |
When a user principal is written with the DirectUserImporter and one exists, the update fails | Stream is wrapped mistakenly during the serialization process from a list. Not all of the principal imports do a check for the DirectPrincipalImporter vs the ImportSetImporter. The streams should be closed effectively. |
Attempt to send a new user principal that updates an existing user. Updates to existing users fail. Removal of a user's group fails. |
|
AI Search External User Mapping API PRB1909146 |
The 'External Content Ingestion JS' API must do an undefined check on 'sourceId' | Use the newly qualified 'External Content Ingestion' APIs for ingesting principals with 'sourceId'. If 'sourceId' is undefined, see that the principals insert or updates fail. | |
|
AI Search External User Mapping API PRB1909153 |
Change SOURCE_ID_FIELD to reference connector_configuration_id instead of connector_configuration_id_s | The current licensing table process fails for some connectors because its querying the wrong field. | |
|
AI Search External User Mapping API PRB1913661 |
Parameters are in the wrong order when calling Java API for (removeUser) | An exception is thrown, saying that the principal ID is null. This shouldn't be the case. | |
|
AI Search PRB1864807 |
Composite multi-field facets with one of the sources evaluates as late binding, then for the other source, doesn't return all facets on all tabs | Facets aren't consistent between the 'All' tab and the 'Article' tab for KBs. |
Expected behavior: The facets should be consistent between the 'All' tab and the 'Article' tab. Actual behavior: Some facets don't show on the 'All' tab. |
|
AI Search PRB1889815 |
KBB should filter out the none-embeddedMatch docs | The default of KKBs sent to LLM is one. |
Expected behavior: Only KBB1 content is sent to LLM. Actual behavior: Both KBB1 and KBB2 content are sent to LLM. |
|
AI Search PRB1911804 |
There's a null point error for the index stats reporter | Note the JavaScript evaluation error on 'new sn_ais. IndexStatsReporter() .reportAllDataSource EmbeddingStats();'. | |
|
AI Search UX PRB1904981 |
There's a console error after selecting the follow-up button for KG NLQ queries | There's a null citation in the chat. |
Notice the console error and last citation is loaded as null. |
|
AI Search UX PRB1907541 |
Revert unused synthesized v2 format code | ||
|
Analyst Workbench PRB1868095 |
The proper user message when a project has error isn't shown | The correct message should be shown to the user when a project has an error. |
Expected behavior: The error message should be shown to the user. Actual behavior: The error message isn't shown to the user. |
|
Analyst Workbench PRB1868099 |
Evaluation projects should have the 'Edit' option on the 'Process projects' page, even if the user is unable to edit | Only a user with elevated privileges can see the 'Edit' option, even though it should be seen by all users even if they're unable to edit. |
Expected behavior: The Edit option shows where ever the project is available. Actual behavior: The 'Edit' option is only seen by a user with elevated privileges. |
|
API Usage Analytics Dashboard PRB1842140 |
API_INT Semaphore queue depth shows a negative value in stats.do misguiding analysis and troubleshooting | There are two problems. First, the count shouldn't go negative when any exception happens. Second, it shouldn't throw an exception, which ultimately drops the request on the floor and never responds to the browser. | |
|
Application Manager PRB1907408 |
A rollback blocking the install/upgrade for non-global scope users in a domain-separated instance | Non-global domain users have been blocked from being able to install/upgrade on domain-separated instances. There is now a fix to allow this behavior and hence this code change made on App Manager can now be rolled back. | |
|
Appointment Booking PRB1902492 |
Issue with missing otherInputs in taskRecord parameter of rest API payload for Appointment Booking Unified UI after upgrading to Yokohama | In the Yokohama release, a common UI for appointment booking was implemented and otherInputs was missed from the payload. Add the otherInputs parameter in taskRecord like in the previous UI. | |
|
Asynchronous Message Bus (AMB) PRB1909861 |
A lazy load of AMB messages cause an additional query for every message published | A performance improvement implemented in Yokohoma was designed to optimize database operations by loading the actual AMB message column from the database only when subscribers for that message exist. However, this optimization has been compromised by a request that updates the redelivery cache, which inadvertently causes the new query to be triggered for every published message, regardless of subscriber status. The intended performance benefit of selective database querying is being negated, as the system is now querying the database for all messages instead of only those with subscribers. | |
|
Asynchronous Message Bus (AMB) PRB1910946 |
The Record Watcher (RW) Asynchronous Message Bus (AMB) message censor doesn't work when AMB lazy load is turned off | When glide.amb.message. lazy.load is set to 'false', having a record open in two browsers and updating it in one doesn't update it in the other browser. |
Notice that the Record field in the other browser window isn't updated. |
|
Authentication PRB1835271 |
IDP-initated SLO fails if 'Auto Redirect IdP' is 'True' |
Expected behavior: The user should be logged out from both SP and IDP. Actual behavior: The user is not logged from IDP only not from SP. |
|
|
Authentication PRB1917269 |
Authentication Agentic AI agent controls | This is a product enhancement. | |
|
Case and Knowledge Management for HR Service Delivery PRB1887320 |
HTML dynamic parameters on HR templates aren't working as expected | HTML dynamic parameters on HR templates are not being replaced with the actual value when used in links. The issue still persists if the description contains variables only in a link. | |
|
Case and Knowledge Management for HR Service Delivery PRB1898674 |
Agentic execution runs into a permission error | There's an error in the logs: 'The attempt to retrieve your open tickets failed due to a permissions error (read access to sn_hr_core_case not granted). Please advise on how to proceed or if there is an alternative method preferred to access your open tickets.' |
Observe the error. |
|
Client Scripts PRB1818770 |
When an onchange script on name-value pairs with a field, the value on the field doesn't change dynamically in the Service Operations Workspace | The state of the NameValue field doesn't change from 'New' to 'In Progress' in the Service Operations Workspace platform UI. |
Notice that the NameValue field doesn't change in platform UI. |
|
CMDB Identification and Reconciliation PRB1895738 |
A fix script causes high DB CPU load/DB backup failure/long running jobs | After upgrading to Yokohama, Discovery jobs querying cmdb_rel_ci is long running and causing high DB CPU load and DB back-up failure. |
Refer to the listed KB article for details. |
|
Column Level Encryption Enterprise PRB1879823 |
The 'Mass Decryption' job doesn't decrypt all the records in the table after EFC is turned off due to escaped and not decryptable HTML fields | The modified row with the HTML value that had the encryption configuration deactivated still display the encrypted value. |
Expected behavior: Both rows are decrypted.Actual behavior: The modified row's HTML value still shows the encrypted value. |
|
Column Level Encryption PRB1820743 |
Inactive caller policy records shouldn't be used when fetching a list of available crypto modules | This problem only applies to fields configured with multi-module EFCs where the field is empty or populated with cleartext data. When determining read/write access on a CLE field, available CLE crypto modules are checked to see which modules the user has access to. When building the list of crypto modules, use the query for caller policy records to find the modules. However, inactive caller policy records aren't filtered out.This causes no visible issues or access issues for users. In cases where there are many inactive caller policy records, this causes a performance issue and slows down the read/write check. |
Expected behavior: no_access_module doesn't show up in the list.Actual behavior: no_access_module shows up in the list. |
|
Column Level Encryption PRB1837482 |
Attachment generation fails when running a flow or background job as a system user, as it tries to encrypt even though it doesn't have access to the module | GlideSession is being reused in background jobs/flows, which already set some values in the session such as CryptoModulePicker. Since CryptoModulePicker is already set, when it attempts to encrypt, it doesn't have access to the crypto module and fails. Any session that has been previously used by an admin user with access will lead to the error when that session is used by the system. |
Expected behavior: It shouldn't encrypt the attachment.Actual behavior: It attempts to encrypt and fails with the error, 'SEVERE *** ERROR *** Crypto module access is denied for an attachment'. |
|
Column Level Encryption PRB1896503 |
Data Migration Job summary doesn't have the correct pending list for incomplete EFCs |
Notice that when the job restarts, it only pick ups the migration pending EFCs from the job summary, but there EFCs marked as 'Migration Pending' on EFC table. |
|
|
Configuration Management Database (CMDB) PRB1847131 |
The Related List condition is not used during task generation | CMDBScriptableAPI isn't honoring the related list condition that is stored in the encoded query field of the policy record. If the condition stored in the policy record is used in a background script, the correct count of configuration items (CI) comes back, so it has to be localized to the java function creating the tasks. |
Refer to the listed KB article for details. |
|
Configuration Management Database (CMDB) PRB1899149 |
Remove sn_cmdb_admin from itil_admin, sn_cmdb_editor from itil, and add CUD access to sn_cmdb_admin / sn_cmdb_editor | An itil user should have CUD access by default and users with the itil role contains sn_cmdb_editor, not sn_cmdb_user. Remove CUD from itil, and a user with the itil role no longer has CUD access because of removing CUD from sn_cmdb_editor. | |
|
Customer Service Management PRB1893694 |
On guided setup, the 'Activate customer central' page displays 'no record found' | There's an issue with the plugin name being hard-coded in configurations. In Yokohama, the 'Customer Central' plugin ID was changed from com.sn_csm_customer_central to sn_customercentral. The guided setup is hardcoded to point to com.sn_csm_customer_central. |
Observe that the button opens a page displaying 'Record Not Found'. |
|
Database Persistence - Data Access PRB1882454 |
db-dml-test failures on Yokohama for DBInsertFullUnicodeIT .testTrickyDBAction and DBInsertFullUnicodeIT .testTrickyGlideRecord | Data inserted via GlideRecord is encoded twice, and the SQL search query uses only one level of encoding in the 'Where' clause, causing the search to return incorrect results. | |
|
Database Persistence - Data Access PRB1896536 |
The 'Database' view isn't working for Workflow Data Fabric tables | An error is generated: 'Logic Error: No Join Found for table: sys_user: no thrown error'. | |
|
Database Persistence - Data Access PRB1907396 |
Graph API needs to honor data filtration/data filter rules |
|
|
|
Database Persistence - Data Management PRB1841958 |
Failure to clean any records on a gateway table if more than 100 records are found | This issue is caused by UnreferncedRecordFinder.verifyUnreferencedRecords returning no records to delete, despite initially finding all the correct records in the unreferencedRecordFinder .getChunkOfUnreferenced RecordIds call. |
Expected behavior: At least 1000 sample records should be visible below on the form view of the URC rule created. Actual behavior: No sample preview records are found. |
|
Database Persistence - Data Management PRB1867090 |
Tables available in the Unreferenced Table Cleaner (URC) rule creation form are unconstrained | Configure an inclusion list for available table names when creating new URC rule, and create a new glide property 'glide.db.unreferenced_record _cleaner.enabled_tables'. |
Attempt to create a URC rule. Expected behavior: Only a subset of tables should be available. Actual behavior: All tables are available. |
|
Database Persistence - Data Management PRB1913617 |
Turn off monthly and yearly stats aggregator jobs | ||
|
Database Persistence - Data Scale PRB1824916 |
Query rewrites don't apply on already optimized queries by union optimization or left join coercion | When implementing the query rewrite for an optimized query, it doesn't apply as a query rewrite applies prior to the optimization. | |
|
Database Persistence PRB1906360 |
The 'Re-Activate All DF Reference Elements' UI action doesn't activate the data fabric (DF) reference element |
Expected behavior: All DF reference elements should be activated again (active = true). Actual behavior: All DF reference elements remain inactive. |
|
|
Database Persistence PRB1907489 |
Update WDF readiness system properties to be changed by users with elevated privileges only |
Update the properties as an admin user. |
|
|
Data Privacy (Classic) PRB1893749 |
Trail License button is not displayed on a new TD instance after installing Data Discovery and Data Privacy App |
Expected behavior: The Trial License button is displayed. Actual behavior: The Trial License button is not displayed, and the user is able to schedule the job. |
|
|
Declarative Actions PRB1876861 |
Customizing a flow from 'Order line item' loads a blank configuration UI screen for Order Agent and Order Admin users | Both Order.agent and Order.admin users are redirected to a blank page when the configuration UI page should open after selecting 'Customize' for ab order line item. |
Expected behavior: Selecting Customize should open the configuration UI page. Actual behavior: Selecting Customize redirects the user to a blank page. |
|
Developer Sandboxes PRB1903573 |
Clone preservers need to be added for all clone profiles | Developer Sandboxes (DSB) should be present in the profile preserver list. |
Expected behavior: DSB preservers are there. Actual behavior: DSB preservers not there. |
|
Discovery PRB1800638 |
Preventing the scenario of running Simple Network Management Protocol (SNMP) GetNext on the same Object Identifier (OID) repeatedly | ||
|
Discovery PRB1898292 |
A Discovery monitoring job should support event framework | Discovery to not use sys_trigger directly, but instead utilize Platform's event framework to distribute the load among nodes. |
|
|
Discovery PRB1899269 |
Discovery dedicated node job criteria used for some users doesn't exclude Cloud Discovery jobs in the Yokohama release |
It's not expected to see the Cloud discovery traffic on the dedicated node, but it is still going to dedicated nodes. |
|
|
Discovery PRB1899276 |
The start of the next Discovery schedule in a daisy chain is delayed by the time taken to complete 'discovery.complete' or 'discovery.cancel' events | In instances where the daisy chain is being used, the start of the next Discovery in the chain depends on the time taken to complete 'discovery.complete' or 'discovery.cancel' events . Most of the script actions for these events in their environment have the same default execution order of 100, including 'Discovery Run Next', which triggers the next Discovery. The more script actions with the order 100, the higher the possibility of delay for starting the next Discovery. |
Notice that it is greater than the time taken by the new script actions. |
|
Discovery PRB1899547 |
Make error suggestions clearer and link them to useful Knowledge Base (KB) articles | After analysis, it was found that the error suggestions for the following codes are insufficient or missing: SN-5301: No sensor defined, SN-1582: Unable to classify, SN-1144: Host is not reachable, SN-1007 : Failed to establish SSH connection, SN-1556: Multiple duplicate records, SN-1561: Multi match, and SN-1558: Missing dependency. |
|
|
Document Intelligence Unified Backend PRB1896682 |
Create a system property for max page and max field limits for GenAI use cases | Currently, the max page and max field limits are not customizable. | |
|
Document Viewer PRB1914045 |
Users are unable to view an attachment when clicking it | The issue is observed for all the components where attachments can be previewed. |
The 'Attachment' view fails. |
|
Dynamic Schema PRB1895584 |
Upgrading from Xanadu removes the dynamic attribute store display data and querying since the fix script from PRB1895584 is not applied | In Xanadu, the data in the database is stored incorrectly, and the group is missing an underscore. |
Notice the display data on the the inc_dynamic_schema column, hardware_dynamic_schema column, and the cmdb_dynamic_schema column are now gone, and the data in the database did not get correctly changed. |
|
Dynamic Translation PRB1899459 |
Dynamic Translation isn't working after upgrading in Yokohama | The translation feature stopped working and is now throwing the following error in 'Translate Text': 'Error: Cannot read property 'status' from undefined. Detail: Cannot read property 'status' from undefined.' | |
|
Edge Encryption PRB1915259 |
Users are uable to attach a 10MB file to a record when logged in with an Edge URL | When logged in with the Edge URL and trying to attach an attachment of 10MB to any of the records in the instance, it keeps loading. But when users load attachments with less than 10MB, it works fine. However, with a normal instance URL, the user is able to attach the larger attachments without any issues. | |
|
Email Notifications PRB1782170 |
Inline images coming from encrypted and signed emails processed by the SMIME plugin are lost | Images sent by Outlook may not be decoded properly when both encryption and signing are used in SMIME. The processed email may also contain artifact characters after decoding. | |
|
Employee Taxonomy Framework PRB1909669 |
Uptake the AI Search EVAM bundle changes for Employee Centre Pro for Web Applications | With this change the following are expected: 1. The image duplication shouldn't be visible for search entries, so no image should be displayed on the left side as thumbnail. 2. Icons would be introduced for category results. | |
|
Encryption PRB1894907 |
Data migration job doesn't report failure records |
Expected behavior: The job reports failure records. Actual behavior: The job doesn't report failure records. |
|
|
Encryption Support PRB1888374 |
Attaching a file to an incident table doesn't generate a hash value, even though the attachment isn't actually encrypted | Once the encryption of attachments is deactivated on the Incident table, the issue is resolved despite the fact that the attachment isn't getting encrypted when it's on. |
Notice that the user will not see the Hash value. |
|
Event Management PRB1904735 |
Existing enrich rules have changes that affect binding (draft rules) | The bind simulation presents an incorrect result. | |
|
Field Service Task Bundling PRB1898283 |
Dynamic Bundling logs aren't accessible to the wm_admin persona | ||
|
Field Service Task Bundling PRB1903547 |
Unable to create bundles with customizations | When a custom field is added to the task grouping policy, the data is not being retrieved. |
Observe that the bundles aren't created. |
|
Flow Engine PRB1855808 |
Callback is not invoked due to null pointer in FlowCallBackExecutor | When an evaluation run from skill kit app is triggered, an attached error log occurred for a particular flow completion, and the run was not marked as complete. |
Trigger an evaluation run from skill kit with many dataset records. Notice that an attached error log occurs in the instance. |
|
Flow Engine PRB1881084 |
The CurrentContextTracker reset scope and meta stack are in the wrong order | CurrentContextTracker attempts to clean up meta stack and script contexts after a flow execution. Both are reloaded in reverse to how they initially appeared when the flow starts. This happens because the ArrayDeque collection removes elements from the stack. The array from the queue is in the expected order (A, B, C, etc). When the elements are added back, the ArrayDeque adds elements at the front of the queue, so iterating from first to last on the list and pushing will result in a reversed stack. So the queue contains (C, B, A) instead of (A, B, C). | |
|
Flow Engine PRB1893452 |
AI Agent context isn't properly configured for quick flows |
Update FlowUserAgentContextIT.java to accurately count the audit. Expected behavior: Quick flow tests in FlowUserAgentContextIT pass. Actual behavior: Quick flow tests in FlowUserAgentContextIT are failing. |
|
|
Flow Engine PRB1903784 |
process_flow.engine related zboot errors in the database dump logs | Errors in the database dump logs from Now Assist. | |
|
Flow Engine PRB1910437 |
Add a script for GenAI app BUs to create flow and action ACLs | A script utility was removed from the Flow AI Access Control effort that would create the flow or flow_action access control rule. That utility has been readded. | |
|
Flow Engine PRB1916146 |
Callbacks invoked on the FD API in Async Quick and from an AI agent shouldn't run as 'system' | This is a product update. | |
|
Flows (Family Channel) PRB1850039 |
Code-related text is appearing in the natural language summary for the Look up records action |
Notice there is a text present saying, 'logged_ON_Yesterday@javascript::gs:beginning....'. |
|
|
Flows (Family Channel) PRB1871518 |
In the Natural language view, the table's internal name shows up for 'Create Task' (table problem_task) | 'Create Task' is displayed as 'Create problem_task Task'. |
Notice that the flow is created in preview, and 'Create Task' is displayed as 'Create problem_task Task'. |
|
Flows (Family Channel) PRB1887330 |
NaN output results in 'Exception while executing request: Could not deserialize value' when opening the flow execution | . |
All users see the error, and won't be able to see any flow execution details. |
|
Flows (Family Channel) PRB1922279 |
Glide changes for Text2flow | This is a product enhancement. | |
|
Granular Delegation PRB1840636 |
Adhoc granular delegation isn't working on production | There's an error in the logs: 'Root cause of JavaScriptException: java.lang.NullPointerException: java.lang.NullPointerException: Cannot invoke 'com.glide.delegation.DelegationRule.isApprovals()' because 'rule' is null: com.glide.delegation. ApprovalDelegationMapper .doesMapRule (ApprovalDelegationMapper. java:46)'. | |
|
Health Log Analytics (Family) PRB1898736 |
The host name resolution for IPKI certificate generation isn't successful when the instance is using an alias | ||
|
Hermes (Family) PRB1860223 |
Hermes Client Metrics Collection loads large records when aggregating client metrics |
Expected behavior: No errors are observed during metrics aggregation.Actual behavior: Notice the error that contains, 'WARNING *** Large Table: Table handling an extremely large result set'. |
|
|
Horizon Component Library PRB1892046 |
The auto-resize limit doesn't work when the text area is read-only | There's a 'now-textarea' read-only component that the user is using on a regular workspace page. The user wants to expand the text area's height, but that is only possible through the 'rows' property. The user is currently using the 'autoresize' and 'autoresizeRowsLimit' properties. However, since the field is read-only, the height of the text area isn't expanding. When they use an existing template from the UI Builder page, there's no way to directly change the property of the 'now-textarea' component. If it was a regular empty UIB page, the user would have been able to change the 'rows' property. | |
|
HTML Field Type Editor PRB1881482 |
Read-only HTML fields aren't rendering the content properly | Users are unable to see the content of the field. The field becomes read-only and no content appears. |
Refer to the listed KB article for details. |
|
HTML Sanitizer PRB1840143 |
OpenITTicket-Web Client gets the santization message, 'You have inputted sensitive information and it has been cleared from the chat history' | This issue is observed intermittently while using Web Client. |
|
|
HTTP Client PRB1916723 |
The 'Request to Now' LLM media action fails due to missing changes made to support multipart on a sync client | Multipart requests support should be added to ynowassist so that the Generative AI Controller (GAIC) can change the 'Now LLM Media' flow to use the Now LLM Connection Alias. | |
|
Identity PRB1894590 |
An admin user is able to change the 'Table name' while selecting the AI agent from the list | There's a new plugin and table for the agent role configuration. |
Expected behavior: The user shouldn't be allowed to change the 'Table name' from the pop-up window. Actual behavior: The agent is able to select non-default tables from the list in pop-up window. |
|
Identity PRB1905443 |
Capitalization is missing for a WSA field notification message |
Expected behavior: The message should be 'Please use identity type field instead'. Actual behavior: The WSA field notification message doesn't start with a capital: 'please use identity type field instead'. |
|
|
Incident Communications Management PRB1901722 |
Add a workaround variable in Resolution Communication (Technical) and Resolution Communication (Business) | If a skill is active, then add the 'workaround' GenAI variable in the template: Resolution Communication (Technical) and Resolution Communication (Business). | |
|
Instance Clone (Family) PRB1908309 |
Authentication fix for recurring clones | ||
|
Integration Hub PRB1844370 |
Reconstructed process plan returns incorrect information when fetching a plan containing a data stream | The flow executes with a data stream, even if the method returns as 'false'. |
Notice that this method returns false, even though the flow executes with a data stream present. |
|
Integration Hub PRB1901076 |
Generative AI Controller (GAIC) fails to handle some streaming responses due to an unexpected format | Not all streaming responses are being returned by GAIC. Upon investigation, the issue was traced to a class in the flow processing code. This component currently supports only SSE or JSON data formats. However, some responses are returned in a different format, which causes the consumer to error out. | |
|
Integration Hub PRB1911068 |
GlideServer SQL API/Query Service limits | This is a product update. | |
|
Integration Hub PRB1911069 |
JDBC driver REST APIs for the ServiceNow SQL API | This is a product update. | |
|
Language and Translations PRB1886122 |
The user observes the wrong translation on Risk Workspace for the sn_risk_advanced plugin component | Incorrect translations on the Risk workspace for sn_risk_advanced plugin component. |
Expected behavior: The text is translated. Actual behavior: Subtitles are shows as 'advanced_risk_assessment_component...'. |
|
License Usage PRB1920048 |
The 'Remove candidate' link in the Progress Indicators card of the Key Metrics section isn't working | In the Key Metrics, 'Removal candidates' should link to the list view of removal candidates. |
Expected behavior: The user should be navigated to the list view of the removal candidates. Actual behavior: Nothing happens when the 'Removal Candidates' link is selected. |
|
Lifecycle Events PRB1881856 |
When a Lifecycle Event (LE) case is created directly in the 'Ready' state, the message 'Case reopened by...' is added to the work notes | This issue only happens in Yokohama and not in Xanadu. |
Refer to the listed KB article for details. |
|
List Administration PRB1875957 |
The 'Personalize List' option isn't working as expected | When using the 'Personalize List' option, if users click anywhere on the list other than the slush bucket, the slush bucket disappears. This causes the list to get stuck, making it impossible to access any of the list elements such as filter, personalize, UI actions, or the contextual menu. |
Refer to the listed KB article for details. |
|
List Administration PRB1880653 |
After a Yokohama upgrade, special characters are incorrectly interpreted in a list when using 'Show column filtering row' only in workspaces | The issue is reproduced only on Yokohama instances in list column header filters when using workspaces. |
Expected behavior: Characters should remain the same and display list results based on characters matching. Actual behavior: Characters get converted to some other hard-coded characters. This issue is reproduced only when using workspaces and works fine in Platform UI. |
|
MetricBase PRB1878006 |
A hanging Clotho server can sometimes cause glide to become unresponsive | A Clotho XMLStats request never returns if Clotho becomes unresponsive, leading to semaphores exhaustion on glide. | |
|
Metric Intelligence (Family) PRB1839739 |
ME queries dashboard configurations that don't filter out metrics without data, and pre-filtering should be added | This may cause a situation where the API returns 10 dashboard configuration with no data, causing the metric explorer to feature an empty metrics graph panel. In addition to this issue, pre-filtering should be added. |
|
|
MID Server PRB1898155 |
Calculated checks are zero after config_publish sent a following MID server restart | During policy publish via an ECC queue message, check sum calculations aren't performed on the MID server for policies that have previously been registered. These calculations are responsible for notifying agents tied with the policies and their check instances that changes have been made and a synchronization of the data must be pushed to agents via the WebSocket connection to reflect the changes. The issue arises from the MID server caching the previous policy during a config_publish message. For agents that register after this message, the schedule message is never sent due to an error associating the cache entry in the MID server with the new agent connection. For updates to existing policies and/or check definitions, the cache isn't updated with them check sum changes indicating the state has changed. |
Refer to the listed KB article for details. |
|
MID Server PRB1900340 |
The SSHProviderTerminal JavaScript probe gets stuck when the client sends a large amount of data when waiting for the identification string |
|
|
|
Mobile Classic app (End of Life) PRB1900493 |
A mobile browser e-signature failure due to a re-authentication error | This issue was found when the instance property configured for SSO and the 'Approval with e-signature' plugin. |
Notice that the user will be prompted for their username and password prior to approving. |
|
Mobile Platform PRB1835448 |
Uppercase in the choice value breaks the dependency on the Mobile App | . | |
|
Mobile Platform PRB1843125 |
Language should be part of the cache key building scripted screen cache | Questionnaires and Surveys translations in the Mobile Agent app are not working as expected. |
Refer to the listed KB article for details. |
|
Mobile Platform PRB1901478 |
Using UI parameters as part of a filter flow leads to a work order task (WOT) sys_id not being read on Field Service Management (FSM) | The users experience an 'invalid input' error. | |
|
Mobile Platform PRB1904246 |
External content should be supported in standard search results | The user can't see the icon or select the URL without adding an admin. | |
|
Mobile Platform PRB1905877 |
For a single attachment case, the attachment title doesn't display | Attachments should be supported in standard search results. Now, for a single attachment case, the attachment title doesn't display. For a multiple attachment case, the count of attachments doesn't display. | |
|
Mobile Platform PRB1909655 |
External content in standard search results should be supported | The full URL is truncated. |
Expected behavior: It should redirect the user to a valid URL. Actual behavior: External content in standard search results redirects the user to an invalid URL. |
|
Mobile Platform PRB1916140 |
Mobile Now Assist skill kit in product support | This is a product update. | |
|
Mobile Platform PRB1916141 |
Attachment and external content for standard search results | This is a product update. | |
|
Mobile Platform PRB1916148 |
Mobile NASS entry point update | This is a product update. | |
|
Mobile Platform PRB1919819 |
An error occurs when returning standard search results that don't have attachments associated with them | This problem occurs with iOS and Android requester 20.2. |
Expected behavior: Standard search results should return. Actual behavior: Error returning standard search results that do not have attachments associated with them. |
|
Next Experience Unified Navigation PRB1908169 |
An exact match for an experience with an invalid routeConfigId doesn't navigate | A new issue was found which results in Zing search results aren't opening properly within a workspace. |
Refer to the listed KB article for details. |
|
Next Experience User Menu PRB1904194 |
Filter users of type AI Agents from the 'Impersonate user' list | Disable users from impersonating any user of the identity_type 'ai_agents'. | |
|
Now Assist in Document Intelligence PRB1876011 |
Conversation hangs after a topic is selected | In the syslogs related to DocIntel, scheduled job errors occur. |
Notice that the topic will be selected, and 'Starting 'Loaner Laptop'...' is displayed, but then gets stuck. |
|
Now Assist in Document Intelligence PRB1898239 |
extractData fails to extract text from a CSV file due to an invalid character delimiter issue | Error: 'An unexpected error occurred while processing CSV file: IOException reading next record: java.io.IOException: (line 1) invalid char between encapsulated token and delimiter: java.lang.IllegalStateException: IOException reading next record: java.io.IOException: (line 1) invalid char between encapsulated token and delimiter...'. | |
|
Now Assist Panel PRB1907557 |
Modify the sys_script_318070047 f3012102 ff5e3136d 86653d.xml for Now Assist panel | ||
|
Now Assist Panel PRB1914236 |
Some channels aren't supported on enhanced chat | These controls aren't supported on all channels: Dynamic Choice, and Script Output. |
Expected behavior: Message asking for utterance appears. Actual behavior: Channel not supported appears. |
|
Now Assist Panel PRB1914534 |
Other components should be able to request AIEL to execute a skill | ||
|
Now Assist Panel PRB1916147 |
AI engagement layer initiative | This is a product update. | |
|
Now Assist Panel UX for Agents PRB1912755 |
Missing inline editing modal for existing ACLs for agentic workflows and agents |
Expected behavior: The modal should appear, and roles can be updated and saved. Actual behavior: No editing modal appears. |
|
|
Now Assist Panel UX for Agents PRB1913515 |
'Run As Triggers' at Agent level isn't initiating a conversation in sys_cs_conversation table |
Notice that 'Trigger Conversation' is not getting initiated. |
|
|
Now Assist Panel UX for Agents PRB1919813 |
Changes to accommodate new AIEL and Now Assist Panel configurations | This is a product enhancement. | |
|
Now Assist Panel UX for Agents PRB1919814 |
Changes to accommodate new AIEL and Now Assist Panel configurations | This is a product enhancement. | |
|
Now Assist Panel UX for Agents PRB1919815 |
Backend changes to align with sunsetted Now Assist Panel chat component and device type | This is a product enhancement. | |
|
Now Assist Panel UX for Agents PRB1919816 |
Capture invocation start to sn_aia_execution_plan to determine if it ran from playground, trigger, or chat discovery | This is a product enhancement. | |
|
OneExtend PRB1894063 |
The sendFeedback method throws an error: 'User is not authorized to update log record' |
Expected behavior: An edited response field should be updated in the sys_generative_ai_log table. Actual behavior: An edited response field isn't updated. |
|
|
Password2 Encryption PRB1893080 |
High memory consumption during SEK ReEncrypt on instances with millions of password2 data |
Expected behavior: The re-encryption completes successfully. Actual behavior: The encryption job ends abruptly because the node ran out of memory. |
|
|
Password2 Encryption PRB1914502 |
The 'Grant' rule is revoked even if there are SEK reEncryption failures |
Expected behavior: The 'Grant' rule isn't revoked due to failures in SEK reEncryption. Actual behavior: The 'Grant' rule is revoked despite SEK reEncryption failures. |
|
|
Performance Analytics PRB1912079 |
The homepage deprecation tool isn't populating the correct amount of 'Homepages not deprecated' in Yokohama |
Expected behavior: The amount of homepages not deprecated should display 7. Actual behavior: The amount of homepages not deprecated displays the value 2. |
|
|
Platform Analytics Dashboard API PRB1873441 |
The description is empty for data visualizations in a library | The description is empty for data visualizations in data-visualization-library when the properties 'com.glide.par.unified_analytics.enabled' and com.glide.par.v_table_join.enabled' are 'True'. |
Notice that the description can be seen in par_visualization.LIST. |
|
Platform Analytics Migration API PRB1863966 |
On the editing library visualization in the dashboard, the 'Save' prompt doesn't have the correct label after migration | This was initially fixed by PRB1713684 but no case fallback was added for visualisation without stored_component_name. The condition 'All stored visualisations will have name populated' is defined. |
Expected behavior: The message should say 'How do you want to save your changes to 'visualization name'. Actual behavior: The visualization name is empty. |
|
Platform Analytics Migration API PRB1869607 |
Platform Analytics Adminstration (PAA) always displays the 'UXA' menu | Customers upgrading to Yokohama without migrating won't have the PAA menu since the unified property is 'false' by default.The UXA setting menu is visible under Platform Analytics Administration whether user has run the migration or not. | |
|
Process Mining External Data Import PRB1870059 |
Record data generation isn't working as expected | The data is cleared from the import table and no records are generated after the user selects 'Create record data'. |
Import an external dataset in the external process mining guided set-up. Expected behavior: The user is able to create records based on the imported dataset. Actual behavior: After selecting Create record data, the page remains stuck at the progress view until refresh. After the refresh, the data in the import table is wiped out and no records are generated. |
|
Process Mining PRB1882225 |
Unexpected exceptions don't get propagated up in the log |
Throw an exception in MdTraceService during log collection. Notice that the exception details or stack trace are missing from the logs. |
|
|
Process Mining PRB1895034 |
Verify all analyst workbench statistics having two date units | Stats formatting in multiple areas in the 'Process details' need to be updated. | |
|
Process Mining PRB1901994 |
Process Mining GenAI skills are failing for 3P models |
Expected behavior: The skill should return a LLM response. Actual behavior: The skill doesn't display any key reasons. |
|
|
Process Mining PRB1905387 |
Addition of Query ACLs in Process Mining | This change adds new Query ACLs on certain table(s) and field(s) to grant query_range access. | |
|
Process Mining PRB1912315 |
Filter set models are calculated on an incorrect number of cases when filter set conditions match more than 10k results | There's issues with filter sets' data upload: 1. Use the correct page size value for fetching filter set case IDs. 2. Add a header line to a filter set file upload for the second page onwards. 3. Avoid a case count query for filter sets' file names to avoid timeouts while the data file name generates for a full mine. |
Expected behavior: It should mine all cases that match the filter sets and display the correct case count. Actual behavior: An incorrect case count is displayed for a filter set model. |
|
Process Mining Workspace PRB1861801 |
The count between tables in MDM is incorrect |
Open the project 'Incidents with Bad Change'. Notice that the count of records between the Incident table mine and Change table mine are incorrect. |
|
|
Process Mining Workspace PRB1862573 |
When the Contextual field is used in a contextual condition and the user edits the transition, 'id' is shown in the value list | The user is unable to select other values from the list when 'Priority' is 'id', and the scheduled task panel shows '2' instead of '2 - High'. |
Observe that the value for 'Priority' shows 'id', and the user is not able to select any other values from the value list; and the scheduled task panel also shows '2' instead of '2 - High'. |
|
Process Mining Workspace PRB1879536 |
Project copied from a Freemium project is accessible to a 'no role' user | The copied mined project is accessible to a 'no role' user, and the permissions itil and snc_internal role are copied over. |
Notice that the copied mined project is accessible to a 'no role' user with either an 'itil' or snc_internal role, and a non-analyst is able to do RCA, Clustering, Show records and Work Notes. |
|
Process Mining Workspace PRB1885485 |
The Overview page of the guided setup isn't loading for a project which is created via PA journey |
Observe that it goes into a continuous loop. |
|
|
Process Mining Workspace PRB1891796 |
Show an alert instead of a modal and update tool tip for 'Get recommendations' in the Guided Process Configuration | This problem was observed in Yokohama. |
Scenario 1:
Notice that the message, 'No recommendations available' appears in an alert pop-up. Scenario 2:
Notice that 'No recommendations available' appears in an alert pop-up. |
|
Project Management PRB1883485 |
A demand state isn't updating to 'Completed' after a project is created from a demand | This problem was observed in Yokohama. |
Notice that the state is changed to 'Completed'. |
|
Project Management PRB1885649 |
A cost plan roll up isn't happening for programs and portfolio |
|
|
|
Related List Action Model PRB1889099 |
When creating Attribute Adjustment for Price list line, the Price List Line id is not getting defaulted in the Attribute Adjustment form | This issue is noticed in Yokohama. |
Expected behavior: Apply to all Price lists should be unchecked and Price list line should be pre-populated with price list line id. Actual behavior: In the Attribute adjustment form, Price Line line is disabled and not pre-populated with price list line id. |
|
Reporting PRB1892235 |
When accessing scheduled reports, users are getting an error | When accessing scheduled reports, users get the error: 'Part of the query on par_coreui_migration _bridge_sysauto has been ignored because of insufficient access for 'query_match' operation' for non-admin users. | |
|
Restricted Caller Access (RCA) PRB1894354 |
A chat attachment doesn't go through to the user's side | . |
See that it is failing. |
|
Roles PRB1905646 |
A upgrade fix_script is taking more than 5 minutes to set the identity type for 8M records | An existing user should have an identity type. |
Notice that the total upgrade has taken 36 minutes. The fix script to update identity_type for sys_user records is taking 5 minutes. |
|
Roles PRB1906067 |
An AI Agent's identity type should be un-editable in the 'List' view | 'New User' creation should have an identity type. |
Expected behavior: The user should be blocked from editing the identity-type of AI-Agents from the 'List' view. Actual behavior: The choices option displays to the admin to modify the identity-type. |
|
Roles PRB1916157 |
Agent role controls for Identity type | This is a product enhancement. | |
|
Roles PRB1916160 |
Agent role inheritance restriction | This is a product enhancement. | |
|
Schedule Optimization PRB1888111 |
Handle ignored the state update on WM jobs correctly | Check ml_solution state before marking it as ignored. Jobs are marked as 'ignored' when the ml_solution state is still 'in progress'. | |
|
Schedule Optimization PRB1890329 |
Handle conflict API for the default intraday configuration |
Expected behavior: The banner message for conflict resolution should be displayed. Actual behavior: The banner message will not appear when there is a default intraday configuration that will run for all the qualifiers active in the instance. |
|
|
Schedule Optimization PRB1893394 |
Support the intraday attribute by overriding the configuration for conflict API |
Create an Intraday configuration with 'Attribute override'. Notice that the conflict API doesn't consider the attribute override. |
|
|
Schedule Optimization PRB1893918 |
When the task limit is exceeded, jobs stay in the 'In Progress' state, and the 'In progress' Prioritized Optimization (PO) job is ignored when the default job runs while it's still in progress | The PO job never comes out of the 'In progress' state. |
Notice that the PO job created stays in the 'In progress' state even after ML solution is complete, and never comes out of the 'In progress' state. |
|
Schedule Optimization PRB1897154 |
Agent Shift horizon time isn't considered correctly for an Intraday run |
Expected behavior: The WOTs should be assigned within a current day. No WOTs should be assigned for next day. Actual behavior: WOTs are assigned to the next day. |
|
|
Security Attributes PRB1852325 |
GlideSecurityManager. dotWalkQueryConditionToBuild QueryElementToGRMap expands dot-walked fields unnecessarily | When executing a query through the Table API or GlideRecordSecure, dot-walked conditions are expanded and the data is subsequently thrown out and not used if all ACLs on the target table are role-based. |
Expected behavior: GlideSecurityManager doesn't query for data that is not used. Actual behavior: GlideSecurityManager queries for the dot-walked condition fields, and throws them away shortly after. |
|
Security Attributes PRB1916143 |
'Are You an Agent?' security attributes | This is a product update. | |
|
Security Attributes PRB1916145 |
Default access posture security attribute | This is a product update. | |
|
Server-side scripts PRB1913500 |
script_include_names cache flushes are frequent and expensive | This may contribute to semaphore exhaustion during plugin install. | |
|
Service Catalog Builder PRB1876659 |
An admin user can't edit the catalog item in Catalog Builder | For an admin user, the role named 'catalog_builder_editor' is not mapped . Even if it's mapped manually, the user is still unable to edit the item using Catalog Builder. |
Expected behavior: It should launch the catalog item for editing in Catalog Builder. Actual behavior: The error message appears, saying the user is not authorized. |
|
Service Catalog Builder PRB1877599 |
Template is created from scratch; mask and url base instance questions are available in item level for Catalog Builder |
Expected behavior: 'mask' and 'url' shouldn't be available for selection in the question subtype for single lines. Actual behavior: 'mask' and 'url' are available. |
|
|
Service Catalog Builder PRB1878524 |
The 'Annotation' tab is missing from all newly supported question types in Catalog Builder | Support new variables in catalog builder. |
Expected behavior: The 'Annotation' tab should appear. Actual behavior: The 'Annotation' tab does not appear. |
|
Service Catalog Builder PRB1879309 |
Reference qualifier field is displayed as a Single line text field in Catalog Builder | Additional features for existing variables in Catalog Builder. |
Expected behavior: The Reference qualifier field should be multi-line text field. Actual behavior:The Reference qualifier field is single line text field. |
|
Service Catalog Builder PRB1879568 |
Values are auto-populated in some Lookup fields once the table is selected | Additional features for existing variables in Catalog Builder. |
Expected behavior: The Lookup field and lookup label should be empty. Actual behavior: The Reference qualifier field is a Single line text field. |
|
Service Catalog Builder PRB1879613 |
Incorrect message is displayed for catalog_builder_editor for a variable with an Advanced reference qualifier | Additional features for existing variables in Catalog builder . |
Expected behavior: The condition builder should be hidden and the message, 'This question contains advanced filter conditions. You do not have the required permissions to modify it' should be displayed. Actual behavior: The condition builder is hidden and the message, This question contains advanced filter conditions that cannot be modified in Catalog Builder' is displayed. |
|
Service Catalog Builder PRB1879905 |
Restricted question type count badge is not correct in template question page in Catalog Builder | Support new variables in Catalog Builder. |
Notice that there are 8 restricted question types. |
|
Service Catalog Builder PRB1879949 |
Question created through Catalog Builder isn't showing when it's opened for editing | The question is missing in the Catalog Builder, but can still be viewed in Platform. |
Observe that the question is missing in the Catalog Builder, but is still available in Platform. |
|
Service Catalog Builder PRB1880031 |
Fields and configurations sections are missing for Custom & Custom label question type in Catalog Builder | In addition to the issues with the 'Custom & Custom' label question type, the Macro and Summary Macro fields are missing in 'Additional details' tab and the 'Default value' tab is missing. |
Notice that the 'Permissions' and 'Auto populate' tabs are displayed for the label question type 'Custom & Custom', which isn't expected behavior. For catalog_builder_editor, the question type 'Custom & Custom' label is completely missing. |
|
Service Catalog Builder PRB1880041 |
Issues with the rich text label in Catalog Builder | In addition to issue for the rich text label, the tooltip text box is present in the 'Questions' tab, and 4 out of 5 fields in the 'Availability' section are unchecked. |
Notice that the 'Permission' configuration section is present for rich text label, and is missing in platform. |
|
Service Catalog Builder PRB1880597 |
Unable to update the default values for variables in Catalog Builder | The user is unable to edit the Default value field in these different scenarios. |
Scenario 1:
Expected behavior: The variable Default value field can be edited. Actual behavior: It is disabled. Scenario 2: Open many existing catalog items to edit. Observe that the Default value field is read-only and can't be edited. Scenario 3:
Observe that it's disabled and user can't edit the variable. |
|
Service Catalog Builder PRB1880645 |
Unable to create client scripts for Record Producers |
Expected behavior: There is no provision to create a client scripts for record producers. Actual behavior: A new section is shown to create a client scripts on record producer variables. |
|
|
Service Catalog Builder PRB1880798 |
The Unique values only checkbox isn't displaying for the variable type list with fixed values in Catalog Builder | Additional feature for existing variables in Catalog Builder. |
Expected behavior: The Unique values only checkbox should be available on the platform for the question type list with fixed values. Actual behavior: The Unique values only checkbox is not available. |
|
Service Catalog Builder PRB1880884 |
Cannot access catalog item from Catalog Builder if a multi-select (list collector) question is added | The user is unable to access the catalog item, and error messages occur. |
Expected behavior: The user should be able to access and edit the catalog item through Catalog Builder. Actual behavior: The user is unable to access the catalog item and an error message occurs, 'You are not authorized to edit this record'. When selecting Edit, and another error message occurs, 'Alert level: critical.unable to fetch variable values for producer'. |
|
Service Catalog Builder PRB1880949 |
The Delete client script button name is not appropriate | The Discard button name should be deleted in the confirmation modal when deleting the client script. |
Notice that in the confirmation modal, the button name should be deleted. |
|
Service Catalog Builder PRB1880953 |
Client script with a compilation error is also saved |
Expected behavior: The script shouldn't saved as is in Platform. Actual behavior: The script is saved. |
|
|
Service Catalog Builder PRB1881284 |
For list values from the table for the Lookup select box, the Choice field is updated in Platform but isn't shown in Catalog Builder | The first value in the Choice field that is updated in Platform isn't updated in Catalog Builder. |
Expected behavior: The value recorded in the Choice field in Platform should also show in Catalog Builder. Actual behavior: The first value for the Choice field from the option is shown in Catalog Builder. |
|
Service Catalog Builder PRB1881380 |
Simple reference qualifier becomes un-editable | The 'Conditions' section can't be seen and can't be edited by the user when the simple reference qualifier is selected. |
Expected behavior: The user should be able to see previously added condition and should be able to edit it. Actual behavior: The user is not able to see the 'Conditions' section when the simple reference qualifier is selected. |
|
Service Catalog Builder PRB1881535 |
Some fields are missing on Platform on the 'Type specification' tab in the list with fixed value variable types | When comparing the fields in the 'Type specification' tab between Catalog Builder and Platform, some fixed value variable types are missing in Catalog Builder. |
Expected behavior: The Choice table, Choice field, and unique values should be present only on Catalog Builder. Actual behavior: The Choice table, Choice field, and unique values only are missing on Catalog Builder. |
|
Service Catalog Builder PRB1881549 |
Some Label variable fields are missing on Platform | Some tabs are missing on Platform. |
Expected behavior: The 'Default value' and 'Permission' tabs should be present on Platform. Actual behavior: The 'Default value' and 'Permission tabs' are missing on Platform. |
|
Service Catalog Builder PRB1881673 |
Editing an existing catalog item client script using Catalog Builder shows the sys_id for the selected question | The selected question shows sys_id, even though was previously blank before switching between the 'Settings' and 'Actions' tabs. |
Notice that it shows sys_id in the selected question, which is not expected. |
|
Service Catalog Builder PRB1881680 |
The tooltip in the 'Question' tab and checkbox in the 'Availability' tab are missing for Rich Text Label fields | Two issues occur in the problem; in the 'Compare Question' tab, the Tooltip field is missing on Catalog Builder, and the 'Visible on Summaries' checkbox is missing 'Compare Availablity' tab on Platform. |
Notice that the Tooltip field isn't visible in the 'Question' tab on Platform, and the 'Visible on Summaries' checkbox isn't visible on platform. Refer attached ss |
|
Service Catalog Builder PRB1881716 |
For the 'Attachment' variable, the 'Default' tab is missing on Platform | The attachment type variable added on the catalog item in Catalog Builder doesn't appear in Platform. |
Expected behavior:The 'Default' tab should be visible on Platform for the attachment variable. Actual behavior: The 'Default' tab isn't visible on Platform for attachment variable. |
|
Service Catalog Builder PRB1881725 |
For custom variables, the 'Permission' tab is missing on Platform | The 'Permission' tab for custom variables doesn't appear on Platform. |
Expected behavior: The 'Permission' tab should be visible on Platform for custom variables. Actual behavior: The 'Permission' tab isn't visible on Platform for custom variables. |
|
Service Catalog Builder PRB1882070 |
Fields under the 'Type specification' tab aren't listed for all the fields for custom/custom with the label variable | Configuration sections of new variable types in Catalog Builder. Fields should have the search option enabled as it is in Platform. |
|
|
Service Catalog Builder PRB1882079 |
For a few variables, the 'Question' type isn't shown in the 'Questions' tab | Configuration sections of new variable types in Catalog Builder. |
Expected behavior: The 'Question' type should be displayed in 'Question' tab. Actual behavior: For lookup multiple choice, 'Question' type is displayed before 'Subtype'. |
|
Service Catalog Builder PRB1884912 |
Client script with a compilation error is also getting saved |
Expected behavior: The script shouldn't get saved as is in Platform. Actual behavior: The script gets saved. |
|
|
Service Catalog Builder PRB1890510 |
In the Catalog Builder, when the Use confirmation option is selected for a masked type variable, the text boxes in the question preview are highlighted in red even before any values are entered | Both fields are highlighted in red before any values are entered or compared in the Question preview. |
Expected behavior: Since no values have been entered initially and both fields are empty, they shouldn't be highlighted in red by default. Actual behavior: Even before any values are entered or compared, both fields are highlighted in red as if they contain mismatched input. |
|
Service Catalog Builder PRB1891330 |
In Catalog Builder, when creating a new lookup variable with a Name field that already exists, the 'Question preview' automatically displays the values of the existing variable by default | The 'Question preview' displays the values by default even before any tables are selected. |
Expected behavior: Since no tables have been selected initially, there should not be any values on the 'Question preview'. Actual behavior: Even before any tables have been selected, the 'Question preview' automatically displays the values of the existing variable by default. |
|
Service Catalog Builder PRB1891381 |
When the 'Add script' button is selected twice, the submission gets stuck forever for client script in Catalog Builder | The user is able to select the 'Add script' button again because its not disabled after the first time, resulting in the user getting stuck on the submission message. |
Expected behavior: The client script is created. Actual behavior: It is stuck with the submission message forever. |
|
Service Catalog Builder PRB1892257 |
Previous default value isn't cleared from the list while editing the question with new set of default values in Catalog Builder | Previously set default value should be cleared off from the list. |
|
|
Service Catalog Builder PRB1916121 |
Create a new role and provision to create a catalog item without templates | This is a product update. | |
|
Service Catalog Builder PRB1916126 |
Platform parity for Catalog Builder | This is a product update. | |
|
Service Catalog Portal Widgets PRB1910324 |
There's a dump error from the catalog in ynowassist | Notice the error: '...glide SYSTEM FailDMTUtil SEVERE *** ERROR *** File GLIDE INF/plugins/com. glideapp.servicecatalog .standard_ticket/update/ sys_ui_list_std_ ticket_action_input_ model.xml contains a record that will not correctly trigger collision detection. Expected the record to be in a file named sys_ui_list_std_ticket_action_input_std_ticket_config_action_null.xml'. | |
|
Service Catalog Portal Widgets PRB1911973 |
Unable to display the 'show more/less' menu for the 'Incident ticket' form |
Expected behavior: The incident standard ticket form must show the description along with the 'show more/less' toggle. Actual behavior: Despite of the configurations, the 'show more/less' toggle isn't displaying. |
|
|
Service Catalog Portal Widgets PRB1917271 |
Data model support for the 'Actions' framework | This is a product update. | |
|
Service Catalog PRB1813722 |
Warning message is displayed in English in 'Fulfillment' under 'Custom task' instead of Spanish |
Expected behavior: The warning message should be displayed in Spanish. Actual behavior: The warning message is displayed in English. |
|
|
Service Catalog PRB1879960 |
Creating a masked variable using Catalog Builder isn't showing the Confirmation field in the preview | After going into 'Additional details' for 'Use Confirmation', the Confirmation field doesn't display in the 'Preview' section. |
Expected behavior: The Confirmation field should be displayed in the preview. Actual behavior: The Confirmation is not displayed in the preview. |
|
Service Catalog PRB1884919 |
Invalid Catalog Builder info banner in case text to catalog is not enabled | The banner appears even if sn_text2catalog isn't active or installed. |
The banner shows 'Created using Now Assist' even if the instance doesn't have sn_text2catalog active or installed. |
|
Service Catalog PRB1888902 |
While creating a new question for the type 'Display Label', the sub type 'Plain Text' shows as the 'Default value' tab |
Expected behavior: As it is a static label of plain text, it shouldn't display the 'Default value' tab. Actual behavior: It shows the 'Default value' tab, which is not correct in Platform UI16. |
|
|
Service Catalog PRB1889278 |
Item links in the 'Categories' page of the Service Operation Workspace (SOW) aren't shown in the color blue | Links aren't underlined in the color blue. |
Expected behavior: The item links shown for each category should be displayed with blue color underlined. Actual behavior: The links are underlined with black color which is not expected. Scenario 2:
Expected behavior: The search results links should be shown in blue color underlined. Actual behavior: It is not shown with blue underlined color. |
|
Service Catalog PRB1889281 |
In Catalog Builder, the lookup source for selectbox variable shows |
Expected behavior: The lookup source shouldn't be there for the selectbox variable. Actual behavior: The lookup source is displayed for the selectbox variable, which has no significance for the selectbox variable. |
|
|
Service Catalog PRB1890938 |
The value in the Name field doesn't change based on the value selected in the Table field for the record producer in Catalog Builder | The Name field is dependent on the value in the Table field with Map to a specific field on the table is selected. |
Expected behavior: The Name field is dependent on the value selected in Table field when Map to a specific field on the table is checked. Actual behavior: When the value selected for the first time, the Table field updates the Name field, but the values don't change when Map to a specific field on the table is checked. |
|
Service Catalog PRB1894620 |
The lookup_depends_on field isn't updated with the new reference on catalog item for copy/checkout |
Expected behavior: The new var2 should have its Choices depends on field point to the new var1 copy. Actual behavior: It still points to the previous items var1. |
|
|
Service Catalog PRB1904034 |
Selected link nudges aren't captured in telemetry |
Expected behavior: The link should be logged to the catalog_builder_analytics table. Actual behavior: None of the link nudges are working. |
|
|
Service Catalog PRB1916120 |
Client scripts in Catalog Builder | This is a product update. | |
|
Service Catalog PRB1916122 |
The ability for catalog authors to control prefill behavior (KG, user personalization API, chat history) | This is a product update. | |
|
Service Catalog PRB1916139 |
Lookup selectbox and lookup multiple choice to take values from the sys_choice table as choices | This is a product update. | |
|
Service Catalog Wizard PRB1874235 |
Scripted UI Policies don't run in the Service Catalog Wizard |
Expected behavior: Scripts of the policy must run in wizard. Actual behavior: Scripts of the policy don't run in wizard. |
|
|
Service Catalog Wizard PRB1877107 |
Variable permissions are not honored on the Catalog Wizard framework | Two scenarios occur in this problem where variables aren't being honored. In scenario 1, the value for the Meta field is reset. In scenario 2, write permissions aren't honored and the script is executed. |
Scenario 1:
Expected behavior: The value for meta should be 'Modified meta tag value'. Actual behavior: The value is reset the default value provided on the question. The same should be the behavior on the variables in the producer set of type one to one. Permissions are not supported if a variable is in the MRVS producer set. The behavior should remain same for MRVS producer set. Scenario 2:
Expected behavior: The mode should be considered if the main record is updated, and should honor write permissions. The script shouldn't be executed. Actual behavior: The script gets executed. |
|
Service Model Foundation - Business Location PRB1896747 |
Addition of Query ACLs in Service Model Foundation - Business Location | This change adds new Query ACLs on certain table(s) and field(s) to grant query_range access. | |
|
Software Asset Management PRB1795842 |
'Created Source' is not always stamped on software models by content update jobs | This issue usually occurs because the scheduled jobs below don't stamp the Created source field if it's empty on the suite parent: SAM - Apply latest content changes and SAM - Create lifecycles and suites for a software model. | |
|
Software Asset Management PRB1807639 |
Some Software Asset Management (SAM) properties can be edited by a SAM admin | Some SAM sys properties exist in different folders and have different write roles. |
|
|
Software Asset Management PRB1857027 |
Performance enhancement for the 'Bookkeeping for dedup on delete' business rule |
The number of records to update may be reduced if there's an additionally query on primary_install is not null and deduplicated=true. |
Refer to the listed KB article for details. |
|
Software Asset Management PRB1916117 |
Create a reclamation rule on the License Workbench 'Product results' page | This is a product update. | |
|
Software Lifecycles (Family Channel) PRB1910582 |
There's a duplicate sys_choice for current_lifecycle_phase in sam_sw_product_ lifecycle_report |
The duplicate might be coming from the older field as they don't exist in that older field anymore. | |
|
Stream Connect Core PRB1899152 |
Change the labels for the sys_sc_alerts table | UX has suggested to change labels for some of the columns in the sys_sc_alerts table: 1. Target ID: Affected Entity, 2. Alert Level: Severity, and 3. Type: Alert Type. | |
|
System Notifications PRB1838563 |
The base instance bell notification hover does not work intermittently | Full details are not showing whenever the pointer hovers on top of the bell notification to see the full details. |
Observe that the full details are not showing. |
|
System Update Sets PRB1885422 |
Importing an update set of an upgrade plan or items also installs the applications on the instance |
Observe that the upgrade plan/items are installing applications on the prod instance while importing it. |
|
|
System Update Sets PRB1909130 |
An installation from an update set overwrites customized records | To remediate the update set, the commit should be backed out (including a rollback of the app install) and a different way of installing the application should be used. |
Refer to the listed KB article for details. |
|
Table Cleaner PRB1860821 |
TableCleaner doesn't resolve gateways | Since TableCleaner is uses the API 'DBConfiguration.getDBI', which can only resolve it. |
|
|
Territory Planning PRB1837020 |
In Dispatcher Workspace, there's an issue with a search territory agent | If the agent belongs to multiple groups, and the last group returned from the glideRecord query doesn't belong to the territory, and triggers the issue. | |
|
Tier 2 Storage Offload PRB1889818 |
The default retry period for failed offloads is too low | The default retry period should be 6 hours. |
Notice that the records never get offloaded. |
|
Tier 2 Storage Offload PRB1890721 |
Tier 2 offload runs should be visible in the 'Archive rules' page | Users have no visibility of whether the offload is running or not. Progress should be viewed in the 'Archive rules' page. |
Expected behavior: On the Archive Rule form next to Archive Run, there is a tab where the users can review offload runs. Actual behavior: Information is not available on the Archive Run form. |
|
Tier 2 Storage Offload PRB1897660 |
Change the sys_property glide. db.archive.offload. free_storage_max_gb value from 100GB default to 36T | ||
|
Transaction Management PRB1871282 |
There's an IndexOutOfBounds and StringIndexOutOfBoundsException exception in transaction prioritization | This issue can occur under heavy load testing. This has been identified as the cause for a memory leak where HTTPTransaction objects are held onto after this exception causes the request to fail. | |
|
UI Actions PRB1879023 |
A workspace modal with an HTML field doesn't render in Yokohama | When using g_modal.showFields() in a UI action to populate the modal from the workspace, the modal doesn't appear if it has an HTML type field defined. | |
|
UI Field Administration PRB1791024 |
The getSelectedOption breaks for records with some script type fields | . | |
|
UI Field Administration PRB1821427 |
An instance runs out of memory when there's unexpected wiki markup table syntax inside of a Wiki text field | When creating a kb_knowledge record on a form with the Wiki field showing, the node runs out of memory. | |
|
UI Form Administration PRB1887884 |
A Dependent field onChange handlers fires when the Depends on field changes when there's no change to the Dependent field | There are client scripts on various task-based tables that clear the assigned_to when assignment_group changes. These tables can't be tested on (for example: change_request, incident, problem, problem_task) as it will appear that the Dependent field onChange handlers fire when the Depends on field changes. A table that doesn't have existing client scripts on the assignment_group field like change task (change_task) must be used. |
Notice that the info message isn't displayed because onChange handlers for the Dependent field (assigned_to) are not fired. |
|
UI Form Administration PRB1893949 |
A Mandatory field hint sometimes is missing the 'Mandatory' prefix | The help text (hint) is missing the prefix of 'Mandatory' for certain fields even when the field is mandatory. |
See that the prefix 'Mandatory' is missing. |
|
Upgrade Center PRB1891562 |
A user is unable to determine the purpose of a link when it has the context 'Here' |
Note that the screen reader announces 'here' as the link and not what the link is for. |
|
|
Upgrade Center PRB1895609 |
Glide upgrade failed due to node getting restarted | This is an edge case where a certain combination of plugins trigger this behavior. |
|
|
Usage Analytics PRB1898047 |
On Yokohama, User Analytics data isn't refreshing post-clone, copy, or restore | Cloned/Restored/Copied instances start tracking usage data and are able to see the data on the UXA Dashboard. |
Refer to the listed KB article for details. |
|
Usage Analytics PRB1904448 |
Some users don't want internal ServiceNow instances such as support, impact, or nowlearning to track their users | ServiceNow instances should be able to turn off the tracking of Usage Analytics data with their custom script and system property. |
Actual behavior: Observe that the metric calls are still going with Essential Tracking Level. Expected behavior: There should be no metric calls. |
|
Usage Analytics PRB1905285 |
An empty or invalid hashUserId column in the sys_user table breaks metric call validation and user event enrichment, leading to inaccurate UXA dashboard metrics | Users with incorrect usage data displayed on the UI due to user table settings now have usage data being collected properly and reflected on the UXA dashboard. | |
|
UX Framework PRB1889441 |
Pagination is broken in Multi-Data source broker | Cursors are stored in the format of the map, which is converted to the byte stream and base64 encoded. While decoding, the cursor is expected to be JSON, and throws an exception. |
Notice that the response doesn't have updated results. |
|
UX Framework PRB1889452 |
The name/sys_id of the data source is not returned in the response of multi-table data | The response of the data broker only returns the table. |
Notice that the response of the data broker only returns the table, but, not the name/sys_id of the data source. |
|
UX Framework PRB1890019 |
Using Zing search results in wrong pagination with Multi-Source data broker |
Notice that is_last_page value is true, when it should've been false. |
|
|
UX Framework PRB1901587 |
Intent Library changes cause a SEND_INTENT_FEEDBACK error due to no meta.generatorForFeedback | The NAP window eventually displays a message that reads: 'An error occurred while saving your app. Please check with your admin.' The following error can be observed in the browser console: 'IntentTranslatorBehavior: LIBRARY-INTENT-CHANNEL#SEND_INTENT_FEEDBACK action is missing generatorForFeedback from meta'. | |
|
UX Framework PRB1904903 |
Results of different data sources have the same source ID | The datasource ID is set as static, hence all the results share the data source of the last result. |
|
|
UX Framework PRB1916142 |
Intent library updates for Gen AI Canvas | This is a product update. | |
|
Virtual Agent PRB1826252 |
User inbound messages to a Live agent end up in the picker pagination logic in specific scenarios for channels | The user inbound message to a Live agent somehow ends up in the picker pagination logic in CAF if the last rich control before invoking the live agent was a paginated picker. |
|
|
Virtual Agent PRB1874005 |
A record in provider_user_map is still inactive, causing Now Virtual Agent to fail approvals | When a sys_user record becomes active after being deactivated, provider_user_map is still inactive and there's no logic to activate the mapping. The user still receives a notification for record approval in Microsoft Teams because the mapping exists, even though provider_user_map is inactive. When the user attempts to approve the record, an error occurs because their record in provider_user_map is still inactive. | |
|
Virtual Agent PRB1892416 |
Incorrect column usage when updating the One API Service Plan Invocation record | A warning occurs in the logs. |
|
|
Virtual Agent PRB1892510 |
Support 'Sync' mode for Java execution path | Currently, the Java execution path for OE system executor capabilities are limited to just the async mode. This is limiting the ability to execute troubleshooting tools via background scripts. The 'Sync' mode execution should be fully supported for the Java path as well. | |
|
Virtual Agent PRB1894471 |
Virtual Agent push notifications aren't coming through on mobile | Noticed on Android. |
Expected behavior: Users should see a push notification. Actual behavior: There's no push notification in NASS. |
|
Virtual Agent PRB1894545 |
LLM responses are not unmasked if streaming is enabled with java proxy enabled |
Expected behavior: The unmasked email/phone numbers are displayed. Actual behavior: The email/phone numbers are displayed with masks. |
|
|
Virtual Agent PRB1895195 |
When the user enters an invalid/partial utterance, an error appears and the conversation is closed | Dynamic capability executor can trigger multiple capabilities with different payloads. However, dynamic capability executor fails when duplicate capability IDs are passed. | |
|
Virtual Agent PRB1896593 |
Shouldn't be relying on the 'Greetings' topic for portal's Virtual Agent hand off | Users can have custom 'Greetings' topics. For those users, the hand off is broken. | |
|
Virtual Agent PRB1898661 |
Non-LLM time has increased from 2544 to 3065 milliseconds (ms), leading to 500-900 ms in some NAVA use cases | In NAVA use cases, users observed 500–900 ms degradation from 2544 to 3065 ms in non-LLM async time. For a synthesized response, the non-LLM has degraded and it's spending additional 1.2 secs on that. Hence, the overall gain on the response stands at 5.3 seconds (6.5-1.2). | |
|
Virtual Agent PRB1903011 |
The error 'Cannot invoke 'org.apache.commons.httpclient.StatusLine.getStatusCode()' because 'this.statusLine' is null' for LTM capabilities | The error is observed in the Gen AI logs for the conversation. |
Observe that in the Gen AI logs for that conversation, there's an error, 'Error: Cannot invoke 'org.apache.commons.httpclient.StatusLine.getStatusCode()' because 'this.statusLine' is null Error Code: 200000'. |
|
Virtual Agent PRB1905944 |
enableDynamicTranslation and enableNativeTranslation should be passed as boolean values | ||
|
Virtual Agent PRB1908511 |
Now Assist panel (NAP) assistants should read agentic mode from now_assist_ va_search_results _output_type | NAP assistants (both legacy client and new dynamic window) should read agentic mode from the Now Assist panel record on now_assist_ va_search_results _output_type. The new dynamic window UI for NAP has been reading from the mweb record instead. | |
|
Virtual Agent PRB1912380 |
Don't log agent skill execution licensing | It shouldn't create a licensing record when an agent skill is executed. The AIA framework does its own calculation/logging for agent execution based on the execution tasks created at runtime. | |
|
Virtual Agent PRB1912588 |
AiAgentSecurityMigration and AiAgentSecurityHelper script includes needs to be in the global scope | ||
|
Virtual Agent PRB1913835 |
Canvas isn't displaying the Show/Hide options when executing a skill | While Web Agent is executing the goal, the live 'Screenshot' view isn't loaded. After the execution, it's displaying the Show/Hide view, which is displaying all the screenshots. |
|
|
Virtual Agent PRB1913892 |
Validation should be added for security attribute ID in global.GenAiSkillSecurityUtils().insertSkillAclBySkillid(...) and global.GenAiSkillSecurityUtils().updateSkillAclByAclId(...) | While calling global.GenAiSkillSecurityUtils().insertSkillAclBySkillid(...) and global.GenAiSkillSecurityUtils().updateSkillAclByAclId(...) with invalid sys id of security attribute, the security attribute is created with an empty condition. Since it is expected to used with Background script, the user should be informed of the invalid value used for the security attribute. | |
|
Virtual Agent PRB1915460 |
gen_ai_agent and gen_ai_workflow advance is turned off in the ACL form16 UI |
Observe that there's no option called 'advanced'. |
|
|
Virtual Agent PRB1915751 |
Midtopic switch isn't switching to a new topic and runs into an error on the continuing existing topic |
Expected behavior: The user should be given an option to switch to the 'Order coffee' topic and have an option to continue the request. Actual behavior: The user gets the order food topic started again and choosing 'continue' runs into an error as well. |
|
|
Virtual Agent PRB1915793 |
There's an incorrect name for flows when creating 'invoke_from_ai' ACLs |
Execute this API to create ACLs for flows used as tools: 'new global. AiAgentSecurityMigration() .run( true)'. Observe that for the subflow ACLs, the ACL is created with 'name' instead of 'internal_name', which is incorrect and it's missing ACL evaluations at run time. It's defaulting to global * ACL due to the incorrect name of the flow. |
|
|
Virtual Agent PRB1916762 |
An ACL restriction on sys_one_extend _resource_edge prevents websearch from being accessible to users |
Observe a 'sorry' message. |
|
|
Virtual Agent PRB1917121 |
Update the ACL name for OE skills to align with changes from the OE team | Update the ACL name format to use the '<sys_name.skillConfigId' format instead of the 'skillConfigId:<sys_name' format (where skillConfigId is the sys_id of the record, and sys_name is the name of the record in sn_nowassist_skill_config). This is only applicable when the 'internal_name' column in the sn_nowassist_skill _config table is empty. | |
|
Virtual Agent PRB1917378 |
Agentic eval metric score standardization | It should incorporate the changes in NASK to display the label in the list view and the drill down view. | |
|
Virtual Agent PRB1918363 |
Canvas isn't working | The 'Show' button doesn't appear at end of the execution. |
Expect behavior: At end of the execution, users will see the Show button. Actual behavior: Nothing appears. |
|
Virtual Agent PRB1918740 |
Querying on virtual column for retrieving skill metadata fails |
Expected behavior: Previously associated skill applicability records should be deleted. Actual behavior: Previously associated skill applicability records still exists. |
|
|
Virtual Agent PRB1921142 |
Pass agentic data to the conversational pipeline | This is a product enhancement. | |
|
Virtual Agent Web Client PRB1893104 |
In Now Assist Multi-Turn Catalog Ordering, the 'Data/Time' type variable isn't showing the current time, but as 00:00AM in Virtual Agent for non-English language mode | The 'Data/Time' type variable should be displayed as the current time across all language modes. |
Expected behavior: The 'Data/Time' type variable should be displayed as the current time, which is the same in the English language mode. Actual behavior: The 'Data/Time' type variable displays as 00:00AM in the Japanese language mode. |
|
Virtual Agent Web Client PRB1897932 |
NAVA isn't picking interaction context variables when enhanced chat is turned on | Account and contact fields aren't populated on an interaction record. Note that the issue isn't reproducible when enhanced chat is turned off in Virutal Agent. | |
|
Virtual Agent Web Client PRB1901424 |
Chat client lets multiple messages be sent through simple scripting |
Expected behavior: Chat client shouldn't allow multiple inbound messages. Actual behavior: Chat client allows multiple inbound messages. |
|
|
Virtual Agent Web Client PRB1904063 |
Typing too fast in an NLU-based text choice picker for a lot of rows prevents upgrades |
Expected behavior: It should update the filtered items in the list. Actual behavior: The results never update due to 423 errors in the backend responses. |
|
|
Virtual Agent Web Client PRB1910411 |
A user receives notifications when a notification toggle in the settings is turned off | ||
|
Virtual Agent Web Client PRB1920026 |
Proactive trigger topics don't launch |
Expected behavior: The topic should launch in Dispatcher Workspace. Actual behavior: The topic doesn't launch, and the user just sees the welcome message. |
|
|
Visual Task Boards PRB1852813 |
If the modal window is closed by selecting outside of the modal, VTB cards aren't refreshed automatically when updated | This only occurs if the modal window is closed by selecting outside of the modal. If the modal window is closed by selecting the 'X' in the top right, the record's card updates automatically as expected. |
Observe the card is no longer on the board. |
|
Web Content Accessibility Guidelines (WCAG) Conformance PRB1818332 |
The tool tip for catalog items is not announced by the screen reader for accessibility | ||
|
Window Manager PRB1920314 |
Upgrade to Yokohama Patch 6 is broken with the Windows Manager (WM) plugin | Adding the Windows Manager plugin to the glide-core-ui-components plugin in a patch creates a new version that uses the next commit SHA. The commit SHA is lower, and in the upgrade process, the lower version is skipped even though it is the 'new' version with the WM plugin added. |
Notice that Window Manager is not activated whereas it should be. |
|
Work Order Management PRB1902998 |
When re-assigning an Agent Work Schedule record from one agent to another in a collapsed group, agent blocks aren't properly reflected | The white markp shows an inaccurate work schedule for the agent with the updated schedule. |
Expected behavior: White markp should be displayed for the updated user, and the previous user that was assigned the Work Schedule should go back to gray. Actual behavior: White markp now appears for the previous agent that was assigned a work schedule as well as the updated agent, and two markps are present. |
|
Zero Trust Access PRB1830413 |
Zero Trust Access (ZTA) policy-based authentication is applied for Impersonation |
Expected behavior: ZTA shouldn't apply for the impersonated user. Actual behavior: ZTA policies are applied, and the ITIL role is relegated from impersonation. |
Fixes included
Unless any exceptions are noted, you can safely upgrade to this release version from any of the versions listed below. These prior versions contain PRB fixes that are also included with this release. Be sure to upgrade to the latest listed patch that includes all of the PRB fixes you are interested in.