| ISS45 | ISS45 Release Table |
|
|
| Name of Link: | FTP Site for 8170-060 | |
| Code Distribution: |
This release can now be applied to stores via the Retalix Code Distribution System. | |
| Posting Date: |
September 20, 2013 | |
|
ISS45 Version 8.1.7.0-060 Release Table Last updated October 8, 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 |
EBT Balance should NOT display on the customer display per Federal Regulations. Per federal regulation:7 CFR 274.12 (h)(7)(I):(7) POS Terminals shall meet the following requirements:(I) Balance information shall not be displayed in the screen of the POS terminal except for balance inquiry only terminals. (CRD 334239 / FSD 334239) |
|
New Feature |
Pending store certification by the state of West Virginia. Support for Virginia eWIC APL processing. (CRD 351633 / FSD 351633) |
|
New Feature |
Add GSP - "Accept promotion coupons at any time during itemization" and POS support of this function. (Appeared in 8.1.6.0-140 as CRD 377587) (CRD 377588 / FSD 377588) |
|
Updated Feature |
POS change to support DRE versions above 304. (CRD 367460 / FSD 367460) |
|
WD 284541 |
Randomly a record will not be written to SQL. This seems to be a timing issue, and has not been able to be reproduced in the lab. |
|
WD 284546 |
SmartCard WIC EBT - HCL file should be verified against the same process as the APL file is verified. (Appeared in 8.1.5.4-100 as WD 284524 and in 8.1.6.0-070 as WD 284545) |
|
WD 337802 |
U-Scan: Alternate Customer Look up function does not work on a U-Scan attached to a Loyalty Server. U -Scan: Alternate Customer Look up function does not work on a US attached to a Loyalty Server. Assigned Function 1441 - Alternate Customer Lookup to the MenuSys.mac. When in direct mode, the Alternate Customer Lookup will not prompt a Customer list if there are customers with the same Alternate Customer Lookup number.Scenario: 1. In direct mode press Alternate customer lookup Expected Results: A list of all the customers with the same Alternate customers lookup. Actual Results: Nothing appears |
|
WD 350435 |
U-Scan Penny Rounding issue: Sometimes the receipt prints at the Attendant station and it should print at the robot. U -Scan Penny Rounding issue: Sometimes the receipt prints at the Attendant station and it should print at the robot. Set the item to 2.07 - rounding is set to round down to nearest nickel therefore down to 2.05 in this case.Scenario: 1. Scan item of $2.07 2. Tender sale 3. Insert $0.05 4. Insert $2.00 Expected Results: Receipt should print at Robot Actual Results: Tendering with a .5 coin and a 2.00 coin - transaction finalizes but prints on the Attendant station (Appeared in 8.1.6.0- 110 as WD 350428) |
|
WD 356131 |
Commands used in the templates for target messages 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: target message should print with large print where specified, and cut where specified. Actual Results: The commands don't work (Appeared in 8.1.6.0- 130 as WD 356130) |
|
WD 357984 |
Balance Innovations - pickup fails on interface function "Pickup". |
|
WD 359184 |
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. (Appeared in 8.1.6.0-130 as WD 35 9183) |
|
WD 359704 |
eWIC free item promotion amount is being apportioned between eWIC and non. Scenario: 1. create a group promotion - reward type free item. threshold 1 for each group. link an eWIC item to group 1 ( Multigrain Cheerios 1600068780) Link a NON eWIC item to group 2 ( Frosted Cheerios 1600027561) apply reward calc to group 1 2. Purchase a group 1 item 4.25 3. Purchase a group 2 item 4.25 4. Tender to eWIC 5. 2.12 is sent to eWIC. 2.13 remains to be paid with a non eWIC tender Expected Results: the full amount of the free item sent to eWICActual Results: the discount is divided |
|
WD 363165 |
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=100Reward: 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 triggerScenario 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 (Appeared in 8.1.5.4-110 as TD 304191 and in 8.1.6.0-130 as WD 361997) |
|
WD 363167 |
8.1.7.0-Extra Spaces in Field Names of Summary Template causing bad communication to DRE. Using a a template created as a part of a SN 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 " (Appeared in 8.1.5.4-110 as TD 364561 and in 8.1.6.0-130 as WD 363162) |
|
WD 363447 |
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. As part of SR 19283, I added a WPPM_empty_file(pd.QDX_RCPT_EJ_FILE) call inside of add_2_Rcpt_EJ_file() when we are adding the first item to the receipt file. This resolved the issue in one store and there were no reported side effects. WFM is currently rolling this patch out to all 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.(Appeared in 8.1.5.4-110 as TD 364555 and in 8.1.6.0-130 as WD 363446) |
|
WD 363729 |
Number of Min. before EOD continues in 24 hour store GSP setting. GSP Setting for Number of Min. before EOD continues in a 24 hour store....Amount of time can be changed but no matter what the setting is, the EOD will wait 15 min Scenario: 1. Set GSP for Number of min. before EOD continues in 24 hour store... 2. Enter 5 min 3. Run EOD Expected Results: The EOD should pause the amount of time that is defined in the GSP setting Actual Results: The EOD always waits 15 min no matter what the setting is. (Appeared in 8.1.6.0-140 as WD 363728) |
|
WD 363762 |
U-Scan is not displaying the Driver's 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. (Appeared in 8.1.6.0-130 as WD 363006) |
|
WD 364020 |
Debit tender with assigned key, defaults to the first listed debit tender in tender maintenance. Debit tender with assigned key will default to the lowest number of debit tender no matter what tender the key is assigned to. Scenario: 1. Set up debit tender #25 2. Set up debit tender #30 3. Assign key on POS to specific tender #30 4. ring up order and total. 5. use tender key for tender #30, and POS will default to the lowest tender on the list, #25. Expected Results: Assigned key should use the defined tender Actual Results: Assigned key still defaults to the lowest tender in the list. |
|
WD 368359 |
Getting automation when doing any type of file maintenance on LFS and if loaded as an MFS2. Scenario: 1.Go to plu managemet 2.Do a price change and update 3.Screen displays error 4.After clearing the error a few times, continues on 5.MFS1 does get updated. Happens with cashier maintenance, tenders, etc. Expected Results: Update toMFS1 and continueActual Results: Automation error displaysAppeared in 8.1.6.0-1 40 as WD 368358) |
|
WD 369971 |
MICR'ing a check that has spaces and using the enhanced bad check file does not block check. with IBM 300 E4A, 4610-2CR. When MICR'ing a check that has spaces and using regular bad check file the check works as expected. When using the enhanced bad file the check goes thru- when entering manually using enhanced bad file it works as expected. Scenario: 1. Add the check account number to enhanced check file. 2. Micr a check with spaces in the account number Expected Results: Check is blocked. Actual Results:Check is accepted. |
|
WD 371053 |
When making an in house charge payment, EBT foods tamps are allowed to make payment and should not. Scenario: 1.Set up function 819 as charge payment 2.Select that function on keyboard 3.Follow process until tender numbet is requested 4.If EBT food stamp tender is selected, it gets approved Expected Results: Should NOT be able to make an inhouse charge payment using EBT Food StampsActual Results: Tender is allowed, payment is made and the customer EBT FS account is reduced by the payment amount.(Appeared in 8.1.6.0-140 as WD 371051) |
|
WD 374670 |
U-Scan dispenses change from previous transaction also in the next transaction. Scenario: 1. Ring an order and cash tender that has change due 2. Do a duplicate receipt reprint 3. Ring another order and tender credit card Expected Results: Change due from previous order is not dispensed Actual Results:Change due from previous order is dispensed (Appeared in 8.1.6.0-140 as WD 372872) |
|
WD 375411 |
SmartCard WIC EBT Claim File: Sub Categories are combining into one record in the claim file. When two jars of peanut butter are sold and used on a card that had one jar in cat 6 subcat 2 and 2 jars in cat 6 subcat 0; one jar should have come from cat 6 subcat 2 and the other jar from cat 6 subcat 0. The card was decremented properly but in the claim the E3 record showed both coming from cat 6 subcat 2. Scenario: 1. Sell two WIC items, where one falls in subcat 2 with only one quantity available and the other then falls through to subcat 0. 2. Finalize the transaction and tender with WIC EBT. Note: The transaction should ring up normally. 3. Perform an EOD to create the claim file. 4. Open the claim file created. Expected Results: You should see two entries for the items, one in subcat 0 and the other in subcat 2. Actual Results: Only one record exists. (Appeared in 8.1.6.0-140 as WD 37 5410) |
|
WD 375744 |
*Fuel* PAP tender is not recorded in TLOG or Media Sales correctly. Scenario: 1. Use a Gift Card to purchase fuel at pump 2. After the tender is finalized, go to Media Report and see no Gift Card tender 3. In TT, the tlog shows the tender is Credit but the media type is Gift Card Expected Results: The gift card will report to the Gift Card tender Actual Results: The gift card reports to credit |
|
WD 375998 |
"Swipe Member Card" Keyboard Programming #932 causes a 2 minute delay at the POS. "Swipe Member Card" Key (Keyboard Programming #932) assigned to the keyboard, the "SWIPE MEMBER CARD" screen shows but user can't scan or manually enter the card for exactly 2 minutes. |
|
WD 377479 |
PLU record gets into transaction file with no completion record and causes sales to be overstated. Media is correct. (Appeared in 8.1.6.0-140 as WD 377478) |
|
WD 379948 |
Smart Card WIC: Pan Length field should be read from the State Maintenance for each state, but the PAN field should be leading 0 padded to 19 always. The Problem : Smart Card WIC: Pan Length field should be read from the State Maintenance for each state, but the PAN field should be leading 0 padded to 19 always. This is how it should be written to the claim file. Example for the state of Wyoming: D4000002022016 00050534957000234320097. The 3 red 0's are the padding to 19.Scenario: 1. Ring Smart Card WIC sale 2. Tender Smart Card WIC 3. Run EOD 4. View Claim Expected Results: The PAN length field should be read from State Maintenance the PAN field shoud always be padded to 19.Actual Results: The PAN field is truncated to what the PAN length field is written. |
|
WD 380091 |
SmartCard WIC EBT - Claim file should use 'System' Date in Header and Trailer records as well as the Claim file name. (Appeared in 8.1.6.0-140 as WD 380090 and 8.1.5.4-080 as WD 284256) |