According to DSM Document:
For the Query content component, extra variations are calculated for any
references to contextual values, meaning the current user’s Group or Segment
assignments, the current Channel, the current content instance, and so on. In
other words, the Query content component specifies variation dynamically
depending on what the user has configured. It is the only out-of-the-box
component type that does this.
When I configure my query component, I did on a way like
select content of type POC_CT_Page
|
| | where id in request.ids
|
| sort by System Name ascending |
Poc_CT_page is a customized content type defintion, and id is attribute of Poc_CT_page, the request.id is the paramenter passed by URL. When I have different value in the request.ids, I would expect a cache variation.
But the result turns out it does not, it still give me the same cache when I pass different ids value, any idea about this?
If I call getCachingSensitivities() in QueryContentComponent, I can find the CachingSensitivities list size is 0, is there any configuration to enable it? We are at VCM 7.6 SP2, and we use both HPD and DSM html fragement cache.
Thank you in advance.
