Validation Rules 
This section describes rules that define specific criteria for considering captured data as valid or acceptable for a specific transaction. You can define a validation rule to look for and retain only preferred customers before launching a bonus offer when a customer’s store credit card is scanned. You can also set up a date validation rule to check for a customer’s age to prevent the sale of restricted items to minors, or to look for the expiry date of a tendered coupon or credit note. To create a new validation rule, specify its behavior and activate its definition, you must attach it to a new or existing prompt. For more information about prompts, see Prompts.
This section describes parameters for validating a number:
Screen Element |
Description |
|---|---|
Minimum Length |
Minimum numeric value character length of the data for validation |
Maximum Length |
Maximum numeric value character length of the data for validation |
Specific Length |
Specific length of data for validation (this is separated by a comma) |
Prefix |
Specifies how many initial identifying characters to use for the data |
Suffix |
Specifies how many ending identifying characters to use for the data |
Match Value |
Ensures that data matches a specific value for the data to be considered valid |
Match Field |
Matches data with the value of a specific field (currently only supports Terminal or Store Number fields). The default value is None if no maximum value is required |
This section describes parameters that validate the data source.
Screen Element |
Description |
|---|---|
Source Device |
Device that obtains the data |
Scan Data Type |
Scan data types |
This section describes parameters for numeric validation.
Screen Element |
Description |
|---|---|
Minimum Value |
Ensures that the data satisfies a minimum numeric value. This is only relevant for numeric values; the default value is None if no minimum value is required |
Maximum Value |
The data satisfies a maximum value. This is only relevant for numeric values; the default value is None if no maximum value is required |
Allow Zero |
Allows numeric data of zero |
Check Digit Position |
Location of the check digit value of the data for validation includes the following:
|
Check Digit Calculate Start Position |
Position of the first character in the data that is validated by the check digit scheme |
Check Digit Calculate Length |
Length (in characters) of the data being validated by the check digit scheme includes the following:
|
This section describes parameters that validate date information from scanned, entered, or swiped data. The POS terminal uses these configured entries to validate dates entered that are compared to the current date, or the current date is adjusted by the specified parameters and compared to the entered date.
If required, there is an exception where you can override these values that is accomplished by defining a data form using prompts with the DATEOFFSET well-known data type. When a prompt specifies this data type, the POS terminal uses the data values to offset the current date before comparing it to the entered date, instead of using the configured dates.
Note
If you use the DATAOFFSET_value to validate a date, you must activate Post Validity in the data form that contains the prompt with the date validation setting.
Screen Element |
Description |
|---|---|
Enable Date Validation |
Validates the date in the captured data |
Date Start Position |
Location within a data stream where the date begins |
Date Format |
The date format |
Date Must Be |
Relationship between the validation and the current date (equal to, greater than, or less than). It specifies the offset to the current date using Years, Months, and Days fields |
This section describes parameters for validated records against positive and negative database searches. In a positive database search, if a record matching the value you are searching for is found, it accepts the number and the transaction is allowed to continue. In a negative database search, if a record matching the value is found, the number is rejected and a new number must be entered. The transaction is not allowed to proceed until a valid number is entered.
If you select positive and negative databases, it checks the negative database first. If a negative match is found, the validation fails and cancels further validation. If a negative match is not found, the search continues to the positive database; for the validation to be successful, the validation rule must find a match on the positive database.
Screen Element |
Description |
|---|---|
Positive DB Name |
Name for the database search that returns a match; it accepts the data for validation (a record match for this item is found in the database). The None option or a blank field indicate that no match is required |
Negative DB Name |
Name for the database search that returns no match; it does not accept the data for validation. The None option or a blank field indicate that no match is required |
This section describes parameters for linking rules.
Screen Element |
Description |
|---|---|
Rule |
Validation rule that links to the new validation rule |
This section describes parameters for rounding rules.
Screen Element |
Description |
|---|---|
Rule |
Rounding rule that links to the validation rule. For more information about rules, see Rounding Rules |
This section describes document print configurations for a validation check.
Screen Element |
Description |
|---|---|
Display Text |
Text that displays on the POS terminal after a successful or failed validation. You must select the literal as defined in the literal.properties file to translate the text for display |
Pass Validation Trigger Document |
The document to print or display when the validation is successful using the following actions:
|
Fail Validation Trigger Document |
|