| ISS45 | ISS45 Release Table |
|
|
| Name of Link: | FTP Site for 8160-150 | |
| Code Distribution: |
This release can now be applied to stores via the Retalix Code Distribution System. | |
| Posting Date: |
November 5, 2013 | |
|
ISS45 Version 8.1.6.0-150 Release Table Last updated November 6, 2013 NOTE: ISS45 Release 8.1.6.0-100 and higher will require a change to the HASP key for Loyalty Sites. The ISS45 system will NOT work with Retalix Loyalty unless this setting is on. NOTE: Retalix Global Payments WinEPS Release 827.2 SP1 or higher is REQUIRED starting with the 8.1.6.0-080 release patch. See the table below for a description of the new features provided and faults addressed in this release. Information in this table prior to 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: many browsers do not support correct color and format printing directly from the Web. For best results, with your cursor highlight the section of the table you wish to print and copy to the clipboard. Then paste from the clipboard into a blank Word document and print the Word document to a color printer. | ||
|
Enhancement or Fault Number |
Item Description |
|
New Feature |
Support Quantity using Loyalty Discounts through POS function 1412. Unit Priced Items only. Split Priced Items will NOT work with this feature. (CRD 384652 / FSD 384652) |
|
WD 363728 |
Number of Min. before EOD continues in 24 hour store GSP setting - Change Description to SECONDS (Appeared in 8.1.7.0-060 as WD 363729) |
|
WD 382118 |
POS
Issue - DRE Support for NCR Printers with Void Transactions Needed including
reprint of a voided transaction.
When performing a Void Transaction on the POS the receipt
does not print. Once another transaction is rung, the receipt for the voided
transaction is printed and the receitp for the current transaction is
printed Scenario: 1. ring a
sale and tender it out, receipt prints 2.ring a
voided transaction, receipt does not print 3.ring a
sale and tender it out, the receipt for the voided transaction prints and
then the receipt for the current transaction prints. |
|
WD 386958 |
Crashed ticket recovery not working properly if crash happens during ticket finalization. Scenario: 1. Sell some items. 2. Tender with cash so that there is a change amount due. 3. Simulate a POS crash by setting a breakpoint and stopping POS during ticket finalization (after tender is entered.) I stopped it immediately after the reorg print transaction is written. 4. Re-start POS and allow it to auto-recover crashed ticket. Expected Results: Ticket is recovered and finalized. Ticket is complete in t-log and recovered records are marked as bad/do-not-process so that multiple media amounts are not reported in media reports. Actual Results: Customer reports were off by change amount of crashed ticket since the original change media record was not marked as bad during recovery. |