This Genesys Cloud for Salesforce integration is driving me absolutely insane! I am trying to map the final recognized intent and the specific slot variables from our Dialog Engine Bot Flow directly into a custom Salesforce Task object when the interaction routes to an agent. I created the Participant Data variables in the Architect flow exactly as the documentation says. The variables show up in the Genesys Cloud interaction details, but they are completely missing from the Salesforce softphone screen, and the Task record is never updated! Does the managed package simply not support complex string payloads from bot flows, or am I missing some hidden configuration setting in the Salesforce Call Center XML file?
Greetings! I understand your frustration entirely! We experienced a very similar challenge when attempting to map patient verification slots from our healthcare bot into Salesforce Health Cloud. The managed package absolutely supports these variables, but there is a crucial mapping step that is easily overlooked. First, you must ensure your variable in Architect uses the exact prefix SF_ or Salesforce_ depending on your managed package version.
More importantly, you must go into Salesforce Setup, navigate to the Custom Settings, and configure the ‘Genesys Cloud Interaction Attributes Mapping’. You must manually type the exact Architect variable name there and link it to the specific Salesforce Task field API name.
It does not synchronize automatically!
It is completely ridiculous that we have to manually map these in three different places! I spent days troubleshooting this exact issue for our patient portal bot. Just a warning regarding the string payloads: Salesforce imposes a strict 255-character limit on standard text fields. If your bot flow captures a long user utterance in a slot and you try to pass it to a standard Salesforce field, the entire managed package data sync will silently fail! You will not see an error in the softphone! You absolutely must truncate the string in your Architect flow using the Left() expression before you assign it to the Participant Data variable, or map it to a Long Text Area field in Salesforce!