Support sfdc-custom-cti instead of using Open CTI#877
Draft
dremin wants to merge 6 commits into
Draft
Conversation
|
0 ESLint error(s) and 0 ESLint warning(s) found in pull request changed files. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
When Salesforce removes Open CTI support, currently customers' options are to migrate to Service Cloud Voice (including its associated licensing cost), or re-implement all of their custom plugins using the Flex SDK within Lightning Web Components. This PR adds a third option: when paired with https://github.com/twilio-professional-services/sfdc-custom-cti this allows the existing Flex UI, including plugins and Salesforce integration, to be embedded within Salesforce with the integration features you would expect--screen pop, click-to-dial, activity logging, utility bar customization, etc. This delivers essentially the same agent experience that Open CTI offers.
This PR introduces a shim class that is loaded within the
window.sforceglobal. This allows existing plugin code that uses Open CTI functions to continue to work normally in a Open CTI-free world. It is enabled using the newcustom_cticonfiguration option, which is disabled by default.The full Open CTI API has not been implemented, but most of it has been, including what we typically see in customer implementations.
Checklist