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

Geneva Patch 5 Hot Fix 4

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

Geneva Patch 5 Hot Fix 4

Geneva Patch 5 Hot Fix 4 provides fixes for the Geneva release.

For Geneva Patch 5 Hot Fix 4:
Build date: 04-28-2016_0829
Build tag: glide-geneva-08-25-2015__patch5-hotfix4-04-27-2016

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

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

Note: This version is approved for FedRAMP.

Fixed problems in Geneva Patch 5 Hot Fix 4

Problem Short description Description Steps to reproduce


Oracle query issued in ElementMetadataQuerier joins lower('sys_id'), degrading performance because desired index is not used
  1. Invalidate cmdb_ci by running GlideTableManager.invalidateTable("cmdb_ci"); in Scripts - Background.
  2. Turn on SQL Debugging.
  3. Navigate to /
Note the large number of long-running queries such as:
19:51:25.789: Time: 0:00:00.111 id:
  SNC10111127[glide.8] for: SELECT * FROM
  sys_dictionary d left join sys_metadata
  m on lower(m."sys_id") = lower(d."sys_id")
  WHERE lower(d."name") = 'sys_ui_action_view'
These take 100+ms because we are missing index utilization on the join, since the columns are being unnecessarily "lowered".


fix_promote_cmdbci_attributes_to_cmdb.xml takes a long time to run with a large number of records in CMDB_CI table Oracle customers are experiencing long upgrades to Geneva. The process of reparenting the CMDB (fix_promote_cmdbci_attributes_to_cmdb.xml) takes longer if there are more than 2 million records in the CMDB_CI table.


fix_short_field_name_types and fix_short_table_name_types sometimes take a long time to run Several users have experienced long upgrades. This is due to the following fix scripts, which can take a considerable amount of time to run:
  • fix_short_table_name_types.xml
  • fix_short_field_name_types.xml
User Interface (UI)


Validation from data policy does not work if you are using a guided task board on a parent table, and the data policy is looking at a field from a child table In an OOB instance:
  1. Navigate to an Incident form > Configure Form Layout.
  2. Create a new Field "Test style" and add it on the form. Save.
  3. Create a data policy on Incident table using the field you created in step 2. For example:
    • Condition: State is 'Closed' or 'Resolved'
    • "Test Style" = Mandatory
  4. Navigate to task.list. Make a filter where Task Type is Incident.
  5. Right-click on the State column > Show Visual Task Board.
  6. Move an Incident card to Resolved or Closed state.
Observe that the move fails, and in Geneva, you do not receive the popup message from the data policy.

Fixes included with Geneva 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.