Document status: RELEASED
Date:
Prerequisites are located in the menu on the left.
Improvements POS
Area | Description |
|---|---|
| General | Payment input field cleared correctly after member search (RTP-27435) When a member is searched for by registering SSN or mobile number or member number in payment input field in payment view, this field is now correctly cleared when search is done. Previously the registered number could still be present in the field when later adding e.g. Bank tender, making the payment fail. |
| Loyalty | Using CompanyID that generates the best bonus when doing member lookup (RTP-27347) Logic for using the CompanyID that generates the best member bonus, if member has several memberships, now works also when parameter 'MemberCardEAN29Codes' is deactivated. |
| Order | Recipient's data (RTP-27150) When creating a Web Order/Reserve & Collect Order in POS, the recipients name is shown correctly in receipts with customer information, picking lists, order confirmations, Dispatch Order screen in Chain Web, and in orders in POS. Information such as customer name, address, phone Number, and e-mail corresponds to the recipient's data. Required Chain Web v. 2.10.284 or higher! Fix for InvalidNumberFormat error (RTP-27421) InvalidNumberFormat error message is no longer entered when Customer Orders are created or during registration of picked Reserve & Collect orders. Required Chain Web v. 2.10.284 WebOrderAlternativeDeliveryMethod for Pay&Collect Chain Web orders (RTP-28075) When creating a web order then adding delivery details and selecting delivery method as Pay&Collect Chain Web, value set in WebOrderAlternativeDeliveryMethod parameter appears then in the Method of the delivery in POSLog. No default value of parameter |
| Payment | Customer can't pay with company cards when using local offer button (RTP-28117) Some rounding problems ended in that Customer couldn't not pat with company card. Changes is done to prevent this rounding problems. |
Improvement POS server
Area | Description |
|---|---|
| POS API | Time zone is missing (RTP-27927) Changed handling of timestamps in POS WCF, to ensure that timestamps are consistent in terms of using UTC offset across different request responses. |