Washington DC Patch 4 Hotfix 1

  • Release version: Washingtondc
  • Updated June 20, 2024
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Washington DC Patch 4 Hotfix 1

    The Washington DC Patch 4 Hotfix 1, released on June 20, 2024, addresses several issues to enhance system functionality. This hotfix is part of the ServiceNow AI Platform and is available in regulated market environments. Understanding the changes and fixes included in this release is essential for ServiceNow customers to maintain optimal system performance.

    Show full answer Show less

    Key Features

    • Fixed Problems:
      • AI Search: Resolves issues with Digital Product Release (DPR) searches returning no results for non-English catalogs.
      • Database Persistence: Fixes inconsistencies in JavaScript generation for GlideFilter when using multiple conditions.
      • Key Management Framework: Addresses the initialization of the 'system' user impacting Glide properties.
      • Reporting: Corrects the behavior of the 'OR' operator in related list condition queries.
      • Service Catalog: Ensures business rules execute correctly when triggered by Record Producer scripts in non-global scopes.
      • Virtual Agent: Fixes the feature name displayed in the sysgenaiusagelog for FSM record summary use cases.

    Key Outcomes

    After applying this hotfix, customers can expect improved reliability and accuracy in search results, data handling, reporting, and business logic execution within their ServiceNow instances. It is recommended to upgrade to the latest version to benefit from these fixes and enhancements.

    The Washington DC Patch 4 Hotfix 1 release contains fixes to these problems.

    Build information:
    Build date: 06-17-2024_2231
    Build tag: glide-washingtondc-12-20-2023__patch4-hotfix1-06-10-2024
    Important:
    For more information about how to upgrade an instance, see ServiceNow Upgrades.

    For more information about the release cycle, see the ServiceNow Release Cycle.

    Note:
    This ServiceNow AI Platform major family release is now available in ServiceNow's Regulated Market environments. For more information about services available in isolated environments, see KB0743854.

    Fixed problem

    Problem Short description Description Steps to reproduce

    AI Search

    PRB1771600

    		 Digital Product Release (DPR) searches across non-English catalogs query with English text A DPR request on a non-English instance finishes with an English query which returns no results.
    1. Provision an instance with NA4S 6.2.3 + DT enabled.
    2. In a Spanish session, enter the query 'Solicitud de categoría de servicio'.

    Using Debug AI search, observe that the DPR request finishes with the query 'Service Category Request', but with the locale 'es'. No results are returned (pre-DT change, this returned Service Category Request catalog item, displaying as 'Solicitud de categoría de servicio').

    Database Persistence - Data Access

    PRB1763146

    		 If GlideFilter has a new query (NQ) to add multiple conditions, it generates different JavaScript from the same encoded query The issue affects certain, but not all, MultipleCondition (^NQ) queries. It specifically impacts those where the first of the conditions satisfies the following: It targets a dot-walked field, the field is of type 'GlideList', and the condition is 'IsOneOf'.

    Key Management Framework (KMF)

    PRB1773544

    KB1646553

    		 Initializing a 'system' user before GlideProperties are loaded leads to caching an invalid 'system' user while initializing Glide. (Glide.init())

    Refer to the listed KB article for details.

    Reporting

    PRB1717895

    KB1629327

    		 The 'OR' logical operator in a related list condition query behaves as the 'AND' operator When reporting over a table, using a related list condition with the 'OR' logical operator, it seems to have the same effect as using 'AND'.

    Refer to the listed KB article for details.

    Service Catalog

    PRB1763535

    KB1646316

    		 When a CRUD operation is triggered from a 'Record Producer' script in a non-global scope, business rules aren't executed due to an incorrect 'current' reference Business rules that are supposed to run due to CRUD operations triggered by the 'Record Producer' script never run. This can affect multiple use cases where they don't rely on the Record Producer's natural flow to create records, but instead use the script field to create records in multiple tables.

    Refer to the listed KB article for details.

    Virtual Agent

    PRB1767655

    The feature name in sys_gen_ai_usage_log is shown as 'Case Summarization'

    		 This occurs when FSM record summary use cases are run.
    1. Open a WOT.
    2. Click the Summarize button.
    3. Navigate to the sys_gen_ai_usage_log table and open the latest record for the above action.

    Observe that the feature name is 'Case Summarization'.

    Fixes included

    Unless any exceptions are noted, you can safely upgrade to this release version from any of the versions listed below. These prior versions contain PRB fixes that are also included with this release. Be sure to upgrade to the latest listed patch that includes all of the PRB fixes you are interested in.