This problem is related to personalizationID. If personalizationID is not updated, the activity will treat it as same user and will be applied. So changing to a new personalizationID is the solution. A new configuration is introduced in instance xml. If configured, the new personalizationID will be created in WC_PERSISTENT cookie when the user logs off. By default, it is not configured and the personalizationID will still be the same as original one. To enable it, need to add "logoffRefresh="true"" element in instance xml. See the following: <PersonalizationId display="false" enable="true" logoffRefresh="true"/>
Friday, 12 July 2019
WCS Webactivity not working properly for Customer segments
Subscribe to:
Posts (Atom)
How to customize java.util.logging.Logger class to write logs in separate file than System.out.log in Websphere commerce/ HCL commerce)
/** * This method updated the passed in java.util.logging.Logger object with * custom file handler to write logs data form that class ...
-
STORECAT This table holds the relationship between StoreEntities and the Catalogs that they offer. Column Name Column Type Descripti...
-
atchast atchastlg atchrel atchtgt atchtgtdsc collateral ...
-
Extended Site architecture diagram & solution outline In WCS Extended site model Multiple stores can exist in a single S...