Jump to: navigation, search

salesforce.debug-notifications

Section: crm-adapter
Default Value: false
Valid Values: true, false
Changes Take Effect: When the session is started or restarted.


Specifies whether Gplus Adapter displays all notifications (positive and negative).

Line 20: Line 20:
 
To configure troubleshooting and confirmation notifications, in the '''Agent Annex''' or '''Agent Group Annex''', create the {{Optionslink|link=Options:Genesys_Web_Services:crm-adapter:salesforce-debug-notifications}} key in the '''crm-adapter''' section and set the value to '''true'''.
 
To configure troubleshooting and confirmation notifications, in the '''Agent Annex''' or '''Agent Group Annex''', create the {{Optionslink|link=Options:Genesys_Web_Services:crm-adapter:salesforce-debug-notifications}} key in the '''crm-adapter''' section and set the value to '''true'''.
  
−
{{AnchorDiv|BrowserLogs}}
+
{{AnchorDiv|BrowserLog}}
 +
==Gplus information in browser log==
 +
For troubleshooting purposes, Gplus Adapter writes the list of all agent level '''crm-adapter''' option settings to the browser log.
  
−
{{NoteFormat|For troubleshooting purposes, Gplus Adapter writes the list of all agent level crm-adapter option settings to the browser log.|2}}
+
Gplus Adapter also automatically writes messages to the browser log when Screen Pop events are successful or unsuccessful, showing all the search results that Gplus found in the interaction media type, the interaction userData, and the Salesforce records database. The messages helps you to identify the root cause when a Screen Pop is unsuccessful.
−
<!--
 
−
{{Chgbar_open}}
 
−
==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:
+
To find the Screen Pop browser log message, search the log for the following string: '''Screen Pop processing'''
  
−
{{{!}} class="wikitable"
+
The following is an example of a browser log message for a successful 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
+
<source lang="text">
 +
2022-08-16 14:04:41.230 [DEBUG] [WWE.Main.Application] Screen Pop processing:
 +
ANI = 647401
 +
KVP matching cti_ found in interaction userData:
 +
cti_LastName = Willard
  
−
Option RegEx to Match UserData is set to ^cti_
+
Salesforce search returned 1 record:
−
 
+
Type: Contact
−
KVP matching ^cti_ found in userData: or  KVP matching ^cti_ not found in userData:
+
Name: Willard Clinton
−
 
+
</source>
−
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"
 
−
{{!}}-
 
−
{{!}} colspan="1"{{!}}object id don't exist search return empty result
 
−
{{!}} colspan="1"{{!}}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
 
−
{{!}}-
 
−
{{!}} colspan="1"{{!}}object id don't exist search return error
 
−
{{!}} colspan="1"{{!}}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.
 
−
{{!}}-
 
−
{{!}} colspan="1"{{!}}object id don't exist search query is empty
 
−
{{!}} colspan="1"{{!}}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
 
−
{{!}}}
 
−
{{Chgbar_close}}
 
−
-->
 
 
<!--
 
<!--
 
==Browser console logs==
 
==Browser console logs==

Revision as of 17:58, August 22, 2022

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.

    GAPI 900 Gplus Field Mismatch Error.png

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

    GAPI 900 Gplus Type Mismatch Error.png

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

    GAPI 900 Gplus Object Doesnt Match Error.png

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.

Gplus information in browser log

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

Gplus Adapter also automatically writes messages to the browser log when Screen Pop events are successful or unsuccessful, showing all the search results that Gplus found in the interaction media type, the interaction userData, and the Salesforce records database. The messages helps you to identify the root cause when a Screen Pop is unsuccessful.

To find the Screen Pop browser log message, search the log for the following string: Screen Pop processing

The following is an example of a browser log message for a successful Screen Pop: 

2022-08-16 14:04:41.230 [DEBUG] [WWE.Main.Application] Screen Pop processing:
ANI = 647401
KVP matching cti_ found in interaction userData:
cti_LastName = Willard

Salesforce search returned 1 record:
Type: Contact
Name: Willard Clinton
Comments or questions about this documentation? Contact us for support!