Cashier and user improvements (RTC-43142)

• Cashier cannot be created with a nonpositive cashier number.
• The user name cannot contain "/", "\" or space characters.

Modifying count groups (RTC-43184)

Count groups created by HQ users can no longer be modified by non-HQ users.

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.

Pickup time in Click and collect orders (RTC-43710)

A "Pickup date" column has been added to the customer orders view in Chain Web.
The column is hidden by default, and must be added via configuration mode.

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)

• SKU is properly saved in database in CustomerOrder.OrderLine table.
• PickingOrder job properly export picking order with not null SKU field.

Email sendout is trigerred before db transaction is commited (RTC-42873)

Email and SMSs sendout is properly triggered after the database transaction is committed. That means the GenerateMessage job is triggered after the complete PickingOrderProcessor job run. 

When returning a DispatchOrder in Chain Web no refund to the customer is done in Klarna (RTC-42247)

Klarna payment assign to certain dispatch order is properly refunded when returning items in dispatch order in Chain Web.

Payment method is not added to receipt pdf in PAC "ready for pickup" email (RTC-39343)

• Attached pdf in PAC "Ready for pickup" email contains payment method for prepaid orders (both created in physical store and on the web)
• Payment methods in attached pdf are fetched from PaymentAuthorizations when order has no attached Tenders.

Order Dispatch templates enable to include different payment methods (RTC-37886)

Payment methods are properly displayed in the email templates for the certain dispatch order. It is properly displayed for Klarna, Gift card and other available payment methods in the email message and also attached PDF receipts. For orders created in Web shop and in Physical store there is no differences how payment methods are displayed. Proper translations for Norwegian, Swedish and Finnish were added.

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 
StorePrepaidWarehouseDelivery and StorePrepaidDispatchDelivery.

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.
It continues processing consecutive events in the same execution, and if at least one of the events fails, the status of the job execution is set to faulted.

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.
When event fails with exception CartIsCancelledFault, then job execution is no longer stopped - job carries on processing consecutive events in the same execution.
If processing of scheduled event fails, then the configurable on job level delay will be added to the next reprocessing of this event.

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.
The default configurable in the job retry count is 10. At 10 retries, it will sets the status to error.