Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Istanbul Patch 0 Hot Fix 1

Istanbul Patch 0 Hot Fix 1

The Istanbul Patch 0 Hot Fix 1 release contains fixes to these problems.

For Istanbul Patch 0 Hot Fix 1:
Build date: 01-12-2017_1445
Build tag: glide-istanbul-09-23-2016__patch0-hotfix1-01-12-2017

For more information about how to upgrade an instance, refer to Upgrade to Istanbul.

For more information about the release cycle, see the ServiceNow Release Cycle. For a downloadable, sortable version of Istanbul fixed problems, see KB0598935.
Note: This version is approved for FedRAMP.

Fixed problem in Istanbul Patch 0 Hot Fix 1

Problem Short description Description Steps to reproduce

Performance Analytics



In the PA module, deleting one record in specific tables from the list drop-down deletes all of the table's records

ServiceNow has identified a potential issue that may cause data loss in the Performance Analytics data tables. When a user attempts to manually delete a record using the list drop-down, the action triggered uses an incorrect primary key, causing the action to execute the delete against all records in the table.

This issue is only present in instances that are created new and configured for Istanbul Patch 0. If an instance is upgraded to Istanbul from a prior release family, it is not at risk.

Refer to the listed Known Error KB article for details.

Fixes included with Istanbul Patch 0 Hot Fix 1

* 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.

This site is scheduled for a small content update on Tuesday, December 18th, between the hours of 4:00pm and 8:00pm Pacific Time (Dec 19 00:00 – Dec 19 4:00 UTC). Access to this site may be slightly delayed during that time.