Difference between revisions of "PEC-GPA/Current/Administrator/GplusTroubleshoot90"
From Genesys Documentation
(Published) |
(Published) |
||
| Line 8: | Line 8: | ||
|Section={{Section | |Section={{Section | ||
|sectionHeading=Expanded troubleshooting notifications | |sectionHeading=Expanded troubleshooting notifications | ||
| − | |anchor=Notifications | + | |alignment=Vertical |
| + | |structuredtext=To configure troubleshooting and confirmation notifications, in the '''{{Link-AnywhereElse|product=PEC-AS|version=Current|manual=ManageCC|topic=Agent_Annex|anchor=AgentAnnex|display text=Agent Annex}}''' or '''{{Link-AnywhereElse|product=PEC-AS|version=Current|manual=ManageCC|topic=Agent_Annex|anchor=AgentGroupAnnex|display text=Agent Group Annex}}''', create the '''salesforce.debug-notifications''' key in the '''crm-adapter''' section and set the value to '''true'''. | ||
| + | |Status=No | ||
| + | }}{{Section | ||
| + | |sectionHeading=Salesforce Client API saveLog() method error Notifications | ||
| + | |anchor=saveLogNotifications | ||
|alignment=Vertical | |alignment=Vertical | ||
|structuredtext=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 the interaction data matches your Salesforce configuration. | |structuredtext=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 the interaction data matches your Salesforce configuration. | ||
The following are examples of Salesforce error notifications when the Salesforce '''saveLog()''' method is called: <ul> | The following are examples of Salesforce error notifications when the Salesforce '''saveLog()''' method is called: <ul> | ||
| − | <li><p>Mismatch between the name of the field in custom field mapping and Salesforce field label for Activity object.</p> | + | <li><p>Mismatch between the name of the field in {{Link-SomewhereInThisVersion|manual=Administrator|topic=GplusActivityHistory90|anchor=Mapping|display text=custom field mapping}} and Salesforce field label for Activity object.</p> |
[[File:GAPI_900_Gplus_Field_Mismatch_Error.png|400px]] | [[File:GAPI_900_Gplus_Field_Mismatch_Error.png|400px]] | ||
</li> | </li> | ||
| Line 23: | Line 28: | ||
</li> | </li> | ||
</ul> | </ul> | ||
| − | + | |Status=No | |
| + | }}{{Section | ||
| + | |sectionHeading=Screen Pop Notifications | ||
| + | |anchor=ScreenPopNotifications | ||
| + | |alignment=Vertical | ||
| + | |structuredtext=To troubleshoot successful and failed screen pop record search, Gplus Adapter can display notifications informing you of why the Salesforce record was not found for screen pop. | ||
| + | |||
| + | The following are examples of Salesforce error notifications when the Salesforce records are searched for screen pop: | ||
| + | |||
| + | <ul> | ||
| + | <li><p>Screen pop by id where record search is by object id.</p> | ||
| + | <p>Record found and screen pop successful:</p> | ||
| + | [[File:xx.png|400px]] | ||
| + | <p>Incorrect record found but screen pop successful:</p> | ||
| + | [[File:xx.png|400px]] | ||
| + | <p>Record not found and screen pop unsuccessful:</p> | ||
| + | [[File:xx.png|400px]] | ||
| + | </li> | ||
| + | <li><p>Screen pop by record search is by query.</p> | ||
| + | <p>Record found and screen pop successful:</p> | ||
| + | [[File:xx.png|400px]] | ||
| + | <p>Record not found and screen pop unsuccessful:</p> | ||
| + | [[File:xx.png|400px]] | ||
| + | </li> | ||
| + | <li><p>Create new record and screen pop.</p> | ||
| + | <p>Record created and screen pop successful:</p> | ||
| + | [[File:xx.png|400px]] | ||
| + | <p>Record not created and screen pop unsuccessful:</p> | ||
| + | [[File:xx.png|400px]] | ||
| + | </li> | ||
| + | </ul> | ||
| + | |Status=Yes | ||
| + | }}{{Section | ||
| + | |anchor=BrowserLogs | ||
| + | |alignment=Vertical | ||
| + | |structuredtext={{NoteFormat|For troubleshooting purposes, Gplus Adapter writes the list of all agent level crm-adapter option settings to the browser log.|2}} | ||
|Status=No | |Status=No | ||
}} | }} | ||
}} | }} | ||
Revision as of 16:43, February 11, 2022
This topic is part of the manual Gplus Adapter for Salesforce Administrator's Guide for version Current of Gplus Adapter for Salesforce.
Contents
If you are having issues with Gplus Adapter integration with Salesforce, you can try some of these solutions.
Related documentation:
Expanded troubleshooting notifications
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.
Salesforce Client API saveLog() method error 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 the 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.
Tip
For troubleshooting purposes, Gplus Adapter writes the list of all agent level crm-adapter option settings to the browser log.Comments or questions about this documentation? Contact us for support!