--- sourceDocument: Zurich Release Notes sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/zurich/release-notes Release : - zurich ft:locale : - en-US ft:publication_title : - Zurich Release Notes ft:clusterId : - rn bundleId : - rn --- # Zurich Patch 2 Hotfix 1 # Zurich Patch 2 Hotfix 1 {#ariaid-title1} Release version: Zurich Updated November 5, 2025 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read 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](https://servicenow-prod.fluidtopics.net/fUsB9lFROd1_5jM2lwjOwQ "The upgrade process moves your instance to a new ServiceNow release version. Understand the difference between upgrading and patching, release definitions, rollback and backup options, and how to test your non-production and production instance upgrades."). For more information about the release cycle, see the [ServiceNow Release Cycle](https://support.servicenow.com/kb_view.do?sysparm_article=KB0547244).{#zurich-patch-2-hf-1-PO__p_download-version} 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](https://support.servicenow.com/kb_view.do?sysparm_article=KB0743854). ## Fixed problem {#zurich-patch-2-hf-1-PO__section_z1n_4fx_2hc} {#zurich-patch-2-hf-1-PO__all-other-fixes__entry__4} | 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. {#zurich-patch-2-hf-1-PO__ol_y4j_3jx_2hc} 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. {#zurich-patch-2-hf-1-PO__ol_gn2_qjx_2hc} 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. {#zurich-patch-2-hf-1-PO__ol_wbt_vjx_2hc} 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. {#zurich-patch-2-hf-1-PO__ol_rvw_ypx_2hc} Notice that when the screen is built, the field values are missing for fields that do have data. | [ ] {#zurich-patch-2-hf-1-PO__all-other-fixes} ## Fixes included {#zurich-patch-2-hf-1-PO__section_abn_4fx_2hc} 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. * [Zurich Patch 2](https://servicenow-prod.fluidtopics.net/3Y_k_JRSgF6zCGckwZBWJQ "The Zurich Patch 2 release contains important problem fixes.") * [Zurich Patch 1](https://servicenow-prod.fluidtopics.net/ryznRs456gpDAGVQsRzm4g "The Zurich Patch 1 release contains important problem fixes.") * [Zurich security and notable fixes](https://servicenow-prod.fluidtopics.net/iSdf73GoBI~IFroDd~8D8A "The Zurich release contains important problem fixes.") * [All other Zurich fixes](https://servicenow-prod.fluidtopics.net/y_JpjqwOyLF0ufqO7vRiug "The Zurich release contains important problem fixes.") {#zurich-patch-2-hf-1-PO__ul_q4f_spx_2hc}