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

New York Patch 3 Hot Fix 1

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

New York Patch 3 Hot Fix 1

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

Build information:
Build date: 11-15-2019_1010
Build tag: glide-newyork-06-26-2019__patch3-hotfix1-11-08-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

Application Installation Engine

PRB1371466

TPP table extensions in the scope with custom fields in the same scope cause storage_alias mapping issue upon deployment When extending a TPP table within a scope and also creating a custom field within the same scope on the TPP parent, the resulting application will deploy incorrectly causing the scoped table extension to be mapped differently than the table it inherited the field from and other extended tables outside the scope. The result is that from the parent table's list, values in the specific class will be empty but will be visible when viewing the extension specific list. The application on the source instance will be correct.

Event Management

PRB1371901

In New York, Event Management users who are running with the Statement replication mode will have corruption in the replicated data of ITOM Event Management This issue only happens in the case of a failover when the instance works with a backup database. During the failover, the impact of alerts on services is calculated incorrectly. The alert panel on the Event Management dashboard shows duplicate records, and the em_alert_history table is not cleaned up.

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.

Feedback