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

Compare with Current View Page History

« Previous Version 54 Next »

Coming next release

Order lines with quantity zero

(RTP-31448)

Trying to get Dispatch Suggestion and Delivery Suggestion. on order lines with zero quantity will result in getting 0 in the delivery confidence answer. Previously a DivideByZero Exception made the request fail.


Released 29.07.2024

Check If Lifecycle of the Startup in the DispatchService is Proper

[RTP-31455] 

Check If Lifecycle of the Startup in the DispatchService is Proper. Removed few dependencies which were unnecessary.


BlobStagingMerger needs an overhaul

[RTP-31485] 

This is a Tech Debt. Implementing overhaul on BlobStaginMerger  has decoupled from  Inventory.StockStatus.Export blob type, ensuring greater flexibility and enabling easy extension to support other blob types as needed.


 DispatchService failed at LrsGresvigProd

[RTP-25039] 

Verified triggering Inventory.StockStatus.Export blobs via FileService, confirming successful data import into staging tables (FlatBatch, FlatBatchJson), and verifying BlobStagingMerger updates to [dbo].[stock], along with scheduled stock exports. Ensured jobs are correctly enabled and operational


Prevent DivideByZero Exception 

[RTP-31448] 

Quantity with 0 value in the request will provide delivery alternatives for both Dispatch Suggestion and Delivery Suggestion.


Upgrade packages specific to test projects

[RTP-31803] 

Remove old postnord service agent repo

[RTC-19143] 

Filter out inactive stores in pacstores method

(RTP-26407)

Inactive stores are not returned as delivery alternatives in pacstores method.


Inactive items should be notDeliverable

(RTC-36773)

Inactive items will be under "notDeliverable" parameter in the response of /api/stock/{storeNo}/deliverability endpoint


obsolete hardcoded deliveryProducts removed 

[RTP-27378]

Remove obsolete hardcoded delivery products. Delivery products Click&Collect, Helthjem standard and Helthjem NA are removed from hardcoded values


Inventory management replaced with new Dispatch management project

[RTC-33073] 

Renaming to Dispatch Management which was earlier Inventory Management


expectedDeliveryDescription" value should be null

(RTP-26423)

Response parameter expectedDeliveryDescription value is changed from "2 timer" to ""(null). This value will be later configured dynamically.




Released 24.06.2024

Dispatch Suggestion splitting fix

(RTC-41696)

Splitting an order with multiple items is possible when the StockStoreNumber and StoreNumber in the used Rule are set different.



Released 10.06.2024

PAC from POS - PAC.CW isn't a delivery option when the stock is 0 or less

(RTP-30474)

Item Stock equals to zero or less than zero, will suggest PAC.CW as delivery option and Item stock greater than zero, will suggest PAC

Service configuration check for a specific tenant.

(RTM-4377)

There is an API method in DispatchService to check if the service is enabled and configured for a specific tenant.

Delivery methods for Dispatch Stores

(RTC-40013)

This is a new feature that can add a list of delivery methods for each store in the dispatch rule. The delivery method set at the store level overrides the common delivery method set in the rule.

Fix for "isFallback" parameter value in Dispatch Suggestion

(RTP-29846)

When using StoreStatuses in the request of Dispatch suggestion endpoint, "isFallback" parameter in the response will provide accurate value.

Fix in Dispatch Suggestion when there are no delivery products set up in dispatch rule

(RTP-29855)

When there are no delivery products set up in dispatch rule, dispatch suggestion returns the correct split suggestion for picking.



Released 18.04.2024

Return ProdConceptID in GetProducts, Delivery Overview and Delivery Suggestion

(RTP-29696)

When provider is Consignor (nShift) then ProdconceptID is returned instead of ProdCSID in the "code" and "deliveryMethod" fields in the methods GetProducts, Delivery Overview and Delivery Suggestion.



Released 16.04.2024

Dispatch Suggestion - Split deliverable order lines based on fallback parameter

(RTC-39872)

When the entire order cannot be fulfilled, based on fallback value, the following is returned in dispatch suggestion:

  • If Fallback is true, then we suggest the dispatchingWarehouse.storeNumber
  • If Fallback is false, then we don't give any suggestions.

A new field in the dispatch suggestion response called IsFallback is added. If this is set true, then we know it's because of fallback mechanism for non-deliverable items.

Split delivery options based on Item Availability based on order line

(RTP-28295)

Order is split according to the item availability when order consists of more than one item. Delivery options are suggested based on each order line.



Released 13.03.2024

Dispatch rule parameter for warehouse stock calculation (excludeFromStockCalc)

(RTP-28931)

A new dispatch rule parameter, excludeFromStockCalc, is introduced to control whether stock in the store defined in dispatchingWarehouse.storeNumber will be considered in stock availability calculation in Dispatch Service.

If excludeFromStockCalc = TRUE, dispatchingWarehouse.storeNumber will be included in the stock stock availability calculation
If excludeFromStockCalc = FALSE, dispatchingWarehouse.storeNumber will NOT be included in the stock stock availability calculation

This parameter is by FALSE by default.

ProdConceptID in createshipment

(RTP-27499)

When using ProdConceptID as the deliveryTypeMethod in the CreateShipment request, it no longer results in an error. Instead, the shipment is properly created with the specified ProdConceptID. The default value for deliveryTypeMethod was changed to pass ProdConceptID, instead of the previous ProdCSID in case of the TypeMethod not being specified in the request.



