The following page provides a comprehensive overview of the current integration files associated with each supported CTI Adapter. In addition to listing these files, it includes detailed version change logs that outline the updates, modifications, and improvements made to each adapter over time.
This resource is designed to help users track changes, understand the evolution of the CTI Adapters, and ensure they are using the most up-to-date integration files for optimal performance and compatibility.
This change addresses a bug that resulted in the addition of the incorrect `WhoId` and `WhatId` to the data payload when creating a task record. This incorrect data was subsequently corrected in updated on call hangup and wrap however the side-affect was that an event was incorrectly recorded in some record feeds if the call related to a Case record. In addition this change includes improved log handling.
Addressed a bug that stops a new entity (contact) being created when the screen pop search is unable to find a match and addNewRecordis set to true in the config. With the fix in place, if the search query does not return a response, a new record will be created and a form will open to allow the agent to fill in the details. This new record will then be recorded against the call record.
Added useSearchSpread option to the config. When set to true, restores the CTI v7 seach and pop behaviour of sending the phone number in more than one format as a search query to Salesforce when handling inbound calls. For example the query string will look like: 0298980000 OR +61298980000.
Changed:
Includes a bug fix to address issues with Autowrap that causes two events to fire resulting in the automated wrap failing.
Lifecycle queue - utilise the queue to allow lifecycle events to cycle completely before the next event. Address the issue where hangup is overwritten by wrap and where calls in queue collide with calls in wrap.
Event handling when CTI is open on multiple tabs. This change stops call screen pop happening on all browser tabs. The screen pop interaction will only happen on the last tab to have focus or if the CTI is visible in two side-by-side windows, in this case they will both receive the screen pop event as they are both visible.
Changed:
Fixed an issue where the related fields were not being populated correctly after a page refresh.
Lifecycle queue - utilise the queue to allow lifecycle events to cycle completely before the next event. Address the issue where hangup is overwritten by wrap and where calls in queue collide with calls in wrap.
Event handling when CTI is open on multiple tabs. This change stops call screen pop happening on all browser tabs. The screen pop interaction will only happen on the last tab to have focus or if the CTI is visible in two side-by-side windows, in this case they will both receive the screen pop event as they are both visible.
Changed:
Fixed an issue where the related fields were not being populated correctly after a page refresh.
Changed the sequence of events so if you happen to “map” a mandatory field, your mapping will overwrite that field. So, for example you could overwrite the “subject” line by creating a data map entry for that if you wished.
Changes in searchAndScreenPop: No longer formatting a query based on phone number types. Search parameter taken directly from the screenPop configuration item. Recommend if using phone should set formatting to national for more reliable search & pop.
Changed the sequence of events so if you happen to “map” a mandatory field, your mapping will overwrite that field. So, for example you could overwrite the “subject” line by creating a data map entry for that if you wished.
Changes in searchAndScreenPop: No longer formatting a query based on phone number types. Search parameter taken directly from the screenPop configuration item. Recommend if using phone should set formatting to national for more reliable search & pop.
Changed the sequence of events so if you happen to “map” a mandatory field, your mapping will overwrite that field. So, for example you could overwrite the “subject” line by creating a data map entry for that if you wished.
