Expand my Community achievements bar.

SOLVED

Issues with updating segment UI

Avatar

Level 4

Hello, we have implemented Context Hub in our project (6.5) and found some issues related to updating the segment UI. Once the segment is created, if you author segmentation components with the values, even though the segment is resolved, the UI does not turn green. We had to refresh the browser to see if the segment is resolved or not. The same issue has been reported in the forum below as well. Basically, rather than refreshing or checking in the browser console, we would like to fix the issue. Please let me know if anyone has encountered a similar issue and what the fix was for it.

http://www.sgaemsolutions.com/2018/12/personalization-using-contexthub-in-aem.html

 

test1234567_0-1729211283848.png

 

Another observation: I see a cache folder (/conf/wknd/settings/cloudsettings/default/contexthub/cache) in the WKND site. I'm just checking if this is required for custom configuration. If so, what is the purpose of it?

test1234567_1-1729212139740.png

 

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @test1234567 ,

This is something which is common in AEM as per the Adobe "All traits are resolved immediately, though most only change on page reload."
For further validation you can look into the network call in browser console which is happening on page load and may be missing during updating the segment.
In he below link you can find a note section where this observation has been added.
https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/sites/authoring/....

For cache node creation in CRX, the system automatically creates a cache node, which saves the generated kernel.min.js and ui.min.js. 

-Tarun

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

Hi @test1234567 ,

This is something which is common in AEM as per the Adobe "All traits are resolved immediately, though most only change on page reload."
For further validation you can look into the network call in browser console which is happening on page load and may be missing during updating the segment.
In he below link you can find a note section where this observation has been added.
https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/sites/authoring/....

For cache node creation in CRX, the system automatically creates a cache node, which saves the generated kernel.min.js and ui.min.js. 

-Tarun