Troubleshooting Gplus Adapter Integration with Salesforce

If you are having issues with Gplus Adapter integration with Salesforce, you can try some of these solutions.

Expanded troubleshooting notifications

To troubleshoot Salesforce Client API saveLog() method errors, Gplus Adapter can display notifications. To fix saveLog() method errors, validate your Salesforce configuration, and ensure that interaction data matches your Salesforce configuration.

The following are examples of Salesforce error notifications when the Salesforce saveLog() method is called:

• Mismatch between the name of the field in custom field mapping and Salesforce field label for Activity object.

  

• When interaction userData type does not match Salesforce object custom field data type.

  

• When Salesforce Object validation rule formula results in an error.

  

To configure troubleshooting and confirmation notifications, in the Agent Annex or Agent Group Annex, create the salesforce.debug-notifications key in the crm-adapter section and set the value to true.

Tip

For troubleshooting purposes, Gplus Adapter writes the list of all agent level crm-adapter option settings to the browser log.

Expanded messaging for troubleshooting Screen Pop

To make it easier for you to troubleshoot the Screen Pop process, Gplus Adapter accumulates messages in the browser log. The messages log the record search process and record the Agent Setup Screen Pop option settings. They indicate whether or not the search was successful and what data was used to find the record.

The following are examples of the messages that Gplus Adapter writes in the browser when the Salesforce records are searched for screen pop:

scenario	Message
object id exist in salesforce	id_ is found in userData and sent to Salesforce
object id don't exist in salesforce	id_ is found in userData and sent to Salesforce
(no. need for this case)object id not correct (not string)	id_ is found in userData and sent to Salesforce Something went wrong in screenPop ! Errors= An invalid value was passed to the parameter recor…han 0 was expected, but object was found instead.
	Option Use ANI in Screen Pop Search is enabled Option Use DNIS in Screen Pop Search is disabled Option RegEx to Match UserData is set to ^cti_ KVP matching ^cti_ found in userData: or  KVP matching ^cti_ not found in userData: keyname1 = keyvalue1 Salesforce search returned (number) record(s): Type: "Contact" Name: "Willard Clinton400"
object id don't exist search return multiple	Option Use ANI in Screen Pop Search is enabled Option Use DNIS in Screen Pop Search is disabled Option RegEx to Match UserData is set to ^cti_ KVP matching ^cti_ found in userData: or  KVP matching ^cti_ not found in userData: keyname1 = keyvalue1 Salesforce search returned (number) record(s): Type: "Contact" Name: "Willard Clinton400" Type: "Contact2" Name: "Willard Clinton4001"
object id don't exist search return empty result	Option Use ANI in Screen Pop Search is enabled Option Use DNIS in Screen Pop Search is disabled Option RegEx to Match UserData is set to ^cti_ KVP matching ^cti_ found in userData: or  KVP matching ^cti_ not found in userData: keyname1 = keyvalue1 Response is empty
object id don't exist search return error	Option Use ANI in Screen Pop Search is enabled Option Use DNIS in Screen Pop Search is disabled Option RegEx to Match UserData is set to ^cti_ KVP matching ^cti_ found in userData: or  KVP matching ^cti_ not found in userData: keyname1 = keyvalue1 Response Error: An invalid value was passed to the parameter recor…han 0 was expected, but object was found instead.
object id don't exist search query is empty	Option Use ANI in Screen Pop Search is enabled Option Use DNIS in Screen Pop Search is disabled Option RegEx to Match UserData is set to ^cti_ KVP matching ^cti_ not found in userData: Search query is empty, operation braced