RELEASE NOTES. December 3, To sign up for Release Notes notifications, please go to:

Transcription

1 RELEASE NOTES 7.9 CIMplicity TM Desktop Web Client December 3, 2015 CIMplicity Desktop Web Client The current release for CIMplicity Desktop is 7.9. To sign up for Release Notes notifications, please go to: Announcements CIMplicity 7.9 will be the last version that supports.net 4.0. The following version will require.net CIMplicity 7.9 does not support Window Server CIMplicity 7.9 does not support Internet Explorer 8. CIMplicity 7.9 will be the last version that supports Internet Explorer 9. Release Fixes CIMplicity Desktop Web Client 7.9 includes the following fixes: Agent Presence: Occasionally, the agent presence tab did not redraw correctly. Currently, the tab redraws correctly (EOS-3373) Core: Since CIMplicity no longer uses reason codes set up as Business Attribute, an unnecessary message appeared in the logs (about a Not Ready Reason group not found). The unnecessary log statement was removed. (EOS- 3210) Core: If no agent signed in for an hour, and an agent refreshed, an error displayed regarding Contact books. Currently, the error does not occur. (EOS- 3436) Core: After closing the CIMplicity browser tab in Internet Explorer 11, and the status bar message changes to not ready, the status bar became green for ready anyways. The status bar no longer appears green on not ready. (EOS- 3508) Core::After triggering Interaction Tasks to pop a screen pop with phone controls, and clicking Mark Done, the error log displayed an error. The error no longer occurs. (EOS-3546) Core: Custom links were causing the entire CIMplicity window to navigate to the link, instead of popping into a frame within CIMplicity (or into a new window). This was fixed. (EOS-3518)

2 Core: After triggering Interaction Tasks on interaction completed, sometimes non-existent interactions appeared in the Interactions dropdown. The unknown interactions no longer display. (EOS-3451) Core: After clicking Mark Done, onstatechanged event may happen before Mark Done is done processing. This caused an error that an object is null or undefined. Currently, the error does not occur. (EOS-3457) Core: If the application tried to pop a new interaction with phone controls in a new window, the screenpop did not display (and it only displayed the Home button). The incorrect screenpop no longer appears. (EOS-3444) Core: Items could not be deleted from the Tree Selector (Multi-Select) and were not visible when row span was set to 1 in the field layout. Currently, items can be deleted and are visible when row span is set to 1. (EOS-3383) Core: When acw-manual-in was set to true in the Configuration Editor, the agent was being set to AuxWork when selecting 'After Call Work' from the 'Go Not Ready' dropdown. This has been changed to set the agent to AfterCallWork. (EOS-3525) Extension: When using very large font sizes in the body, the text from different lines overlapped. This occurred in all versions of Internet Explorer and Chrome. The overlap no longer appears, due to upgrading the web text editor (CKeditor) to (EOS-3215) Extension: When an agent (using Internet Explorer) received a transferred outbound , a editor.setreadonly failed error occurred in the error log file. Consequently, the editor buttons were not disabled. The error no longer occurs. (EOS-3226) Extension: After saving s in the workbin, they did not display edited and updated subjects. Currently, the s display the updated subjects. (EOS- 3337) Extension: When an agent received an with html and formatting, and is replying and viewing the in the editor, all styles and formats disappeared (such as colors, styles, etc). The outbound s currently retain the previously incoming format. (EOS-3492) Extension: After clicking the Down key (in the text editor window where the browser height is shorter than the text editor window height), the user interface did not render and display correctly. The Down key no longer causes a display error. (EOS-3434) Extension: Hitting the enter key (in an text editor window where the browser height is shorter than the text editor window height) caused a rendering issue. The rendering issue no longer occurs. (EOS-3336) Outbound Campaign: Outbound Custom fields did not update properly, while using interaction.attacheddata as the data source. Currently, the fields update correctly. (EOS-3448)

