Chain Web v. 2.10.
...
331 - next main release
| Status | ||||
|---|---|---|---|---|
|
Improvements
| Area | Description | |||||
|---|---|---|---|---|---|---|
| Customer order | Set original net cost price when returning items (RTC-41706) Net cost price in the return is the same as used in the original order. | |||||
| Dispatch order | Removing last line does not cancel dispatch order (RTC-42467) Dispatch order is cancelled after last normal item is removed from whole order in picking order. Rejected order is not visible in dispatch orders view in Chain Web. No validation of failed refund due to locked order (RTC-42012) When trying to refund order which has locked status, the user interface displays a validation message at the bottom of the site about the failed refund. Product description differs on templates (RTC-41100) Product description does not differ between OrderConfirmation and CreditNote templates. Orders don't close automatically when there is no more items to deliver (RTC-40707) Orders are closed automatically when all items have been delivered, also after items have been removed manually. Statuses in database are also updated properly. SKU for Click&Collect (Reserved&Collect) orders (RTC-40091)
| |||||
| Picking orders | Delay of picking order creation for specific order types (RTC-41290) The delay of picking order creation, by the PickingOrderProcessor job, only applies to the order types | |||||
| PickingOrderProcessor job | Picking order processor job saves partially modified data for picking order despite of exception (RTC-42952) Partially modified data is not saved by the PickingOrderProcessor job. PickingOrderProcessor job improvement (RTC-42482) The PickingOrderProcessor job does not stop processing pending events when one of them fails. PickingOrderProcessor job does not export picking orders when one of events processing fails (RTC-42291) PickingOrderProcessor job exports picking order to other systems instantly after processing each event, so it is done even if some of the events failed in the same job execution. PickingOrderProcessing job contains RIS orders that are trying to delete delivered order (RTC-41842) When user try to delete Click and Collect (RIS) order with picking order status set to delivered then Picking Order Processor job execute it properly with completed status including reject order message. PickingOrderProcessor job automatically reprocessing failed events (RTC-41492) PickingOrderProcessor job processes failed events with status "RetryPending", if no other pending events were found. | |||||
| Receipt journal | Improved search performance (RTC-41230) The performance when searching in the Receipt Journal has been significantly improved, and reduced the timeout occurrence. Vat rate with decimals on Receipt details (RTC-43255) VAT can be displayed with one decimal number in the receipt details in The Receipt journal view.
| |||||
| Scale labels | Convert scales to atte.dat files (RTC-35873) Exported from Item Management Strongpoint scales are now converted to atte.dat files on on premise server. Job to convert scale labels was renamed to LabelImport and can be configured to support both Strongpoint and Myhrvold scales. For Strongpoint scales, files are created per store and can contain more than one scale label and more than one item. Files are named atte.StoreNumber.TimeStamp and are saved in a configured folder. In first row, there are stored all required information from item-scale: if the scale label is new or removed, PLU, retail price, promotion price, status (0 if price is per Kg , 1 in all other cases), best before, tare, item group, storage temperature and origin. Next rows contain information on font size and weight declaration text. When scale is removed from label, created file contains only first row (with numeric data), which starts with letter R. If some of exported values from item have more digits than expected in file, then job finishes with status 'CompletedWithWarninigs' with clear warning message and file is not created. However, If more item-labels are exported in the same time, files will be created, but will not include scales from incorrect item. | |||||
| Users/Cashiers | Fix for: Import of user fails when long user name + update CashierNo (RTC-40630) StoreGroup with type CloudPermission is correctly created in the database and the job UserMerger is correctly executed when the username has more than 50 characters. |
...