Enhancement or Fault Number

Item  Description

New Feature

Support Member Card Number from Fuel with a Check Digit.

(CRD 329022 / FSD 329022)

New Feature

Add support for the new IBM 67 key keyboard to ISS45 V8.

(CRD 328594 / FSD 328594)

New Feature

Add Support for Epson TM-H2000 for ISS45 V8.

(CRD 292212 / FSD 292212)

WD # 269181

Automatic EOD does not run after upgrading to 8.1.5.4-050 unless a manual EOD is run first.

WD # 280096

S&H You Tech - Voided Transactions are not sending 01=Void normal item in sale for 'I' Item Information Message.

WD # 313512

Epson TM-6000IV printer is emulating a 6000III and using Epson OPOS 266E as released. The first check endorsement is fine with the check writing on face of check and endorsement on the back of the check. The 2nd time a check is tendered the check writing occurs on the back of check and the endorsement is printed on the face of the check. The odd # of times a check is tendered prints correctly and the even # of times a check is tendered prints incorrectly.

WD # 316283

RouteSrv only sends 11 digits for validation on barcode entry at the pump.

Scenario: Scan a barcode with more than 11 digits (usually the check digit) at the pump.

1. RouteSrv should see the card as a member card, assuming it is set up as one.

2. The RouteSrv console returns MediaMasterType=3, this is credit not member.

Expected Results: RouteSrv should allow configuration of variable barcode lengths.

Actual Results: RouteSrv only allows 11 digit barcodes.

WD # 325081

If a 13 digit loyalty card is scanned at the pump for a pay inside (PAK), when the ticket is recalled there is invalid data instead of the member card. The problem is seen when sending the member card number we get from PumpSrv to Rtaps:

Scenario:

1. At the pump, perform a PAK using a 13 digit loyalty/employee card number at the pump (without the check digit) (8009999990010).

2. Fuel prices at the pump rollback.

3. Pump several gallons.

4. At the POS, recall the PAK.

Expected Results: PAK should be accepted into the ticket at the POS. Customer can pay for the fuel and cashier can finalize the ticket.

Actual Results: Error displays at the POS and PAK is not accepted at the POS so customer cannot pay for the fuel.

WD # 326229

 Merge Rttrsmng fixes from StoreLine.

WD # 336297

After upgrading to 8.1.6.0-080 patch auto EOD will not run. It appears to run right after patch is applied, for approx. 2 consecutive days, it will then fail after that point. The POS_SRV_MGR services looks for the Auto EOD job, but it will not start. A manual EOD is able to be started and finishes with no problems. It appears the problem lies with either the V8EndOf Day.exe, according to customer's testing in a lab environment. The V8EndOfDay.exe, dated 5/18/2012, was pared with V8G_EodInt.dll, dated 5/18/2012. Both files were put in place for TD# 158755 to correct "EOD running outside the specified time on the registers". Logs and screen shots of customers Auto EOD settings are attached.

Scenario: Apply Upgrade Patch up to 8.1.6.0-080

1. Auto EOD is set up to run

2.Auto EOD runs (for two consecutive days)

3.Auto EOD doesn't run after that

Expected Results: Auto EOD should run

Actual Results: Auto EOD does not run

WD # 336492

Rounding is calculated incorrectly in some scenarios if the balance due amount has a "1" or "2" in the hundredths place.

Rounding is calculated incorrectly in some scenarios if the balance due amount has a "1" or "2" in the hundredths place. All rounding calculations should be +/- $0.01 or +/- $0.02.

Issue 1: Rounding is calculated incorrectly in these scenarios if the balance due amount has a "1" or "2" in the hundredths place:

- Over tendering with cash (with rounding enabled)

- Over tendering with cash general tenders when rounding is not enabled (in tender maintenance: cash/general)

- Partial tendering with cash (over tendered) as the final tender

These amounts should round the balance due down $0.01 or $0.02.

Issue 2: When performing a negative total transaction, an "over tender is not allowed in negative total transaction" message is displayed for amounts that should round up. This includes balance amounts with a "3," "4," "8," or "9" in the hundredths place. This occurs in the following scenarios:

- Refund

- Coupon only transaction

Scenario:

1. Add a grocery (tax free) dept item for 3.01

2. Tender $4.00 cash

Expected Results: Round down to 3.00 and give 1.00 change

Actual Results: Round balance up to 3.10 and give 0.90 change

WD # 336603

POS crashes with large orders and loyalty card used in the transaction.

The crashes happen at the end of the order.

Scenario:

1. Scan a valid loyalty card

2.Ring in 50 or more items, they can be the same or different make sure the total is over 150.00

3.subtotal the order

Expected Results: the order completes and prints

Actual Results: the POsw32 crashes and puts an error on the screen. Upon restarting of the POS application the transaction recovers and allows the order to complete