(Created page with "=Troubleshooting Gplus Adapter Integration with Salesforce= If you are having issues with Gplus Adapter integration with Salesforce, you can try some of these solutions. ==E...") |
|||
| Line 17: | Line 17: | ||
</li> | </li> | ||
</ul> | </ul> | ||
| − | To enable this feature, you can configure notifications by using the ''' | + | To enable this feature, you can configure notifications by using the '''salesforce.notifications''' option on a test Agent object or test Agent Group object in GAX. |
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'''. | 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'''. | ||
[[Category:V:HTCC:9.0.0DRAFT]] | [[Category:V:HTCC:9.0.0DRAFT]] | ||
Revision as of 16:00, December 7, 2020
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.
The following are examples of Salesforce error notifications when the Salesforce saveLog() method is called:
The field does not exist in Salesforce object.
When interaction userData type does not match Salesforce object custom field data type.
Salesforce validation rule for the Task object does not match the expected result.
To enable this feature, you can configure notifications by using the salesforce.notifications option on a test Agent object or test Agent Group object in GAX.
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.