Home
TeamSite
TeamSite, LiveSite and OpenDeploy
targeting rule to display text/header in header
catorarn
Hi, We have a component which is a header. The header consists of an icon, header text and a navigation bar.
The header text has to be targeted on the basis of a segment which is based on a header referrer condition or a url click condition (not sure yet which).
The business would like the messaging controlled by a DCR text field, so the user updates a dcr which has a segment field and a text field.
Question is: how should we implement the appearance xsl and content xml to get the rule section in content xml to pick up the text field item from the DCR?
Is it something like this?
I have a rule section which will then be subjected to an external class. The external class will check the rule against a segment variable. The returned xml will then be a text that was part of the action in the rule.
Then I should write some other class which takes the returned xml and then check that against the DCR datum's text field on the basis of which segment is used
beware: I am know for overcomplicating myself and I am not developing step by step. In this case I got to the point that
a. the OOTB targeting-heartbeat spar works end to end
b. i managed to get a rule display a targeted header text in the component. I am using this structure:
appearance xsl:
[html]
$MODEL{/Properties/Data/RulesEngine/output/result}
[/html]
content xml:
[html]
$ALL
Targeting Header Text Result Investor
Targeting Header Text Result Investor.rule
[/html]
However with this implementation the text is content managed in the condition. The business want the content management of that header text to take place in the DCR rather than in the condition.
How should I approach this? There seems to be nothing out-of-the-box integrating a Form with Targeting, can that be?
Should I write an external and/or generator to swap the default text that a rule
Can someone give me some advice on what would be the way to approach this best?
Find more posts tagged with
Comments
There are no comments yet