Document status: RELEASED
Date:
Prerequisites are located in the menu on the left.
Highlights | |
---|---|
Release version: 3.0.0.118 |
|
Sales hours for alcohol
(Work ID: 179804)
Start and stop time for sale of alcohol in relation to for example mobile holidays can be configured for specific dates in parameter RequirementConfigDates. The start and stop time configured on specific dates overrides the configuration for weekdays in RequirementConfig parameter. The configuration for dates is only for a specified year, so they will be used only once. New dates should be added to the parameter every year. The message shown in POS when the item cannot be sold will always be taken from existing parameter RequirementConfig.
Gate receipts for Checkmark gates
(Work ID: 179806)
Gate receipts for both ITAB and Checkmark can be printed from POS and self-service. New variables [SUBTOTAL] and [ITEMQUANTITY] can be configured in existing parameter GateReceiptHeader to display total item quantity and subtotal amount on the printed gate receipt.
Additional receipt for brokerage sale (postal items)
(Work ID: 175750)
In addition to marking printed lines regarding postal services on original receipt an additional receipt can be printed. The add-on receipt will contain VAT summary for the brokerage sale (postal items/services). a configurable title, top text and bottom text.
Example additional receipt:
Treatment code in ARTS POSLog XML
(Work ID: 177446)
Treatment code (Action_LineItem) from POSLog XML was added to ARTS POSLog XML as an extension for item transactions. The new parameter IncludeActionCodeExtension was added to JournalService (in ArtsConfigParams). It is set to False by default. When it is switched to true, the action code from POSLog is included in ARTS POSLog XML.
Sell digital gift card and send image on e-mail
(Work ID: 177902)
A digital representation of issued gift cards can be distributed to customers by mail instead of (or as a supplement) to the physical plastic gift cards.
The dialog to sell digital/plastic gift card can be configured to show a field for e-mail address. If an address is supplied, a mail with the gift card attached as an image will be sent to the customer.
This functionality requires the digital gift card module in Chain Web / EG Cloud.
Concession sale in POS
(Work ID: 177989)
Concession items can be sold in POS and reports in Chain Web can be used to see how much concession sale is done in each store. Selling items on concession will reduce capital costs.
An item is set as concession item in Chain / Item master and a flag "isConcession" is included in POSLog XML receipt when these items are sold.
Support for setting concession flag when paying customer order in POS will be delivered in a hotfix.
Improvements POS
Module | Description |
---|---|
Bank | Company card via Aera pay terminal (Work ID: 179799) Coop company cards configured in parameter "CompanyCardIssuer" trigger specific behaviour when used in Aera pay terminals. A dialog for entering a reference number and -text is shown in cashier mode and self-service. |
Klarna | Refund of Klarna v.3 web orders in POS (Work ID: 179189) Order paid in Klarna v.3 via POS API can be refunded in EG POS. |
Loyalty | Finish receipt when completely paid by bonus (Work ID: 177023) When member bonus is used to pay the entire subtotal, the receipt will be finished automatically. Previously, the cashier had to finish it by paying 0 cash. CoopID shown when scanning member card (EAN29) (Work ID: 179711) When member card (EAN29) is scanned, CoopID (external member number) will not be shown even if it is configured in parameter LoyaltyHeaderInSaleView. This improvement requires version 394 of MemberService. Show if member terms have been approved in sales view (Work ID: 179886) The "Terms Approved" field was added to the LoyaltyHeaderInSaleView parameter. The information about terms can be displayed in the header for a member in the sales view. MemberNumber from QR-code missing when offline (Work ID: 180317) When POS is offline and QR-code is scanned, member number and Coop ID are properly added to the POSLog XML and to ARTS POSLog XML. (CoopID in ExernalLoyaltyNumber, Member number in LoyaltyAccountID in ARTS) |
Mobile payment | Coopay cashback (Work ID: 182913) Cashback when using payment Coopay is now completely blocked if deactivated by existing parameter AllowCoopayCashBack. Previously, deactivation only suppressed automatic cashback dialogue for cashier but allowed cashier to enter a higher amount before pressing “Coopay” button. Now such attempt will show a message saying cashback is not allowed. |
Order | SMS not sent when deleting Click and Collect order (Work ID: 179741) We have fixed an issue related to sending SMS to customer when Click and Collect order is deleted. Sales channels in orders (Work ID: 179891) When cashier searches for order from backoffice, price channel and shopping channel are automatically set to the value from the order. This means that if you click-and-collect order through POS API with channel = "Web", and later fetch this order to POS and pay it, the price channel and shopping channel in the receipt will also be "Web. Any additional lines added in POS will get shopping channel = "Cashier". These changes require Chain Web 2.9.270 or Chain 2.1.1, patch 7 (depending on which backoffice application is used as order master). |
Improvements POS Server
Module | Description |
---|---|
POS API | Store Number when fetching gift card balance (Work ID: 152875) StoreIdentificator is a required field in method GetGiftcardBalance, but actually sending a storenum when AllowAnyStorenum parameter of the APIKey was set to False, would result in an exception. Issue has been corrected, so that getting gift card and credit note balance works with AllowAnyStorenum = False. The request is still required to use the store number specified in the APIKey parameter, but if the store number does not match the configured value, you will get an exception with an understandable error text, pointing out that the store number in the request was wrong. Update order date on checkout (Work ID: 179895) The CustomerOrderDate field in POSLog XML is updated when CheckoutCart and ReserveCartInStore methods are called to make sure that the order date is set to the date when the order is confirmed. Database index defragmentation job (Work ID: 142972) Improvements have been implemented for the IndexDefragmentation job, so it runs outside any transactions. The timeout was increased to a higher value so timeouts and rollbacks should not occur. Adding item to active customer order fails after cleanup (Work ID: 179698) We've corrected an issue where you could get an error in Chain Web when trying to edit order lines on a customer order if cleanup of receipts in POS API had run while you were editing. |
POS Services | Error message for BBS gift cards in POSLog processing (Work ID:164881) Previously, BBS gift cards sold through bank terminals could cause unnecessary error messages in the POSLog processor for Chain Web. These gift cards should not be imported to Chain Web, so they are now ignored. |
POS Master | Cleanup of items without relations (Work ID: 167382) Added 3 parameters in [staging].[DeleteExpiredPrices], @skipItemsNewerThanDays, @maxItemsToDeleteWithoutLinks, @maxItemsToDeleteWithDeletedStoreLinks which defines which items should be deleted from database. The procedure can be used manually to delete old and unused items in POS Master. |
MessageService database | Performance improvement for receipt cleanup (Work ID: 176455) An index was added to increase performance in cleanup of old POSLog XML's in the MessageService database. (SQL proc POSLog.usp_DeleteOldMessages). |
POS Import | Automatic resume of data import after restart of SQL Server (Work ID: 127986) LIP will automatically resuming import of data from backoffice after SQL Server has been restared. |
JournalService | POSLog XML envelope for subscribers (Work ID: 179561) We've fixed an issue where using OutputFormat other than LRSPosLog on POSLogBatch subscriber would result in an extra envelope around the actual POSLog when sending to the subscriber. This would mean you could only use this subscriber with LRSPosLog, and the actual output when using that output format, was not just the POSLog. With the improvements we've made, you can now choose which output format you want, and the output will be according to the configuration, instead of having a hardcoded override of the config. When upgrading JournalService to 3.75.164.0 or newer, the OutputFormat parameter for POSLogBatch subscribertype needs to be changed from LRSPOSLog to LRSPOSLogWithDataHolderGz for existing users. Otherwise the receipts will fail during processing in Azure. SkipTransform should also be set to False (default), but default version should be -1. |