Released 01.02.2024

Web order order reassignment

(RTP-27119)

Orders placed to a webshop store will automatically be dispatched to a central warehouse. The central warehouse should be set as a dispatch store also for this to work. 

Extend createshipment method

(RTP-23391)

This change includes adding extra parameter to createshipment end point to get response with some data. Below parameters are added to the request and response of the endpoint:

  • TrackingURL (1- response will contain the url, 0- response will not contain tracking url)
  • DeliveryMethodType
  • OrderNo
  • PickupDt
  • Messages

This change also updates the order number in the references section of NShift portal.

GetDispatchSuggestionAsync fallback

(RTP-27140)

GetDispatchSuggestionAsync  will return default warehouse as the suggestion when fallback is set to true in the request and there are no other stores that can fulfill the order.

Delivery alternatives suggestion for split web orders

(RTP-26081)

Delivery alternatives are correctly suggested for a split order scenario, where a web order will be fulfilled by more than one store.



Released 14.12.2023

Get stock from InventoryService

(RTP-20320)

When changing stock in InventoryService, the changes are now also imported into the DispatchService, and reflected in the service's responses. 
The prerequisite for it to work, is to have the BlobStagingmerger and BlobStagingImport jobs from DispatchServiceIntegration LIP package enabled on a given tenant. They can be running with the default configuration.

Stock Deliverability method

(RTC-35970)

Introduced a new method to return if requested item/s and quantity are deliverable or not in a store: POST/api/stock/{storeNo}/deliverability

Deliverability for multiple items can be sent in a single request and the method returns a list of items with available quantity and grouped into deliverable or not deliverable. Items will be returned as notDeliverable if they do not exist in the store or available stock value in the store is less than the requested quantity.

Dispatch suggestion fallback to webshop 

(RTP-20269)

When there are no suggestions from dispatch suggestion and fallback is used, the orders fall back to webshop and webshop store is suggested.



Released 26.10.2023

Delivery alternatives suggestion

(RTP-25777)

When returning delivery alternatives, delivery suggestion now follows rules that are set in configuration (delivery products).


Released 13.10.2023

New method to get shipment

(RTC-12295)

The GetShipment method was added in order to allow for searching the NShift shipment information by using the ShipmentCSID number (assigned when the shipment is created). The method gives back data including date, place, ID, tag etc. and can be used to easily fetch information about previous shipments.


Released 24.08.2023

Upgrade to support end-of-life for TLS 1.0 and 1.1 by nShift

(RTP-23138)

.NET Framework for DispatchServiceIntegration was upgraded to version 4.8 so that the DispatchService jobs for transferring items, stock and store info will not be affected with the end-of-life for TLS 1.0 and 1.1 by nShift.

Reprint order labels

(RTP-22912)

ReprintLables method is added to the DispatchApi.Client, which makes it now possible to reprint shipping labels of already printed labels using nShift. If you are unlucky and run out of paper, you now have the option to print again.

Migration to .NET 6

(RTL-5397)

Dispatch Service module is migrated to .NET 6.



Released 31.05.2023

nShift: Print return label at the same time as shipping label

(RTP-19581)

When creating a shipment, it is now possible to print return label at the same time as shipping label.

Dispatch Suggestion logic (Distance calculation)

(RTP-21762)

Logic of dispatch suggestion has been improved. Postcode calculation has been fixed, so correct stores are now suggested.



Released 15.03.2023

Add support for collect in store, but with fulfillment from warehouse

(RTC-21083)

A new delivery type - Pay&Collect CW was added. It allows suggesting stores, that do not have enough stock, but where missing items exist in warehouse.

Support for DropPointId null or blank

(RTP-22522)

CreateShipment

It is now possible to set the DropPoinId parameter as NULL or not assign it any value.

[nShift] Create a table for storing actor and key

(RTP-21581)

[nShift] Change contracts to include storenumber

(RTP-21582)

[nShift] Implement using actor and key from new DS table

(RTP-21583)

It is now possible to add different actors and keys and assign them to a given shipment provider/store. Later the stores can be used in SubmitShipment, ReprintLabels, TransmitShipment.

PAC in delivery suggestion

(RTP-21316)

When using the delivery/suggestion method, PAC is now properly suggested when it was previously available in the overview.



Released 16.01.2023

Extend with pickuppoints - nShift

(RTP-19524)

Drop points lets the end-user select where they want to pick up their parcels.
DropPointId is added while creating a shipment. This later allows for printing labels with the pick up point address on them. 



Released 14.12.2022

Import items from ItemService.

(RTP-19545)

DispatchSerivce does now import items from ItemService.
Updates and additions is imported to database through the ItemImport job.
The service still support import from Chain Classic.

Import stores from StoreService

(RTP-19121)

New stores are now imported and updated from StoreService.

Added method TransmitShipments for sending consignments to carriers.

(RTC-26701)

A new method called TransmitShipments was added.
It needs to be called to make the consignments go to carriers, while the CreateShipment method is meant to only print now.



Released 19.10.2022

Add sender, receiver and phone when creating nShift shipments

(RTM-4710)

When creating nShift shipments it is now possible to finish the order with different delivery contact info than the one assigned to customer's account.
New delivery contact info is generated on the shipment label.

Reprint order labels

(RTC-23569)

It is now possible to reprint shipping labels of already printed labels using NShift. 
If you are unlucky and run out of paper, you now have the option to print again.


  • No labels