Missing Picking Order Blobs (RTC-38731)

The Picking Order job stored in BackOfficeBatchGenerator exports picking orders to blob storage when a dispatch order is created.

Do not Include deleted order lines in the PayAndCollectDispatched message (RTC-38251)

Deleted lines do not appear in the ready-for-pickup email message.

Support WeborderFromPhysicalStores in the package delivery view (RTC-37216)

Weborders created in physical stores are shown in the deliver package view in CW and it is possible to deliver them to customers.

Add logging of completed runs in the PickingOrder export job (RTC-38799)

Completed PickingOrder export job runs log information about what has been exported. When no action is performed the job is completed with "CompleteWithNoEffect" status.

Fetch Central Warehouse store from Dispatch Rules (RTC-38653)

The Central Warehouse store number is fetched from the dispatch rules. 

Fix for InvalidNumberFormat error (RTP-27421)

InvalidNumberFormat error message is no longer entered when Customer Orders are created or during registration of picked Reserve & Collect orders.

Dispatch order email templates with multiple language support (RTC-35614)

Email content, subject and filenames are translated based on the origin of the order. Order origin is fetched from the address of the store where the order was placed. 

Stock list (RTC-37811)

All rows from the stocktaking results grid are exported to Excel.

Timeout during export of the stock list to PDF (RTC-37208)

The timeout limit is set to 30 minutes, so that larger files can be generated before a timeout occurs.

Refund Lines in Dispatch Order Details View (RTC-36193)

Refund lines are visible in the picking order lines grid in dispatch order details.

Edit discount for Dispatch Orders refund (RTC-36184)

Dispatch orders paid using Klarna can be refunded partially or fully using these discounts:

•  % discount,
• Amount 
• New Price
  
  

Refund Component in Dispatch Orders (RTC-36183)

Dispatch Orders paid using Klarna can be partially or fully refunded. The new 'Refund' button that allows for the refund is displayed in the dispatch order details view and visible only when the payment type is Klarna.

Picking Order is Exported Twice on dispatch Order Creation (RTC-33753)

One picking order is exported when a dispatch order is created.

Extend CustomerOrder.Export.PickingOrder for Dispatch Orders (RTC-35764)

The CustomerOrder.Export.PickingOrder blob exported to 3rd part was extended and contains both item number and item text.

Recipient Name, Email and Mobile Available in Order View (RTC-34677)

Recipient, email and mobile from order delivery details are added to the order dispatch grid. The new fields are searchable / filterable, and hidden as default. 

Picking Order is Exported Twice on dispatch Order Creation (RTC-33753)

One picking order is exported when a dispatch order is created.

Count list grid view (RTC-35052)

The view is not blocked anymore, the grid is loaded only one time per request/ each change.

Fix: EHF invoices (RTC-35288)

The PayableRoundingAmount is properly calculated when store has disabled rounding option.

Count list grid view (RTC-35052)

The view is not blocked anymore, the grid is loaded only one time per request/ each change.

Holidays are not excluded from the delivery time limit (RTC-33632)

Delivery time calculation excludes holidays to ensure that the time limit of picking orders are calculated correctly. 

Introduce Log Level for Dispatch Orders (RTC-32437)

It is possible to set log levels for DispatchOrders in Chain Web (BackOffice Services).
The logs contain requests and responses from DispatchService.

Automatic reassign doesn't delete order lines (RTC-32308)

For selected option 'Allow delete of rejected orders/order lines' rejected orders will be cancelled and deleted if it will not be possible to reassign order from dummy store. 

DispatchOrderReassign job fails when trying to trigger export of modified picking order (RTC-32233)

DispatchOrderReassign doesn't fail when trying to reassign any dispatch order.

