| ISS45 | ISS45 Release Table |
|
|
| Name of Link: | ||
| Code Distribution: |
This release can now be applied to stores via the Retalix Code Distribution System. | |
| Posting Date: |
April 10, 2015 |
ISS45 Version 8.1.7.0-180 Release Table
Last updated April 24, 2015
|
NOTE: ISS45 8.1.7.0-150 and later require the ProLogic/YOU Tech/S&H/GreenPoints option to be set on the HASP keys. ISS45 will not work with Prologic/etc. without HASP key support. NOTE: ISS45 8.1.7.0-150 and later require the Self-Checkout option to be set on the HASP keys. The ISS45 system will not work with any self-checkout system without HASP key support. NOTE: ISS45 8.1.7.0-140 requires LPE Release 10.1.187, which is provided with the 8.1.7.0-140 ISS45 patch install. NOTE: ISS45 8.1.7.0-130 and later require Fuel release 8170-130 (or later). The Fuel release is available by clicking above or from the Fuel Maintenance Page. NOTE: ISS45 8.1.6.0-100 and later require the Loyalty option to be set on the HASP keys. The ISS45 system will not work with Retalix Loyalty without HASP key support. The table below provides descriptions of the new features provided and faults addressed in this release. Information prior to this software release is provided in order to assist dealers in their planning, and while they are not commitments, this list represents StoreNext's best view at time of posting regarding highly likely new feature content and faults most likely to be addressed. Printing Instructions: some browsers may not support correct color and format printing directly from the Web. You may also highlight the section of the table you wish to print, copy to the clipboard, then paste from the clipboard into a blank word processing document and ouput to a color printer. |
|
Enhancement or Fault Number |
Item Description |
| Updated Feature |
Support of Windows Updates Windows updates were applied 4/6/2015 to the following system types MFS1 - Equus Nobilis running Windows 7 POS - Fujitsu 300 - WePOS |
| Updated Feature |
The 8.1.7.0-180 patch is being released and has been tested with the
following MTX dlls: Connected Payments: MTX_EPS.dll - 828.1.11.625 MTX_SE.dll - 828.1.0.3 MTX_POS.dll - 828.1.0.98 WinEPS: MTX_EPS.dll - 828.0.1.372 MTX_POS.dll - 828.0.1.207 |
| WD 426176 |
Cashiers have been being prompted to change their password on a daily basis. Site instituted a 90 day cashier password policy requiring passwords be changed every X days. After EOD ran the next morning they were required to change password even though GSP was set to 90 Days. Cashier changed the password and then after EOD the next morning they were prompted to change password again. Scenario: 1. Set GSP in General Parameters \Store\POST\Operational\secure\sign off\sign on\No. of days for password = 90 2. Have cashier signed in and running with a password other than 0. 3. Sign out cashier and declare/lock till. 4. Run an EOD 4. Sign cashier back in Expected Results: Cashier will be prompted to change password after X days set in GSP is reached. Actual Results: After EOD ran the next morning they were required to change password even though GSP was set to 90 Days. Cashier continues to be prompted to change password the following day also and this continues. |
| WD 427874 |
U-Scan - Scanning a frequent shopper card after items are rung results in
incorrect discounts. When Frequent shopper is setup using X for $Y and the frequent shopper card is scanned after items are rung the discount is incorrect. Scenario: 1. Setup PLU 11 in item maintenance using a Frequent Shopper X for $Y discount with a regular price of $4.00 and a Frequent Shopper X for $Y set for $3.00 with Item Limitation = 1 and FS Quantity = 1 2. Set GSP, Reprocess at Late Swipe = Yes 3. Set GSP, Prompt for Frequent Shopper on U-Scan = Yes 4. Set GSP, Do not prompt for Frequent Shopper at beginning of ticket = No 5. Ring up PLU 11 6. Scan Frequent Shopper Card 7. Press Pay Now Expected Results: Should be $1.00 discount Actual Results: $3.00 discount is applied and it should only be a $1.00 discount. |
| WD 428137 |
If LOYALTY is turned on, and "Catalina" is turned on in POS Configuration,
the POSW32 will crash when a promotion is rung. Upgraded customer from 8170-090 to 8170-140. After upgrade of Winpos and applying the Loyalty patch per instructions, they are receiving POSW32 errors when an item is scanned that triggers Loyalty savings. POS will run fine until a promotion is rang in and attempts to activate savings. Scenario: 1. Have Loyalty turned on. 2. In POS Configuration, have "Catalina" selected. 3. Ring a sale at the POS that has a Loyalty Promotion and the POS crashes with error. |
| WD 428169 |
"Manual Price" or "Price Verify" conflicting with "Return Code" and
Reprocess on Late Swipe. Scenario: 1. Set "Reprocess on Late Swipe" to YES 2. Set a PLU with "Manual Price" or "Price Verify" checked 3. Set "Return Code" to any code 4. On the POS, ring this PLU 5. Change the price 6. Swipe the member card. Expected Results: The price will stay the same and the member card will be applied Actual Results: The price of the item will revert back to it's default price. |
| WD 428980 |
Recall of Fuel Prepay with Member Card Late Swipe shows no fuel transaction
in ticket. Scenario: 1. Retalix Loyalty 2. Reprocess ticket at late swipe = Yes 3.Sell fuel prepay 4. Scan Member Card 5. Tender 6. Pump fuel 7. Recall prepay at POS Expected Results: Fuel sale will be pulled into current ticket. Actual Results: No fuel sale is pulled in. Ticket total = $0.00. |
| WD 429095 |
EWIC- Getting over tender message and some declines when tendering EWIC on
some transactions (West Virginia). Cost Plus store. Some EWIC transactions approve and others decline. Scenario: 1. Ring up items 2. EWIC tender Expected Results: Ewic items are tendered without issue. Actual Results: EWIC gets declined sometimes with over tender message. |
| WD 429246 |
Prepay recall with Loyalty cents-off promotion sells for non-discounted
amount at POS. Scenario: 1. Retalix Loyalty promotion for 25¢ off per gallon 2. Swipe a Member Card 3. Ring $15.00 Pre-Pay 4. Tender to CASH 5. At the pump, prices roll back .25¢ for the Loyalty Discount. Grade was $3.50/GAL, then reduced to $3.25/GAL. 6. Pumped up to $10.90 7. At POS, RECALL PRE-PAY 8. Receipt shows: 3.353 Gal @ $3.500/Gal $11.73 Balance Due $11.73 Cash $15.00 CHANGE $3.27 Expected Results: Customer receives $4.10 back in CHANGE (10.90 Pumped – 15.00 Pre-Pay). Actual Results: Customer receives $3.27 (not getting the discount). |
| WD 429361 |
Online WIC: Voiding a WIC tender when using cost plus with online WIC will
give incorrect total due. Best tested using a mixed basket. If there is an
item WIC did not pay for at tender time and the cashier needs to void the
item, the WIC tender needs voided then the unpaid WIC item. This causes the
Balance due to be incorrect. Scenario: 1. Ring a sale of WIC items and 1 item that WIC will not pay for 2. Tender WIC 3. Return to sale and void WIC tender 4. Return to sale again and void item WIC did not pay for Expected Results: The balance due is still more that what WIC will pay for. Actual Results: Balance Due should be only total of WIC items. |
| WD 429945 |
Cancelling Cash Back results in Over Tender Not Allowed error and cancels
tender. Scenario: 1. Ring some items 2.Tender with EBT Cash (TAC=B/ G$FjL>Z) 3. When prompted "Do you want cash back?" choose Yes. 4. Select a Cash Back amount. 5. When prompted if new total is OK, choose NO. 6. Cashier sees "Customer Requests Different Amount" prompt. Enter the ticket Balance Due. 7. Customer is again prompted "Do you want cash back?". Choose NO. Expected Results: Customer should be prompted if the new amount (actual ticket balance) is OK. Upon answering YES, the ticket should finish normally. If the answer NO, they should be returned to the "Do you want cash back?" prompt. Actual Results: Cashier sees "OVER TENDER IS NOT ALLOWED! Hit (C) to Continue" error. Upon pressing Clear, the tender is cancelled. Notes: The cashier prompt for a new amount should only apply if using Cashier Cash Back in the TAC. The "Over Tender is Not Allowed" message is only applicable in that scenario, as well. |