Zurich Patch 2 Hotfix 2

  • Release version: Zurich
  • Updated November 14, 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 2

    Zurich Patch 2 Hotfix 2, released for the Zurich version of ServiceNow on November 11, 2025, delivers important fixes addressing mobile platform issues related to offline functionality and data integrity. This release is part of the ServiceNow AI Platform family and is available in Regulated Market environments, supporting isolated deployments.

    Show full answer Show less

    Key Fixes

    • Offline Query Accuracy (PRB1959673): Corrects an issue where offline query results on mobile devices showed null values for reference data columns. The fix ensures accurate data display in offline caches when reference columns are defined on child tables.
    • UI Policies Application Offline (PRB1957087): Resolves the problem where UI policies for a screen table were not applied offline on mobile when records come from extended tables. Now, UI policies such as field visibility correctly apply during offline edits.
    • Data Loss During Offline Cache Updates (PRB1959666): Prevents data loss caused by incomplete offline cache updates during online operations. This fix ensures that referenced records retain all necessary field data, avoiding null overwrites when switching between screens.

    Practical Impact for ServiceNow Customers

    Customers using ServiceNow mobile applications will experience improved reliability and data consistency when working offline, especially with complex table relationships and UI policies. These fixes enhance the user experience by ensuring that offline caches accurately reflect the intended data and that UI behaviors remain consistent offline.

    Upgrade Considerations

    This hotfix can be safely applied to Zurich Patch 2 and previous Zurich releases, including Zurich Patch 2 Hotfix 1 and Zurich Patch 1. It consolidates earlier fixes and should be included in upgrade plans to maintain optimal mobile platform functionality and security.

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

    Build information:
    Build date: 11-11-2025_1307
    Build tag: glide-zurich-07-01-2025__patch2-hotfix2-11-10-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

    Mobile Platform

    PRB1959673

    		 Offline query results are incorrect due to reference data columns being populated as null in the offline cache payload On mobile, the offline query results are incorrect due to reference data columns being populated as null in the offline cache payload. This happens when the column is defined on the child table of the table used for reference input.
    1. Create a column 'test_user' in wm_task.
    2. Create a mobile screen based on wm_task where the data item test_user is empty.
    3. Create a record in wm_task where wm_task.test_user is set to a value (not empty).
    4. Create another record in wm_task where wm_task.test_user is empty.
    5. Create an action with an input form screen which has a reference input based on the task table which will result in records from wm_task to be included where test_user is not empty.
    6. Log in to the application.
    7. Download a cache.
    8. While online, navigate to the screen that was created.
      • Observe that there's only one record.
    9. Navigate to settings.
    10. Go offline
    11. Navigate to the screen that was created.
      • Observe that it displays an additional record (it includes the wm_task record which had a test user populated).
    12. Inspect the cache that was generated.

    Observe that there's a record for the wm_task record in the data section, under the task table. It has a test user populated with a null value specified for the test_user field.

    Mobile Platform

    PRB1957087

    		 UI policies applicable to the screen table aren't applied when offline on mobile While offline and on mobile, UI policies applicable to the screen table aren't applied when the underlying record comes from an extended table of the screen table.
    1. Start with an existing table, such as 'wm_task'.
    2. Create an extension of the table, 'wm_task_crc'.
      • Observe that a mobile screen is created against the wm_task table (a record screen with a detail tab).
    3. Create a button which will result in an edit of the wm_task table while offline.
      • The writeback action will require an offline step which edits a field in the detail screen or uses the declarative update action.
    4. Ensure that you have mobile UI policies created for the wm_task table where it hides or shows the fields based on fields in the wm_task table, which are exposed in the detail screen.
    5. Create records in the wm_task_crc table.
    6. Download the cache.
    7. Go offline.
    8. Navigate to the wm_task detail screen for a record created in the wm_task_crc_table.
    9. Select the button to update the record.

    Observe that the document rebuilds. The UI policies aren't applied and don't hide or show the fields.

    Mobile Platform

    PRB1959666

    		 Data is lost when updating the offline cache during online operations While offline and on mobile, data is lost when updating the offline cache during online operations such as viewing screens or performing actions. This happens because the first screen updates information for the dot-walked (referenced) fields record, but the document doesn't contain all the information for all the fields for the referenced fields record. Null is filled in the database update for any field for which there isn't information.
    1. Set up two screens:
      • Screen 1: A screen that's based on the wm_task table and has data for the current task. It should also have data for a reference field, which is also based on wm_task. (The referenced record on wm_task will only display 2 fields via dot-walk.)
      • Screen 2: A screen that's based on the wm_task table and displays referenced records from the record in the above screen. This screen should have a condition on fields not included in the above screen.
    2. Log in to the application.
    3. Download a cache and don't go offline.
    4. Navigate to Screen 1's detail screen.
      • Observe that the offline cache updates for the current screen and referenced records.
    5. Navigate to settings.
    6. Go offline.
    7. Navigate to Screen 2.

    Observe that the screen is missing the referenced record from Screen 1.

    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.