Document status: RELEASED
Date:
Prerequisites are located in the menu on the left.
Improvements POS
| Module | Description |
|---|---|
| Coupons | Coupon discounts in combination with mix and campaigns (RTP-16387) When combining a coupon discount with a mix where you by x and get one for free, and a campaign on the same item, this could result in wrong price calculation. This has been fixed to the customer does not get too many free items according to respective coupon and mix rules. |
| Receipt | Mix 24 in combination with line discount (RTP-16737) There has been done a fix for mix 24 in combination with line discount on articles that starts with a 20-code. Earlier when selling an item that had this combination, it would not be visible on the printed on receipt. |
| Self-service | Do not fetch loyalty number from CoopKey QR code (digital age control) (RTP-17144) When scanning a CoopKey QR code in self-service POS, used in accordance with digital age control, loyalty number from QR will not be added to receipt. This is due to loyalty number tag in CoopKey QR may have a value even for non members, who otherwise would get member benefits they are not entitled to. Changes have effect when CoopKey QR tag 'B' = '2' only. Messages shown to user when item quantity is limited (RTP-16936) For items which are allowed to be sold only with a limited quantity explaining messages is shown to user. These message texts, shown both in cashier mode and in self service mode, will be different based on the reason why quantities are limited. Item quantity may be limited due to either items are linked to a specific requirement ID, or they may be limited due to containing identical active substances. The latter typically affects medical products. |
Improvement POS Server
| Module | Description |
|---|---|
| JournalService | Fix for updating customer order id's in the sequencenumber table in database (RTP-15986) There is now done a fix related to customer order id's in the sequencenumber table in the journal database. So now all orders except orders that are created in POS will update the sequencenumber. Previous the number would be set to the highest number, regardless of where the order was created. This would cause problem when reinstalling POS, because store central database would be updated with this number (and get in conflict with number series from Chain/WCF). PS! For this fix to be effective it's important to do cleanup/refresh in the [Lindbak POS Journal].[dbo].[sequencenumber] table in the database. Where the 'NumerSeriesId' = 6, just set 'LastNumber' to 0. ** |