Coming next release
| Area | Description |
|---|---|
| Procurement API | API for item deliveries with given item and given store (RTC-42742) Endpoint (/api/gateway/Deliveries/[storeNo]/itemDeliveries) in Procurement Service returns order lines for the given item and store, in orders with status other than draft. Response contains: id (of order line, used for default sorting), orderNo, remainingQuantity, deliveredQuantity, deliveryDate, orderLineDeliveryStatus, orderStatus. OData is supported for custom filtering, sorting, response batching. |
...
Release 03.09.2024
| Area | Description |
|---|---|
| Order despatch advice import | Validations (RTC-42304) It's possible to import order despatch advice with item without assortment code. There is an information that order contains items that do not belong to store assortment. Created order has status confirmed. There is no validation of item-supplier link also. |
| Order lines | Performance of loading order lines (RTC-43127) Performance of loading order lines is no longer affected by number of order despatch advice lines and number of entries in order history. |
| System | Fix: external mergers exceptions (RTC-41300) If there are two purchase orders/order despatch advices/goods receipts being processed by merger, that refer to same stores/suppliers/etc. and first one has thrown exception, second one is then processed properly anyway. Items imported from item service are saved in procurement database with unit (Norwegian code) from the list: stk, m, kg, l, dm3. If item has assigned unit not from this list, its unit is saved as 'stk' as default. Units of existing items are properly migrated with an upgrade script. Quantity of order line and when receiving goods cannot have decimals when item unit is 'stk' (replaced existing rule for unit 'Pcs'). |
...