Siebel Marketing Guide > Administering Siebel Real-Time Marketing > Sorting and Filtering By Scores Using Decision Broker >
Filtering on Dynamically Calculated Data
You write personalization rules that use these calculated dynamic profile attributes to specify filter specifications and sort specifications for the offers to be presented to contacts. For more information, see Filtering an Offer List Dynamically Using Profile Information.
If the expressions use dynamic profile properties created during the Decision Manager set-up process, make sure you use exactly the same property names in your expression statements or the rule will not work. For more information, see Creating and Testing Decisions.
To filter on dynamically calculated data
- Create a Personalization Rule Set with one or more rules to execute a decision using the Decision Broker Service.ExecuteDecision business service method.
Table 49 contains a description of the rules fields.
- Include the profile attributes returned by the Rules invoked in Step 1 in the Conditional Expression, the Include Expression, or the Exclude Expression in another personalization rule designed for filtering the offers.
Outputs from a decision executed from a personalization rule are stored as a dynamic profile attribute with a name of the format [decision name].[decision output argument name]. For example, if a decision named GetChurnScore has an output argument named ChurnValue, then the result will be stored in a profile attribute named GetChurnScore.ChurnValue.
Table 49. Rules Fields for Executing Decisions
Field
|
Description
|
Active
|
TRUE
|
Business Service Context
|
the name of the Decision and any arguments required by the decision configuration based on your requirements. Examples:
Decision=Get Customer Value Score
Decision=GetChurnScore,ContactId=GetProfileAttr("Id")
|
Business Service Method
|
ExecuteDecision
|
Business Service Name
|
Decision Broker Service
|
Conditional Expression
|
Based on your requirements.
- If you leave this property blank, this filter specification will apply to all users. (Not recommended.)
- Anonymous users should always be excluded. To apply to certain users conditionally, type a suitable logic expression using profile attributes. For example:
GetProfileAttr(`Me.Is Anonymous') <> TRUE
|
Rule Type
|
Business Service
|
Sequence
|
Each rule should be assigned a number that establishes its order in the rule set. Each rule will be executed in sequence.
|
Table 50 describes rules fields for offer filters.
Table 50. Rules Fields for Offer Filters Using Decision Customer Scores
Field
|
Description
|
Active
|
TRUE
|
Conditional Expression
|
Based on your requirements. To apply this filter specification to all users, leave this property blank (not recommended) Anonymous users should always be excluded using the following example:
To apply to certain users conditionally, type a suitable logic expression using profile attributes. Example:
GetProfileAttr(`Me.Is Anonymous') <> TRUE AND GetProfileAttrAsNum(`GetChurnScore.ChurnValue') > .85
|
Exclude Expression
|
Based on your requirements. Offer property criteria to exclude from the list if the Rule conditional expression is true. Example:
[Inbound Priority] >= LookupValue("OFFER_PRIORITY", "4 - Low")
|
Include Expression
|
Based on your requirements. Offer property criteria to include in list if the Rule conditional expression is true. Example:
[Margin] <= LookupValue("OFFER_MARGIN", "3 - Medium")
|
Rule Type
|
Expression
|
Sequence
|
Each rule should be assigned a number that establishes its order in the rule set. Each rule will be executed in sequence
|
