You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

Document status: PLANNED

Date: 

Prerequisites are located in the menu on the left.

Encrypted digital signatures stored in Journal database

(RTP-26668)

Signatures from the Signotec pad will be encrypted and stored in the Journal database. Pos Services / ReceiptService has a new endpoint 'GetReceiptSignatures'  to enable fetching and decryping the signatures again to view them. The endpoint will return the encrypted signature and the corresponding encryption key.

POS Configuration
New parameter 'PublicKeyForSignatures' default empty - when specified is used by POS to encrypt the digital signatures from the Signotec signature pad. The value will be generated by Chain Web.

Improvements POS 

Module

Description

Bank

Missing CardIssuer when doing reversal in PSDK pay terminal solution (RTP-27761)

We have improved integration with PSDK pay terminal solution to secure that type of payment card used for the last payment also is used and saved to receipt if this transaction is cancelled afterwards.   

General

Putting receipt on hold no longer generates missing sequence numbers (RTP-27959)

When a receipt is put on hold this may no longer generate missing sequence numbers. For a short period of time this could happen due to previous changes.

Correct item line deleted even when item originally added by configured CTRL key function (RTP-27861)

When an item is added to receipt via a configured key on physical keyboard like e.g. PREH, and the item is immediately afterwards wanted to be deleted, the delete function will now delete the correct item line (the active line, which has focus). Previously an incorrect item line could be deleted in stead. This could happen if the configured key that added the item to the receipt was connected to the 'CTRL' function in parameter 'KayMap'.

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.

Item details

Hyperlinks and texts in Item Description (RTP-27730)

Hyperlinks and text descriptions can be separated by entering them in separate lines in Item Management.

Mobile payment

Svea payment tender will show a QR code on screen, with link to finish payment (RTP-27407)

When paying by Svea, and customer's information has been entered in POS, the message telling an SMS is sent to customer's mobile phone is shortly after replaced by a QR code, on both main screen and customer screen. This code may be scanned by customer with the mobile phone, leading to a link / website where the payment may be finished.

Improved handling of mobile payment attempts when PaymentService throws error (RTP-20209)

In situation where mobile payments like e.g. Vipps, Swish etc. is used, and PaymentService throws a 'TaskCanceledException', POS will retry the payment until successfully finished, or until cashier aborts the started payment. Both the retry attempts and the abort attempts will be verified being successful by POS. This will secure that payments are either finished or aborted in both POS and in mobile.

Orders

Order confirmation e-mail sending (RTP-27392)

Order confirmation for web orders is sent after payment has been finalized in POS.

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

Price calculation

Improvement in stored procedure 'usp_getDiscountGroupByArticle' (RTP-27995)

The stored procedure 'usp_getDiscountGroupByArticle' has be changed to prevent getting duplicate rows when item exist in another company but is not linked to a store. Previously any duplicates would cause an exception and the item could not be added to the receipt. This was a problem for both the POS WCF and POS API but not in POS.

Self-service

Configurable CartState for Datema self-service receipts put on hold (RTP-27698)

Self-service receipts created by Datema scanner may now be configured to be put on hold using the state 'InProgress' in stead of 'Suspended'. This will make Datema system able to interpret the receipt's status correctly, without any changes in Datema system. 

POS Configuration (new parameter): 'SetSuspendedCartStateToInProgress' (default 'False') - If activated, Datema receipts put on hold when scanners docked will get status 'InProgress' in stead of 'Suspended'. 

User interface

Error handling when POS is minimized (RTP-27406)

When POS is minimized and error is occurs in the background (when WPFPop-up appears) POS maximizes automatically. Cashier can take action and continue.  

Voyado integration

Changes in visibility and selectability for Voyado coupons where conditions are not met (RTP-25849)

When adding a member to a receipt all coupons for the current member will now be visible in the coupon select view regardless if any items has been added to the receipt. If the conditions for triggering a Voyado coupon is not met the coupon be visible but not selectable in the coupon select view. This goes for both manned POS and SCO POS. Previously the coupon would not be displayed until some item was sold and then would be selectable even if the condition for triggering the coupon was not met.

Improvement POS Server

Module

Description

POS Import

Improvement in handling VPI files in the error directory (RTC-32140)

Error handling in POS Import has been improved. The VPI error .txt files are removed from the Error folder after the insert to the database is successful.

Required

POS Import v. 4.0.64 or higher!

  • No labels