Skip to main content
Argomenti#Embedded Service Deployment

#Embedded Service Deployment2 utenti parlano di questo argomento

Fai una domanda...
Seema Borse (TCS)
27 ott, 03:56
MIAW / Enhanced Chat fails to load in French (Blank Screen) when browser language is ā frā 

Hi everyone, 

We are experiencing a critical issue with our Messaging for In-App and Web (MIAW) / Embedded Service Deployment failing to load specifically when the user's browser language is set to French (ā frā  / ā fr-CAā ). 

Everything functions perfectly when tested in English browser (both English and French User). However, when switching the browser language to French, the chat window fails to mount the pre-chat form, leading to a blank screen with no specific error in console both for English and French User. 

 

Native Setup Test Window Reproduction: This issue reproduces out-of-the-box inside the native Salesforce Setup Test Window when the browser language is changed to French. This confirms the defect is independent of our custom Visualforce page or custom code.  

 

 Configurations Already Verified & Implemented: 

 1. Embedded Service Deployment Settings: French (ā frā  / ā fr-CAā ) is explicitly added, active, and published under the deployment settings. 

 2. Experience Cloud / Site Languages: French is enabled and active under Digital Experience Site Settings, and the site has been fully Published. 

 3. Custom Labels & Translation Workbench: All standard and custom pre-chat form field labels, button text, and instructions have active, fully mapped French translations saved. 

 4. Code Snippet Locale Mapping: Dynamic language mapping (ā embeddedservice_bootstrap.settings.language = userLang;ā ) and ā useHostSiteLanguage = trueā  have been verified. 

 5. Testing Variations: We have tested toggling pre-chat forms on/off and forcing deployment republishes without resolution. 

 

Has anyone encountered this specific CDN package / localized component initialization crash for non-English locales in Enhanced Chat? Any insights on backend CDN bundle compilation or missing metadata flags for ā frā  locales would be greatly appreciated! 

 

Thanks in advance for your help!  

 

#Embedded Service Deployment 

Scrivi una risposta...
0/9000
Seema Borse (TCS)
29 ago, 05:50
Embedded service deployment - Deployment from one org to other

Hello Folks, 

I have created whole chat application using embedded service deployment in Salesforce. My chat window will be in salesforce only to another app user. My application is working perfect in my dev org. While deployment from Dev to QA - I am totally stuck, getting 

site.com

 issue everywhere. I couldn't deploy embedded service deployment from one org to other - I tried with Git, workbench and Changeset everywhere it's failing with site is not found or can not be created error. Is there anyone who faced the same and able to solve?  

Thanks, 

Seema. 

 

#Embedded Service Deployment  #Embedded Service

1 risposta
  1. Himanshu Shekhar (AQBEE Innovations Pvt. Ltd.)
    31 ago, 14:40

    Hi Seema, this is expected. An Embedded Service Deployment always points to a Site endpoint, and Sites (Force.com

    or Experience) do not migrate through change sets or the Metadata API, so in QA the deployment references a Site that does not exist, hence site not found or cannot be created. 

     

    Fix, in order: 

    1. In QA, create and ACTIVATE the Site first (Setup, Sites, or the Experience site if Dev uses one) so QA has its own site domain. 

    2. Re-add your CSP Trusted Sites and CORS allowlist entries for the host page domain, or the widget loads but stays blocked. 

    3. Then deploy the Embedded Service Deployment plus its supporting metadata (chat or messaging config, flows, fields) pointing at that QA Site. 

    4. Do not reuse the Dev code snippet on the page, it hard-codes Dev org URLs. Copy the fresh snippet Salesforce generates for the QA deployment. 

     

    The Site is org-specific, so it can never come across in the change set itself. You build and activate it in the target org first, then layer the deployment on top. 

     

    If this helps, please mark it as the Best Answer so it helps the next person, thanks šŸ™‚

Scrivi una risposta...
0/9000
Megan Johnson (Salesforce Consultant presso InspireAI) ha fatto una domanda in #Agentforce
19 ago, 12:05
Customising an Agent Chat Window

Hi Everyone :)  

 

Is there a way to add a fixed 'banner' to an embedded service deployment so that there's a constant disclaimer on the chat? Similar to the 'Powered by Agentforce' but customised text? 

 

#Agentforce  #Embedded Service Deployment  #LWC  #Trailhead  #Help

