Enhancement or Fault Number

Item  Description

New Feature

(CR 167663 / FSD 167663)

New Feature

LaneHawk interface.  Add support for the <price> field in the <posItem> messages that are sent to LaneHawk when an item is sold.

(CR 217751 / FSD 217751)

New Feature

Create a new utility or add to Swxtract.exe a way to fix bad dates used in claim filenames.  Matching them to the dates in the header record of the file.

(CR 217456 / FSD 217456)

POS add fields in <posConnected> message to LaneHawk.

<heartbeatSupport>

<heartbeatInterval>

<serverTimeout>

<applicationVersion>

<withinTransaction>

(CR 217756 / FSD 217756)

LogCollector.exe on the post does not work because PKZIP is unavailable on the PoS.

Scenario:
1. Either open a DOS window or use Windows Explorer on a post
2. Change directories to C:\PROGRAM FILES\POSWARE\WINPOS
3. Either key in <logcollector> or double click LogCollector
4. Click on the COLLECT button
5. Check the LogCollector log file and you will see it failed due to not finding PKZIP.EXE
6. PKZIP.EXE has been removed from the system and the existing LogCollector.exe on the post has not been updated

Expected Results: A zip file of important data on the post to work on problem is not collected.

Actual Results: A zip file of important data on the post is collected in a ZIP file.

WD 205308

State Name and Postal code is disappearing on the WIC EBT Maintenance Screen.  Once entering the Second state maintenance to view the data and exit out, the State Name and Postal code will no longer display. To get it back, the user is required to modify the SmartWIC.INI file and put the state name and postal code back.

Scenario:
1. Enter screen 1-6-15 and added Wyoming as state #2.
2. Hit ESC to back up to screen 1-6, went to 1-6-15 and no Wyoming?
3. Or choose Modify State and exit out, the Wyoming is gone

Expected Results: State Name and Postal code is still displaying and is in the Smartwic.ini

Actual Results: State Name and Postal code is not displaying and is deleted in the Smartwic.ini

WD 215309

Claim report by range will error if either the to or from field has a date that a claim file does not exist.

Scenario:
1. Create a Claim file by range.
2. Enter in the To field a date that does not have a claim
3. Enter in the From field a date that does have a claim

Expected Results: Report should not error.

Actual Results: Report will error and display no data.

WD 215310

Claim file was created with erroneous Julian date.  The claim file was created with a Julian date of 366. This is invalid for a year that is not a leap year. This is causing the claim file to error.

Expected Results: Claim file should not error.

Actual Results: Causes claim file to error.

WD 217436

Training mode should calculate the patients WIC ending balance. The Payment terminal does updates the ending balance when not in training mode. But the POS has to calculate the ending balance in training mode.

Scenario:
1. Put POS in Training Mode
2. Ring WIC items
3. Tender WIC EBT
4. View receipt to see Beginning and Ending balance.

Expected Results: WIC Ending balance needs to calculated in training mode

Actual Results: WIC ending balance was not being calculated in training mode.

WD 218449

Quantity Sold field is incorrect in the claim file. This field could not handle a large enough value for the multiple quantity.

Expected Results: Quantity Sold field should handle calculated value.

Actual Results: Quantity Sold field cannot handle the calculated value.

WD 217452

Import of a bad APL will cause the QDX to be cleared.  If the APL or HCL is a bad file that is pulled from the FTP, the verification to see if the files are ok is done after the the QDX is cleared.

Expected Results: APL and HCL files need verified before the QDX is cleared.

Actual Results: The QDX is cleared before APL and HCL files are verified.

WD 217752

The POS should not send blank values for Trans# and Operator# in <posConnected> message to LaneHawk. If, at the time the <posConnected> message is sent, the POS should check these values and if they are blank, send a "-1" value instead.

WD 217757

Late items from Lanehawk cause the "Found Items" icon to remain after next sale starts. POS currently responds to BOBIgnoreLate message by displaying the icon, which is fine, but it should be cleared at the end of the ticket by calling LHClearTicketState().