Siebel Personalization Administration Guide > Managing User Profiles > Working with Multiple Value Profile Attributes >

Exists Operator Usage Scenarios


Table 13 lists the usage scenarios using the EXISTS operator. 

Table 13. Usage Scenarios Using the EXISTS Operator
Usage Scenario
Example
Expression

Searching for an MVG field in a business component against an MVG profile attribute.

A bookseller site wants to recommend books from all the categories that interest a user.

A book can belong to multiple categories, that is, book ABC can belong to action, adventure, and history.

Similarly, user XYZ is interested in multiple categories of books, that is, science fiction and action.

The personalization engine matches user XYZ to all the books that belong to the categories that the user is interested in, including book ABC.

This is done by matching the MVG profile field Interest with the MVG field Categories in the products business component.

Expression:
EXISTS ([Categories] = GetProfileAttrAsList( ))

Searching for an MVG field in a business component against a single value profile attribute.

A product is targeted to multiple states and the marketing manager wants to recommend the product to only the people who live in one of the targeted states.

Expression:
EXISTS ([Categories] = GetProfileAttrAsList("Interests"))

Searching for a single value field in a business component against an MVG profile attribute (for example, Portfolio Product Id).

A product is targeted to multiple states and the marketing manager wants to recommend the product to only the people who live in one of the targeted states.

Expression:
[Product Id] = GetProfileAttrAsList ("Portfolio Product Id"))

NOTE:  The EXISTS clause is not required when searching for a business component's single value field against a MVG profile attribute.

Siebel Personalization Administration Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.