Washington DC Patch 1 Hotfix 2

  • Release version: Washingtondc
  • Updated April 2, 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 1 Hotfix 2 Release Notes

    The Washington DC Patch 1 Hotfix 2, released on April 2, 2024, addresses several critical issues within the ServiceNow platform, particularly enhancing performance and compliance. This hotfix is now available in Regulated Market environments.

    Show full answer Show less

    Key Features

    • Build Information:
      • Build Date: March 31, 2024
      • Build Tag: glide-washingtondc-12-20-2023patch1-hotfix2-03-27-2024
    • Fixed Problems:
      • Flow Engine: Resolved issue with large flows failing due to REST payload size limits.
      • Identity: Addressed compliance issues with time-limited user role assignments.
      • Performance Analytics: Fixed the inability to save modifications on migrated dashboards.
      • Platform Licensing: Corrected access issues for SubscriptionEntitlementsService in Java layers.
      • Restricted Caller Access: Eliminated duplicate records caused by the 'Prevent invalid source & target on RCA' business rule.

    Key Outcomes

    ServiceNow customers can expect improved functionality and compliance with this hotfix. It is essential to upgrade to this release from earlier versions to benefit from the included fixes, particularly if you are experiencing issues related to flow performance or user role management. Ensure that you are on the latest patch to maintain optimal system performance and compliance.

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

    Build information:
    Build date: 03-31-2024_1047
    Build tag: glide-washingtondc-12-20-2023__patch1-hotfix2-03-27-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

    Flow Engine

    PRB1743462

    KB1638768

    Large flows are failing with Flow Designer Large flows are failing with Flow Designer with the following error: 'Rejected large REST payload with content-length = 27239395 bytes. Max allowed: 10485760 bytes.'

    Refer to the listed KB article for details.

    Identity

    PRB1744985

    A time-limited user role assignment should be restricted for licensing compliance Users can assign ITIL roles to multiple users for a limited time without auditability. Temporary role assignments aren't visible in the user roles section, exacerbating auditing challenges.
    1. Navigate to sys_user_has_role_time_limited.do.
    2. Verify that any role can be selected, and that 'End time' can be larger than 'Start time', so a role can be assigned indefinitely.

    Performance Analytics

    PRB1739870

    No modifications can be saved on a migrated dashboard All Next Experience dashboard tables but par_dashboard have empty sys_package and sys_scope fields upon migration. This causes failures.

    Platform Licensing

    PRB1746750

    SubscriptionEntitlementsService aren't accessible in a Java layer SubscriptionEntitlementsService aren't accessible in a Java layer. This causes an error to be logged during the IH transaction. Transactions are incorrectly attributed as 'unlicensed'.
    1. Install the Microsoft OneDrive spoke.
    2. Create an action with the REST step in the Microsoft OneDrive spoke.
    3. Try running the action with a background script.

    There should be no cross scope error.

    Restricted Caller Access (RCA)

    PRB1741012

    The 'Prevent invalid source & target on RCA' business rule is causing duplicate records in the sys_restricted_caller_access table The 'Prevent invalid source & target on RCA' business rule is causing the 'Target' field to be set to NULL. This lets duplicate records be inserted into the sys_restricted_caller_access table.

    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.