4.5.2 Rule Types
The following rule types are supported at the field and file level:
- Range of values rule: Allows a field to be checked against various ranges of values. For instance, an Australian postcode should be in one of the ranges 2000 - 2999, 3000 - 3999, etc. Refer to Range of Values Checks in the .
- List of values rule: Allows a field to be checked against a list of values. For instance, an Australian state should be in the list QLD, NSW, VIC, etc. Refer to List of Values Checks in the .
- Code/table file lookup rule: Allows a field to be "looked up" in a code file or table. For instance, a product number may be looked up in the product master file to check that it is a valid number. Refer to Code File/Table Lookup Checks in the .
- Simple logic rule: Allows simple conditions to be evaluated to check a field. For instance, "item weight must be less than (item volume * 10.643)" may be a check used in an order entry system. Refer to Simple Logic Check in the .
- Complex logic rule: Allows complex validation checking to be performed by your own LANSA functions or 3GL application programs. For instance, the validation of a "due date" may be done via a function or program that can account for public holidays, weekends, etc. Refer to Complex Logic Check in the .
- Date format/range rule: Allows a field to be validated as a date in a certain format (DDMMYY, MMDDYY, etc.) and in a certain range. For instance, a "date order due" may have to be in format DDMMYY and no more than 90 days into the future. Refer to Date Format/Range Check in the .
In addition to these rule types, you may use Triggers, in the , to add validation rules to your applications.
Also See
Rule Definitions in the