Zurich Patch 2 Hotfix 1

  • Release version: Zurich
  • Updated November 5, 2025
  • 3 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 Zurich Patch 2 Hotfix 1

    The Zurich Patch 2 Hotfix 1, released on November 5, 2025, addresses specific issues and enhances the performance of the ServiceNow platform. It is essential for customers to stay updated for optimal system functionality.

    Show full answer Show less

    Key Features

    • Fixed Problems: Several critical issues have been resolved in this release, enhancing the flow engine and mobile platform functionalities.
    • Upgrade Information: For upgrading your instance, refer to the ServiceNow upgrades documentation. The release is also available in Regulated Market environments.

    Key Outcomes

    By applying this hotfix, customers can expect improved flow execution and mobile offline functionality, ensuring smoother operations and enhanced user experience. Fixes include:

    • Flow Engine Issue: Resolved an issue where trigger inputs were inaccessible after a do-until loop.
    • Mobile Platform Enhancements: Addressed problems with UI policies not applying correctly and the loss of fields in table hierarchies.

    For successful upgrades, ensure you are on the latest version that includes relevant PRB fixes.

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

    Build information:
    Build date: 11-03-2025_0248
    Build tag: glide-zurich-07-01-2025__patch2-hotfix1-10-31-2025
    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

    PRB1941990

    		 Trigger inputs aren't accessible after a do-until loop execution

    This issue is caused by the changes to GlideFlowStages Updater.java (older name GlideStage UpdateListener.java). It's observed that, in this specific flow structure, the 'in.request_item' flow input isn't passed to the 'Create Catalog Task' action. Querying the sys_flow_value table, there are 2 entries for 'in.request_item' one for the flow input and another with the parent loop associated. As the same key 'in.request_item' is now associated with parent loops, it can only be accessed in the loop body (and for the specific iteration), and all other references to it out side the loop aren't available.
    1. Import the flow XML.
    2. Open Service Portal.
    3. Place a request for 'iPad Pro' with the color set to 'Silver'.
    4. Retrieve the RITM.
    5. Open Flow Designer.
    6. Test run the flow XML with the copied RITM as the input.
    7. Open the RITM when the flow waits at the AFA.
    8. Approve the request created for Abel Tuter.

    Expected behavior: The flow resumes, exits the loop, and reached the 'Create Catalog Task' and will be in the 'Waiting' state.

    Actual behavior: After exiting the loop, it is errored at 'Create Catalog Task' with an error executing the instruction.

    Mobile Platform

    PRB1953826

    		 UI policies applicable to the screen table are not applied in Mobile Offline when the underlying record comes from an extended table of the screen table The page document should not be rebuilt unless there were changes in offline to the records referenced in the screen.
    1. Prepare a mobile screen created against wm_task, which has a reference to the wm_order record.
    2. Creating the wm_task record.
    3. Update the wm_order record.
    4. Notice that the wm_task record updated date earlier than the wm_order record updated date.
    5. Open the offline Download cache.

    Notice that when navigating to the wm_task detail screen for the record, it results in an underlying document being rebuilt when it is not required.

    Mobile Platform

    PRB1953804

    		 The processing of hierarchy of tables results in the loss of fields, causing a returned object containing only a partial set of fields for M This also results in actions not appearing due to missing values used in the button condition.
    1. Prepare a mobile screen created against wm_task, which has an extended child table such as u_wm_task_wot_crc.
    2. Open the offline Download cache.

    Notice that when the screen is built, the field values are missing for fields that do have data.

    Mobile Platform

    PRB1953824

    		 The document is rebuilt when there are no changes in Mobile Offline due to an incorrect logic comparing the server update time on the Reference field in the screen to the current screen record update time
    1. Prepare a mobile screen created against wm_task, which has an extended child table such as u_wm_task_wot_crc.
    2. Open the offline Download cache.

    Notice that when the screen is built, the field values are missing for fields that do have data.

    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.