SalesforceCommerceCloud / b2c-crm-sync

... a contemporary perspective on how to integrate B2C Commerce and the Salesforce Customer 360 Platform to power frictionless customer experiences in the B2C domain.
https://salesforcecommercecloud.github.io/b2c-crm-sync/
BSD 3-Clause "New" or "Revised" License
64 stars 47 forks source link

[BUG] MAJOR ISSUE IN PRODUCTION: Session been shared in multiple PCs with OOBO #53

Closed luismiguelferreiraPWC closed 2 years ago

luismiguelferreiraPWC commented 2 years ago

Describe the bug A clear and concise description of what the bug is.

We have integrated every cartridge on the b2c-crm-sync. We have some agents that are working in production and they are using OOBO normally, but if I'm on the website as a guest I'm able to see the red banner at the top and I'm not even an agent. This only happens in one page.

To Reproduce Steps to reproduce the behavior:

  1. Go to Search-Show page
  2. It will appear the Red Banner at the top from other customers.

Expected behavior It shouldn't appear customer information in other customers PCs.

Screenshots If applicable, add screenshots to help explain your problem.

redbanner Your local environment details:

Additional context This is happening in Production so this is a major issue. Are you able to join to a call?

redbanner .

sandragolden commented 2 years ago

@luismiguelferreiraPWC Thanks for opening this issue. It looks like the agent header is getting cached on header/pageHeader.isml. This was fixed around June (see changes here). Can you review your header/pageHeader and ensure this template is using a remote include (<isinclude url="${URLUtils.url('OOBO-agentHeader')}" />) vs of a local include (<isinclude template="components/header/agentHeader"/>)? This will allow the agent header to be cached separately.

As a quick fix, you should be able to temporarily disable the agent header via the b2ccrm_syncAgentHeaderIsEnabled site preference

luismiguelferreiraPWC commented 2 years ago

Thanks. I will do that fix and then give you some feedback.

jbachelet commented 2 years ago

Hello @luismiguelferreiraPWC ,

Hope you are doing good. Can you please provide us with feedback regarding the issue? Did the change proposed by @sandragolden do the trick and fix the issue? If so, please go ahead and close the issue.

Thanks!

luismiguelferreiraPWC commented 2 years ago

@jbachelet that update have fixed the issue