-
Notifications
You must be signed in to change notification settings - Fork 1
[FIX] Fix escalation block on quick chat establish #52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
[FIX] Fix escalation block on quick chat establish #52
Conversation
|
@Shailesh351 have a look please. |
| let salesforceAgentName; | ||
| for (const msg of messageArray) { | ||
| if (msg.message.name) { | ||
| salesforceAgentName = msg.message.name; | ||
| } | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are also accessing chasitorIdleTimeout and sneakPeekEnabled from the chatEstablishedMessage. Shouldn't we also add those?
| if ((Object.keys(res).length === 0 || res !== 'undefined') && response.content === '{}') { | ||
| response = res; | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why response = res; when Object.keys(res).length === 0?
Shailesh351
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When I tried this locally, SF Agent Name is not showing up in Livechat Widget
|
@AlexanderKanakis are there any RC logging associated with this crash you are describing? |
This fix makes sure that we retain the response from Salesforce when the Salesforce agent accepts a visitor in the short time between connecting to Salesforce and looking for an agent