Compares single value content property to single value property

Question

Hi,
I am using WLPS 3.2 with weblogic apps 5.1.
This is when regarding content selection rules. When u go into the rules
management and try to create a content selection rule : Then display content
based on:
we see 3 templates to choose from. Now if u look at template 2 it says
:Value with Property Example
This template compares a single-value content property to another
single-value property. content.investor_type equals user.investor_type
It says this template compares "single value" content property to another
"single-value property". What i did was set up a rule that comared a single
value content property to a "multiple" value user property (i.e. the user
property was allowed to have multiple values-check boxes). The rule was set
up fine. When i ran the rule with the <pz:contentselector> tag it dint
return the desired content object. Now if i set up the same rule to match a
single valued user property then it worked!!! Could you please let me know
why this happens and is this a limitation of the tool. What is an
alternative solution for me to compare a content property to a multi valued
user property.
Thanks,
--Kapil

Answer 1

Hi Kapil,
You're correct on all counts. This workaround does move the content
selection into the JSP, rather than using a rule -- which is not ideal.
Also, your suggestion to build one query string to cut down on the number of
database calls is a good improvement.
- Ginny
"kapil khanna" <[email protected]> wrote in message
news:[email protected]...
Hi Ginny,
I really appreciate ur response. This work around was not knew to me. Iwas
expecting a better work around from some reasons:
i) The definition of this rule is hard coded and not administered thu the
tools interface.
ii) There are multiple database calls for each property value retrieved
every time the <cm:select> tag is executed which is very expensive.
iii) The query that i build for the <cm:select> or <pz:contentQuery> tag
doesnt support the in statement.
My work around was something like this:
Build the query string first which would look something like this
CONTENT.interest like '*Science*' || CONTENT.interest like '*Astronomy*'
Then run the <cm:select> or <pz:contentQuery> tag so that i have only one
database call.
Considering the user has 2 interests chosen Science and astronomy. I usethe
like so that CONTENT can be tagged to accomodate multiple values which is
very possible in a real life situation. For eg: <meta name="interest"
content="Science,Astronomy" >
Is this a better work around or am i totally out of line.
Thanks for your help and time
--Kapil
"Ginny Peterson" <[email protected]> wrote in message
news:[email protected]...
Hi Kapil,
Yes -- this is a limitation with the phrase templates. The "Value with
Property" phrase template compares a single-value content property to
another single-value property. What's key here (and often overlooked)
is
that fact that the property you're using must be a single-valueproperty.
>>
There is a workaround using the <cm:select> tag rather than the <pz>tags.
Basically, it involves getting a list of the values for yourmultiple-value
property, and iterating over that list, selecting the content for each
of
the items in the list.
Here's some sample code. Assume you have a text, multiple, unrestricted
property called "MyInterests" in property set "TestPropertySet"; a user
might have values like this: "Science, Astronomy, Cooking".
<%@ page extends="com.beasys.commerce.axiom.p13n.jsp.P13NJspBase"%>
<%@ page import="com.beasys.commerce.content.ContentHelper"%>
<%@ taglib uri="es.tld" prefix="es" %>
<%@ taglib uri="cm.tld" prefix="cm" %>
<%@ taglib uri="um.tld" prefix="um" %>
<!-- Get the user and group names -->
<%
String userName = (String)getSessionValue(SERVICEMANAGER_USER,request);
String groupName = (String)getSessionValue(SERVICEMANAGER_SUCCESSOR,
request);
%>
<!-- Get the profile for the user -->
<%
// Check to see if logged in, then getProfile for the user with groupas
successor
if(getLoggedIn(request))
%>
<um:getProfile scope="session" profileKey="<%= userName %>"
successorKey="<%= groupName %>" />
<%
else // use the default profile for the group
%>
<um:getProfile scope="session" profileKey="<%= groupName %>"
groupOnly="true" />
<%
%>
<!-- Get the property value for the user -->
<um:getProperty id="areas" propertySet="TestPropertySet"
propertyName="MyInterests" />
<br><br>Interests for <%= userName %>:
<%
// Multi-valued properties are retrieved as an ArrayList, so cast to a
Collection so we can iterate through
Collection c = (Collection)areas;
String queryString;
Iterator i = c.iterator();
while(i.hasNext())
String nextVal = (String)i.next();
queryString = "CONTENT.interests == '" + nextVal + "'";
%>
<cm:select contentHome="<%= ContentHelper.DEF_CONTENT_MANAGER_HOME %>"
query="<%= queryString %>" id="docList"/>
<es:forEachInArray id="aDoc" array="<%= docList %>"
type="com.beasys.commerce.axiom.content.Content">
<li>Matched document message:
<cm:printProperty id="aDoc" name="message" encode="html"/>
</es:forEachInArray>
<%
%>
FYI, this limitation is not present in WLCS 3.5; it's much more flexiblein
terms of using mutli-valued properties (and multi-valued meta tags) in
rules.
I hope this helps!
- Ginny
"kapil khanna" <[email protected]> wrote in message
news:[email protected]...
Hi,
I am using WLPS 3.2 with weblogic apps 5.1.
This is when regarding content selection rules. When u go into the
rules
management and try to create a content selection rule : Then displaycontent
based on:
we see 3 templates to choose from. Now if u look at template 2 it says
:Value with Property Example
This template compares a single-value content property to
another
single-value property. content.investor_type equalsuser.investor_type
It says this template compares "single value" content property toanother
"single-value property". What i did was set up a rule that comared asingle
value content property to a "multiple" value user property (i.e. the
user
property was allowed to have multiple values-check boxes). The rule
was
set
up fine. When i ran the rule with the <pz:contentselector> tag it dint
return the desired content object. Now if i set up the same rule to
match
a
single valued user property then it worked!!! Could you please let me
know
why this happens and is this a limitation of the tool. What is an
alternative solution for me to compare a content property to a multivalued
user property.
Thanks,
--Kapil