Zurich security and notable fixes
The Zurich release contains important problem fixes.
- Zurich was released on July 31, 2025.
-
- 07-23-2025_1759
- glide-zurich-07-01-2025__patch0-07-15-2025
For more information about the release cycle, see the ServiceNow Release Cycle.
For a downloadable, sortable version of the fixed problems in this release, click here.
Notes for Zurich
- 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 |
|---|---|---|---|
|
Access Control PRB1833782 |
There's slowness when loading forms with TableChoice fields related to the RecordFamilyResolver .archiveTableHas ACLTerms code path | Accessing any form with a TableChoice field where the instance has more than 250 archive tables can result in slowness due to RecordFamilyResolver .archiveTableHasACLTerms code path and a change to CACHE_ARCHIVE_TABLE _HAS_ACL_TERMS in Xanadu. |
Refer to the listed KB article for details. |
|
Access Control PRB1840256 |
Excessive syslog logging from AccessTerm 'Slow ACL' | Excessive logging from AccessTerm 'Slow ACL' is detected in syslog shards. | |
|
Access Control PRB1840787 |
itil role users receive an error on short description suggestions | itil role users observe several errors when selecting the Suggestion button on short descriptions on incident records. |
Observe errors regarding the 'sys_choice' table. |
|
Access Control PRB1868511 |
Adding other roles to the 'Contains role' tab in the 'snc_internal' role causes unexpected behavior | Newly created users don't receive the 'snc_internal' role when logging in, or getting impersonated, for the first time. |
Expected behavior: Roles can't be added to the 'Contains role' related list in the 'snc_internal', or there's a business role or another check that informs the user when they are doing it. Actual behavior: A newly created user doesn't receive 'snc_internal'. In node logs, users can observe: '*** WARNING*** RoleAccessHandler: User does not have the role...' |
|
Action Bar Component PRB1840507 |
An incorrect action bar intermittently displays |
Expected behavior: The action bar shouldn't change. Actual behavior: The action bar changes in a few seconds after the case is accepted. |
|
|
Activity Stream Compose Component PRB1897434 |
The 'Email' tab in the Activity Stream in the CSM Configurable Workspace doesn't resize when the text is larger than the vertical limit | This issue is found in Yokohama, but works as expected in Xanadu. |
Expected behavior: The email text box auto-resizes vertically. Actual behavior: The email text box doesn't auto-resize. |
|
Activity Stream PRB1830587 |
Activity Stream doesn't limit the size of journal fields | The maximum size of journal entry appears to be either 50Kb or 100Kb by default. UI16 has a 10MB limit on the total journal field size. Once this limit was reached it truncates every journal entry to 50K. The entry cap is 250 by default. The entry cap is 30 for attachments. The size cap + entry cap is what ensured no out of memory errors in UI16. |
Expected behavior: The incident should load with these massive strings. Actual behavior: Chrome and Edge crash as the browser runs out of memory.
Expected behavior: The incident should load in SOW. Actual behavior: The Glide server crashes with an out of memory error. |
|
Activity Stream PRB1858894 |
Application Programming Interface (API), Now Platform, and GraphQL are slow due to the Table Cleaner being throttled causing heavy replication lag | API, Now Platform, and GraphQL calls are slow specifically because of the Table Cleaner on sys_activity shards. Using Instant Alter added an index, and as a result, all records were replicated with the load causing replication lag. When replication lag is detected, Table Cleaners are throttled, which can exacerbate the amount of data that is being replicated and cause timeouts. Timeouts are caused by the Table Cleaner running synchronously in the Activity Stream load request. |
Refer to the listed KB article for details. |
|
Activity Stream PRB1860591 |
Work notes are presented as encrypted text within the 'Activity' section of the ServiceNow Workspace when the encryption configuration is active | There's column-level encryption enabled and configured for the work_notes field. When a user with a target role specified in the sys_platform_ encryption_configuration record is posting worknotes in workspace, they are unable to see unencrypted text. Instead, they're seeing encrypted text. When the same user posts worknotes in the native view, the text isn't encrypted. | |
|
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 PRB1893483 |
No activity displays in UI16 when a blank journal event is added to the Activity Stream | After upgrading to Yokohama, some records display 'No Activity' on the platform view. A null pointer exception displays. | |
|
Agent Chat PRB1862727 |
A 'Show audio' modal appears when an agent presence state is changed to 'Available' for Safari users | A user interaction is required on the page for the audio to work, especially in inactive tabs. This was enforced by a modal when the audioContext was detected to be suspended, which occurs when a new AudioContext is created in the page. Now, the modal appears for Safari whenever the presence changes in the inbox to 'Available' to avoid having users refresh the browser to see the modal. | |
|
Agent Chat PRB1887118 |
The 'new message' sound and desktop notification aren't working in legacy workspace |
Expected behavior: When desktop and sound notifications are turned on, an agent should hear the sound for a new message and receive desktop notifications for the new message. Actual behavior: There's no sound or desktop notification. |
|
|
Agent Chat PRB1900981 |
Inbox audio is delayed when the 'Workspace' tab is inactive or out of focus before receiving the first work item | When the work item assigned, audio isn't heard. Audio is heard only after switching back to the workspace. The agent may not get notified at the time of assignment due to this issue, and the work item may expired by the time agent is back on the workspace tab. |
Refer to the listed KB article for details. |
|
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. |
|
AI Search Glide PRB1590070 |
Index events take a long time when there's a substantial amount of data in the sys_translated table | When indexing the Translated field from the sys_translated table, all the data for a particular table is cached at once. When there's a frequent update or insert to the sys_translated table, the rebuild cache takes an average of 5 seconds to 8 seconds per event. |
Observe the cache was rebuilt with all data from that table. |
|
AI Search PRB1823459 |
AI Search indexing 'Topic Path Translation' doesn't work for a non-system user preference language | Session users assigned as 'guest' with the sys_user_preference file 'name=user.language' and 'value=some_non_ user_session_language' have topic paths indexed in this language. The set language isn't effective, which is the cause of incorrect translations. |
Expected behavior: AI Search should index, and be able to search with the 'en' topic value. Actual behavior: AI Search indexes content with Deutsch translations for documents with both English and Deutsch languages, and the search for English fails. |
|
AI Search PRB1824166 |
A translated reference field is indexed in a different language in a single record update instead of a full table index | The peekahead is using the same value for different langauges. |
Expected behavior: kb_knowledge_base is in Spanish. Actual behavior: kb_knowledge_base is in English. |
|
AI Search PRB1825963 |
Index KBB throws an exception about journal peekahead | An error is thrown: 'IngestService: Unable to index Glide Record [9b85baaa3bf11a10 c4589c8c24e45a2b] u_kb_template_topic_category. fa8191f6fb059 e507863f46b5eefdc1d : Cannot invoke "java.util.Map.get(Object)" because "journalElementToValuesMap" is null java.lang.NullPointerException: Cannot invoke "java.util.Map.get(Object)" because "journalElementToValuesMap" is null...' |
Refer to the listed KB article for details. |
|
AI Search PRB1836358 |
A race condition causes an incorrect deleteMultiple() query to be generated on the v_search_genius_result and sys_variable_value tables | When the AI Search Genius Result is requested and processed in a multi-threaded, high-concurrency environment, such as when multiple users simultaneously perform search functions on a portal or virtual assistant (VA), a thread safety issue arises. This issue may cause an incorrect deleteMultiple() query to be generated, potentially leading to the deletion of excessive records from the sys_variable_value table. As a result, various components, including the Integration Hub, Service Catalog items, and workflows, may malfunction due to the absence of these critical records. |
Refer to the listed KB article for details. |
|
AI Search PRB1837035 |
Catalog item access isn't evaluated correctly when there is service_portfolio in some cases |
Refer to the listed KB article for details. |
|
|
AI Search PRB1837962 |
When a query is performed in 'OR' mode, the pagination breaks | 0 results are returned. |
Observe that there's no matches. |
|
AI Search PRB1841283 |
There's errors in logs during ingestion for users without GAIC or Semantic Search | If there's no semantic search configured, the log shouldn't be polluted with errors. | |
|
AI Search PRB1843005 |
The text '(number) results for (keyword)' text is not translated when using AI Search | After installing a language plugin and switching the language to a non-English language, the text '(number) results for (keyword)' is not translated when using AI Search. This occurs when a keyword is misspelled when using AI Search. |
Expected behavior: The text '(number) results for (keyword)' text is translated to the non-English language. Actual behavior: The text '(number) results for (keyword)' text is seen in English and is not translated. |
|
AI Search PRB1844340 |
The AI Search class can't handle a non-rotated table | If the [sysevent] table isn't configured for table rotation, AI Search can't process indexing events and an error is seen in the system logs. |
Refer to the listed KB article for details. |
|
AI Search PRB1850631 |
The Table field for EVAM view configuration matching of a search record is always the parent table | With the new EVAM-lite implementation, there are 3 gaps in the logic for determining which view configuration to use for a given search result. 1. If a view configuration has a condition based on a field that isn't included in the list of table fields, that field won't be returned from AIS, and so the condition never matches. Even if the field is included on the 'Table Fields' list, if it's a field that only exists on a child table of the table the indexed source is based on, the field won't be returned from AIS and so the condition never matches. If the first view configuration for a particular table comes after the default/global view config, it is never used. Whereas, EVAM had a more nuanced selection process that would look for all view configuration that matched on the table before falling back to those for ancestor tables or the global/default table. |
Expected behavior: Service Portal's EVAM Def'n has a view configuration called 'Catalog Search Results - Order Guides', which has a condition of 'sys_class_name = sc_cat_item_guide^EQ'. This is the view configuration that should be used, and the syslog entry should contain: '[SEARCH EVAM] SearchResultTemplateGenerator: Using View Config 44c37371 c32020108 25039b06 e40dd4b for Result with table sc_cat_item and sys_id 6690750 f4f7b4200086 eeed18110c761'. Actual behavior: The incorrect view config is being used. 633c3b5 d53a71010968 addeeff7b1218 is the sys_id of the view configuration called 'Catalog Search Results', which is the generic view configuration for catalog items, and doesn't have any conditions beyond table. But the 'New Hire' category item is an 'Order Guide', and there's an EVAM view configuration specifically for that. |
|
AI Search PRB1862241 |
There's an error in the logs when using a catalog Genius Result | One generates every time that a user requests a Catalog Genius result when the mode is async. |
Observe the error: '[SEARCH API] SearchCheckpointService: Unable to post checkpoint, Callback name missing: no thrown error'. |
|
AI Search PRB1875775 |
Field-level permissions should only apply when building template props |
Expected behavior: The user is taken to the 'sc_cat_item' guide page. Actual behavior: The user is taken to the 'sc_cat_item' portal page. |
|
|
AI Search PRB1885285 |
When Zing is the search engine for global search, data broker is still executed and pollutes the syslog | The underlying cause is that the composite data broker resource in the UI Builder app for the global search page is wired up to use the search term from the URL as an input, and so executes every time it changes after the initial search. |
Refer to the listed KB article for details. |
|
AI Search PRB1885594 |
AI Search attachment results aren't redirecting to the parent record | The issue is reproducible in Yokohama and Xanadu instances. |
Notice that it's not redirected to the parent record. It's redirected to the sys_attachment.do? sys_id=undefined& searchterm=detail. |
|
Analytics Data API PRB1845187 |
Drilling down on KPIs in a Performance Analytics dashboard produces an error 'no internet connection"' | Drilling down on any value redirects the user to the KPI details page with a 'No Internet connection' error. |
Refer to the listed KB article for details. |
|
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 Install Engine PRB1846815 |
Admins users aren't able to repair/install all dependencies when domain separation is enabled | An issue was observed where a parent application (e.g., Now Assist For CSM) was installed successfully, even though its dependencies (e.g., sn_genai_platform) weren't installed during the process. This behavior is unexpected. |
All the dependencies should be installed with the parent app. |
|
Application Manager PRB1834952 |
The Service Bridge Base plugin doesn't automatically upgrade when the Service Bridge for Providers plugin is upgraded | This issue occurs for users in a non-global domain or scope. | |
|
Appointment Booking PRB1894193 |
The scope of the Appointment Booking service's configuration was changed in Yokohama, which leads to a scope access issue | After upgrading to Yokohama from Washington, the value of the 'Availability' table changed from wu_appointment to empty in some Appointment Booking service configuration records. | |
|
Approvals PRB1845668 |
Multi-Level approval skips steps due to race conditions | Overlapping transactions on the sc_req_item table cause race conditions allowing approval steps to be skipped. |
Refer to the listed KB article for details. |
|
Attachments to Records PRB1849752 |
There's an issue with archive table clean-up using the 'PurgeOrphanAttachments' job | There's an issue that may result in the unintentional removal of records from the sys_attachment table under specific conditions. The issue may impact instances on Washington DC and later releases. |
Refer to the listed KB article for details. |
|
Audit History PRB1795159 |
Business rules aren't running on the 'Audit delete' table | The issue was reproduced in a Washington instance. |
Expected behavior: The BR triggers and creates a log. Actual behavior: The BR isn't triggering. |
|
Authentication PRB1889955 |
The new banner menu of Yokohama refers to glide.multifactor. enforcement. acknowledged by the sys_id instead of the property name | This causes an issue if the sys_id has already been used by the instance. |
Expected behavior: Verify that the admin should be able to acknowledge the message and the glide.multifactor. enforcement. acknowledged property should be true now. Actual behavior: The Acknowledgment link does not work. |
|
Banner Frame PRB1679019 |
UX Banner announcements appear for users with orphaned roles when they don't belong to the group needed to view the announcement | UX Banner announcements appear for the user even though they have an orphaned sys_user_has_role record and don't belong to the banner group. |
Notice that the UX Banner announcement created appears for the user even though they belong to the group. |
|
Banner Frame PRB1878987 |
An HTML link for a page header caption (glide.product. description) is broken in a logo tooltip | On Yokohama, an HTML href attribute (link reference) included into a page header caption on the 'Basic Configuration UI16' page (glide.product.description sys property) doesn't render the href attribute. |
Refer to the listed KB article for details. |
|
Business rules (Classic) PRB1759349 |
The child table of the cmn_location table doesn't trigger the business rule for full names | The business rule doesn't populate for child tables for cmn_locations, 'Location - generate full name'. The business rule on the table just calls the 'HierarchicalReference #generate()' function, and the changes need to happen in the function. |
Expected behavior: The full name 'Apac/India/Hyderabad/test' is populated. Actual behavior: The full name doesn't populate accurately. |
|
Case and Knowledge Management for HR Service Delivery PRB1860702 |
The Vendor Portal 'Take-questionnaire' page stops working when the HR application is installed | Users observe an error on the page. | |
|
Case and Knowledge Management for HR Service Delivery PRB1905312 |
Feedback definition table doesn't display any feedback records | Feedback definitions aren't visible. Also, users can't create a feedback definition. |
Actual behavior: Feedback definitions aren't visible. Expected behavior: Feedback definitions should be displayed.
Actual behavior: Users are unable to create a feedback definition. Expected behavior: Users should be able to create a feedback definition. |
|
Change Management Collision Detector PRB1868251 |
The 'Conflict Detection' job, especially the ChangeCheck ConflictsSNC script include, can lead to an OutOfMemoryError and node restarts | This seems to happen when the Affected CIs [task_ci] table has a large amount of records on it. In one of the cases, there were 93,685,849 records. |
Run the 'Conflict Detection' job and notice it loops in the ChangeCheckConflictsSNC script include. |
|
Change Management PRB1880887 |
com.snc.change_management .standard_change_catalog is activated on an upgrade | com.snc.change_management. standard_change_flows is installed on an upgrade and zboot. This has a dependency on the standard change catalog. The dependency needs to be removed. |
Refer to the listed KB article for details. |
|
Cloud Provisioning and Governance with Amazon Web Services PRB1788540 |
The API transaction '/api/now/cloud_event' triggered by 'AWS events-driven discovery' is overloading Default Semaphores and should be routed to Integration Semaphores | These transactions are processing on Default Semaphores instead of Integration Semaphores, leading to semaphore exhaustions impacting the user experience. During a severe influx, these transactions can take more time for processing due to DB locks, and a single transaction can take 45 seconds to execute due to the wait time. This can potentially cause an outage. |
Refer to the listed KB article for details. |
|
CMDB Query Builder PRB1889722 |
The 'CMDB Query Builder Suggested Relations' job can fail to process all CMDB_REL_CI records | The 'CMDB Query Builder Suggested Relationships' job changed in Yokohama to use a new batched approach to improve memory consumption and processing speed. However, there are two scenarios (Invalid relationship data and Environment date format) under which it doesn't proceed to the next batch, resulting in an incomplete data set in cmdb_class_relationships. |
Refer to the listed KB article for details. |
|
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 Yokohoma 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. |
Refer to the listed KB article for details. |
|
Communities PRB1865845 |
Some characters are displayed as unicode in blog titles | When a blog article in posted in the Community portal, some characters are encoded in unicode and then are displayed without being decoded. |
Observe that the title is now 'test漢字テストテスト77'. |
|
Condition Builder PRB1843987 |
Predicate Builder's 'Date Time' filter displays a JavaScript condition with quotation marks missing around the date parameter | Quotation marks should be surrounded by the condition '-->', causing an issue with the query. |
Refer to the listed KB article for details. |
|
Configuration Management Database (CMDB) PRB1830256 |
If eligible records are more than the batch size, certification audit results are duplicated for failed CIs | The checkTableAttributesAgainstTemplate method doesn't respect the current batch it is running in. It instead queries the entire CI class tables and logs the failed results. |
Expected behavior: The number of records in the cert_audit_results table shouldn't be more than one. Actual behavior: The total_num_records/1000 +1 times the results get duplicated for failed results. |
|
Configuration Management Database (CMDB) PRB1840516 |
When using an absolute value for a lifecycle stage, it moves to empty, but it accepts and saves a string value with a 'contains an' operator | On that policy form, the filter is using the Lifecycle stage reference field where the dictionary is configured to use 'reference key' = 'name'. The record lookup is done using the Name field instead of default 'sys_id'. | |
|
Configuration Management Database (CMDB) PRB1893468 |
The 'Sync Managed By Group from CI Class' script action has an infinite loop edge case | ||
|
Configuration Management Database (CMDB) PRB1895685 |
If a CI's sys_mod_count value is empty, CMDB Health jobs become stuck | The platform allows the autoSysFields function to be used when inserting and updating CIs from a script. A script turns on or off the update to the fields sys_updated_by, sys_updated_on, sys_mod_count, sys_created_by, and sys_created_on. This is often used for manually updating field values on a record while leaving historical information unchanged. CMDB Health jobs becomes stuck if a CI's sys_mod_count value is empty due to being inserted like that. | |
|
Content Management System PRB1880403 |
The CMS portal is corrupted after a Yokohama upgrade | It looks like there are CSS files for the portal that aren't loaded as expected. | |
|
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. | |
|
Core Platform PRB1775831 |
When the user accesses a CTI record URL before SSO or a local login, they are redirected to an incident.do record | When the user is logged in to an instance, a CTI link takes them to the correct record. However, when they are logged out, they are directed to the incident.do page. |
Refer to the listed KB article for details. |
|
Database Indexes PRB1788235 |
Redundant indexes are created on a column with a non-unique index when a unique index is created on it | Creating a unique index on a column that already has a non-unique index on it leads to duplicate indexes on the same column. |
Scenario 1:
Notice that there are two indexes on the same column, where one is unique and the other one is non-unique. Scenario 2:
Notice that the activity will be successfully completed. |
|
Database Persistence - Data Access PRB1857656 |
A Glide function with a substring function may return a 'negative substring length not allowed' error if the arguments are negative | A Glide function with a substring function may return a 'General Data Exception detected by database (ERROR: negative substring length not allowed)' error if the arguments are negative. |
Refer to the listed KB article for details. |
|
Database Persistence - Data Management PRB1840970 |
Monthly/Yearly scheduled jobs named 'Physical Table Stats Aggregator/Gatherer' causes slow CPU and instance responses | This problem manifested primarily on demo instances that have more than 300 DBIs, but it isn't necessarily isolated to demo hosts. |
Refer to the listed KB article for details. |
|
Database Persistence - Data Management PRB1859358 |
The orphan cleaner does not check both the primary and archive tables to determine if a record is an orphan | Orphan cleaner is enabled by setting property 'glide.db.orphan_cleaner.peripheral_tables' to clean records from the peripheral tables sys_attachment, sys_attachment_doc, and sys_audit, sys_journal_field. It only checks if a record exists based on the document ID reference's tablename. When the document ID reference's tablename is not updated after archiving records during archive reparenting, the orphan cleaner deletes non-orphan records. |
Refer to the listed KB article for details. |
|
Database Persistence - Data Management PRB1868796 |
Updating a record in the sn_vul_vulnerability table via Data Management Update Jobs (sys_dm_update) throws an error | The user can open a record in the sn_vul_vulnerability table and update it, but when the same user tries to update it via the sys_dm_update job, it throws an error. Error: 'The user does not have the necessary permissions to update records in table sn_vul_vulnerability'. |
Refer to the listed KB article for details. |
|
Database Persistence - Data Management PRB1881515 |
The 'Collect Reliability Metrics for Data Management' job causes history lest length (HLL) | The instance experiences resource constraints. | |
|
Database Persistence - Data Scale PRB1266075 |
If all tables that are part of a database view are on the same gateway database, Glide should be able to redirect the query to the gateway | Database views that are connecting to tables that are sharded aren't working. They aren't honoring the gateway configuration and still look in the base database. |
Refer to the listed KB article for details. |
|
Database Persistence - Data Scale PRB1759098 |
A Glide connection gets stuck when statement cancelation response from the server is lost | When a statement is canceled, Glide sends a request to the Oracle server, which replies with 'break', and sometimes the reply doesn't return due to some error. | |
|
Database Persistence - Data Scale PRB1829039 |
Users are unable to add query rewrite if the execution time greater than 10 seconds | Trying to add a index hint/rewrite on Xanadu where the total execution time is greater than 10 seconds rewrites if the execution time is greater than 10 seconds. | |
|
Database Persistence - Data Scale PRB1840823 |
Temporary files are left by PG-JDBC driver | There must be obsolete .trs files in /glide/nodes/node port/tmp directory. Obsolete files are created 1 hour ago or before and not touched. | |
|
Database Persistence - Data Scale PRB1844798 |
An error message for an unknown system variable 'sql_generate_invisible_primary_key' warning is received | This issue was observed in a Xanadu instance. |
Observe the warning error message, 'Unknown system variable 'sql_generate_invisible _primary_key''. |
|
Database Persistence - Data Scale PRB1846741 |
Adjust tuple size thresholds to avoid failing legitimate queries | Adjusting the threshold to a reasonable value to avoid failing some queries. | |
|
Database Persistence PRB1593310 |
Updating an application from the application repository to change the column type from 'Date' to 'String' doesn't change the column type in the database | . | |
|
Database Persistence PRB1849730 |
Oracle prepared statements leaked for sys_attachment_doc queries | When running Glide with an Oracle database, when loading an attachment, a PreparedStatement leaks. This leak eventually cleans up when its database connection is recycled. However, if enough attachments are loaded before the connection is recycled, an OutOfMemoryError can occur, resulting in the application node restarting. |
Refer to the listed KB article for details. |
|
Discovery PRB1648843 |
Active processes from Windows ADM fails to collect active processes on some devices | The issue may present itself as process classifiers not being triggered, for example vCenter or MSSQL patterns not being triggered. The 'Active Processes' table isn't populated, causing the classifiers to not be triggered. |
Refer to the listed KB article for details. |
|
Discovery PRB1657280 |
There's inaccurate error logging for failed application patterns due to running processes that have bounced or stopped before pattern process detection executes | Commands using the PID and PORT from the ADM Probe return null in the pattern failures. There's no log in the 'Discovery Log' table of what occurred during process detection, and no indication in the failure message of the HD Log that the pattern failed due to the running process having bounced with a new PID or PORT. |
Notice that commands executed that use the PID or the PORT discovered by the ADM Probe will return null, as they no longer exist on the target server. There's no logging to the Discovery Log table of what occurred during Process Detection. |
|
Discovery PRB1681149 |
The Storage Server (SMIStorageServer) probe causes a MID server OutOfMemoryError | When running storage discovery, multiple SMIStorageServer probes are triggered. Each probe uses large amount of memory, eventually causing an 'OutOfMemoryError: Java heap space' error. |
Refer to the listed KB article for details. |
|
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. | |
|
Discovery PRB1812384 |
Inclusion pattern discovery fails with a NullPointerException if one of the identifications fails for a parent pattern | When the main pattern identification a fails, a NullPointerException exception is thrown: 'com.snc.sw.exception. PatternDebuggerException: Debug task failed to initialize parent CI for entry point: null.' |
Refer to the listed KB article for details. |
|
Discovery PRB1843836 |
There must be guardrails/warnings for 'mid.sm.discolog. max_object_size' properties | Setting 'mid.sm.discolog.max_object_size' too high can lead to a ECC Queue payload too large and can cause an instance to run into memory errors when processing the results. |
Refer to the listed KB article for details. |
|
Discovery PRB1843863 |
Shazzam Insights doesn't display any data in Discovery Admin Workspace | Shazzam Insights information isn't populated in the table 'Shazzam_Insights' and an error appears in the system logs related to 'com.glide.util' usage. |
Refer to the listed KB article for details. |
|
Discovery PRB1874074 |
A slow query with the hash '874618095' is triggered from the script include 'ShazzamInsights' | There's a slow query with the hash '874618095' is triggered from the script include 'ShazzamInsights' while processing the event with the name 'discovery.complete'. |
Observe that when comparing the two noted times, the discovery completed event of Shazzam insights is much less. |
|
Document Management PRB1884923 |
Users can't preview or publish to a case, and a null pointer exception (NPE) is thrown: 'Cannot invoke "java.io. ByteArrayOutput Stream.toByteArray()" because "pdfOS" is null: HtmlToPdf ConversionController' | In this process, if the HTML has images fetched from the db_image table then shared service, it's unable to process it. In a few scenarios, it's throwing a NPE. | |
|
Document Management Services PRB1847231 |
There's a PDF error when scheduling reports with the donut or graph types on classic dashboards | Scheduled PDF type reports are failing for donut, graph, and bar chart report types. | |
|
Dynamic Translation PRB1875022 |
Users observe /> tags when translating | A translation displays /> tags instead of line breaks. |
Observe that /> prints. |
|
Edge Encryption PRB1887439 |
In Yokohama, when a user goes through an Edge proxy with a home page that includes encoded characters such as %2f as a re-direction result after login, a 400 error occurs | When the user's default home page contains encoded characters, or is redirected to a URL with encoded characters, Edge throws a 400 error, blocking access to the home page. |
Observe the http 400 error. |
|
Email Notifications PRB1764089 |
The display_ name 'email address' set on 'Select From List' or 'text' of 'From Generation Type' doesn't work if the template is custom table based | When using two email templates, the oldest one gets 'error invalid' from the address when the email is sent. This error occurs when two email templates are on the same table but are from different addresses. Both email templates work if the 'from' address is set to the same value. |
Notice the display_ name format and the error message, 'The email address in the From field is invalid.' |
|
Email Notifications PRB1778099 |
The inbound action Update comments and attachments doesn't account for email image filtering, and copies all attachments from the email | Email image filtering should filter out unwanted images smaller than a specific size, such as images in email signatures. Images and attachments should be filtered out based on the properties 'glide.email.inbound. image_sys_attachment. filter.action' and 'glide.email.inbound. image_sys_attachment. filter.minimum_bytes'. | |
|
Email Notifications PRB1815750 |
The instance doesn't generate the access token for push applications |
Expected behavior: The token is added to the instance. Actual behavior: It is throwing insert error. |
|
|
Email Notifications PRB1878510 |
'Could not process unsupported sys_attachment' isn't properly logged by sn_sec_cmn | When a user reports a phishing email with an unsupported attachment, the instance receives the email and discards the attachment without logging the issue properly. The issue is only logged in node logs even though it should properly be logged in the syslog_email and sys_email_attachment tables. | |
|
Email Notifications PRB1881286 |
In Yokohama, recipients are no longer populated in Email Client and the Major Incident Recipient list when using JavaScript | The Recipient field should be populated with all recipients. |
Refer to the listed KB article for details. |
|
Event Management PRB1838597 |
Event Rule changes can cause event_rule.update _events to block system events processing, causing a performance issue in the instance | When Event Rules are inserted or updated, an 'event_rule.update_events' system event is fired in the default events queue to re-check any event records not yet covered by any previously existing event rule. The script action 'Update event rules for empty events/Update rules after deletion of ER' runs for the event, which processes batches of system events from the platform and other features. When an instance has a large number of em_event records matching the new rule criteria, this causes a long running transaction. Events can take several minutes to process, blocking the 'Events process 0' job of the app node, delaying the processing of other important events that should be processed in near real time. |
|
|
Event Management PRB1840029 |
There's an out of memory error due to glide.db. DBLazyWriter | com.glide.db.DBLazyWriter causes an 'OutOfMemoryError: GC overhead limit exceeded' error. | |
|
Event Management PRB1844087 |
SCOM Connector goes down sporadically and the configuration file content becomes blank | A SCOM Connector goes down with the following error: 'Error running SCOM client: The system cannot execute the specified program.SCOM connector failed. The system cannot execute the specified program'. | |
|
Event Management PRB1877169 |
Event Management Events in certain buckets are stuck in 'Ready' for hours after migrating | . | |
|
Field Service Quality Management PRB1860999 |
The dictionary override on wm_task causes issues | In a Washington DC instance, there's no override attribute for the State field at the wm_task. In the Xanadu, the override attribute is introduced for the State field at the wm_task. | |
|
File-based Discovery PRB1843684 |
Since Xanadu, Discovery runs 'Fire FBD Probes for Java Processes' even though FBD discovery is turned off | Since FBD is turned off, it should not run any FDB probes. |
Expected behavior: Since FBD is turned off, it should not run any FDB probes. Actual behavior: The discovery_log in the discovery_status logs 'Fire FBD Probes for Java Processes', even though it doesn't actually fire any probes. |
|
Flow Engine PRB1751544 |
There's a change in behavior from V1 to V2 in handling JS arrays | This change in behavior causes the failure of a following REST step in a Surf action where the 'If_Matches' header whose value is 'etag' isn't matching. |
Refer to the listed KB article for details. |
|
Flow Engine PRB1818766 |
There's flow issues when rejecting an approval | The flow becomes problematic when the person who requested the approval is a non-admin and the approval is rejected by a non-admin user and goes to the 'Send Email' activity. The following are the problematic flows: Change - Cloud Infrastructure - Authorize, Change - Emergency - Authorize, Change - Normal - Assess, Change - Normal - Authorize, and Change - Unauthorized - Authorize. | |
|
Flow Engine PRB1825217 |
When applying inline scripting to pass the value in an input of a dynamic template, it's not working, and the field appears empty | When users create an action from scratch with one input of a dynamic template and apply inline scripting to pass the value to this input in the flow, it doesn't work. | Refer to the Jira spoke action 'create issue'. |
|
Flow Engine PRB1828174 |
The 'Do-In-Parellel' branch remains in a 'Waiting' state after a MID action | The flow should go to a 'Complete' state after it returns from MID, but it remains in a 'Waiting' state with only one of the parallel branches having been executed. |
Refer to the listed KB article for details. |
|
Flow Engine PRB1829297 |
Sub-flow updates aren't reflected in the parent flow | When a subflow updates a record which was passed to it as a reference type, those updates are available in the calling flow if the 'Wait for completion' checkbox is checked. | |
|
Flow Engine PRB1832599 |
There's an unparsable date when a transform is applied on the 'Date/time' pill in a condition string | There's a strict type check for date comparison in V2, but the 'Year' transform applied on the date is giving the year as an integer, which is an unparsable date. | |
|
Flow Engine PRB1834120 |
A flow variable is changed when the flow variable is set from values in MRVS | This issue occurs when there's three or more Date/Time variables used in MRVS. It arises when the smallest date among the entered variables is retrieved using a For Each loop and then set to a flow variable. | |
|
Flow Engine PRB1840526 |
The Submit Catalog Item Request action fails if a multiline text variable is populated with a string containing '\"' | Appears to be the same behavior as PRB1718202, but this affects multi-line text. |
|
|
Flow Engine PRB1846526 |
A scripted sub-flow behaves differently with a stage set in a parent flow for Flow Engine v2 | If the user has a sub-flow that carries out a scripted action, there's a difference in execution when using Engine v2, which can interfere with previously published flows. | |
|
Flow Engine PRB1861062 |
A dot-walk in a custom action fails when executing on MID server | This is related to MID, since this works as expected if the flow is forced to move back to the instance, either by adding a lookup record or waiting before the action using the value is executed. |
Expected behavior: The 'Opened by' user sys_id is in the log. Actual behavior: The log is empty. |
|
Flow Engine PRB1863274 |
There's a unique key violation error in Integration Hub steps when its ran in a loop | The error_message key is written in to runtime values in case of a failure (non-null error_message ouptut) in retryable integration operations. The duplicate key violation error is causing the flow context to terminate with an error when checked for errors during the OutputRepository.writeToDB call. |
Refer to the listed KB article for details. |
|
Flow Engine PRB1874873 |
A deserialization issue occurs to flows when upgrading from Washington DC to Yokohama | Flows containing the 'Make a decision' logic don't resume and error out after upgrading to Yokohama. This is caused by a deserialization issue in Flow Engine V2, which prevents the flow from progressing. |
Refer to the listed KB article for details. |
|
Flow Engine PRB1881084 |
The CurrentContext Tracker 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 PRB1888071 |
Deserialization issue with 'Make a decision' | When upgrading from a Washington DC to Yokohama instance, flow executions created with 'Decision' in both families don't resume and result in an error. |
Refer to the listed KB article for details. |
|
Flows (Family Channel) PRB1774269 |
When a catalog item's flow has an 'Error' state set, the message 'Set current stage state to : [Error]' occurs upon submitting the item on the 'Request Summary' page | If a flow has the 'Error' state set, an item using that flow is submitted from portal and the error message, 'Set current stage state to : [Error]', occurs on the 'Request Summary' page. |
Observe the message 'Set current stage state to : [Error]' on the Request Summary page; when the page is re-loaded, the message goes away. |
|
Flows (Family Channel) PRB1816646 |
The update number on the record remains the same when it is updated by the subflow and parent flow in sequence, causing inconsistencies in SLA executions | When the subflow updates the trigger record, and parent flow updates the same trigger record, the update number on the trigger record remains the same. This impacts respective SLA executions on the record. | |
|
Flows (Family Channel) PRB1834406 |
App installation deletes the base instance sys_complex_object 'FDCollection' | Deleting the flow doesn't remove the sys_complex_object record from the source instance, but the app installation removed the record from the target instance. Sys_complext_object isn't listed in the application file of the app, but appears in the payload of the sys_hub_flow record. |
Notice that after the installation, the base instance sys_complex_object removes a sys_id on the instance. |
|
Flows (Family Channel) PRB1834495 |
On a save, a flow is sending extraneous/corrupt data to the backend | After upgrading to Xanadu, flows with extraneous/corrupt data are being exposed by the stricter v2 engine data model. | |
|
Flows (Family Channel) PRB1841737 |
Users are unable to make changes to a flow after deleting a flow variable | The variable is broken once it is used as a reference in the Send Email action and later removed. The Save button is also turned off when trying to remove the variable. | |
|
Flows (Family Channel) PRB1849882 |
The sysapproval_ approver. source_table changes after upgrading | The source table shows the child table after addressing PRB1780076. Before addressing PRB1780076, the source table showed the parent table. | |
|
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. |
|
Form Builder PRB1820975 |
A form isn't saved on a cross scope in ServiceNow Studio | There's an error in the networking calls. When 'Form layout' is opened in the Form Builder, if the form belongs to a Xanadu scope while the session scope is set to Yokohama, a cross-scope banner appears. However, after selecting 'Edit in original scope' from the banner, any changes made in the Form Builder aren't saved. |
Refer to the listed KB article for details. |
|
Form Controller PRB1812174 |
The Glide form saves the previous date |
The report generates for the previous day. |
|
|
FX Currency Conversion PRB1861950 |
Daily currency rates retrieval from European Central Bank (ECB) may fail due to a lack of response from an Online Certificate Status Protocol (OCSP) endpoint | The 'Retrieve System Rates' and the 'ECB Exchange Rate Load' jobs, which are used to capture currency exchange rates using the ECB endpoint, are failing intermittently across multiple instances because the OCSP endpoint for ecb.europa.eu isn't answering validity questions during certain times. |
Refer to the listed KB article for details. |
|
GlideAggregate API PRB1827509 |
The Platform Analytics Experience Migration tool creates a dashboard data visualizations error: ''No data available' after migration' | When using the Platform Analytics Experience Migration tool to move a dashboard to the Platform Analytics Workspace, reports seem to break when using this tool. For certain reports, the Data Visualization returns the following message: '"No Data Available" There is no data available for the selected criteria'. |
|
|
GlideRecord PRB1796984 |
The event alert 'Inactive Delegator' triggers a message inserted into sys_status, which can lead to a downstream impact as sys_status isn't designed to contain thousands of records | There's a 'FAILED TRYING TO EXECUTE ON CONNECTION' error on select query results in a GlideRecord API return false when next() is invoked. Subsequently an insert is invoked, and it succeeds. This resulted in excessive inserting of glide.policy.eventdelegator records into sys_status. This results in the slow loading of xmlstats.do. | |
|
GlideRecord PRB1837475 |
There's a NullPointerException in GlideElement Compressed. setValue() | Users may notice that upgrades may fail to populate details on the upgrade history when running the 'Upgrade summary' job. | |
|
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)'. | |
|
GRC Platform Plugins PRB1843595 |
The Details field is missing in Attestation Designer after an Xanadu upgrade | . |
Observe that the Details field is present. |
|
Hermes (Family) PRB1834407 |
Reduce DB calls during initialization for Hermes |
Refer to the listed KB article for details. |
|
|
History Set PRB1844946 |
There's intermittent duplicate comments in an activity stream due to sys_email records | Some comments are duplicated due to the presence of sys_email records. This duplication occurs when a comment is added in a way that causes the incident's sys_updated_on timestamp to be one second earlier than the corresponding sys_journal_field record. If emails are triggered by the incident update, the loading of sys_email records within the related sys_history_set interferes with the last_update_recorded field in sys_history_set. This disruption ultimately results in the duplication of the comment whenever the next update to the incident occurs. |
Refer to the listed KB article for details. |
|
HR Service Delivery PRB1819942 |
HTML tags are seen in the Description field of an HR case | This issue occurs using a single method to populate both the rich Description field and the Description field. |
Refer to the listed KB article for details. |
|
HR Service Delivery PRB1830128 |
Quotes aren't correct in HTML in HR Workspace and Playbook after upgrading from Vancouver to Xanadu | Special characters are rendered in an encoded format. | |
|
HR Service Delivery PRB1831691 |
HTML dynamic parameters on HR templates don't work as expected | There's an issue in Xanadu and Yokohama where HTML dynamic parameters aren't replaced with their actual values when used in links. The issue arises in the HTML-sanitizer enabled HTML and translated HTML fields during template replacement with HTML data. |
Refer to the listed KB article for details. |
|
HR Service Delivery PRB1874464 |
The 'Suspended Reason' is overwritten with its previous value when the case moves from 'Draft' to 'Suspended state' | The issue is only reproducible when: the state moves directly from 'Draft' to 'Suspended', on HR Agent Workspace and not on UI16, and when the 'Suspended reason' [sla_suspended_reason] field is on the form. |
Expected behavior: The 'Suspended Reason' should be 'Group'. Actual behavior: The 'Suspended Reason' is set to 'User'. |
|
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. |
Expected behavior: The article body should be read-only and the content should appear. Actual behavior: The article body is read-only and the content doesn't appear. |
|
Inbound Email Actions PRB1841147 |
Sensitive Data Redaction doesn't work for inbound email actions if 'Stop processing' is turned on | This issue impacts inbound email actions even if 'Stop processing' is turned on. | |
|
Integration Hub PRB1775255 |
Increase the attachment limit in the SFTP step in Integration Hub | There's a hard-coded value of 100,000 KB for SFTP imports. When the user attempts to import more than the hard-coded limit, it fails. Even though it lets the user to set a limit, if it is higher than 100,000 KB, it isn't allowed. | |
|
Integration Hub PRB1834445 |
GCF Data Egress recorder should support 0 byte inputs | GCFDataEgressRecorder throws an error with an invalid event value when an event with 0 bytes is recorded, creating an error in the log. |
Post to the instance on an endpoint. Notice that this returns an 204 (no content) zero byte response. |
|
Interactive Filters PRB1837354 |
Filters no longer support reference list types | It used to be possible (up until Xanadu) to select 'Incident."Watch List"' as the data to filter in the filter configuration. This seems to no longer be possible. | |
|
Internal Platform Security Services PRB1813597 |
There's a MIME type check error when attaching a txt (sjis code) file after upgrading to Xanadu | MIME Type check error: '[File type not permitted or mime type does not match the file content]'. |
Refer to the listed KB article for details. |
|
JVM at Scale PRB1810485 |
Memory remediator is killing transactions and restarting glide | Notice the log 'low.memory.remediation.restart No transactions were cancelled' are on standby nodes only. | |
|
Knowledge Article Templates PRB1852356 |
Articles in the 'Published' state aren't changed to the 'Pending retirement' state when retired | Knowledge Base (KB) articles that have the retire policy set to 'Knowledge - Approval Retire' can't be changed to the state 'Pending review'. This problem is found in Yokohama. |
Notice that the workflow state hasn't been updated yet. |
|
Knowledge Article Templates PRB1855083 |
Toolbar options and plugins for the TinyMCE editor are missing in the dictionary attribute for the Knowledge Article body field | Options like A11yChecker, Clear formatting, Anchor, and others are missing. |
|
|
Knowledge Management PRB1819563 |
Some keystrokes aren't recognized when typing in the Post Comment field of a knowledge article, resulting in typing errors | The issue is intermittent. | |
|
Knowledge Management PRB1827639 |
Selecting a knowledge base from 'Explore our Knowledge Bases' in a portal redirects to the incorrect URL | A URL with incorrect search results is returned when selecting a knowledge base from /esc?id=kb_home with AI Search enabled on the application 'Knowledge Management - Service Portal' version 1.0.0. | |
|
Knowledge Management PRB1849608 |
Knowledge Management (KM) notifications are unable to be triggered | Email notifications aren't triggered for Knowledge Articles because some KM artifact records in the Knowledge Advance plugin are overridden by the Activity Subscription plugin. This occurs in Xanadu and Yokohama. |
Notice that the notification is not getting triggered for 'KM Subscription: Article published'. |
|
Language and Translations PRB1750563 |
The translation of notes is updated when installing the plugin sn_doc | The record sys_ui_message.list notes is updated and translated when installing the plugin sn_doc. |
Expected behavior: The record sys_ui_message.list isn't updated. Actual behavior: The record sys_ui_message.list is updated with the key, notes, and message values. |
|
Language and Translations PRB1814149 |
'AND' isn't translated into Japanese in the list for Condition Builder | In Condition Builder, 'AND' is not translated in Japanese after upgrading from Washington DC to Xanadu. |
Expected behavior: 'AND' is translated as 'および'. Actual behavior: 'AND' is shown as 'AND'. |
|
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 PRB1237246 |
String values displayed in list V2 and list V3 automatically remove or truncate more than one empty space to one empty space | This issue causes inconsistency to users when they copy the string from the display of the list, as the actual value isn't truncated, and only the displayed value is truncated. |
Expected behavior: The data should be displayed without any auto truncation, and the short description should be displayed as 'test 123'. Actual behavior: The data is displayed with auto truncation, and the short description is displayed as 'test 123'. |
|
List Administration PRB1402594 |
Users are unable to edit a field in the list view when it is dependent on another field that is read-only for the user | This issue has been observed since New York. Users aren't able to edit a field on a list view when it's dependent on another field that is read-only or has an ACL making it read-only. |
Expected behavior: The field should not be editable only when there is a list_view ACL preventing the field from being edited. Actual behavior: In the form view, the field 'Contact type' is editable, but in the list view it is not. |
|
List Administration PRB1698906 |
The Workbench license consumption breakdown list view changes when the software product life cycle report changes | Editing columns in the Software Asset Workspace License Usage Report updates columns on the related lists. |
Notice that the details do not render in the table. |
|
List Administration PRB1801160 |
In the calendar picker, the start of the week isn't the same on the Workspace list and form | Changing the day format to 'Monday to Sunday' doesn't work, and the 'start of the week' system property glide.ui.date_ picker.first_ day_of_week isn't honored. |
Notice that the format is Sunday to Saturday. |
|
List Administration PRB1840299 |
The user is unable to dot-walk via column selection for lists | Dot-walking doesn't work in column editing. | |
|
List Administration PRB1844708 |
Changes to 'My Lists' from the 'List' bundle SNC variant aren't saved | When the user creates a list under 'My Lists' in Service Operations Workspace and configures the columns or changes the filters, the changes reflect immediately. But if the user switches over to another page or list, the changes are reverted. | |
|
List Administration PRB1862590 |
Non-admin users see ACL errors when using suggestions on form fields | Non-admin users who do not have sufficient access to the sys_choice table fields encounter ACL errors when selecting the suggestion icon on a form field. | |
|
List Administration PRB1865237 |
Checking 'Hide quick edit' in a UX List record doesn't hide the Quick edit button | After checking 'Hide quick edit' in a UX List record, the Quick edit button isn't hidden in Service Operations Workspace. | |
|
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. |
|
List Administration PRB1881066 |
A list editor pop-up disappears as users scroll down on a dashboard/report | It's not working in the case of snListEditContainer, where a list is in some parent container. |
Notice that as users scroll down the list and attempt to edit additional cells, the selection context is lost, and some fields don't even populate the editable input, making it impossible to edit them. |
|
List Controller PRB1847141 |
Lists in Service Operations Workspace (SOW) aren't automatically refreshing | When users enable the glide.lists.live_ list_enabled property and make any changes in any record of the list, then the list refreshes in SOW version 5.0.1 but not in version 6.1.1. |
Observe that the list on the first browser session doesn't change. Eventually, a number appears on the refresh button at the top of the list. Select the button, and the data refreshes. |
|
List Controller PRB1872228 |
Upgrading an instance from Washington to Yokohama is breaking the New button | Upgrading an instance from Washington to Yokohama is breaking the New button in Service Operations Workspace when the 'Knowledge' template isn't activated. |
Expected behavior: The form loads. Actual behavior: The 'knowledge record not found' error message appears. |
|
List Editor PRB1842085 |
A 'Discard your changes?' modal displays when quick editing and the record was already saved | This issue isn't reproducible in Xanadu. |
Refer to the listed KB article for details. |
|
List Filters PRB1764233 |
The 'Report' filter isn't working on the Workspace Dashboard when selecting 'View all' | This issue occurs in the CSM/FSM Configurable Workspace for Vancouver and Washington DC instances. |
Observe that the count changes and the list containing all the incidents doesn't respect the filters. |
|
List Filters PRB1801767 |
Japanese names can't be filtered by a Japanese term but can be filtered by an English term under the Japanese setting | Users are unable to filter lists by Translated Text fields in non-English languages when using the non-English translation. | |
|
List Filters PRB1818705 |
Group By tags are not working in extensible lists | The Group By column action won't be available for certain column types like 'Tags' (internal_type: related_tags). Group By tags works in UI16, but it's not supported in NRLC and Group By and filtering options are turned off. |
Expected behavior: If Group By isn't supported for the 'Tags' column, the Group by column action shouldn't be available for 'Tags'. Actual behavior: It doesn't return results based on Group by for tags. Returns 'No data to display'. |
|
List Views PRB1854405 |
The Xanadu Date Picker Calendar pop-up appears below the field, making it difficult to select other dates | The Xanadu Date Picker Calendar opens on the below field and isn't letting users select other dates when they add a variable editor on the form configuration. |
Notice that the calendar pop-up appears below the field, making it difficult to select other dates. The date picker should open above the field. |
|
Major Incident Management PRB1891876 |
The View Workbench UI action is redirecting to a broken 'Activity' section when opening it for a second time on a major incident form on the classic UI | After upgrading in Yokohama, when managing a major incident (MI) in the classic UI and moving to the 'Workbench' view, it's not loading properly. It's redirecting to a MI management broken activity view. |
See that a different form view is loaded instead of workbench. It seems to be that the redirection URL is changing to this form view. |
|
Metric Intelligence (Family) PRB1784201 |
'ITOM model building' jobs cause CPU spikes on Clotho, which causes processing metrics issues | A ITOM fitter class uses a parallel stream for model fitting, this parallel stream uses all the resources available in the JVM settings which causes CPU spikes and issues in the metric processing pipeline of Clotho. | |
|
MID Server PRB1777909 |
Container-based MIDs fail to upgrade from Utah or Vancouver to Washington DC | Since the Washington DC release, MID servers deployed through the docker recipe stop working when self-upgrading after each restart. | |
|
MID Server PRB1840424 |
MID Server ECCSender thread gives an 'Invalid byte 2 of 4-byte UTF-8 sequence' error, blocking sending of valid ecc_queue inputs to an instance | This is most likely to be seen in LDAP user imports, or Import Set JDBC Data Sources, where large data is involved. Large data is likely to include extended unicode characters such as emojis. For LDAP probes, emojis have been seen in OU/CN group names and user details data. For REST integrations synching incidents, emojis have been seen in comments of cases. They could potentially appear anywhere, for any feature's probe result data. |
Refer to the listed KB article for details. |
|
MID Server PRB1842102 |
Session mismatch on MID server when an agent experiences VPN issues | Host data collection also fails with MID logs showing, 'Failed to send check instance check-discovery-basic due to closed communication session'. |
Expected behavior: Notice the MID logs with the agent ID mapped to the message, 'Agent registered for communication', and the agent websocket session should be different than it was before it disconnected. Actual behavior: Notice the MID logs with the agent ID mapped to the message, 'Agent registered for communication', and the agent websocket session is the same according to MID logs. |
|
MID Server PRB1864193 |
Upgrading a Linux MID Server to Xanadu reverts mid.shconf_override to the default setting | mid.shconf_override has an empty setting. It's reverted to default setting after upgrading. | |
|
MID Server PRB1870465 |
ECCSender does not use the correct character set when reading XML queue files | ECCSender uses the default file encoding/character set when reading XML queue files from a disk. This results in incorrect characters in the response for some special characters. ECCSender should use UTF-8 when reading these files, as XML queue files on disk are always UTF-8. |
Refer to the listed KB article for details. |
|
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. | |
|
Mobile Platform PRB1835448 |
Uppercase in the choice value breaks the dependency on the Mobile App | . | |
|
Mobile Platform PRB1840375 |
InputFormScreen doesn't work when the function containing the InputFormScreen comes from a list | An InputFormScreen with Fetch Type = Prefetch/OnDemand doesn't display the dependent parameter of level three (parameter3 depends on parameter2 which depends on parameter1). |
Expected behavior: Choice three shows the option 'None', and when picking values in choice one and choice three, choice three shows the values configured to it. Actual behavior: Choice three doesn't show value at all, and when picking values in choice one and choice three, choice three does not show the values configured to it. |
|
Mobile Platform PRB1843738 |
Field parameters for the URL button type that are used for the URL template are encoded even when it's not needed | When selecting the options on the Now Mobile app, the page doesn't navigate as expected. Instead, it is taken to a 'The page you are looking for could not be found' search screen. After selecting Go, the page is redirected correctly. Options: 'Open my Reservation » mesp?id=wsd_reservations' and 'Create a new general reservation »mesp?id=wsd_search'. | |
|
Next Experience Notifications Menu PRB1851718 |
A URL isn't updated when navigating from the migrated dashboard by clicking the notifications | There's an issue on the unified navigation side that is causing this for several releases. |
Observe that while the record displays in the main window, the URL bar isn't successfully updated and the tab name is wrong. |
|
Next Experience Unified Navigation PRB1690651 |
Zing Exact Match search on workspaces intermittently navigates to an incorrect URL in Next Experience | Zing Exact Match search opens the record in the record view instead of the kb_view. |
Observe that the record opens in the record view. |
|
Next Experience Unified Navigation PRB1814384 |
Adding a parent application and child module to the configurable menu breaks the menu API |
Expected behavior: The API should return the menu items' response. Actual behavior: The API returns 500. |
|
|
Next Experience Unified Navigation PRB1836091 |
There's a 'Session Expired 401' modal on public pages | The 'sn-banner-announcement-list' component emits an HTTP_ERROR_OCCURRED event causing a CANVAS_GLOVAL_ERROR event to open the 401 alert dialog. |
Notice a 'Session Expired (401)' dialog displays. |
|
Next Experience Unified Navigation PRB1871341 |
Text is truncated in the 'leave page' pop-up in Next Experience after upgrading to Yokohama | The issue isn't happening on previous releases like Washington DC or Xanadu. The issue is also not happening with UI16 on the Yokohama release. |
Expected behavior: The 'Leave page' pop-up appears, which displays a completed message. Actual behavior: The 'Leave page' pop-up appears, but it displays a truncated message. |
|
Next Experience Unified Navigation PRB1875808 |
The desktop notification banner doesn't display in Windows when multiple tabs are open | It displays the notification in the Notification Center but it doesn't display the banner. | |
|
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. | |
|
Now User Experience PRB1890272 |
A custom banner logo for an instance doesn't display for unauthenticated users | A broken image icon displays on the 'Log in' page. | |
|
On-Call Scheduling PRB1868011 |
The 'Show Schedule' link doesn't work for a non-admin user | After upgrading to Xanadu, non-admin users aren't able to access the on-call schedule. |
Observe that an error is thrown. |
|
On-Call Scheduling PRB1886730 |
The 'On-call Who' API intermittently isn't returning users | ||
|
OneExtend PRB1864500 |
Activating Now Assist skills creates unnecessary [sys_update_xml] records which shouldn't be transferred between instances | Unexpected customer updates are being automatically generated for one_api_* tables extending [sys_metadata]. This causes confusion among users as they are unaware of how the updates are generated and these records aren't intended to be transferred via an update set. |
Refer to the listed KB article for details. |
|
PDF Generation PRB1890095 |
A PDF created from a view with dot-walked fields aren't displaying those fields or the exported PDF (30B size) is corrupted | When exporting a form, if the form contains dot-walking fields, then the value of those fields are empty in the exported PDF file. If the parent of the dot-walking field isn't present and dot-walking fields are present, then a corrupted PDF is generating with an error: 'Failed to load PDF document.' |
Notice that the dot0walked fields Model.model_number and Model catergory.Name aren't displaying. Also, if the parent of the dot -walking field is missing, then the corrupted PDF is generated with 30 bytes. The exported file (30B size) displays 'Failed to lad PDF attachment'. |
|
Performance Analytics Dashboards PRB1900147 |
Users are unable to open responsive CoreUI dashboards | An error message appears: 'Sorry! The requested dashboard has not been shared with you.' | |
|
Platform Analytics Dashboard API PRB1760775 |
There's an issue with reports on a workspace dashboard | Legends display duplicate values when translated into a non-English language. |
|
|
Platform Analytics Dashboard API PRB1865224 |
The first modal displays despite 'Don't show...' being checked | ||
|
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. | |
|
Platform Analytics Filters PRB1838937 |
When a non-admin user creates a Platform Analytics 'Date' filter, 'Field' flashes briefly and is then cleared when selected, depending on the table chosen | Depending on the table chosen in the data to filter modal, entries selected in 'Field' flash briefly and are then cleared, and don't remain selected. |
Observe that 'Created' flashes briefly and is then cleared, and the selection does not remain. |
|
Platform Runtime PRB1855493 |
Nodes are closing the TCP socket after 20 seconds of being idle and ignoring the property tomcat.connector.all. keepAliveTimeout, causing ADC to generate a HTTP 502 response | Application nodes are closing the TCP socket after 20 seconds of being idle and ignoring the property tomcat.connector.all. keepAliveTimeout, which is set to 70000 in the file '/glide/nodes/ NODE_NAME/conf/ overrides.d/03-custom.properties'. This causes the ADC load balancer to generate an HTTP 502 response. | |
|
Playbooks (Family Channel) PRB1839341 |
An update set with a Playbook change failed to install | The invalid preview error, 'Could not find a record in sys_pd_snapshot for column snapshot referenced in this update' occurs when moving changes to related to Playbook via an update set from one instance to another. |
Refer to the listed KB article for details. |
|
Process Mining PRB1903878 |
After upgrading from the Xanadu to Yokohama release, process mining filter sets and scheduled tasks are deleted | During the upgrade from Xanadu to Yokohama, the process mining filter set conditions and scheduled tasks are being deleted. Due to a backend issue, the upgrade script execution unintentionally deletes saved filter sets and scheduled tasks of Process Mining Projects. This particularly affects configurations with 'transition filters' linked to scheduled tasks. Although no other user data was affected, this issue may disrupt functionality where the deleted filter sets or scheduled tasks were actively used. |
Refer to the listed KB article for details. |
|
Project Management PRB1829307 |
A project actual isn't populated in the resource aggregated monthly for October, though it's populated for September and November | A category project actual isn't populated in table resource_aggregate_monthly for October. It does populate for September and November. There's one record for a project actual in October. When looking in resource_aggregate_weekly, all project actual records are there. |
|
|
Project Management PRB1850637 |
Duplicate resource_aggregate_weekly and resource_aggregate_monthly records are created intermittently | Code in the UpdateActualsFromTimeCard function of the ResourceActuals SI raises an event to update aggregates for each day when a time card is approved or recalled, causing duplicate resource_aggregate_weekly and resource_aggregate_monthly records to be created intermittently. | |
|
Project Management PRB1880926 |
The Overall health field and other related fields aren't displaying as per the option selected on the project status report on a project form | For example, when selecting values in the Overall health field, the color should be displayed as per the value selected. | |
|
Related Lists PRB1884173 |
Users can't add/remove the first option in the slushbucket from side to side when accessibility is enabled in Classic (Core UI) | Users can't move the first 'Available' option to the 'Selected' side with a double-click or by using the Add button. Selecting one option but then double-clicking another moves both over. If users shift-click to select multiple options, they don't all move over - one remains. CTRL+A doesn't select all options; rather, it appears to toggle the set of selected options. | |
|
Related Lists PRB1887019 |
Users can't edit from a related list on a reference field configured to be read-only in the dictionary | Users are no longer able to add existing related records via the 'Edit' function on a related list when the reference field on the target table is marked as read-only. This behavior was previously functioning as expected. The issue has been verified in multiple relationships. Removing the 'read-only' attribute from the reference field restores expected functionality, confirming the change in behavior post-upgrade. |
Refer to the listed KB article for details. |
|
Reporting PRB1324625 |
Stack trace error 'No matching records: com.glideapp.report. charting_v2. exceptions. ChartDataGenException' is thrown when no data is returned for a multi-level pivot report | When a multi-level pivot report doesn't have any data to return, the following error is logged to the syslog table: 'No matching records: com.glideapp.report.charting_v2.exceptions. ChartDataGenException: No matching records...' |
Expected behavior: The error message appears, 'Cannot generate the report. No matching records'. Actual behavior: The error message appears on screen, 'Cannot generate the report. No matching records' and an error is generated in syslog table: 'No matching records: com.glideapp.report.charting_v2.exceptions. ChartDataGenException: No matching records...'. |
|
Reporting PRB1853349 |
Visualizations in non-global domains aren't displayed in the list of visualizations | When trying to add some dashboard to a library, it's not saved in any sub domains. It's getting saved only in the global domain. In the sub domains, when they try to save the dashboard, it says it's saved but it's not. | |
|
Reporting PRB1874881 |
A calendar report doesn't display Japanese characters correctly | The issue is reproducible in Yokohama. |
Expected behavior: '保守:YokohamaへVerUpリグレ開始'. Actual behavior: '20:36 保守:YokohamaへVerUpリグレ開始 - 保守:YokohamaへVerUpリグレ開始'. |
|
Reporting PRB1878029 |
A drill down report isn't working as expected with sorting added to the report | It's impacting the filter conditions by appending 'ORDERBY' at the beginning of the condition value to the last filter condition of the report. |
Refer to the listed KB article for details. |
|
Reporting PRB1881863 |
Drilling down into a multi-level pivot report that is following an interactive filter isn't working as expected | Multi-level pivot report drill down functionality isn't working as expected when a report is added to a dashboard or when a report has 'Follow Interactive Filter' turned on for the 'Report' widget. |
Refer to the listed KB article for details. |
|
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. | |
|
Role Delegation PRB1828712 |
Updating sys_user_group.parent is done on the frontend, which causes a timeout of the transaction and leaves sys_group_has_role inconsistent | Since updating sys_user_group.parent is done on the front side, a transaction can timeout. As the result, the sys_group_has_role records become inconsistent. |
Refer to the listed KB article for details. |
|
Rollback Contexts PRB1844400 |
The 'Clean Expired Rollback Contexts' job causes memory issues and node restarts | The job is streaming through large rowblocks of data and causing node restarts. The heap dump shows 1.2GB of memory taken by this job. |
Refer to the listed KB article for details. |
|
SaaS integration with Adobe Cloud (Glide) PRB1843443 |
sn_samp. UpdateReclamation Candidates > getUser SubscriptionCost code issue | The potential_savings field is only present on the samp_sw_ reclamation_candidate table, and not in samp_sw_rc_m2m_subscription. This is causing the 'SAM - Updating Existing Reclamation Candidates' job to fail when updating the hybrid subscription cost. |
Refer to the listed KB article for details. |
|
Scheduled Jobs PRB1794747 |
The Updated field on the 'Progress workers' table isn't updating after a node restart | The Updated field on the 'Progress workers' table isn't updated when the node on which the job is executing gets restarted. |
Notice the log: '2024-08-15 04:11:21 (685) worker.5 worker.5 txid=5827be15c30c JobExecutor Starting: Fix Script: Test: Script.8427fa15c30c961044093806050131d2, Trigger Type: Once, Priority: 25, Upgrade Safe: true, Repeat: Name: Fix Script: Test: Script Job Context: . . 2024-08-15 04:16:03 (189) glide.scheduler SYSTEM SchedulerThread [Scheduler Graceful Shutdown] Shutting down thread...No database connection pool available for name glide org.mozilla.javascript.JavaScriptException: java.lang.IllegalStateException: No database connection pool available for name glide'. Notice that the progress worker state is changed to 'Cancelled' but the Updated field is not updated. Review if the 'Update hung running progress controllers on startup' job has run. Notice that is the 'Update hung running progress controllers on startup' job has run, it updates the progress worker records. |
|
Schedules PRB1831078 |
The 'Timeline' page isn't displaying properly with sub items after an Xanadu upgrade | When there is a [cmn_timeline_sub_item] record attached, 'View Timeline' doesn't seem to work. The issue is only there when there's a timeline sub item in the 'Timeline' page. If there's no timeline, there's no issue. |
|
|
Seismic Framework PRB1878687 |
Users are getting an error message on a few instances sometimes: 'An Unknown Error Occurred, Please try after sometime' | User accessible roles are fetched and used further to determine the 'Run with Roles' list. This issue is due to a large payload size. The qualifier string is big. |
A user can see the 'An Unknown Error Occurred, Please try after sometime'. This is not happening all the times. |
|
Server-side scripts PRB1794568 |
Xanadu ES12 JavaScript in global scope isn't working for fix scripts and fails with a 'Script compilation error' | Apart from 'const' and 'let', no new ES features seem to be working. There's a script compilation error: 'Script Identifier: null.null.script, Error Description: syntax error (null.null.script; line 4), Script ES Level: 0, Interpreted Mode: true'. This issue doesn't exist in scoped apps. |
Refer to the listed KB article for details. |
|
Server-side scripts PRB1848232 |
A TD instance hangs and is unresponsive due to recursive calls when capturing Generic Collection Framework (GCF) metrics | While publishing the GCF metrics for scripts, MInMaxPriorityQueue is used for collecting 20 longest executions. It attempts to access indices more than 20, causing ArrayIndexOutofBound exceptions. | |
|
Server-side scripts PRB1883239 |
ESLatestScriptLoader returns a warning message | The message reads, 'Version loading was stopped by ESLatestScriptLoader for sys_es_latest_script...'. | |
|
Service Catalog PRB1761951 |
An error in AI Search occurs, 'ERROR *** dot-walk column doesn't exist sc_cat_item.ref _sc_cat_item_content. content_type' | After upgrading the instance to Washington DC, an error occurs in the system log: 'SEVERE *** ERROR *** dot-walk column doesn't exist sc_cat_item.ref _sc_cat_item_content. content_type'. | |
|
Service Catalog PRB1857685 |
g_user.userID isn't returning a string but a native object in the Virtual Agent conversational catalog item | It gives an error. | |
|
Service Level Management PRB1849627 |
Improve SLA Calculator's handling of very large sets of Task SLA records during trigger processing | Under certain circumstances, bulk SLA calculations can cause node memory issues if the set of Task SLAs being calculated is very large. |
Note that it first processes the list of Task SLA and adds them to an array. This is consumes memory unnecessarily. |
|
ServiceNow Security Center (Family Release) PRB1843476 |
At upgrade time with updated content, the completed steps of a user action keeps the action status as 'ready', which turns off the action's Complete button | ||
|
Service Portal Core Widgets PRB1862176 |
Service Portal fails to a submit catalog item when a required HTML variable is empty and re-submitted with a filled value | After pressing 'Submit' on a Service Catalog Item widget when the required HTML variable is empty, it rejects the submission as expected. However, filling the HTML variable after the submission is rejected and still detects the HTML variable as not filled. Because of this, users are only able to submit catalog items from Service Portal when the required HTMl variables are filled properly before submission. | |
|
Service Portal PRB1502280 |
The file attachment field doesn't appear on a Portal 'form' page | The file attachment field My file doesn't appear on the 'form' page of an incident record. |
Notice that the file attachment field My file doesn't appear on portal, but shows in native view. |
|
Service Portal PRB1537370 |
Field messages styling (using showFieldMsg()) for types of errors isn't consistent between Portal and Platform | The use of showFieldMsg() to display the error type isn't consistent between the Portal and Platform views. On the Platform view, the error is displayed in a red background. However, in Portal, the error is displayed as a red string in italic form without a red background. |
Expected behavior: The styling of the field messages is same for info, warning, and error. Actual behavior: The styling of the field message for error is different from info and warning, and there's no background color for the error message. |
|
Service Portal PRB1765867 |
The 'Widget' form throws an error when trying to save | An error appears after attempting to save changes to the 'Widget' form. |
Expected behavior: The form should save successfully. Actual behavior: An error is seen under the Client controller field: 'Could not save record because of a compile error: JavaScript parse error at line (25) column (25) problem = missing name after . operator (; line 25)'. |
|
Service Portal PRB1829670 |
Genius results shows both catalog items and knowledge articles even when the user is filtering with the navigation tabs | Searching in a portal displays Now Assist Genius results, including catalog items and knowledge search results. Selecting a catalog navigation pane or a knowledge navigation pane, the filtered results display both a catalog item and Now Assist QnA instead of displaying respective filtered results. |
Expected behavior: When selecting the Requests navigation pane, it should only display a catalog item Genius result and not knowledge. If users select the knowledge navigation pane, it should display only knowledge and not a catalog Genius result. Actual behavior: Irrespective of the navigation pane, the Genius result displays both a catalog item and a knowledge summary. |
|
Service Portal PRB1839297 |
A SPEntry page error 'Execute operation on script include 'SPEntryPage'' from scope occurs | Switching the scope and refreshing the page gives the error, 'Execute operation on script include 'SPEntryPage' from scope 'Knowledge Management - Service Portal' was denied'. |
Notice that the same error message occurs. |
|
Service Portal PRB1854147 |
'Popular Items' display a blue font on the SWP Portal | Popular items display a blue font and are a larger size after the Xanadu upgrade. | |
|
Service Portal PRB1855070 |
Post-upgrade to Yokohama EA, an error is caused by the business rule 'Create SP Communication ChannelList' | An error found in the logs after upgrading to Yokohama EA 'Recursive business rule call for 'Create SP Communication ChannelList' on sp_portal'. A number of simple transaction results in this error. | |
|
Service Portal PRB1875043 |
In the 'Canada - French' language, submitting a date in 'dd-MM-yy' format causes an error | When a user sets their language to 'Canada - French' and attempts to submit a date in the format 'dd-MM-yy', the date doesn't apply correctly, resulting in an error. |
Observe that there's an error, and the date doesn't apply to the field. |
|
Session Management PRB1704076 |
XMLStates can throw an 'Attempt to use GlideSession owned by another thread' error while retrieving statistics related to sessions | Statistics related to GlideSessions iterate over all the sessions and access gs.getClientDataMap(), which throws the 'Attempt to use GlideSession owned by another thread' error at the same time the user claims ownership of the session while running the transaction. |
Refer to the listed KB article for details. |
|
Session Validation PRB1846625 |
Deeplinks redirection failed with a node switch from an unauthenticated session to an authenticated session | On opening a deeplink URL, the user should authenticate and redirect to a specific resource. |
Refer to the listed KB article for details. |
|
Sidebar (Family Release) PRB1849937 |
When sn_hr_core. impersonateCheck is set to true, users are unable to add users to the sidebar | When sn_hr_core.impersonateCheck is set to 'true', users can't add users to the sidebar discussion for sn_hr_core_case_payroll records. There's instead an error message: 'Participants can't join the discussion because they don't have access to this record.' |
Refer to the listed KB article for details. |
|
Software Asset Management PRB1632141 |
The scheduled job 'SAM - Normalize discovery models using content library rules' fails when the Content Data Service (CDS) library is not complete | The scheduled job 'SAM - Normalize discovery models using content library rules' fails with the following errors: '08:14:33.158 Warning worker. 1 worker.1 txid= 9df7afed1b47 WARNING *** WARNING *** Get for non-existent record: samp_sw_package: 78a1f708db96ef0 0c41a10825 b9619c4, initializing 08:14:33.159 Error worker.1 worker.1 txid=9df7afed1b47 SEVERE *** ERROR *** NormalizationEngine: Error: No Match found for in samp_sw_publish'. |
Refer to the listed KB article for details. |
|
Software Asset Management PRB1794370 |
Deprecated fields are not deactivated | There are various fields across Software Asset Management which are deprecated but not deactivated. |
Refer to the listed KB article for details. |
|
Software Asset Management Publisher Pack for Microsoft PRB1871730 |
The 'Collect CAL Info' extension section causes a huge payload for Windows discovery | When running Windows OS - Servers patterns, if the server has a large amount of records in the MsftUal_DeviceAccess and MsftUal_UserAccess through WMI queries, then the payload is substantial. Such large payloads may cause mutex locks and impact performance. |
Run discovery against a Windows server with a large number of devices/users returned from the WMI queries in the 'Collect CAL Info' extension section. |
|
Software Asset Normalization PRB1847748 |
Sometimes Norm product/publisher isn't cleared/stamped on a few installs |
Refer to the listed KB article for details. |
|
|
Software Asset Reclamation PRB1896341 |
There's reclamation candidate and reclamation rule issues |
Refer to the listed KB article for details. |
|
|
Special Handling Notes PRB1836082 |
Simplify 'Refresh SHN' conditionals for readability and backportability | In Xanadu, if users set the Special Handling Notes (SHN) property 'Display special handling notes only once per session' to false, then the SHN pop-up window isn't displayed at all each time a user accesses a record. However, in Xanadu, once the property is set to false, the SHN pop-up window isn't displayed at all each time a user accesses a record. According to the documentation, the SHN pop-up window should be displayed each time a user accesses a record. |
Notice that the 'Special Handling Notes' pop-up window isn't displayed at all each time a user accesses the record in either workspace. |
|
Standard Change Catalog PRB1856886 |
A value isn't populated from the template if a new text area field is added when creating or modifying a standard change proposal | The template_value field contains 'STARTSWITH' instead of the '=' operator, which doesn't allow the field to be populated with the value when the template is applied to the change request record. |
Refer to the listed KB article for details. |
|
System Archiving PRB1815571 |
Archive runs can be stuck in an active state when the process times out when creating ar_* tables | Archive runs can be stuck in active state when the archive rule on CMDB is run for the first time and if the CMDB hierarchy is big. While creating all the ar_* table in this hierarchy, it could timeout. | |
|
System Import Sets PRB1753408 |
The 'Import Set Deleter' job is contributing to replication lag due to long running DELETE statements and batch executions | . | |
|
System Import Sets PRB1804838 |
New fields with double byte characters aren't created automatically on loading data | If the loading file or data source contains headers that don't match the fields in the import set table, when loading data, new fields are created. Since the Xanadu release, new fields aren't created when headers contain double byte characters, and a warning message is logged in the import log. This occurs even if the com.glide.use_ column_name _optimizer property is 'true'. |
Refer to the listed KB article for details. |
|
System Import Sets PRB1850436 |
There's unexpected column creation when importing an Excel file with Japanese headers | When importing a file with Japanese headers, a new 'u_xxx' column is created, even though the u_email column already exists. This issue also occurs in Washington DC. |
Refer to the listed KB article for details. |
|
Table Administration and Data Management PRB1681343 |
convertToPDF WithHeaderFooter is slow to convert with a business rule | . | |
|
Table Administration and Data Management PRB1852726 |
Users get an error: 'Syntax Error or Access Rule Violation detected by database ((conn=316832) Unknown column 'ba.a_ref_10' in 'on clause')' |
Refer to the listed KB article for details. |
|
|
Tags PRB1767453 |
The 'Group by' tag list view count isn't accurate | The 'Group by' tag in the list view count isn't accurate on the 'Task' table when a tag is added to newly created records from a custom extended table. |
Expected behavior: The group counter amount is the same as the number of records in the list. Actual behavior: The group counter is two even though there are three records in the list. |
|
Time Card Management PRB1890157 |
On the Time Sheet Portal, tooltips sometimes remain stuck on the screen in Yokohama | If a user hovers over another tooltip, the original one remains in most cases. |
Notice the tooltips remain for a prolonged time or indefinitely. |
|
Transaction Logs PRB1827610 |
The errors and logs metrics were removed in the XMLStats servlet include, causing the 'Logs' graph in the ServiceNow Performance dashboard to be 0 after an upgrade | When the user goes to ServiceNow Performance Dashboards, some of the graphs aren't displayed, and instead display the error message 'Error:Invalid series data'. |
Expected behavior: The graph should display values accordingly. Actual behavior: The graph flatlines at 0. |
|
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 PRB1779043 |
There's an error inputting a decimal value into a decimal field when glide.system.locale has a value set | This issue is reproducible on any workspace and when the system property glide.system.locale isn't empty. |
Notice that the message is seen: 'Could not parse 123.456.789,6 as a number'. |
|
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 Field Administration PRB1827405 |
A UI16 form loads slowly when the Composite Name type field is added and the instance has a lot of metadata | If a form has a Composite Name type field on it and there's much metadata present, the form can take upwards of 15-20 seconds to load. | |
|
UI Field Administration PRB1877769 |
The info (i) icon for reference catalog variables is missing on requested items and the 'SCTASK' form under Service Operations Workspace | The issue is seen with all the workspaces since Yokohama. |
Refer to the listed KB article for details. |
|
UI Field Administration PRB1879955 |
The sys_user record isn't retaining the phone number format on the Phone number type fields |
Expected behavior: The value in the field shouldn't get formatted. Actual behavior: The value in the field gets formatted. |
|
|
UI Field Administration PRB717514 |
A dotwalked glide_list field with choices doesn't display dropdown choices | Users are unable to adjust/administer a list as expected. |
Refer to the listed KB article for details. |
|
UI Form Administration PRB1814991 |
A bulk-edit pop-up form in a presentational list won't refresh after the previous transaction | The bulk-edit UI action pop-up form contains input from the Description field from a previous transaction to other records that are opened. |
Notice the Description field still contains the user input 'ABCDE' from the previous transaction. |
|
UI Form Administration PRB1824242 |
The Add/remove multiple button on list fields doesn't work if required fields are present | When selecting the Add/remove multiple button in a glide_list type field while there are other required fields on the form (that are not filled in) the slushbucket popup doesn't open and all required fields flash red. This includes the list collector itself (if it is mandatory). |
Observe that this throws an error. |
|
UI Form Administration PRB1829603 |
Workspace fields are cleared when using multiple tabs with an agent | After upgrading to the Washington DC release, an issue occurs when accessing multiple tabs during a chat with a live agent, in which already completed interaction records are cleared. |
Expected behavior: The updated values in the interaction record shouldn't be cleared after opening multiple tabs. Actual behavior: The updated values in the interaction record are cleared after opening multiple tabs. |
|
UI Form Administration PRB1843602 |
There's an issue with the date picker position | The date picker position doesn't change when scrolling through the page. |
Notice that the date picker remains in the same position on the screen even when scrolling. |
|
UI Form Administration PRB1847059 |
Formatting on the special handling notes header is aligned to the left in Xanadu | Special Handling Notes aren't aligned properly and is formatted completely to the left. | |
|
UI Form Administration PRB1859837 |
UX View Rule Configuration isn't applied in the Workspace when a record is opened from a reference field | UX View Rule Configurations aren't applied when a record is opened in a Workspace from a reference field on a form, but when opening the same record from a related list in a Workspace, the UX View Rule Configuration is applied. |
Observe that the Custom View created in isn't applied. |
|
UI Form Administration PRB1863573 |
A 'Scope tag not permitted' error is thrown when the UXC Generative AI plugin is active | The scoped UI macros are added to the UI16 form by the 'UXC Generative AI' plugin clash with scoping rules, causing a 'Scope tag not permitted' error to be thrown. Visually, users notice related lists and others macros not loading on the form. |
Observe that the form is in a broken state. The approval _summary form renders on the page, but everything else is missing. Related lists won't display. Users aren't able to right-click on the header or see the scoped UI macro rendered. |
|
UI Form Administration PRB1866407 |
Activity Stream attachment tile actions don't work when a page has been set up to use the multi-controller template | Attachments aren't downloadable from the Activity Stream. |
Refer to the listed KB article for details. |
|
UI Form Administration PRB1868782 |
While composing an email in Vendor Operations, the cursor occasionally jumps, making it difficult to continue typing | When the user types rapidly, the position event is triggered multiple times, resulting in the cursor unexpectedly jumping to the end. |
Observe that the cursor jumps to the end of the file. |
|
UI Form Administration PRB1870603 |
A read-only HTML field displays a horizontal and vertical scroll | The field shouldn't have a scroll bar. |
|
|
UI Form Administration PRB1894995 |
A requested item (RITM) created from an interaction in Service Operations Workspace (SOW) with an HTML variable automatically re-attaches images from the variable as the current user | When a user copy-paste text + images from Word, email, etc. to an RITM created from an interaction in a SOW HTML variable, reloading the RITM automatically re-attaches images to the record and gets displayed in the activity stream as a new attachment. |
Expected behavior: The RITM opens normally and images aren't reattached. Actual behavior: Images from the variable are reattached every time a user opens the RITM record. Newly re-attached images are show in the activity stream. These images can also be found in the sys_attachment table with Table sys ID = <RITM sys_id>. |
|
User Criteria for Service Catalog PRB1819841 |
Semaphore exhaustion is caused by the getAllUserCriteria function getting called in widgets | When a public page is accessed by a guest user or web crawler, this prompts a call to the getAllUserCriteria API, which causes semaphore exhaustion. |
Refer to the listed KB article for details. |
|
UXF Components PRB1826745 |
Highlighting and copying data from related records or any list results in additional help text being copied | In the Service Operations Workspace, when highlighting and copying rows of data from related records or any list, additional help text appears. The copied data includes the message: 'Press and hold Shift then press Enter to edit'. | |
|
UX Framework PRB1788084 |
Using g_aw.openRecord on a new record in the Service Operations Workspace (SOW) doesn't work if a tab to the right of the UI action is selected | Using the UI action on g_aw.openRecord doesn't function correctly if it is used on a tab that has other tabs to the right of it. For example, if there are multiple tabs opened for a new interaction and the UI action is used to open a new incident record to escalate it, the UI action doesn't work. |
Refer to the listed KB article for details. |
|
UX Framework PRB1827900 |
The New button is missing in the 'Cases for Opened for User' related list |
See that the New button is missing. |
|
|
UX Framework PRB1869757 |
There's a performance degradation when loading the home page on Xanadu | When the system property glide.ux.user_criteria_enabled=true, there's a performance degradation between Washington DC and Xanadu when loading the home page. |
Refer to the listed KB article for details. |
|
Virtual Agent PRB1825597 |
The user is unable to select a subflow in a Virtual Agent flow with the action activity | The action utility pulls the first 100 records into the query by the category sorted by name for each spoke. | |
|
Virtual Agent PRB1833571 |
When _max_wait_topic_ is ended using the 'End Conversation' option, the conversation hangs and never completes | The 'Resume flow after topic switching' inside of the _max_wait_topic_ properties should be flipped to false. |
Expected behavior: The conversation ends. Actual behavior: The conversation hangs and never ends. |
|
Virtual Agent PRB1850815 |
In NLU conversations following language switch control, the search term is always 'null' | When Language Detection is enabled for NLU Virtual Agent conversations, any initial search term provided by the requester results in a search of 'null' and associated results. | |
|
Virtual Agent PRB1862370 |
Skill executions are stuck when Now Assist guardian settings (prompt injection, offensiveness) are enabled | Skill test runs aren't working from the skill kit, whereas executions outside of the skill kit (for example: OneExtend.execute() in async mode) are working fine for the same settings. This is due an unsupported operation exception coming from EvaluationServiceImpl.java. |
Expected behavior: Run Test should work irrespective of the guardian setting because users can execute the same One Extend capability outside of the skill kit. Actual behavior: Run Test is stuck due to an exception (Error Execution of evaluation request failed for batch result: fbb3afc4c348 e2149e83d62 f0501312b due to error: null). |
|
Virtual Agent PRB1866633 |
In APAC data center instances, AI agents aren't working even after accepting the Global Routing Consent information message | Global routing is not working even after consenting on the info message for data center instances in the Asia-Pacific region. |
Expected Behavior: The AI Orchestrator should be invoked. Actual Behavior: Even after accepting the consent, AI agents are not functioning, and the error message occurs: 'Sorry, there was a problem on my side trying to complete this request. Try asking again later'. |
|
Virtual Agent PRB1866702 |
'Summarize a record card' isn't displaying when reactivating the case summarisation in Workspace when domain separation is turned on | ||
|
Virtual Agent PRB1866717 |
In Agent Chat, there's an oversized New messages below button | In Virtual Agent (VA) UI Experience, the New messages below button is disproportionately large compared to the rest of the text within the VA. |
Expected behavior: See the down arrow with the 'New messages below' hint text when hovered over displayed, and of a size appropriate to the rest of the VA conversation text. Actual behavior: See the new button display the down arrow and the 'New messages below' text, which is fine, only the size of the arrow and text is disproportionate to the rest of the text within the VA chat. |
|
Virtual Agent PRB1878360 |
'Show more' links are displayed, even for a topic which doesn't have any additional lines in an Edge browser | . |
Refer to the listed KB article for details. |
|
Virtual Agent PRB1879865 |
Now Assist doesn't generate Japanese answers properly | The results are mostly in English. | |
|
Virtual Agent third-party integrations PRB1837988 |
Unable to acquire conversation lock leads to repeated impersonation and excessive logging | Certain long-running Virtual Agent transactions, such as file uploads, can cause excessive impersonation logging. |
Observe the impersonation messages that occur repeatedly until the lock is acquired. |
|
Virtual Agent Web Client PRB1824151 |
A message preview shows the NLU preview message or doesn't show any message even when the user has switched to LLM | The user sees the first message from the previous NLU mode conversation with LA. |
Expected behavior: The user should see the first message in the list of message sent by LA to user for the interaction in LLM mode. Actual behavior: The user still continues to see the first message from the previous NLU mode conversation with LA. |
|
Virtual Agent Web Client PRB1869658 |
There's an error: 'TypeError: Cannot destructure property 'clientContext' of 'y.properties' as it is undefined.' | When this issue happens, users don't see any proactive message, just a create_request call in a 'Network' tab in developer tools. If users have rules and actions setup properly for a URL or portal home pages, users should first see create_request and then get_action calls. The getACtions endpoint should get called and display respective proactive 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. |
|
Walk-Up Experience PRB1873610 |
After an Yokohama upgrade, the walk-up queue isn't displaying any users who are checked in for any location | The issue occurs because the Rest API contains the snc_internal role and as the user has snc_external role, so it disqualifies the walkup user and doesn't render any users in the queue. |
Refer to the listed KB article for details. |
|
Web UX Runtime PRB1799951 |
Saving a field change on a form doesn't update the screen status once changes are saved | A warning message appears because changes to the incident record aren't saved despite the user saving the changes. |
Notice that a warning appears, 'Closing this tab will cause your changes to be lost. Do you want to continue?'. |
All Other Fixes
To view a list of all other PRBs fixed in Zurich, refer to All other Zurich fixes.