| ISS45 | Release Table |
| |
Name of Link: | FTP Site for 8.1.4.0-080 Patch |
| Code Distribution: | This release will be automatically applied to stores with the StoreNext Code Distribution System. | |
| POSTing Date: | 07-Aug-09 | |
|
ISS45 Version 8.1.4.0-080 Release Table Last updated August 3, 2009
See the Release Table below for a description of this planned release. This table below describes the current plan for the new features and faults to be addressed in this scheduled software release. |
||
|
||
|
Enhancement or Fault Number |
Item Description |
| E. R. 81216081 | Use a Variable percentage promotion tied to a specific department to discount items. This promotion will prompt for a percentage for a cashier to enter each time it is triggered with a coupon. |
| WD 10982 | Ability to Scan Member Card at the Pump with LPE |
| WD 11621 |
Multiple sessions of POSWR32 running: The 92R, M or U keyboard appears dead if multiple copies of POSW32 are running. The scale did not function when using the RS232 dual cable scanner/scale RS232 when there are multiple copies of the POSW32. TP3000XL SP3 was working after the weekend shutdown with this particular configuration. I signed off and the V8 server started the end of day and when the TP3000XL POST finished, the Fujitsu 92 key keyboard is non functional and shows two POSW32.exe running in the task manager. It looks like the end of day refreshed failed to shutdown the first POSW32.exe. Also blanked out the scanner and scale in the configuration and retested without the dual cable scanner/scale and the POST did work ok with only one copy of the POSW32.exe showing after the End of day or exit to POS function. Scenario: 1. Functioning 100% prior to exiting the POST to DOS. This is ISS45 keyboard function 1 (Exit to DOS). 2. Started up WinPoS again by clicking on the WinPoS Startup Icon and could not use the 92R, M or U connected keyboard when it came up. The keyboard appeared dead. Was able rouse the PC keyboard to sign on to the POST. 3. Signed on, noticed that the scale did not function and only the scanner was working. The scale part was on COM4 and the Scanner part was on COM5 being a dual cable unit. 4. Windows task manager showed that there were TWO POSW32.exe running. 5. Restarted the POST by doing a Microsoft PC restart from the desktop and when the POST came up, 92R, M or U keyboard and scale were functional again. 6. Used the Exit to DOS function to exit WinPoS. 7. Windows Task Manager showed that the POSW32.exe was still showing as a running task. 8. Started up WinPoS by clicking the WinPoS startup Icon and the 92R, M or U and the Scale were not working again. The task manager showed TWO copies of POSW32 running. Expected Results: There should only be one copy of POSW32.exe at a time. Actual Results: Multiple copies of POSW32.exe can sometimes be running causing some peripherals not to work like the 92R, M or U keyboard and the RS232 connected scale. |
| WD 11753 |
If a promotion is setup with a Credit program to generate a Fuel Voucher and the Group Type on the promotion is set to "By Value" the voucher will not print. If the Group Type is set to "Units" the voucher will print if only 1 item is sold, if more than 1 item is sold then the voucher will not print. If the 2nd threshold is set to 0 and multiple items are sold it will print the voucher. Scenario: 1.Setup a credit program for Gas Rewards 2. Setup a promotion with the credit program selected. 3.Set Group type to "By Value" Reward type to Credits Reward to 1 Threshold to 1 and 2nd threshold to 1 4. Set attachments. 5.Sell items and verify if voucher prints Expected Results: A voucher should print with the amount off based on amount of items sold. Actual Results: No voucher prints if Group type is "By Value" IF Group Type set to "Units" and 1 item is sold the voucher prints but if multiple items are sold no voucher prints |
| WD 11761 |
Credit card swipe on MRS attached to TeamKey causes Incorrect Card Type error on version 8.1.4.0 and higher Scenario: 1. Using Fujitsu D25 displays with attached TeamKey PIN pads and attached MSR and Key-locks with OPOS. NOT using MTX. Have a tender type built for every acceptable type of credit card along with card ranges for each tender and are maintaining a list of supported cards via the srvdig.qdx file. 2. In all previous versions of V8, up to version 8.1.3.0 they could ring up items, press the total key, and swipe a customers credit card on the attached MSR and the terminal would process the track 1 and track 2 data from the card and finalize the transaction under the correct tender type. After updating to version 8.1.4.0 they receive an Incorrect Card Type Press (C) to Continue error message. If they press the clear key the transaction will finalize correctly. If they select a card type before swiping the card the transaction completes correctly. Expected Results: Can still use the attached MSR for credit cards Actual Results: Get Incorrect Card Type error when credit card is swiped |