ISS45      ISS45 Release Table
     

Name of Link:  FTP Site for 8160-130
  Code Distribution:  

This release can now be applied to stores via the Retalix Code Distribution System.

  Posting Date: 

May 28, 2013

ISS45 Version 8.1.6.0-130 Release Table

Last updated June 21, 2013

NOTE: this ISS45 release was previously planned as 8160-120. 

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

Add support for FTP communication and APL processing through the SQLhuk.bat and WICCOMM.BAT.

(CRD 356432 / FSD 356432)

WD 356130

Commands used in the templates for target messages (this example) are not functioning properly.

Scenario: Set up target message promo and assign a template to print the target message

1. Edit the template that has been chosen to print for the target message

2. Insert an "L" before a line to cause the line to print in large print

3. Insert a "#Cut" into the template to have a cut done inside the template

4. Save the template

5. Ring up trans that will cause the target message promo to trigger, and to print out template as part of receipt data

Expected Results: The target message should print with large print where specified, and cut where specified.

Actual Results: The commands don't work.

WD 358405

Loyalty DRE 8.1.6.0-Tax Flags 5-8 are not being sent to DRE because they are not printing on the receipt.

Scenario:

1. Set up PLU's with TAX 1-8.

2. Have Dynamic Receipt turned on (Loyalty).

3. Ring the PLU's.

4. See that the Tax 5-8 characters are not printing on the receipt.

WD 358690

High numbered promotions in eWIC transactions crash posw32.

While testing promotions with eWIC in training mode, some transactions would cause PosW32.exe to crash with the message "POSW32.exe has generated errors and will be closed by Windows. You will need to restart the program. An error log is being created." Not all promotion transactions caused the crash and the crash only occurred when paying with eWIC

Scenario:

1. Create a promotion with the IDs in the 200000000s or 300000000s

2. ring a transaction that will trigger the promotion

3. tender to eWIC

Expected Results: transaction tenders properly

Actual Results: the posw32 crashes

 

WD 359183

Smart WIC: EBTWIC_Incoming.exe causes error during EOD with the new WICCOMM.bat running at EOD, if there are no states active.

This work was done so thet Smart Card States can FTP claims/APL/HCL/Reconciliations to and from ISS45. Also this will call the EBTWIC_Incoming to process APL/HCL during EOD. However if the store does not have a state active, the EBTWIC_Incoming.exe gets a 424 error Object required error. During an EOD, this error should be written to the log and suppressed. See attached screenshot.

Scenario:

1. Place the WICComm.bat and SQLHUK.bat in place

2. Make sure no states are active for Electronic WIC

3. Run EOD

Expected Results: Error should be written to the log and suppressed to allow the EOD to finish.

Actual Results: EBT WIC_Incoming displays error and hangs the EOD.

WD 360970

Prologic/Youtech a Frequent Shopper transaction is entered on the POS Terminal and totaled and tendered by Cash. Then, the next transaction entered is a CASH PURCHASE TRANSACTION (Check Cashing), the text coupons from the previous FS Trans.

a Frequent Shopper transaction is entered on the POS Terminal and totaled and tendered by Cash. Then, the next transaction entered is a CASH PURCHASE TRANSACTION (Check Cashing), the text coupons from the previous Frequent Shopper transaction are printed on the POS Printer at the end of the CASH PURCHASE TRANSACTION.

This only occurs with Frequent Shopper (member) transactions. Non-Frequent Shopper transactions print only the POS Receipt.

Steps to recreate:

Enter a Frequent Shopper (member) transaction.

Enter several items that will trigger a discount and will print one or more text coupons.

Total and tender by Cash.

Enter a CASH PURCHASE TRANSACTION (Check Cashing) for $10.00.

Tender CASH PURCHASE TRANSACTION.

WD 361997

8.1.7.0-Loyalty_LPE Ticket Spend Promotion is not excluding items by Dynamic attribute.

Ticket Spend Promotion is not excluding items by Dynamic attribute

Prom 2: Member Card Required - Online Only

Cond: Ticket Spend =$50.00; Exclude Dynamic Attribute - Mix&Match=100

Reward: Earn Points Mmbr Acct 1 = 5

Scenario:

1. Scan Member card

2. Sell between than $45.00-$49.00 in items that do Not have Dynamic Attribute-Mix&Match=100

