Bookshelf Home | Contents | Index | Search | PDF

Siebel Personalization Administration Guide > Content Targeting > Expressions >

Personalization Business Rules Designer

---

The Personalization Business Rules Designer (Figure 6) appears when you click the icon in any selected expression field.

Figure 6.  Personalization Business Rules Designer

It contains the following:

Categories. Contains the main categories available for building business rules:
Function. Siebel Query Language functions (see Siebel Query Language for more information).
Operator. Siebel Query Language operators.
Me Profile Attributes. The profile attributes of the primary user, such as a Siebel eSales customer or Siebel Call Center agent.

Valid subcategories are:

ShowAsString. GetProfileAttr is used in the expression.
ShowAsNumber. GetProfileAttrAsNum is used in the expression.
ShowAsInteger. GetProfileAttrAsInt is used in the expression.
ShowAsDate. GetProfileAttrAsDate is used in the expression.
ShowAsTime. GetProfileAttrAsTime is used in the expression.
ShowAsDateTime. GetProfileAttrAsDateTime is used in the expression.

For more information on GetProfileAttr functions, see Siebel Query Language.

You Profile Attributes. The profile attributes of the secondary user, such as a customer calling a call center agent. Uses the same subcategories as Me Profile Attributes.
Business Component Fields. These depend on the context of the rule, that is, where the Rules Designer is invoked. This category will or will not have data in its elements, depending on the following contexts.

Context	Data Shown
View	None
Applet	Fields in the business component on which the applet is based
Rule set not associated with an applet	None
Rule set associated with one applet	Fields in the business component on which the applet is based
Rule set associated with more than one applet, and the applets are based on the same business component	Fields in the business component on which the applets are based
Rule set associated with more than one applet, and the applets are based on different business components	None
Applet event	Fields in the business component on which the applet is based
Application event	None
Business component event	Business component fields
Action set not associated with an applet event or business component event	None
Action set associated with one applet event	Fields in the business component on which the applet is based
Action set associated with one business component event	Business component fields
Action set associated with more than one applet event or business component event	None

Subcategories. Contains subcategories of the selected category. Its context is controlled by the Categories box and it controls the context of the Elements box.
Elements. Contains all of the elements used to build business rules. Its context is controlled by the Categories and Subcategories boxes.
Expression. Displays the business rule. You can type and edit in the box, as well as add elements to it.
Quick bar (Operators). Provides buttons for frequently used operators.
Description. Gives a description of the element selected in the Elements box.
Errors. Displays errors in expressions or highlighted parts of expressions when you click Validate.

Use the following process to create business rules:

Select an element, and then click Add Element to begin building your rule. Double-clicking an element has the same effect as Add Element. You can also type text in the Expressions box.

The Rules Designer automatically provides the correct syntax for elements. For example, adding the Left string function displays Left(<string>,<n>) in the Expressions box.

Fill in arguments in the element, and then enclose it in parentheses if necessary.
Add other elements and complete them.
Connect elements using the Quick bar or by typing.
Click Validate to check your expression for errors. If part of an expression is highlighted, only the highlighted string is evaluated. Errors are displayed in the Errors box.
Save the business rule and return to the expression field. This also validates the entire rule. If valid, the rule is saved and the Rules Designer is closed. If the rule has any errors, they are displayed and the Rules Designer is not closed.

Bookshelf Home | Contents | Index | Search | PDF