Data Entry Processing 
Data entry processing (DEP) parameters are rules that define how data is entered into and processed by the POS terminal. An example that requires data entry processing configuration is triggering a function based on the data being entered.
Data entry processing options allow you to specify details for information that must be captured through a magnetic stripe reader (MSR), scanner device, or through keyboard entry at the POS terminal. You must define parameters to specify details such as the state of the POS terminal, how captured information is validated, and what, if any, subsequent functions should be triggered.
|
Description |
Screen Element |
|---|---|
|
Order |
Order number of the DEP rule |
This section provides information about the data entry process parameters.
|
Description |
Screen Element |
|---|---|
|
POI State |
State that the POI (point of interaction) must be in to accept the data entry |
|
Worker Thread |
Sets the rule to validate only if it is running from the off-thread process. Off-Thread processing is used for swipe-ahead debit and credit processing while in the process of scanning items (parallel processing). This option helps to indicate exactly when a rule can be run using the input data |
|
Active Menu |
Sets the rule to validate only if the menu ID matches the currently active menu on the POS terminal. It indicates exactly when a rule can be run using the input data |
|
Transaction Type |
Transaction that is affected by the data entry process |
|
Validation Source |
Device that reads the data source include the following: keyboard, scanner, magnetic stripe reader (MSR), customer MSR |
|
Data Field |
Extracts data that configures a specific value from the string of information that is read by the data entry device
This is only available when the data entry source is a MSR device. For scanner or keyboard entered data, this field is populated with either scan data or keyboard data. No other selection options are available for scanner or keyboard entered data End of the note. |
|
Scan Data Type |
The symbol standard by which the scanned data is formatted, if the data being validated comes from a scanned source |
This section specifies a function or a User-Defined Transaction (UDT) to start after receiving and validating entered data.
|
Screen Element |
Description |
|---|---|
|
Match Validation Rule |
Validation rule that checks the received data. It specifies that entered data must match in order for it to be acceptable. Some of these are the expected length of the data, the check digit details, and the data validation parameters |
|
Trigger Function |
Starts the POS function selected when data is received and validated |
|
Function Parameters |
Details for the data to extract from information that the data source device provides |
This section provides information about setting parameters for rules that have two possible functions.
|
Screen Element |
Description |
|---|---|
|
Use Secondary |
Displays the following secondary function options:
|
|
Prompt |
Prompt type |
|
Use Primary Response |
Primary function when you enter a value |
|
Use Secondary Response |
Secondary function when you enter a value |
|
Parameter |
Sections of data to extract from the complete data when you provide field or parameter names
To launch a Resume suspended transaction function from a bar code scan, the POS terminal extracts the Site ID, Device ID, and transaction number to identify and recall the transaction to resume End of the example. |
|
Parameter Source |
The source value is as follows:
|
|
From Data |
Start position and maximum length of the section of data to extract. Data values to include are as follows:
|
|
Strip Leading 0’s |
Deletes the leading zeros from the number. It displays the final value as 1 for scanned barcode numbers such as 00001 that are padded with leading zeros |
|
Append Data |
Adds a prefix and suffix to data as follows:
|