Client side error for store names with apostrophe (') (RTP-23002)

Choosing stores with names that contain apostrophe (') in POS Configuration no longer causes a client side error to appear.

"Fetch last X receipts for receipt copy" in Convenience sales (RTP-22040)

It is now possible to configure a button with function "Fetch last X receipts for receipt copy" in Convenience sales.

Customer data (RTC-32071)

The import of customer data from Retail database has been extended with Organization Number. The view pub.vDimCustomer is also extended with this information.

Item synchronization error handling (RTL-5829)

Processing of item update events with use cache type "memory" is improved, the job should not throw errors/ should not be locked, when adding to cache record with already existing key.

Set system parameters back to blank (RTC-29801)

User is able to set system parameters to blank value.

Display of selected invoice method in customer's view (RTC-30248)

After changing setup of invoicing in customer's details by selecting electronic invoicing, consolidated invoice column in customers view is now updated correctly.

Refund/Return process (RTP-22025)

The order should not be blocked for further refunds/ returns, if the process will fail on e.g. timeout, or payment. The returned/ refunded lines will be removed from order, or set as deleted and the started transaction will be cancelled - removed.

Refund/ Return - fix for Not Paid status in dashboard (RTC-31261)

The issue was only related to displaying Not Paid for completed orders on dashboard for the Orders where prices from order lines sum up to sum value with more than 2 decimals after comma. E.g. Total on order was 211,00 while lines sum up to 211,0002.

Extend POSLog processing with shipment details (RTC-22515)

It is possible to create an order with defined shipment details.

Support OrderSourceID 'Store' for Dispatch Orders Grid (RTC-31650)

All dispatch orders are visible in the dispatch orders grid, including both orders from the web shop and physical stores.

Settlement reports (RTC-31644)

Two new version of settlement reports for operator and workstation. Both reports are based on existing versions of reports. 

0613_StoreSettlementPerOperator

Name: Store settlement

Description:
Report allows to follow up store settlement per cashier. The first page show statistics for all selected cashiers (if all cashiers are selected, the values equal to the totals for given store). The individual cashiers are shown on the following pages. Report is divided into following sub-reports: settlement, statistics, sales per hour, tender type, discounts and item sales.

Selections:

• Date from: Default today
• Date to: Default today
• Store: Multivalue; default all
• Operator: Multivalue; default all (filtered by selected stores)
• Price channel: Multivalue; default all.

0614_StoreSettlementPerWorkstation

Name: Store settlement

Description:
Report allows to follow up store settlement. The first page show statistics for all selected cash registers (if all cash registers are selected, the values equal to the totals for given store). The individual cash registers are shown on the following pages. Report is divided into following sub-reports: settlement, statistics, sales per hour, tender type, discounts and item sales.

Selections:

• Date from: Default today
• Date to: Default today
• Store: Multivalue; default all
• Workstation: Multivalue; default all (filtered by store)

Simple search in count groups view (RTC-30733)

Pasting number/name of the item to simple search field in count groups edit view works correctly after fixes.

Anonymization of customers (RTP-20782)

Social security number is removed when doing anonymization of customer.

Item groups (RTP-21923)

Problem with alphanumeric item group searching and adding discounts for alphanumeric item group.  Searching for all item group and adding discounts for all item groups is now working correctly.

Refund/Return process (RTP-19382)

The order should not be blocked for further refunds/ returns, if the process will fail on e.g. timeout, or payment. The returned/ refunded lines will be removed from order, or set as deleted and the started transaction will be cancelled - removed.

Refund/Return process (RTP-18663)

The order should not be blocked for further refunds/ returns, if the process will fail on e.g. timeout, or payment. The returned/ refunded lines will be removed from order, or set as deleted and the started transaction will be cancelled - removed.

Picking orders export job (RTC-29897)

• PickingOrder job in BackOfficeBatchGenerator package exports PickingOrder blob's containing one or more picking order id's.
• The job only exports picking orders assigned to store numbers configured in the system parameter PickingOrderExport.

Comments on POS Configuration parameters (RTC-26752)

Adding comments on parameters in Chain web works correctly now: the POS Configuration page is refreshed correctly and the "Activate" button on configuration set does not appear.

Support tandem items in convenience mode (RTP-20795)

In POS Configuration PLU Button properties, when the "Sell article with EAN" function is selected, EAN of the item to be sold can be entered and this will be available for selling in POS convenience mode.

Configurable name of "External Loyalty Number" (RTC-29525)

After adding new system parameter "ExternalLoyaltyNumberFilterOptions" it is now possible to configure name of the "External Member Number" field in sales filters in Receipts Journal.

Store Info (RTC-30351)

To improve report information, GlobalLocalizationNumber was added to our store information. GLN is imported from both POS Master and Store Service and updated in Reporting DW / OLAP and Azure DW.

Segmentation on favorite item (RTL-4355)

It is possible to create segmentation on brand, department, item, and item group based on a Favorited item for the Web Activities category.

Refund/Return process (RTP-22025)

The order should not be blocked for further refunds/ returns, if the process will fail on e.g. timeout, or payment. The returned/ refunded lines will be removed from order, or set as deleted and the started transaction will be cancelled - removed.

Refund/ Return - fix for Not Paid status in dashboard (RTC-31261)

The issue was only related to displaying Not Paid for completed orders on dashboard for the Orders where prices from order lines sum up to sum value with more than 2 decimals after comma. E.g. Total on order was 211,00 while lines sum up to 211,0002.

Support tandem items in convenience mode (RTP-20795)

In POS Configuration PLU Button properties, when the "Sell article with EAN" function is selected, EAN of the item to be sold can be entered and this will be available for selling in POS convenience mode.

Error when using "Simple Search" in Balances summary (RTC-29049)

"Simple Search" field has been removed from Balances summary view.

Exporting customer groups from Chain Web to POS (RTC-28657)

Export of customer groups from Chain Web to POS was not including brand-discounts. After implementing changes, every type of discounts is exported correctly from Chain Web to POS.

Customer Groups filtering (RTC-30021)

After changes, one can now filter by "store" in Customer group grid and use "Mark all" button, which allows user to mark all lines meeting the filter conditions. If a user has appropriate rights to change selected rows or delete them he can do this. HQ user can modify and delete only common discounts and store users only discounts for their specific store.

Locking customer orders (RTC-28319)

Fixes were implemented to eliminate locking order without proper reason with false message "The order cannot be changed since it is edited by another user".

Email on split orders (RTC-25645)

Email communication has been extended with new split order and Pay & Collect confirmation messages. New implemented email are:

• Split order message - User receive email with confirmation of order splitting. The email contains a summary for all stores that the order has been split into
• Split order shipping confirmation - Confirmation of delivery from a given store where picking order is picked
• Pay & Collect message - Confirmation of delivery from the store where the Pay & Collect order has been picked

Email send out depends on communication channel defined in POSLog.

Add support for invoice payment interest % "Dröjmålränta" (RTC-27449)

Implemented changes added functionality of setting and displaying "Interest with delayed payment", "Dröjmålränta" in the invoice template "Standard V3".

Translations to Finnish language (RTP-20121)

Providing the possibility to change user language to Finnish in User Management or during user profile edition. Information and notifications in Chain Web are translated except from invoices, vat formatting, postcodes etc. 

Resend EHF (RTC-33534)

Timeouts doesn't occur anymore on "Resend EHF" view.

Regenerate order/offer (RTC-31068)

A new functionality for regenerating order/ offers was implemented. There is new button in customer order details view called "Regenerate". After clicking, order should be re-fetched from POSWCF (based on latest related receipt state), duplicated order lines should be removed. No data should be lost (incl. discounts, online returns).
It will not work for payed and delivered lines, it was mainly implemented for active orders.

This functionality is available for admin users and the users with new role "Regenerate order" assigned.

Customer Groups filtering (RTC-30021)

After changes, one can now filter by "store" in Customer group grid and use "Mark all" button, which allows user to mark all lines meeting the filter conditions. If a user has appropriate rights to change selected rows or delete them he can do this. HQ user can modify and delete only common discounts and store users only discounts for their specific store.

Exporting customer groups from Chain Web to POS (RTC-28657)

Export of customer groups from Chain Web to POS was not including brand-discounts. After implementing changes, every type of discounts is exported correctly from Chain Web to POS

Email on split orders (RTC-25645)

Email communication has been extended with new split order and Pay & Collect confirmation messages. New implemented email are:

• Split order message - User receive email with confirmation of order splitting. The email contains a summary for all stores that the order has been split into
• Split order shipping confirmation - Confirmation of delivery from a given store where picking order is picked
• Pay & Collect message - Confirmation of delivery from the store where the Pay & Collect order has been picked

Email send out depends on communication channel defined in POSLog.

Translations to Finnish language (RTP-20121)

Providing the possibility to change user language to Finnish in User Management or during user profile edition. Information and notifications in Chain Web are translated except from invoices, vat formatting, postcodes etc. 

Error when opening Balance Summary (RTC-28251)

Implemented fixes eliminated error occurring in Balance Summary view.

Discounts imported from Item list and Item group list (RTC-21862)

Providing the possibility to replace store and common discounts already existing in a grid (added from UI or imported from Excel file) with discounts imported from Item list and Item group list. If the item has both common and store discounts defined in the customer group discount grid, then the change of it's value is defined as Store value in the import pop-up screen.

Store and common level discounts (RTC-21860)

Providing the possibility to create discounts at the store level and common level for the same item with overlapping dates. Adding the hierarchy of created discounts which means that store discount is taken into consideration even if there is a common discount. However, common discount is used for stores which don't have setup store-level discount.

HQ user can see all created discounts, but for store user only their own store discounts and common are visible. 

Validation of overlapping dates is shown if the same item is added for the same store or common store multiple times with overlapping dates. 

Import items into Customer group from Excel file (RTC-21854)

Providing the possibility for store users and HQ users to import items into Customer group from Excel file with header (format .xlsx) that includes three expected columns:

• Number (GTIN/EAN)
• Price effect (number)
• Value  

If the values in these columns are incorrect or out of range then the user is informed by appropriate notifications. Moreover if file contains more than three expected columns then the import is proceed and unnecessary columns are ignored. 

Changes to discounts done by HQ user is added as common discount, while changes done by a store user is added on store level. 

Additionally flag in database is added to the customer group while import is ongoing. As a result, other imports/ changes cannot be done using UI at the same time.

Added button "Mark all" to select all lines and make it easier to delete them from customer group.

Discounts imported from large Item lists (more than 1000 items) (RTC-21430)

Providing the possibility to import large item lists without timeout by both Store and HQ user. Users during import can work in Chain Web, change tabs and create Customer orders/sales/offers. Messages about starting processing and summarizing it have been added. 

Adding new field for Original ordered quantity (RTC-26642)

Changes were implemented to store original ordered quantity in the retail database, so now it is possible for POS to check what quantity was ordered in the beginning. 

Order from physical store without DispatchRuleID (RTC-28318)

Only customer orders with a DispatchRuleId are considered for dispatching when created in physical store.

Correctly handle dispatch orders with blank DispatchRuleId - fallback to web shop number.

Multiple lines with the same EAN (RTC-27648)

Dispatch orders with multiple lines containing the same EAN are correctly dispatched (picking orders created) to the same picking store.

Confirmation messages for physical stores (RTC-26226)

It is possible to send confirmation messages for dispatch orders from physical stores. The contents of the message will be decided by the assigned dispatch rule. It is possible to modify this message by going to the confirmation message tab inside the dispatch rule. If the dispatch rule is not specified the settings for the dispatch rule for web shop will be used.  

Can not set invoices to paid state because of very small remaining amount (RTC-26700)

After fixes there is possibility to overpay a little bit (0,01) for invoices with 3 digits precision and very small amount left to pay (0,00x). While creating new invoice from internal transfer, the amount is now rounded, so the issue was eliminated.

Fix: Mismatch between number of members in the target group (RTC-26469)

The mismatch between number of members in the target group of the campaign shown in 'Details' and 'Dashboard' was resolved.

Translations (RTC-28392)

Deposit activities are properly translated in generated Excel files.

Lookup of stock failing CW 2.10.210 (RTC-28202)

Stock info is fetched properly - no popup "Error getting stockinfo" or similar occurs while adding item from Home page or Price Control.
Correction of issue implemented in CW 2.10.210. 

Refund/ Return - fix for Not Paid status in dashboard (RTC-31261)

The issue was only related to displaying Not Paid for completed orders on dashboard for the Orders where prices from order lines sum up to sum value with more than 2 decimals after comma. E.g. Total on order was 211,00 while lines sum up to 211,0002.

Error when opening Balance Summary (RTC-28251)

Implemented fixes eliminated error occurring in Balance Summary view.

Confirmation messages for physical stores (RTC-26226)

It is possible to send confirmation messages for dispatch orders from physical stores. The contents of the message will be decided by the assigned dispatch rule. It is possible to modify this message by going to the confirmation message tab inside the dispatch rule. If the dispatch rule is not specified the settings for the dispatch rule for webshop will be used.  

Discounts imported from Item list and Item group list (RTC-21862)

Providing the possibility to replace store and common discounts already existing in a grid (added from UI or imported from Excel file) with discounts imported from Item list and Item group list. If the item has both common and store discounts defined in the customer group discount grid, then the change of it's value is defined as Store value in the import pop-up screen.

Store and common level discounts (RTC-21860)

Providing the possibility to create discounts at the store level and common level for the same item with overlapping dates. Adding the hierarchy of created discounts which means that store discount is taken into consideration even if there is a common discount. However, common discount is used for stores which don't have setup store-level discount.

HQ user can see all created discounts, but for store user only their own store discounts and common are visible. 

Validation of overlapping dates is shown if the same item is added for the same store or common store multiple times with overlapping dates. 

Import items into Customer group from Excel file (RTC-21854)

Providing the possibility for store users and HQ users to import items into Customer group from Excel file with header (format .xlsx) that includes three expected columns:

• Number (GTIN/EAN)
• Price effect (number)
• Value  

If the values in these columns are incorrect or out of range then the user is informed by appropriate notifications. Moreover if file contains more than three expected columns then the import is proceed and unnecessary columns are ignored. 

Changes to discounts done by HQ user is added as common discount, while changes done by a store user is added on store level. 

Additionally flag in database is added to the customer group while import is ongoing. As a result, other imports/ changes cannot be done using UI at the same time.

Added button "Mark all" to select all lines and make it easier to delete them from customer group.

Discounts imported from large Item lists (more than 1000 items) (RTC-21430)

Providing the possibility to import large item lists without timeout by both Store and HQ user. Users during import can work in Chain Web, change tabs and create Customer orders/sales/offers. Messages about starting processing and summarizing it have been added. 

Adding new field for Original ordered quantity (RTC-26642)

Changes were implemented to store original ordered quantity in the retail database, so now it is possible for POS to check what quantity was ordered in the beginning. 

Order from physical store without DispatchRuleID (RTC-28318)

Only customer orders with a DispatchRuleId are considered for dispatching when created in physical store. 

Correctly handle dispatch orders with blank DispatchRuleId - fallback to webshop number.

Lookup of stock failing CW 2.10.210 (RTC-28202)  

Stock info is fetched properly - no popup "Error getting stock info" or similar occurs while adding item from Home page or Price Control.
Correction of issue implemented in CW 2.10.210. 

Locking order (RTC-27093)

Message displayed to user in Chain Web, when customer order is locked, was changed for more appropriate message in all languages. (English, Swedish, Norwegian).

Newtonsoft.Json.dll breaks weborder export to 3.part (RTC-24801)

Web orders export was fixed. There are no longer error messages occurring during processing of "ExportCustomerOrder" POSLogs related.

Sorting the Eldest Orders Ascending (RTC-28054)

The default sorting of the dispatch order list is: orders containing missing items, then active orders with the status "new" or "in progress", then oldest to newest.

Order not reassigned from dummy store (RTC-27734)

When considering if order line should be deleted automatic reassign gets dispatch suggestion for individual line instead of its available stock, which takes into account dispatch rules and stock reduction rules.

Order not deleted from POS when re-dispatched (RTC-27031)

• When the last item line in a picking order is deleted by automated reassign, POS is informed about the aborted picking for the assigned store (and the picking order is not reassigned further).
• When the whole picking order is reassigned to another store POS is informed about aborted picking for the previously assigned store.

Support dispatching of orders from physical stores (RTC-23380)

When DispatchRuleId (DeliveryDetails) is defined in POSLog then BackOffice service will use it to select dispatch rule used for dispatching picking orders.

Description in the popup for creating a new dispatch rule (RTC-26521)

The Description for New Dispatch Rule creation has a clear and correct message: 'Rule applies for Webshop'.

Reassign limits in dispatch rules (RTC-26227)

It is possible to modify reassign limits and opening days/hours for both Webshop rules and custom rules. 

Export to Myhrvold scales (RTC-27273)

FixedWeight in exported labels has a value from UnitPriceFactor in item details or 0 if there is no value there.

Invoices

Adjustments to the invoice layout standard V1 and V2 (RTC-16646)

Adding color and size to the Invoice based on transactions using POS Services/ POSLog processing. If there are both color and size given during Customer order creation, these properties will be displayed on Invoice just below item text. If color or size is given then only one value will be presented on Invoice. If none of the properties are given, then there is no extra line with information about color and size.

False warning displayed in the invoice base (RTC-26036)

Fixes eliminated false warnings in the invoice base about internal transfers not being sent to credit. After improvements, warning occurs only when in the selected store is at least one internal transfer which was not sent to credit.

Inconsistent results and timeouts in Receipts Journal (RTC-26098)

Process of free text searching in Receipts Journal was fixed and results are now consistent and timeout does not occur anymore. Process of searching for short date range has been improved.

External member number (RTC-23536)

Processing of receipts was extended for "ExternalLoyaltyNumber" handling, the number will be stored in Journal database and it will be possible to use it in Receipts journal search. External member number field was added under the Sales filters in Receipts journal, it's visible if Chain Web system parameter "ShowExternalLoyaltyNumberFilter" is set to true. It is also possible to use External member number in quick search filter. External member number is visible next to member number (Loyalty number: xxxxxxxxx / xxxxxxxxx) on the receipt preview.

Campaign sales (RTC-25674)

Selection for 'All campaigns, are removed from report 0042. It is only possible to select one campaign.

Processing of basis files (RTC-27203)

The processing of Basis files was improved, so now it is possible to setup additional scheduled trigger, which is independent of already existing directory content updated trigger. A new trigger should be started even if the standard trigger will be frozen. Additionally, the faulted basis file will be moved to subfolder with the date stamp, so there is no limit of how many files related to the same store could be moved + the retry mechanism was implemented to re-try the processing of not moved file 3 times.

BasisImport job (RTC-26498)

The logs and processing of Basis was improved, so now more detailed error message - with the related line content will be thrown, if the processing of Basis file will fail and additionally the corrupted file will be moved to failedBasisFiles subfolder. Additional log message was added for CompletedWithNoEffect execution status.

Filtering in exported Excel file from stocktaking (RTC-26853)

After fixes the value of the parameter ServerSideExportBatchSize does not limit the number of rows taken into account during filtration. All rows in the Excel file can be filtered.

Count list activation (RTC-26413)

The process of count list activation was improved, for "Items Not Counted" and "Cycle stocktaking". Count list processing/ activation process should not be blocked anymore even if it's related to a default count group creation, or if the Items from related count list, already exist in stocktaking result with empty CountingGroupInStocktakingId.

Automatic logout (RTC-26407)

Automatic logout was fixed and now time is counted since last activity in Chain Web instead of counting time since login like it was before fixes.

BasisImport job (RTC-26498)

The logs and processing of Basis was improved, so now more detailed error message - with the related line content will be thrown, if the processing of Basis file will fail and additionally the corrupted file will be moved to failedBasisFiles subfolder. Additional log message was added for CompletedWithNoEffect execution status.

Creating new customer order (RTC-23460)

By choosing "+1" icon on the customer order from customer menu a new window is opened where the user can fill in store, customer and project data, the same as during the standard order creation process. The same store as in store picker is selected by default. The focus is set in customer field when the window is opened.

New methods for updating picking status (RTP-17642)

It is now introduced two new methods for updating picking status:

• SetCustomerOrderPickingStatus
• GetCustomerOrderPickingStatus

The methods make setting and confirming the current picking status of an order possible. 

Dispatch rule details for physical stores (RTC-26047)

It is possible to display and edit dispatch rules created for physical stores using a custom name/id.

Changes are also made to the drop down list for "rule apply for Web shop" and "Central warehouse"  making it impossible to select options that are not included in the list. 

Order with shipping item only not cancelled (RTC-26291)

DispatchOrderReassign job cancels customer order where there is only non-sale item left after removing other line(s).

DispatchOrderReassign job removes line from picking order (assigned to dummy store) when there are still other lines left in picking order.

Adjustments to the invoice standard V3 (RTC-26113)

Remove Reference text and number fields from invoice header and place them into invoice grid to avoid loosing information during consolidate invoice generation. If there is no reference text/ number added to the order, this fields are invisible on the invoice. Additionally,  Payment terms and Our references fields have been added in invoice header and text "Reference" before the date in grid has been removed.

During testing the previous assumptions (task: RTC-22650) related to logo size and margins also have been checked.

Partially paid invoices (RTC-25823)

EHF invoice's PayableRoundingAmount field is now taking PrepaidAmount into consideration as during calculation.

Translation correction (RTP-18999)

Proper Swedish translations have been added for activity "Deposit refund" in Receipt journal logs.

Customers without sale (RTC-25822)

To get a better understanding of result in report, logic behind fetching data is changed.

When we earlier listed all customers in the report, it showed last sale as '1900-01-01' for customers without sale after the selected date. Now, we are only listing customers without sales after selected date. For customers with no sales (ever), the last sales date will show a hyphen.

Activating count list (RTC-24681)

When getting error message during activation of a count list, the user is no longer redirected to stocktaking window without having a chance to read the error message as of why it didn't activate. 

Fix related to sign in for Azure AD user (EG Cloud user) (RTC-26754)

Providing configuration in BackOffice.Web.ActiveDirectory/Web.config to avoid duplicated references regarding Microsoft.Owin version. After fixes Azure AD user can login properly into Chain Web.

Comments on POS Configuration parameters (RTC-26752)

Adding comments on parameters in Chain web works correctly now: the POS Configuration page is refreshed correctly and the "Activate" button on configuration set does not appear.

Adjustment in color and size display (RTC-23994)

When color and/or size has value "-" or field is empty, then there is no extra line with information about color and size, for all templates after fixes.

Adjustments to the invoice standard V1 and V2 (RTC-23994)

Adding color and size to the Invoice based on transactions using POS Services/ POSLog processing. If there are both color and size given during Customer order creation, these properties will be displayed on Invoice just below item text. If color or size is given then only one value will be presented on Invoice. If none of the properties are given, then there is no extra line with information about color and size.

Fix related to sign in for Azure AD user (EG Cloud user) (RTC-26754)

Providing configuration in BackOffice.Web.ActiveDirectory/Web.config to avoid duplicated references regarding Microsoft.Owin version. After fixes Azure AD user can login properly into Chain Web.

Partially paid invoices (RTC-25823)

EHF invoice's PayableRoundingAmount field is now taking PrepaidAmount into consideration as during calculation.