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

Helsinki Patch 2 Hot Fix 6

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

Helsinki Patch 2 Hot Fix 6

Helsinki Patch 2 Hot Fix 6 provides fixes for the Helsinki release.

For Helsinki Patch 2 Hot Fix 6:
Build date: 05-25-2017_1812
Build tag: glide-helsinki-03-16-2016__patch2-hotfix6-05-25-2017

For more information about how to upgrade an instance, see Upgrade to Helsinki.

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

Note: This version is approved for FedRAMP.

Fixed problem in Helsinki Patch 2 Hot Fix 6

Problem Short description Description



In the presence of multiple duplicate records, incorrect record gets selected as candidate for matching, leading to record reclassification The code for processing for de-duplicating records in CMDB works as follows:

The code enumerates relations in the CMDB, based on criteria from the payload passed to the Identification Engine. The first phase creates a list of all the records involved in a certain relation with another record. The second phase refines the list down to the records that actually match the input data (thus detecting real duplicates). Finally, one of the records from the second list is used as the match for the Identification process. The problem is a code bug where the wrong list is used for the final step, thus leading to the selection of an incorrect record.

Fixes included with Helsinki Patch 2 Hot Fix 6

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