Geneva Patch 7 Hot Fix 2 The Geneva Patch 7 Hot Fix 2 release provides fixes for the Geneva release. For the Geneva Patch 7 Hot Fix 2 release: Build date: 06-30-2016_1304 Build tag: glide-geneva-08-25-2015__patch7-hotfix2-06-25-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 7 Hot Fix 2 Problem Affected Plugins Short description Description Steps to reproduce ChatPRB668543 Connect Support - Chat Queue Entry: Unexpected results for aggregate data (wait time and action) make reporting and tracking difficult/impossible Chat queue entry data is generated in a way that seems strange to administrators and makes reporting difficult. Specifically, the wait time appears to be updated to match the total duration when the session is closed, and the action is set to abandoned when complete. However, this does not align with customer expectations. Additionally, in Helsinki, it does not appear that there is a way for a user to end a chat - that responsibility appears to be available only to the Support Agent. Activate the Chat plugin. Activate the Connect Support plugin. Open two distinct browser sessions, one impersonating Joe Employee, the other impersonating Fred Luddy. As Joe, navigate to this URL and start a chat: $chat_support.do?queueID=c54f0abf0a0a0b452db84664f409c79c As Fred, accept the chat, then: Bring up the chat queue for Service Desk chat. Find the Chat Queue Entry for the chat you just created in the related list. Note the wait time and action. The wait time should reflect the amount of time that the user waited for the chat to be accepted, and the action should reflect 'accepted'. These values make sense. Send a few replies to the chat. As Joe, send a few replies to the chat, then: Realize that you no longer need assistance and attempt to close the chat. You cannot. Send a message to Fred indicating that you are good to go. As Fred, end the chat, then: Navigate back to the chat queue entry for the chat. Note that the wait time matches the duration and that its status is 'abandoned'. Summary of issues The wait time should not change, but it seems to reflect the total duration of the chat instead of only the wait time. The action shows as 'abandoned', which seems a bit strange since no one actually abandoned the chat. The customer expectation is that 'abandoned' should only be set when the user leaves a chat before it was accepted, and there should be other actions to indicate that the issue was solved in the chat or that the chat was transferred to an incident. The action shows as abandoned even if you create an incident from the chat. ChatPRB682848 Connect Requests to /api/now/collaborators/all are slow for large conversation lists Users who are members of many conversations (100+) can experience slow load times in Connect. In particular, requests to collaborators/all can take multiple seconds to resolve. Include a user in 100 groups that each have 10 members. Make a request to /api/now/collaborators/all. Notice that the response can take several seconds to complete. DiscoveryPRB674184 File Probe Template may still execute even if a matching local file based probe does not exist File probe templates limit what probe a MID Server may execute to probes that only exist on a file system. Starting with Geneva, even though there is an error that indicates a template does not exist, the probe is still executed. An input ecc_queue record is returned that contains both an error and the results of the probe. In a Geneva instance: Create a new Linux MID Server (or link an existing one). On the MID Server host, create some file location to use where you would store these File Probe Templates (e.g. /tmp/probes). In the config.xml file on this MID Server, add these following parameters: <parameter name="file_probe_template_dir" value="/tmp/probes"/> <parameter name="file_probe_template_debug" value="true"/> ("file_probe_template_dir" is the location you created from step 2 above and "file_probe_template_debug" is optional, but available to use) Note: Do not add "file_probe_template_capture", as this will allow you to create new records here, which is not what we want at this time. In your instance, open the ecc_queue list view and create a new record here with these values: Agent: mid.server.[MID Server name] Topic: Command (or SSHCommand) Name: ls -l Source: [Can leave empty or put the localhost IP of the MID Server] Queue: output State: ready As this command runs and you get the input back, you may get the following error: Probe not executed. file probe template not found: Command.ls__lHowever, if this probe ran, you will get results resembling the following: drwxr-xr-x. 3 user.name user.name 4096 Apr 26 22:43 bin drwxr-xr-x. 2 user.name user.name 4096 Apr 27 09:54 conf -rw-rw-rw-. 1 user.name user.name 6121 Apr 27 10:16 config.xml drwxr-xr-x. 2 user.name user.name 4096 Apr 23 22:34 etc .... User Interface (UI)PRB668554KB0596137 UI16 Duplication of banner image sys_attachment records after Geneva/Helsinki upgrade causes slow response times Slow response times have been seen after upgrading to Geneva and some builds of Helsinki when logging in and navigating in the instance. Login is taking 1+ minute in some cases. This issue is due to duplicate records inserted during the upgrade from a fix script that cause the sys_attachment table to become very large. A frequent encoded query against sys_attachment triggers delays in the instance. Refer to the listed Known Error KB article for details. User Interface (UI)PRB679621KB0595003 Clicking the Calendar button next to a date field for a Catalog item causes the Calendar widget to appear at the top of the page rather than near the field When you open a Date Field variable on a Catalog item, the Calendar widget appears at the top of the page rather than near the field. Refer to the listed Known Error KB article for details. Fixes included with Geneva Patch 7 * 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. Geneva Patch 7 Geneva Patch 6 Hot Fix 3 Geneva Patch 6 Hot Fix 2 The PRBs in GP6HF2 were also fixed in * GP7: PRB670075, PRB668555 GP7, GP8: PRB674257 Geneva Patch 6 Hot Fix 1 Geneva Patch 6 Geneva Patch 5 Hot Fix 6This release includes the GP5HF6 PRBs that were also fixed in GP7. * GP6, GP7: PRB670075 GP7: PRB671433 GP11: PRB681035 Geneva Patch 5 Hot Fix 5 Geneva Patch 5 Hot Fix 4 Geneva Patch 5 Hot Fix 1 Geneva Patch 5 Geneva Patch 4 Hot Fix 10 Geneva Patch 4 Hot Fix 7This release includes the GP4HF7 PRB that was fixed in GP7. * GP6: PRB665856, PRB666396 GP7: PRB654191 Geneva Patch 4 Hot Fix 6 Geneva Patch 4 Hot Fix 5 Geneva Patch 4 Geneva Patch 3 Hot Fix 9 Geneva Patch 3 Geneva Patch 1 Geneva fixes Note: The fix for PRB598926, which was originally fixed in the Geneva feature release, was reverted in Geneva Patch 7. This reversion only applies to Geneva releases, starting from Geneva Patch 7. Helsinki releases will still contain a fix for PRB598926.