Verbalization/targeting

Hi,

I am trying to achieve targeting, where I want to swap DCRs using TeamSite Rules.

Where the assumption is to have the inputs available for the rule.

I am trying to create a condition based on the gender of the user. The OOTB conditon available for "gender" takes the input value from a session as "session.userProfile.gender". I want to update this condition to take the gender as a constant value.(or a plain text file having the gender specified)

Please suggest on how this can be achieved.

Thanks,

Sneha

Find more posts tagged with

Comments

Rick Poulin

Have you read the documentation and taken a look at the other examples? Creating a condition that reads from a constant value is pretty simplistic...

SAK25

Hi,

Yes I have read the documentation and seen the examples as well. But that is confusing me.

Let me explan what I have done till now:

1. I have created a condition (using OOTB gender condition) and written an action and have created a rule based on it.

2. Below is the condition (xml) which has got created:

<?xml version="1.0" encoding="UTF-8"?>

<If Version="2" Operator="AND">
<Editor>
<Description>When user's gender is female</Description>
</Editor>
<Condition Operator="StringEquals" IgnoreCase="true">
<Value Source="InputModel">
<Path>Session/UserProfile/Gender</Path>
<Bean Object="context">
<Path>session.userProfile.gender</Path>
</Bean>
</Value>
<Value Source="Constant">
<Data>F</Data>
</Value>
<Editor>
<Verbalization>conditions/gender.xml</Verbalization>
<Inputs>
<Constants>
<UserInput InputId="bean.path" Control="hidden">
<Value Type="String">session.userProfile.gender</Value>
</UserInput>
<UserInput InputId="xml.path" Control="hidden">
<Value Type="String">Session/UserProfile/Gender</Value>
</UserInput>
</Constants>
<Paragraph Id="paragraph">
<Sentence Id="sentence">
<Clause>
<UserInput InputId="engine.operator" Control="hidden">
<Value Type="String">StringEquals</Value>
</UserInput>
<UserInput InputId="template-type" Control="hidden">
<Value Type="String">single</Value>
</UserInput>
<UserInput InputId="input.operand-1">
<Value Type="String">F</Value>
</UserInput>
<UserInput InputId="input.operator">
<Value Type="String">option.equals</Value>
</UserInput>
</Clause>
</Sentence>
</Paragraph>
</Inputs>
</Editor>
</Condition>
</If>

3. This condition takes user gender from session and matches it with the selected gender at the time of creating the condition. As i am using existing OOTB userProfile->Gender condition , I can not update this to provide the input value rather than getting it from session.

Also , when I am trying to edit the condition I have created, it is opening it in Editor. I am not getting the xml version of it so that I can try to upate that.

Could you please help me with the path where the xml version for the conditions get saved.

4. Now what I am trying to do is, write a new conditionusing verbalization. Where I can get the gender entered at the time of conditon creation. I am planning to use :

<UserInput Control="combo" InputId="input.operand-1"/> or

Please suggest if i am on the right path.

Rick Poulin

SAK25 wrote:

Also , when I am trying to edit the condition I have created, it is opening it in Editor. I am not getting the xml version of it so that I can try to upate that.
Could you please help me with the path where the xml version for the conditions get saved.

Well first let's just clarify one thing. There's a difference between exposing a condition criteria for use in a rule ("verbalization") and creating a specific instance of that condition as a business user (File > New Condition). Exposing the criteria is done in XML in /iwadmin/main/livesite/config/WORKAREA/shared/rules/verbalizations/conditions.

SAK25 wrote:
3. This condition takes user gender from session and matches it with the selected gender at the time of creating the condition. As i am using existing OOTB userProfile->Gender condition , I can not update this to provide the input value rather than getting it from session.

This statement, especially this part in red, makes no sense. If you replace the variable part of a condition with another user input, then you're basically allowing the user to create a condition instance that says "if 1 == 1". You might as well use the Base > True and/or Base > False criteria if you have a use case for that type of thing.

SAK25 wrote:
4. Now what I am trying to do is, write a new conditionusing verbalization. Where I can get the gender entered at the time of conditon creation. I am planning to use :
<UserInput Control="combo" InputId="input.operand-1"/> or
<UserInput InputId="input.operand" Control="textfield"/>

I think you should have a look at the verbalization examples and rephrase. This isn't wrong, but it kinda doesn't make sense as you've phrased it, at least in the context of verbalizing your criteria. I think maybe if you explain the actual use case you're building maybe I can help a little better.

SAK25

Thnks for the reply. Sorry if I have created more confusion.

I will try to explain what I am trying to achieve:

1. I want to create a rule which will show different DCRs based on different inputs.

2. For e.g If user gender is male, then the products which are specified for Male should be shown. If gender is female then products specified for Female are shown.

3. Now, to implement this,

a) I created a simple condition( File->New Condition) using OOTB gender condition .

b) Then I created an action (File->New Action) to show the DCRs based on condition + Content Type (MAle/Female).

c) I created a rule using above condition and action.

d) Created a component using this Rule as a Datum and called OOTB RulesEngineExternal to execute the rule.

e) Component was previewed without error.

4. But now I dont have actual user input (as don't have actual user profile available in session).

5. So I had to assume that input is already available for the rule. For this I tried to edit the existing condition as stated above, but was unsuccessful.

6. So use case as of now is: I want to create a condition (expose a condition) which will allow to enter the user input and will allow to match it against the gender (which I will get from provider).

7. Once I will achieve this then I should be using site level pre-controller to show the DCRs as per rule.

8. I am doing a POC for this thing and have taken Gender based rule as an example. I can use any other criteria as well. e.g Locale / State.

I hope I am a bit more clear now. Let me know if more clarifications are needed.

Thanks

Rick Poulin

SAK25 wrote:
5. So I had to assume that input is already available for the rule. For this I tried to edit the existing condition as stated above, but was unsuccessful.

"Faking" a UserProfile is actually kinda difficult, so you didn't really pick the easiest rule to test with. To test whether your DCR changes on the page, use the "true" and "false" conditions instead (just as a test). If you use anything that's dependent on the context, then the only way you can "force" values is creating hooks in Java code that set the gender (or whatever variable you're targeting on).

SAK25 wrote:

6. So use case as of now is: I want to create a condition (expose a condition) which will allow to enter the user input and will allow to match it against the gender (which I will get from provider).

How is this different from the OOTB rule? It already asks for input, so you should be able to create a condition that says "When gender is F".

SAK25 wrote:
8. I am doing a POC for this thing and have taken Gender based rule as an example. I can use any other criteria as well. e.g Locale / State.

For a POC, you're better off picking a condition that's not relying on something as complex as a UserProfile. The locale is a good one, because that's easy enough to toggle.

SAK25

Thanks for your help.

I will take locale based rule for the POC. However when I checked now there is no OOTB condition available for locale, that said I will have to create a new condition using verbalization .

Correct me if I am wrong.

Rick Poulin

Correct, there isn't an OOTB condition for that but it's almost the same as gender -- instead of looking at "session.userProfile.gender" you'd go to "locale" (since the bean path is relative to the RequestContext object).

Or if it's easier, you can try the "web browser / user agent" condition instead. That one should work fairly well OOTB and it's easy enough to provide different inputs for testing.

SAK25

Hi,

Thanks a lot for allyour inputs. Really appreciate alot Smiley Happy

I have created a new condition for locale using verbalization . Now next part is I have to assume the input is available to site pre-controller and have to swap the DCRs based on context and rule.

I am working on it. Will get back if face any more issues in that.

Thanks again for your help.