Washington DC Patch 5 Hotfix 1

  • Release version: Washingtondc
  • Updated July 18, 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 5 Hotfix 1

    The Washington DC Patch 5 Hotfix 1, updated on July 18, 2024, addresses several key issues to enhance system functionality. It includes important build information and is applicable to ServiceNow's Regulated Market environments.

    Show full answer Show less

    Key Features

    • Fixed Problems: The hotfix resolves various issues affecting AI Search, Condition Builder, Server-side scripts, Service Catalog API, and UI Form Administration.
    • Build Information:
      • Build Date: July 16, 2024
      • Build Tag: glide-washingtondc-12-20-2023patch5-hotfix1-07-11-2024
    • Upgrade Guidance: For instance upgrades, refer to the ServiceNow Upgrades documentation and the ServiceNow Release Cycle for detailed procedures.

    Key Outcomes

    After applying this hotfix, customers can expect improved performance in search functionalities, accurate date formatting in CAB workbench, and proper handling of memory limits in server-side scripts. Additionally, it resolves issues with catalog item requests and workspace page loading, ensuring a smoother user experience.

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

    Build information:
    Build date: 07-16-2024_1316
    Build tag: glide-washingtondc-12-20-2023__patch5-hotfix1-07-11-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

    PRB1779636

    		 Carousel and regular search results do not appear intermittently The carousel gets stuck in a loading state when a search query is performed.
    1. Provision a latest track instance.
    2. Make sure Now Assist Actions and Now Assist QnA are attached to a Service Portal search profile.
    3. Perform a search for any Catalog or QnA query.

    Notice that the carousel is stuck in a loading state.

    Condition Builder

    PRB1777164

    		 Change Advisory Board (CAB) workbench displays an extra backslash in the Planned start date field CAB workbench displays an extra backslash in the Planned start date field every time the CAB meeting is saved and refreshed.
    1. Navigate to the Agenda Management form section Change Request addition conditions field.
    2. Add a new condition term: Planned start date at or after (Select the calendar icon, then select the green checkmark to save/close the picker).
    3. Save the record and view the form again.
    4. Look at the condition term added.

    Expected behavior: The date should be in the format (yyyy-MM-dd 00:00:00).

    Actual behavior: The date shows a slash in the format (yyyy-MM-dd\ 00:00:00).

    Server-side scripts

    PRB1786423

    		 Transpiler doesn't respect the custom per-thread memory limit, causing an error

    Some threads in the transpiler do not respect the value of the system property, com.glide.script.swc .memory_threshold_in_kb, and instead throw an exception when memory usage exceeds the default per-thread limit of 16MB. The error is logged repeatedly and prevents a portion (up to 1/4) of the server-side scripts executed on the node to fail.

    Service Catalog API

    PRB1782677

    		 Input utterance in conversation catalog is not working Output has empty slots.
    1. Create a record producer with several questions.
    2. Make one of the questions a single line text question that takes a Sys ID as an input.
    3. Create a topic and add the 'Request catalog item (LLM)' topic as a topic block in the newly created topic.
    4. Pass an input utterance to catalog through the topic and make sure to add an utterance for the Sys ID as well.

    Expected behavior: The utterance should populate properly.

    Actual behavior: None of the variables in the catalog are populated from the utterance.

    UI Form Administration

    PRB1784983

    KB1649352

    		 Duplicate UI Scripts that have the same exact name prevent a workspace page from loading

    Workspace pages fail to load if there are duplicate UI scripts with the same API name in the sys_ui_script table. This is caused by a functional change to how the workspace UI scripts are called.

    Refer to the listed KB article for details.

    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.