2 risposte
  1. Kundan Kumar Jha (Infosys Limited)
    19 ago, 16:58

    Hey Megan, 

     

    Adding one thing to Himanshu's answer since it's mostly right but slightly understates option 2: Salesforce actually has a fully supported LWC-based header customization for Messaging (lightningSnapin__MessagingHeader target), you extend the base chat header component and can add whatever fixed text/markup you want inside it. This is documented and stays visible for the whole conversation, unlike the greeting-message approach, which scrolls away. 

     

    So realistically you have two solid, supported paths: 

    1. Custom LWC header (extends BaseChatHeader/MessagingHeader), gives you a persistent banner area inside the actual chat window that Salesforce won't overwrite on releases, since it's a supported customization point, not DOM hacking 

    2. A banner on your host page around the widget (Himanshu's option 1), simplest if the disclaimer doesn't need to be inside the chat window itself 

     

    Both are supported. The custom header route is probably closer to what you're picturing since it sits inside the widget alongside "Powered by Agentforce," not just around it. 

     

    Reference:

    https://developer.salesforce.com/docs/service/messaging-web/guide/customize-header.html

Scrivi una risposta...
0/9000
Tom Bassett (Senior Solution Architect presso Vera Solutions) Forum Ambassador ha postato in Service Cloud Users
29 dic 2020, 22:22

Hello Trailblazers,

 

Please upvote my latest Service Cloud Idea;

Add Email as a Channel Menu Option

 

https://trailblazer.salesforce.com/ideaView?id=0874V000000ciUuQAI

 

Thanks, Tom

2 commenti
  1. Tom Bassett (Vera Solutions) Forum Ambassador
    4 gen 2021, 09:05
    Thanks for this suggestion, this is a neat workaround for now until Email is added as it's own option :)
Scrivi un commento...
0/9000
Tom Bassett (Senior Solution Architect presso Vera Solutions) Forum Ambassador ha postato in B2C Solution Architects
29 dic 2020, 22:23

Hello Trailblazers,

 

Please upvote my latest Service Cloud Idea;

 

Add Email as a Channel Menu Option

 

https://trailblazer.salesforce.com/ideaView?id=0874V000000ciUuQAI

 

Thanks, Tom

Scrivi un commento...
0/9000
Tom Bassett (Senior Solution Architect presso Vera Solutions) Forum Ambassador ha postato in * Service Cloud *
29 dic 2020, 22:23

Hello Trailblazers,

 

Please upvote my latest Service Cloud Idea;

 

Add Email as a Channel Menu Option

https://trailblazer.salesforce.com/ideaView?id=0874V000000ciUuQAI

 

Thanks, Tom

Scrivi un commento...
0/9000
Ivan Harris (CPTO presso Provar) ha postato in * Service Cloud *
12 mar 2020, 16:39

Hi Trailblazers! I have a question about Embedded Service Code Snippets. If someone is using different website pages, rather than different subdomains, for brands (i.e. example.com/brandA rather than brandA.example.com), is it possible to have an embedded chat window that is different for each brand and for the chat window to stay visible as the website visitor navigates sub-pages for the brand. Thanks in advance!

Scrivi un commento...
0/9000
Andrew Russo (#SaaL presso BACA Systems) Forum Ambassador ha postato in * Service Cloud *
20 dic 2019, 14:54

Hi,

I am having issues with adding the webchat to our website. I configured the chat colors to be orange and grey and they works fine during the chat session. The problem is before the chat session the button is black and the icon is missing and just shows a box. you can view it on the website.

 

https://bacasystems.com/support-test/

 

Any help is appreciated. 

prechat.PNG
1 commento
Scrivi un commento...
0/9000
Emma Ruefli (Managing Director presso File Room Pty Ltd) ha postato in * Service Cloud *
31 ott 2019, 07:44

Hi All and Anyone who can help :-) We are due to go live with our site later today and I have an issue with the web chat styling and screens changing and case automation disappearing with the installation of custom chat buttons.  I had some assistance from Salesforce support with the web chat set up and it working. They said to follow the documentation steps for the custom chat buttons which we did and then after deploying the code the custom chat buttons, the pop up chat screen, pre-chat form and styling from the Embedded Service Deployment were replaced with a rudimentary chrome chat pop up and no pre-chat as previously configured. Cases no longer autogenerate and a chat transcript window replaces the other case/chat configuration. We don't know why this happened but need URGENT assistance here.

 

We can delete the code and go back to the standard included buttons with embedded chat but we don't understand why this happened and why we can't connect it to our custom chat button.

 

These are the steps we followed:

1. Followed Salesforce Documentation Instructions to install Custom Chat Buttons.

2. Added Chat Button Code to Staging Site Pages.

3. Added Chat Deployment Code (Javascript) to Staging Site Pages - this finally changed the button but then replaced the other components.

 

There were no error message just complete change. Documentation reads as though embedded chat is an extension of Live Agent. Are they two different things?

Thanks for anything you can offer.

Emma

1 commento
  1. Beth Bornstein (Privia Health)
    31 ott 2019, 19:48
    I'd bet it was the prechat...that has the code for all the automations, such as creating a case, record type, etc. I don't have much timwe to dive deeper on this, but at a glance, that is what I'd start with for troubleshooting.
Scrivi un commento...
0/9000