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 5 Hot Fix 4

Istanbul Patch 5 Hot Fix 4

The Istanbul Patch 5 Hot Fix 4 release contains fixes to these problems.

For Istanbul Patch 5 Hot Fix 4:
Build date: 07-27-2017_2304
Build tag: glide-istanbul-09-23-2016__patch5-hotfix4-07-20-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 problems in Istanbul Patch 5 Hot Fix 4

Problem Short description Description Steps to reproduce




Restored record points to archive table instead of original table A restored record URL points to the archive table instead of the original table, for example, ar_incident instead of incident.
  1. Enable the data archiving plugin.

    For more information, see the documentation topic Activate data archiving.

  2. Set up archiving rules for a table, for example, the incident table.
  3. Archive a few records.
  4. Restore the archived records.

    A message suggests record restored to original table, for example, incident.

  5. Go to the original table, for example, incident, and open the restored record.

Note that the URL points to the archive table instead of the original table, for example, ar_incident instead of incident.

Note also that there are now duplicate records, one in the original table and one in the archive table. This causes the UI action Archive Record to fail with the message "No Archive table defined in Archive Map for: archive table name"

Service Catalog


Reference type variables with a reference qualifier are ignoring the reference qualifier in the lookup popup when the tree_picker attribute is set to true When the tree picker format is used for the list of records on the referenced table, after users click the reference lookup icon on a Service Catalog reference variable, the reference qualifier is not applied in some situations.
  1. Navigate to the Service Catalog module and create a new catalog item.
  2. Create a reference field variable with attribute set as tree_picker=true in default value column. For example, the table is referring to cmn_location.
  3. Make sure that variable has a reference qualifier condition as a simple one. For example, [Condition] [is] [Where City] [is one of] [Baltimore, Seattle].
  4. Save the catalog item and click Try it.

Expected behavior: The list should respect the condition defined under the reference qualifier variable (e.g. Baltimore and Seattle).

Actual behavior: The list of records only respects the defined table - it does not honor the condition defined when users set the tree_picker attribute as true. For example, when users type 'San Diego' (which is not part of the defined condition), and click on the reference icon, it displays the list of records belonging to San Diego.

Fixes included with Istanbul Patch 5 Hot Fix 4

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