Translate
No discussion around the idea, description is quite poor
The idea was reported more than 3 years ago and amount of votes is quite low
Below is the history of changes to this idea's status. Return to the idea.
No discussion around the idea, description is quite poor
The idea was reported more than 3 years ago and amount of votes is quite low
It will be useful to have some concrete use cases here.
Note that the concept of Component Presentation conditions already exists: Component Presentations can have Target Group conditions. Admittedly, this is considered "legacy" Personalization & Profiling functionality nowadays, but it is still supported in conjunction with the Context Expressions extension.
If the main use case is indeed in the area of Personalization: is the current mechanism sufficient for you? If not, what is missing?
What are other use cases for metadata on Component Presentations? Component Presentation parameters? Note that a Component Template can already have a Parameter Schema, but we never actually implemented the mechanism to set parameter values on the Component Presentations.
Would conditional Component Presentations (personalization) in combination with Component Presentation parameters be sufficient?
