service-client-api.accepted-web-content-origins
Section: interaction-workspace
Default Value: No default value
Valid Values: A comma-separated value list of URL or '*'
Changes Take Effect: After the next platform configuration refresh interval.
Introduced: 9.0.000.31
Specifies the list of granted origins and allowed APIs that are used in the web extension views. You can filter requested API with the following self-explanatory keywords:
- 'agent.get'
- 'agent.getStateList'
- 'agent.setState'
- 'agent.getState'
- 'interaction.getInteractions'
- 'interaction.getByInteractionId'
- 'interaction.getByBundleId'
- 'interaction.getByCaseId'
- 'interaction.setUserData'
- 'interaction.deleteUserData'
- 'system.closeToast'
- 'system.popupToast'
- 'system.updateToast'
- 'voice.dial'
- 'voice.startCallRecording'
- 'voice.stopCallRecording'
- 'voice.pauseCallRecording'
- 'voice.resumeCallRecording'
- 'email.create'.
For example, the value for of this option could now be: http://my-web-server0, http://my-web-server1 , http://my-web-server2 (agent.*, voice.dial), http://my-web-server3 (agent.*, interaction.*).
In this example, all requests are allowed for the http://my-web-server0 and http://my-web-server1 domains. For the http://my-web-server2 domain, only the following requests are allowed: 'agent.get', 'agent.getStateList', 'agent.setState', 'agent.getState', 'voice.dial'. For the http://my-web-server3 domain, only the following requests are allowed: - 'agent.get'
- 'agent.getStateList'
- 'agent.setState'
- 'agent.getState'
- 'interaction.getInteractions'
- 'interaction.getByInteractionId'
- 'interaction.getByBundleId'
- 'interaction.getByCaseId'
- 'interaction.setUserData'
- 'interaction.deleteUserData'.
In addition to filtering by origin, you can filter by API with a wildcard in parentheses after the allowed origin. This option cannot be overridden and must be set in the WS_Cluster application.
salesforce.message-channel.name
Section: crm-adapter
Default Value:
Valid Values: A string that contains the name of a message channel in Salesforce in the following format: NameSpacePrefix__ChannelName__c or ChannelName__c.
Changes Take Effect: When the session is started or restarted.
Introduced: 9.0.000.57
Specifies the name of a message channel in Salesforce for the Service Client API.
(Created page with "=Gplus Adapter support for Service Client API= {{AnchorDiv|SCAPI}} ==Support for Service Client API in Salesforce Lightning == Gplus Adapter supports the Documentation:HTCC:...") |
|||
Line 1: | Line 1: | ||
=Gplus Adapter support for Service Client API= | =Gplus Adapter support for Service Client API= | ||
+ | Gplus Adapter supports the Genesys Service Client API, which you can use for custom features. | ||
{{AnchorDiv|SCAPI}} | {{AnchorDiv|SCAPI}} | ||
==Support for Service Client API in Salesforce Lightning == | ==Support for Service Client API in Salesforce Lightning == |
Revision as of 19:47, April 21, 2021
Gplus Adapter support for Service Client API
Gplus Adapter supports the Genesys Service Client API, which you can use for custom features.
Support for Service Client API in Salesforce Lightning
Gplus Adapter supports the Service Client API, which you can use for custom features such as invoking click-to-email, starting or stopping a recording when a sensitive field is on the screen, and attaching data from Salesforce to Genesys key/value pairs. Complete the following steps in Salesforce Lightning:
- Deploy your Salesforce domain.
-
Create and deploy a message channel using Salesforce CLI or a third-party tool such as
Workbench. For example, here's a breakdown of the steps you must complete using Workbench:
- Create a folder called messagedeploy and add a new file called package.xml with the following contents:
<?xml version="1.0" encoding="UTF-8"?> <Package xmlns="http://soap.sforce.com/2006/04/metadata"> <types> <members>*</members> <name>LightningMessageChannel</name> </types> <version>47.0</version> </Package>
- In your messagedeploy folder, create a new folder called messageChannels and add a new file called GplusChannel.messageChannel with the following contents:
<?xml version="1.0" encoding="UTF-8"?> <LightningMessageChannel xmlns="http://soap.sforce.com/2006/04/metadata"> <masterLabel>GplusChannel</masterLabel> <isExposed>true</isExposed> <description>This Lightning Message Channel sends information from VF to LWC and back.</description> </LightningMessageChannel>
- Zip (compress) the messagedeploy folder.
- Navigate to https://workbench.developerforce.com/login.php and log in to Salesforce with the account you will use for the Service Client API.
- Open the migration menu, click Deploy and attach the zip you previously created.
- Open the info menu, click Metadata Types & Components and choose LightningMessageChannel - you created this in step 2-a.
- Create a folder called messagedeploy and add a new file called package.xml with the following contents:
- Download gplus-service-client-api.js from here and add it to your static resources in Salesforce.
- Download the SCAPI example from here.
- Create a Visualforce page in Salesforce that uses your new message channel (from step 2-b) and the Service Client API to implement your custom functionality.
- Add the Visualforce page to your dashboard.
Set the salesforce.message-channel.name option to the name of the message channel you created in step 2-b — for example, GplusChannel__c.
The value of the salesforce.message-channel.name option must be specified using one of the following formats:
- NameSpacePrefix_ChannelName__c
- ChannelName__c
You must use this format to confirm to the Salesforce Naming Conventions for Custom Fields.
In the interaction-workspace section of the Workspace configuration object, configure the following options:
- service-client-api.accepted-web-content-origins — Set the value to *
- service-client-api.allow-full-api — Set the value to true
Support for Service Client API in Salesforce Classic
Gplus Adapter supports the Service Client API, which you can use for custom features such as invoking click-to-email, starting or stopping a recording when a sensitive field is on the screen, and attaching data from Salesforce to Genesys key/value pairs. Complete the following steps in Salesforce Classic:
-
Download the SCAPI script from here.
-
Download the SCAPI example from here.
-
Add service-client-api-classic.js to your static resources in Salesforce.
-
Create a Visualforce page with SCAPI (according to the SCAPI example) or a custom console component.