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

Geneva Patch 5 Hot Fix 6

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

Geneva Patch 5 Hot Fix 6

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

For Geneva Patch 5 Hot Fix 6:
Build date: 06-09-2016_0848
Build tag: glide-geneva-08-25-2015__patch5-hotfix6-06-08-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 6

Problem Short description Description Steps to reproduce


Presence kill switch does not stop all Presence requests The property glide.ui.presence.disabled does not shut off all presence requests. The presence system is looking for $window.NOW.presence_disabled, but that value is only set if ng_amb_header.xml is included on the page in question. Not all implementations of presence are including this template.
  1. Set glide.ui.presence.disabled to false.
  2. Open the main frameset.
  3. Open Chrome developer tools and look at the network requests.
Notice that requests for presence are still being executed.




Connect Support chat message entries between two people are all shown in activity stream as one account All chat messages which are posted before an incident is created will show up on the activity stream as being inserted by one person, even though there are two people messaging.
  1. Activate the Chat, Connect, and Connect Support plugins.
  2. Create a queue and select the Service Desk assignment group.
  3. In one browser, log in as Abel Tuter (do not impersonate).
  4. In a different browser, log in as ITIL User (do not impersonate).
  5. With Abel Tuter, create a new chat in the queue.
  6. Answer the chat as ITIL User.
  7. Post a few chats back and forth between the two users.
  8. With ITIL User, create an incident from the chat and save the incident.

Expected result: The activity stream in the incident should show a chat conversation between the two people with their respective names.

Actual result: You will see only the ITIL User listed for every posted chat message.

Platform Performance



ServletTransaction does not account for recycled requests and leaves sessions in session sync The RESTAPIProcessor throws an exception that causes the transaction to be cancelled, but not release the session sync on the session. This results in sessions "leaking" in the queue and can eventually, in a worst case scenario, consume the whole transaction queue. The affected end user(s) experiences HTTP 429 "Rejecting request" errors. Refer to the listed Known Error KB article for details.


[Geneva] Memory consumption on de-duplicatable Strings (0, 1, true, false, user preferences)

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