3.Sell more than $5.00 in items that do have Dynamic Attribute-Mix&Match=100

4. Total

Expected Results: Promotion 2 does not trigger

Actual Results: Promotion 2 does trigger

Scenario 2

In ISS45:

1. Assign several PLU's to Mix Match = 2

In Loyalty:

1. Go to Campaign Manager

2. Select New Promotion

3. Select Single Condition

4. Give the Promotion a name

5. Next

6. Next

7. On the Conditions page, change trigger type from "Quantity" to "Ticket Spend"

8. Enter 10.00 for the Trigger Value

9. Open Item Search

10. Open the first drop down that says "Items" and change it to "Attributes"

11. Hit the "send down" button to the right. A new screen will open with Dynamic Attributes

12. Select the Mix and Match field and enter 2

13. Click out of the field and then Apply

14. Send the Mix and Match selection down with the "down arrow" to the left and click Apply

15. You will notice this Mix and Match will be added to the promotion with a red X beside it (This means it is excluded)

16. Click Next

17. On the Reward page, choose Amount off and set it to a value of 2.00

In ISS45:

1. Once the promotion is on the lane, ring up the items in Mix and Match = 2 until you reach $10

Expected: The promotion will not be triggered

Actual: The promotion will trigger

WD 363006

U-Scan does not display the Drivers License screen when age restricted item is scanned.

Scenario #1:

1. Turn on Frequent Shopper in dealerconfig.exe to scan and enter

2. Turn on Frequent Shopper to prompt at U-Scan in GSP

3. Press non member button to accept default FS #

4. Scan grocery item

5. Scan age restricted item

Expected Results: U-Scan displays age restricted screen to alert customer.

Actual Results: U-Scan tells customer to place item on scanner/scale. Attendant gets prompted to input date but hit NO. Customer can rescan age item and now U-Scan displays Drivers License screen properly.

Scenario #2:

1. Turn on Frequent Shopper in dealerconfig.exe to scan and enter

2. Turn on Frequent Shopper to prompt at U-Scan in GSP

3. Press non member button to accept default FS #

4. Scan age restricted item as first item

Expected Results: U-Scan displays age restricted screen to alert customer.

Actual Results: U-Scan tells customer to place item on scanner/scale. Attendant gets prompted to input date but select NO. ISS45 is at the Frequent Shopper prompt so when customer scans age item attendant is alerted that it is invalid card. U-Scan needs to start a new order. The original Freq Shopper info is still displayed on U-scan Screen.

WD 363162

8.1.7.0-Extra Spaces in Field Names of Summary Template causing bad communication to DRE.

Using a template created as a part of an enhancement back in 03. The template is call _SUMM_RPT2. As a part of this template, several fields were introduced. The fields are attached (PC_8_4_2_51_0002.txt). In this template, all of the field names are saved as 10 characters long. The issue with this is that when the field name is not actually 10 characters long, I am receiving additional spaces after the filed name as a part of the field name. This results in an inability to line up the field name with what is the field name in DRE.

For example:

"SAVNGS_TTL" is 10 characters and is sent as 10 characters

"MPROM_TTL" is 9 characters, but is sent as "MPROM_TTL "

"CPNS_TTL" is 8 characters, but is sent as "CPNS_TTL "

See posTransaction-ISS45.xml for an example of the bad fields. This works properly with StoreLine using the same template import (see posTransaction - StoreLine.xml). Also attached is the template import being used (pw_b_001.tpl), along with instructions on how to do the import (Template Summary Report 1 and 2 import instructions for ISS45.docx) and the original FSD (000679_FSD - Savings Breakdown on Receipt.docx).

WD 363446

Occasional receipt corruption with sort receipt enabled.

Occasionally with sort receipt enabled, the resulting receipt will contain entries from other older transactions, the items will be out of order, under the wrong heading, etc (see attachment for example). We've never been able to reproduce this in the lab, however, we have had a constant stream of examples from the stores.

Scenario:

1. Unable to be reproduced. QA testing should ensure that there is no negative impact from the change. I would recommend also checking in self-checkout environment, with and without DRE where appropriate, etc.

Expected Results: Receipt should print correctly

Actual Results: Receipt is printed out of order, items missing or added from other orders, department headings incorrect.