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.

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.

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.

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 excecution 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.

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.

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. 
Users with CasihierNo in BackOffice other than in the cloud user management are updated correctly, along with their cashierNo.