Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

New York Patch 1 Hot Fix 1

Log in to subscribe to topics and get notified when content changes.

New York Patch 1 Hot Fix 1

The New York Patch 1 Hot Fix 1 contains fixes to these problems.

Build information:
Build date: 09-05-2019_1536
Build tag: glide-newyork-06-26-2019__patch1-hotfix1-09-04-2019
Important: For more information about how to upgrade an instance, see Upgrade to New York.

For more information about the release cycle, see the ServiceNow Release Cycle. For a downloadable, sortable version of New York fixed problems, see KB0748891.

Note: This version is approved for FedRAMP. The following products are not approved for FedRAMP in New York: Benchmarks, Document Viewer, Instance Data Replication, and ServiceNow mobile.

Fixed problems

Problem Short description Description Steps to reproduce

Core Platform


The default expiry date for sys_user_delegate is set to 01/01/2020

Event Management


Alert panel (and impact calculation) does not show the correct number of alerts according to the defined limit Alert history query for alert panel does not return the correct value according to the defined limit.

Event Management


Records in em_impact_status table with NetworkPath field defined on them will be inactive although it's still valid When Network Path is used, wrong impact will be calculated.

Event Management


Business Service Group: long query to receive service group impact SQL query to receive service group impact takes a long time running from Impact for service groups job.

Event Management


The backfill job is stuck The backfill job is stuck and slowing down DB performance in use cases when Alert has thousands of snapshots in Alert History.

Event Management


Impact jobs get stuck and the dashboard does not load in heavy EM load environments em_impact_status jobs are stuck and the EM dashboard doesn't load. This happens in environments with high throughput and large em_history and em_impact_status tables.

Knowledge Management


The default expiry date for KB articles is set to 01/01/2020, and articles will expire on this date and not be searchable if it is not updated The valid_to field on knowledge articles and templates used to have a default value of '01/01/2020'. To avoid articles getting expired after 01/01/2020, this fix will only update the articles that have a valid_to date of 01/01/2020 to have a new value of 01/01/2100. Articles where users have changed the valid_to date from the default value of 01/01/2020 will not be updated.
  1. Navigate to Knowledge > Articles > Create New.
  2. Populate required fields and save the article.
  3. Verify the valid_to date value. It is set to 01/01/2020.

Knowledge Management


Whenever a new knowledge submission is created, the valid_to is defaulted to 2020-01-01 The default value of the valid_to field on knowledge submissions used to be '01/01/2020'. After this fix, the default value of valid_to will be changed to '01/01/2100'.

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.