Washington DC Patch 8 Hotfix 1

  • Release version: Washingtondc
  • Updated October 14, 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 8 Hotfix 1

    The Washington DC Patch 8 Hotfix 1, released on October 14, 2024, addresses several issues within the ServiceNow platform, particularly impacting users of the Vancouver instance. This hotfix is vital for maintaining optimal functionality and user experience.

    Show full answer Show less

    Key Features

    • Fixes for HTTP Errors: Resolves an intrusive modal error message for failed 400 and 500 HTTP requests in the UX Framework.
    • Impersonation Notifications: Ensures a modal appears for bad impersonation attempts, improving user awareness.
    • CMDB Log Message Correction: Fixes incorrect log messages related to partial payload processing in the Configuration Management Database.
    • AI Search Functionality: Rectifies issues where the AI Search feature fails to yield results on the Now Mobile app, ensuring consistency with the Service Portal.

    Key Outcomes

    By upgrading to this release, customers can expect enhanced user experience through resolved errors and improved functionality, ensuring smoother operations within their ServiceNow environments. It is advisable to upgrade from any prior version listed to benefit from all included fixes.

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

    Build information:
    Build date: 10-09-2024_1059
    Build tag: glide-washingtondc-12-20-2023__patch8-hotfix1-10-03-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

    UX Framework

    PRB1695799

    		 A failed 400 and 500 HTTP request displays an intrusive modal error message in a Vancouver instance Making a bad request in a seismic component to a Representational State Transfer Application Programming Interface (REST API) prompts an intrusive modal 400 and 500 error message on the user interface of a Vancouver instance.
    1. Open a Vancouver instance.
    2. Make a bad request in a seismic component to a REST API.
    Next Experience User Menu

    PRB1764924

    		 The modal prompted to inform the user of bad impersonation attempt does not appear A modal informing the user that an impersonation cannot be performed because it is a bad impersonation attempt is not prompted.

    Trigger any impersonation that should not be allowed.

    Expected behavior: A modal appears to inform the user that the impersonation cannot be performed.

    Actual behavior: The modal notifying the user of the bad impersonation attempt does not appear.

    Configuration Management Database (CMDB)

    PRB1748280

    		 The log message 'Stopped processing partial payloads' appears even where there are no partial payloads to process The log message 'Stopped processing partial payloads' is an incorrect message to be displayed even when there are no partial payloads processing.
    1. Change the memory threshold property 'glide.identification_engine.partial_processing_max_node_memory_percent' to 'very low'.
    2. Run an enhanced identification and reconciliation (IRE) payload.

    Observe that the log message 'Stopped processing partial payloads' appears.

    AI Search

    PRB1808466

    		 AI Search yields 'No results found' message on the Now Mobile app, but works as expected in the Service Portal Using AI Search on the Now Mobile app does not render results and displays errors in the logs, but using AI Search in the Service Portal works as expected.
    1. Log in to a Washington DC instance.
    2. Ensure AI Search is enabled.
    3. Open the Now Mobile app.
    4. Search for content with AI Search.

    Expected behavior: Results are yielded after searching for content with AI Search in the Now Mobile app.

    Actual behavior: No results are yielded, the 'No results found' message is prompted, and error logs appear after searching for content with AI Search in the Now Mobile app.

    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.