| ISS45 | Patch Table |
| |
Name of Link: | CD Only |
| Posting Date: | 01-Apr-04 | |
|
See the Patch Table below for a description of this release. This patch table includes a new Front Office and POST. |
||
|
Enhancement or Fault Number |
Item Description |
|
New Feature |
Add a parameter for Canadian Weights and Measures/scanning to process to be compliant. |
|
New Feature |
Cash Office rework to assist with displaying the Over/Short in shifts - does NOT use Delayed Balancing. |
|
New Feature |
Expiration Date masking for credit/debit payments. |
|
New Feature |
Add the current Coupon Table from the council for coupons 5, 7 ,8, 9 ,13 and 61. |
|
New Feature |
Modify the key/plug enquiry screen to look like a table and to match all additional functions that have been added. |
|
Enhancement |
GTIN support |
|
Enhancement |
Check Imaging via Epson 6000 Trans-Scan |
|
E.R. 809260301 |
The system will now combine MSU items ( 3 for $1.00) on the receipt if buffer printing activated. |
|
Fault 1187 |
Cashier Over short report is incorrect and does reflect accurate data for weekly/monthly/yearly. |
|
Fault 1543 |
On the MFS, perform an ROA or Payout. In the reference field type in a name with an apostrophe or comma, dash, etc. Press apply. System will ask are you sure and do you wish to print. No errors occur. However, print out is blank, viewing the Daily ROA/Payout report is blank and safe totals have not changed. If you do the same transaction WITHOUT special characters, the transaction is good and appears on reports. Either let the system allow the special characters or generate an error telling the user you can not use the characters. |
|
Fault 1719 |
Red Print on EPSON 6000II in ISS45 version
8.0.6.0-000 is not supported |
|
Fault 1817 |
When system parameter, "Perform
expansion of PLU input of 6 or 7 digits" is set to "Yes", a
6 or 7 digit PLU is not automatically expanded when trying to add an item
to a "Price List", using the Rapid Entry function in Price List
Maintenance. |
|
Fault 1839 |
loading file no.65:
qdx\poscpn.qdx |
|
Fault 1875 |
If the system parameter, "Mask Member Card" is set to "yes", pan masking of the member card does not print all characters of the member card on the customer receipt. For example, a 11 digit member card number will only print 10 digits on the customer receipt. |
|
Fault 1885 |
In V8.0.6.50, a bug was introduced that impacted the ability to create or process "single promotions" (promotions, offers or reductions). For more details, refer to Bug 1852. In V8.0.6.53, this problem was fixed...unfortunately, a new problem was introduced. The user is now able to create new "single promotions" and they execute properly at the POS terminal. However, single promotions that existed prior to the "Patch 53" upgrade, do not process at the POS terminal. The only way to "activate" these existing single promotions, is to edit the "promotion" (for example, change effective dates) at the MFS. |
|
Fault 1887 |
Customer
requested that Frequent Shopper 'like items' should be combined on the
receipt at the same time that is showed REG price and Sale price. |
|
Fault 1892 |
Corema - scanned FS card incorrectly sent as type M |
|
Fault 1893 |
Only the first 12 items display on a POST configured with fuel. The pump icons overlay on top of the short group page and if there are more than 12 items they cannot be viewed. Also, the scale weight and member card information do not display because of the pump icons. |
|
Fault 1914 |
Existing
Plu Batch only works for Unit Pricing. Create Plu batch as New Item. |
|
Fault 1924 |
Upgrading
from 8.4 to 8.0.6 and RBX - old promotions not deleted in QDX. Need to fix
the deletion of expired promotions on EOD from the QDX files. When the
store updated ISS45 to 8.0.6.XX, promos did not work totally until all
promos were deleted from ISS45 and re-applied from RBX. |
|
Fault 1928 |
The old parameter for ELDAT still exists in \system administration\technical support\technical parameters. This should be removed as all new parameters are in the General System Parameters folder. Having the parameter in 2 places is confusing and misleading. |
|
|
|