...
| Module | Description | ||
|---|---|---|---|
| POS API | Items blocked for sale and multipack items in POS API (RTP-16210) Items that are blocked for sale will get a specific error code in the response when trying to add an item to the shopping cart in POS API. This makes it possible to show a specific error message in the Shopping app. The response for blocked items will be "<RequirementFaultType>ItemIsStopped</RequirementFaultType>" When adding an items that also could be included in multi pack units, the shopping cart returned from the POS API will contain information about this. The response for items that also is sold in multipacks will be "<IncludedInMultipack>True</IncludedInMultipack>. This makes it possible to automatically show a quantity dialog for these items in the Shopping App. Caching of Klarna merchant key in POS WCF (RTP-17259) Changed MerchantID when order is updated from Web Shop. Loyalty coupons added as tender correctly displayed (RTP-16811) Adding loyalty coupons as a means of payment (tender, not subtotal discount) is correctly displayed in the cart and POSLog XML. | ||
| POS Import | Improvements for mix 35/41 from promotion module (RTP-17229) The following improvements have been done:
| ||
| POS Master database | Fix for method to fetch items with stock from POS Services (RTP-16977) A missing column was added to table SearchItemsWithChangedStock that caused exception when PosServices GetItemsWithChangedStock was called. Replication fail on some unfiltered publications (RTP-16937) A problem that caused some unfiltered replications to fail has been fixed. Import of MBXP items (RTP-16931) Since 'MbxpWeb' is used in the POS Master database, the itemType for MBXPwebsale items in dbo.ExtSaleProvider has to be defined to 'MbxpWeb' as well. When itemType in both POS Master and Item master are consistent, such items are properly imported to POS Master database. Import of campaigns on model+color (RTP-15206) Import of campaigns from the cloud promotion module now support the model+color level. This makes the import much faster than importing individual EAN/GTIN's. | ||
| JournalService | Fix for updating customer order id's in the sequence number table in database (RTP-15986) There is now done a fix related to customer order id's in the sequence number table in the journal database. So now all orders except orders that are created in POS will update the sequence number. 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).
|