Field
|
Description
|
Name
|
Choose a name that suggests the purpose of the rule.
|
Sequence
|
Required. Enter numbers in this field to set the order in which the rules should be evaluated. Evaluation begins with the rule with the lowest sequence number and continues until all rules are evaluated, except that -1 is evaluated last.
Rules with the same sequence number are evaluated in random order.
The sequence number for rules does not have the same significance as for rule sets because all the rules in a rule set are evaluated whether content is returned or not.
Rule sequence can be very important, however, for the order of the text strings displayed in salutation applets.
|
Rule Type
|
Select a rule type from the drop-down menu:
- Expressions. Evaluates inclusion and exclusion expressions directly.
- BusService. Invokes a business service and expects a property set in return, which is passed on to the business component.
The input argument to Business Service is a property set with four properties: Context, BusComp, RuleSet, and Rule.
- Invoke Method. Invokes a method on the business component to get a string, which is the search specification.
The input argument to Invoke Method is a string.
|
Active
|
Check the box to use the rule.
|
Conditional Expression
|
Optional. Use the conditional expression to control the evaluation of the rule, or to set up Boolean logic for evaluation of all the rules in the rule set.
|
Start Date
|
The date when the rule starts to be applied.
|
End Date
|
The date after which the rule stops being applied.
|
Description
|
Fill in this field with whatever information will help users understand the purpose of the rule.
|
Include Expression
|
Used with the Expressions rule type. An expression that sets parameters to include content.
|
Exclude Expression
|
Used with the Expressions rule type. An expression that sets parameters to exclude content.
|
Business Service Name
|
Name of the business service to invoke, if the conditional expression evaluates to TRUE and the rule type is BusService.
|
Business Service Method
|
Method to invoke on the business service.
|
Business Service Context
|
Parameter to pass to the business service method. While a business service can take many name/value pair parameters, you can only pass one parameter—called Context—in Siebel Personalization.
An example of a business service context is "UserType=Partner;AccountState=Gold" .
|
Method Name
|
Method to invoke on the business component, if the conditional expression associated with the rule evaluates to TRUE and the rule type is Invoke Method.
|
Method Argument
|
Parameter to pass the business component. You can only pass one argument.
|