Skip to main content
Skip table of contents

ipSCAPE CTI Integration Change Log

Overview

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.

For information about improvements or bug fixes for the CTI Adapter see our Release Notes: https://knowledgehub.ipscape.com/Workspace/ipSCAPE-Release-Notes.1639710770.html


1. Current Versions


2. Change Log

11/09/2024

Integration: MsDynamics

Version: 1.0.6

https://developer.onipscape.com/integrations/8.19/dynamics/ips-dynamics-integration.v1.0.6.min.js

Added:

  • Nothing added.

Changed:

  • Refined the handling of multiple tabs

  • Improved the reliability of related objects handling.

Removed:

  • Removed the lifecycle queue solution introduced in the previous version as it was proving problematic in some browsers.

11/09/2024

Integration: Salesforce

Version: 1.0.5

https://developer.onipscape.com/integrations/8.19/salesforce/ips-sf-integration.v1.0.5.min.js

Added:

  • Nothing added.

Changed:

  • Refined the handling of multiple tabs

  • Improved the reliability of related objects handling.

Removed:

  • Removed the lifecycle queue solution introduced in the previous version as it was proving problematic in some browsers.

20/08/2024

Integration: MsDynamics

Version: 1.0.5

https://developer.onipscape.com/integrations/8.19/dynamics/ips-dynamics-integration.v1.0.5.min.js

Added:

  • 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.

Removed:

  • Nothing Removed

20/08/2024

Integration: Salesforce

Version: 1.0.4

https://developer.onipscape.com/integrations/8.19/salesforce/ips-sf-integration.v1.0.4.min.js

Added:

  • 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.

Removed:

  • Nothing Removed

10/07/2024

Integration: Zendesk

Version: 1.0.3

https://developer.onipscape.com/integrations/8.19/zendesk/ips-zd-integration.v1.0.3.min.js

Added:

  • onCallFailed handler - failed calls should trigger call-hangup

  • onOpenInteraction handler - opening a recovered interaction should find existing ticket

Changed:

  • Addressed the end of call data reliability. This includes wrap code, durations, etc. 

     To this end we have added a few fields into the call data that you can map from. This includes:

    • callDurationInSeconds: interaction.activity.callDurationInSeconds

    • callDurationInMinutes: interaction.activity.callDurationInMinutes

    • callDisposition object that contains:

      • description: interaction.wrapData.callDisposition.description

      • statusCode: interaction.wrapData.callDisposition.statusCode

  •  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.

Removed:

  • Nothing Removed

8/07/2024

Integration: Salesforce

Version: 1.0.3

https://developer.onipscape.com/integrations/8.19/salesforce/ips-sf-integration.v1.0.3.min.js

Added:

  • Nothing Added

Changed:

  • Addressed the end of call data reliability. This includes wrap code, durations, etc. 

     To this end we have added a few fields into the call data that you can map from. This includes:

    • callDurationInSeconds: interaction.activity.callDurationInSeconds

    • callDurationInMinutes: interaction.activity.callDurationInMinutes

    • callDisposition object that contains:

      • description: interaction.wrapData.callDisposition.description

      • statusCode: interaction.wrapData.callDisposition.statusCode

  •  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.

Removed:

  • Nothing Removed

3/07/2024

Integration: MsDynamics

Version: 1.0.4

https://developer.onipscape.com/integrations/8.19/dynamics/ips-dynamics-integration.v1.0.4.min.js

Added:

  • Nothing Added

Changed:

  • Addressed the end of call data reliability. This includes wrap code, durations, etc. 

     To this end we have added a few fields into the call data that you can map from. This includes:

    • callDurationInSeconds: interaction.activity.callDurationInSeconds

    • callDurationInMinutes: interaction.activity.callDurationInMinutes

    • callDisposition object that contains:

      • description: interaction.wrapData.callDisposition.description

      • statusCode: interaction.wrapData.callDisposition.statusCode

     

    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.

Removed:

  • Nothing Removed

20/06/2024

Integration: MsDynamics

Version: 1.0.3

https://developer.onipscape.com/integrations/8.19/dynamics/ips-dynamics-integration.v1.0.3.min.js

Added:

  • Nothing Added

Changed:

  • Updated SDK to v1.0.8

Removed:

  • Nothing Removed

20/06/2024

Integration: Salesforce

Version: 1.0.2

https://developer.onipscape.com/integrations/8.19/salesforce/ips-sf-integration.v1.0.2.min.js

Added:

  • Nothing Added

Changed:

  • Updated SDK to v1.0.8

  • Fixed issue where related items not cleared from previous interaction

Removed:

  • Nothing Removed

20/06/2024

Integration: Service Now

Version: 1.0.3

https://developer.onipscape.com/integrations/8.19/servicenow/ips-snow-integration.v1.0.3.min.js

Added:

  • Nothing Added

Changed:

  • Updated SDK to v1.0.8

Removed:

  • Nothing Removed

20/06/2024

Integration: Zendesk

Version: 1.0.2

https://developer.onipscape.com/integrations/8.19/zendesk/ips-zd-integration.v1.0.2.min.js

Added:

  • Nothing Added

Changed:

  • Updated SDK to v1.0.8

Removed:

  • Nothing Removed

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.