3 Javascript API: After performing a new interaction task with a screen pop for a new window (with phone controls), the API test page suffered from a race condition causing a loss of functionality. This issue no longer occurs. (EOS-3510) Javascript API: After performing an Interaction task with a target new window (with phone controls), it did not show the softphone in new window. Currrently, the softphone does display. Also,the Transfer/Conference/Consult dialogs did not render correctly in the new popped window in IE9. Currently, they render properly. (EOS-3517) Salesforce Extension: In SalesCloud, the softphone link does not work after auto-popping CIMplicity and refreshing. Currently, the link does work. (EOS- 3440) Salesforce Extension: Salesforce targets are available from Agents Tasks. See Add a New Agent Task in the Configuration Editor guide for more information on configuration. (EOS-3309) Salesforce Extension: Standard responses were not inserted into chats and s in the Salesforce Service Cloud Console. Currently, the standard responses can be inserted. (EOS-3500) UCS History: UCS History: Depending on the source, sometimes previously sent s displayed the current time, instead of the initial time they were sent. The s currently display the correct time. (EOS-3378) UCS History: Selecting Click-to-Dial configuration in an interaction task (in Internet Explorer 11) caused an error in the logs. The error no longer occurs. (EOS-3454) UCS History: When an agent viewed UCS Voice history in CIMplicity and they were in a different time zone than the Genesys server, the timestamps were different. Currently, the timestamp displays correctly. (EOS-3432) Release Improvements CIMplicity Desktop Web Client 7.9 includes the following improvements: Contact Books: When an agent opens up the contact book, the agent can view an associated statistic. See Contact Books: Add Statistics to an Contact Book, and See Chat Contact Books: Add Statistics to a Chat Contact Book, and see Phone Contact Books: Add Statistics to a Phone Contact Book in the Configuration Editor guide. (EOS-3258) Core: The option layout/stable-not-ready-reason-dock is deprecated, and replaced with layout/statebar-status-text-dock option. See Options Section:layout in the Configuration Editor guide. (EOS-3392)

4 Core: Current release features improved logging for Manual Tasks. (EOS-3536) Core: The softphone has an on call indicator, which is configurable from the Configuration Editor. The indicator will appear after the call is answered. See Options Section: Softphone and Configure Softphone Options in the Configuration Editor guide. (EOS-3392) Core: Configuration Editor erroneously displayed the Condition field for Manual Tasks. Currently, the Condition field in Manuals tasks is disabled and does not display (EOS-3472) Configuration Editor: Administrators can create a workflow custom task to configure a list of custom tasks. See Custom Tasks: Manual Tasks: Create Workflow in the Configuration Editor. (EOS-3509) Extension: CIMplicity Desktop is compatible with Salesforce Winter 16. (EOS-3482) Extension: The CK Editor was updated from CKEditor version to version (EOS-3257) Salesforce Extension: Updated or created salesforce records will pop, after creating a custom task to trigger the creation or update. See Create or Update Record-CTI in the Configuration Editor guide. (EOS-3302) UCS History: UCS History (versions of UCS greater than ) writes inbound and outbound interactions to UCS. (EOS-3273) UCS History: When an interaction is sent, the SentDate and header date are updated in UCS History. The header date displays the timestamp. In the case of a hmail server, it will override the SentDate of the interaction. (EOS-3487) UCS History: UCS History: Administration can disable or enable writing to UCS History. See Options Section: ucs-history in the Configuration Editor guide. Release Known Issues CIMplicity Desktop Web Client includes the following known issues: Configuration Editor: The use of the + key, tab, page down and down arrow keys may cause an error in some scenarios. (EOS-3293) Core: If Auto Answer is enabled, the Accept and Reject buttons may appear incorrectly, or the buttons may be selectable for an instant before the interaction is auto answered.(eos-2806) Core: The.NET framework cannot be updated to 4.6. The 4.6 version will causes in an error in any operating system. Some HTML elements, attributes and styles may not render or function correctly in the body text window. (EOS-3260) After saving an with attachments, the attachment checkboxes may not be greyed out as expected. (EOS-3335) If any agent presses the Enter key in the text editor (with browser height shorter than the text editor), it causes a rendering issue. (EOS- 3336) Salesforce Extension: When running CIMplicity (in Internet Explorer 11 as an administrator) in the Salesforce Sales Cloud, an additional blank window is created on softphone initialization. (EOS-3381)

5 Salesforce Extension: If unsecured resources (HTTP) are loaded with an (or through an s custom fields inside of Salesforce) Salesforce can throw an unsecured resource exception, which causes a loss of functionality with CKEditor. This applies to Internet Explorer 9, 10, and 11. (EOS-3515)