| ISS45 | Release Table |
|
| |
Name of Link: | FTP Site for 8.0.8.1-090 Patch |
| Posting Date: | 15-Oct-04 | |
|
See the Release Table below for a description of this release. This release table below includes Back Office and POST changes.
|
||
|
Enhancement or Fault Number |
Item Description |
|
New Feature |
USCAN � the 101 keyboard will now be recognized at the USCAN attendant station |
| New Feature | CDS/QDX � an internal utility will be added to the ISS45 upgrade procedure - this utility will check upon upgrade if certain QDX files are larger than the default � CDS will NOT upgrade those QDX and preserve the data. |
| New Feature | Custom Weekly Account Report - CWAR (Code only -- not generally released. Support not yet available.) |
|
WD 5262 |
:Fuel - Reprint PAP receipt on Axiohm 760 printer doesn't duplicate the entire receipt. Scenario: 1. Do PAP transaction 2. At POST select "Reprint" and select pump#. Expected Results: Receipt printed at pump will be duplicated at POST printer Actual Results: Receipt is duplicated with the following differences The last 6 lines of the receipt at pump are missing from the receipt printed at POST TOTAL SALE ---------------- Terminal: Approval # REF: and trailer Message |
|
WD 5263 |
Fuel - Reprint PAP receipt on Epsom H6000II printer doesn't duplicate the entire receipt and the print lines are not formatted correctly (wrap). Scenario: 1. Do PAP transaction 2. At POST select "Reprint" and select pump#. Expected Results: Receipt printed at pump will be duplicated at POST printer |
|
WD 5292 |
Secondary ID is not populated through to the Member screens on Front Office Scenario: 1. Run the batch with Member secondary ID Expected Results: Secondary ID in the LOYAL_CUST table is updated. Actual Results: Secondary ID in the LOYAL_CUST table is not updated |
| WD 5322 |
USCAN -CPU usage by the PosW32.exe increases to 100% on USCAN direct mode when using the keyboard. ___________ Scenario: 1. Start USCAN and go to direct mode. 2. On the attendant station - select a department 3. At the prompt to enter the amount, hit a key in the PC keyboard Expected Results: WinPOS should accept the keystroke Actual Results: WinPOS doesn't recognize the keystroke and the posw32.exe enters a loop that uses 100% of the CPU |
|
|
|
|
|
