Rule Components
Most rules are statements that define conditions and specify actions to be taken if the conditions prove true. Such a rule might state, for instance, If an authorization or posting transaction scores at or higher than 800 (condition), then create a case (action).
Falcon Expert also provides access to data fields that may be used in rules, and to “components” that manipulate the data. Some fields are from the Falcon database or from scoring request and response messages exchanged with an external system; most fields come from the transactional data feeds sent to the Falcon Scoring Server.
Components include rule-control keywords, operators, functions, variables, and values. This chapter describes the use of these components.
Falcon Expert uses SRL (Structured Rule Language) syntax to write a rule.
 | Important: SRL is
case-sensitive. For example,
LookupList() is the recognized function name, but
lookuplist() is not.
|
Note that the rule examples contain line breaks and indentations that are for reading convenience, but have no effect on the processing of rules.
Notation Conventions
The following symbols and conventions are used in the documentation:
- User-supplied values and variables are enclosed in parentheses and appear in italics, such as arg1 and dateStr.
- Square brackets (
[]) indicate that the enclosed symbols (or sequence of symbols if parentheses enclose the sequence) can occur no more than once and are optional. - A pipe (
|) indicates a choice between individual symbols or between syntax forms. Either the symbol to the left of the|metasymbol or the symbol to the right of the|syntax symbol are valid, but you cannot use both.