Customer order - structured note (RTC-40479)

Structured note value length in CustomerOrder.OrderLineStructuredNote table was extended from 255 to MAX.

Search for customer orders by external order number (RTC-40201)

Customer orders can be found by searching for the external order number in POS.

Picking orders must be re-assignable to the store that rejected it (RTC-40005)

It is possible to automatically reassign orders to stores that rejected the picking orders.

Extend tracking number logic for dispatch orders (RTC-39802)

A tracking number in the form of a clickable link was implemented in the dispatch orders UI making it possible to follow the shipment progress. The tracking number value is displayed based on the OrderLineDeliveryTracking data and prioritized as followed:

• PackageTrackingNumber
• ShipmentTrackingNumber
• ExternalShipmentTrackingNumber

Exclude dispatching warehouse from stock calculation (RTC-39600)

The "Exclude webshop store from warehouse stock calculation" parameter was added to Dispatch Rule settings. It is set to False by default however it is possible to set its value to TRUE or FALSE in the Dispatch Rules user interface. 

Manage cashiers in Cloud (RTC-40341)

A new group store type with id:7 and the name CloudPermission has been added to the database. It is assigned to store groups that were created during the import of a user and are related to Receipt journal permissions. A user who has permission to Receipt journal at the team/profile level will be assigned this value at that level, and a new store group with the CloudPermission type will not be created. All store groups containing stores to which the user has access to the Receipt journal created so far have their type changed from configuration to CloudPermission. Store groups that were already created earlier and configuration is their correct type are not changed.  The Journal Access tab in Chain Web contains an option in which the user is informed that permissions are managed in the Cloud.
Prerequisite also mentioned in original story: A role in BackOffice must also have permission responsible for receipt journal.

Manage cashiers in cloud (RTC-26875)

Hashed Pin is imported from the cloud into Backoffice and is saved in a new column in the user data.
The login mechanism for POS and InStore App has been changed to verify the hashed PIN when a cloud cashier logs in.
A cashier created in the cloud with appropriate permissions can log into the POS and open the Receipt journal page in BackOffice. 
Support for the old flow still works and a cashier managed on the server and who does not have a cloud hashed pin can log into the POS correctly.
Receipt journal permissions are imported correctly to the server and the cashier can only see the stores he has access to. 
A new unique store group is then created for the user, which is assigned to him and stores he has access to are stored in it.