Extend Tracking link logic to support full URL in dispatch order details grid (RTC-40419)

A clickable link informing about the shipment status is present in the dispatch order details grid in the Tracking Number column.

Split picking order if some of the items are deliverable (RTC-39914)

Picking orders are split when some of the item's are deliverable and dispatched to dispatching store with the freight item:

• Items that are available for picking + freight item(s) are sent to CW/dispatchstore
• Items not available for picking are assigned and stay at the dummy store 

When previously unavailable items are ready to be picked, the automatic reassign job  assigns them (from dummy store) to CW/dispatchstore and exports a picking order.

Splitting order between dummy store and dispatching stores is only possible when Delete of order lines is not allowed.

Store that can deliver the whole order should be prioritized (we rely on dispatch suggestion and what is provided there).

New trigger for picking orders: Order fully paid (RTC-38919)

When customer order has StorePrepaidDispatchDelivery variant then export generates only for fully paid web order:

• Order created is skipped for orders containing CustomerOrderVariant: StorePrepaidDispatchDelivery.
• Order paid is only sent for orders containing CustomerOrderVariant: StorePrepaidDispatchDelivery.

Creation of PAC.CW doesn't prioritize correctly (RTC-41146)

PAC.CW orders priority:

• Item A is only available in stock in Central warehouse and Item B is available in stock both in the store and in CW, ALL pick able order lines are sent to the Central warehouse.
• Item A is only available in stock in Central warehouse and Item B is only available in stock in the store, all pick able order lines in stock at CW are sent to the Central warehouse, order lines not in stock at CW but in stock at store are split to the store.
• Item A and Item B are available in Central Warehouse, Item A and Item B are available in dispatching store, pickup store get the whole order.
• Item A is only available in stock in the store and item B is not available in stock both in the store and CW then all pick able order lines in stock at store are sent to the pickup store, order lines not available in any stock are split to the Central Warehouse.
• Item A is available in CW and store, item B is not available in stock both in the store and CW then ALL pick able order lines are sent to the Central warehouse.
• Item A is only available in store, item B is available in stock both in - CW and store then ALL pick able order lines are sent to the pickup store.

Create empty picking orders for PAC.CW (RTC-41340)

When orders have PAC.CW delivery method and picking order is rejected due to picking line removal then new picking order in pickup store is created.

Manually reassign PAC.CW from dummy store (RTC-41319)

It is possible to manually reassign PAC.CW picking orders or its separate picking lines from dummy store to Pickup Store or CW.

PickingOrderProcessor job improvements (RTC-40613)

• job log messages
• job execution statuses
• fake clients added
• filling createdBy/modifiedBy column in ScheduledJobExecution table
• documentation of the job added
• default job URLs
• delay of the job execution moved to Chain Web configuration
• PickingOrderWriter removed

'DelayPickingOrderProcessingMinutes' parameter has been added to Chain Web and it allows to configure the delay time of customer order processing.

Extend PickingOrderExport job with external store and external order numbers (RTC-40482)

The PickingOrder job contracts :CustomerOrder.Export.PickingCancelled, CustomerOrder.Export.PickingDelivered, CustomerOrder.Export.PickingStarted and CustomerOrder.Export.PickingCompleted was extended with:

• externalOrderStoreNumber 
• externalOrderNumber 

and the PickingOrder job contract CustomerOrder.Export.PickingOrder was extended with:

• externalPickingStoreNumber
• externalOrderStoreNumber 

Picking order export counter (RTC-40406)

The Picking order export contract is extended with "pickingOrderExportCount".Everytime a change is made to an order, it results in a new export of a picking order and the pickingOrderExportCount is +1. What is more, picking order export contract is extended with "deliveryPointName". That means, DeliveryPointName is filled with store name when ExternalId in OrderDeliveryDetails is not null.

Add triggers in CustomerOrderService for Reserve& Collect orders (RTC-40089)

The new blob types:

• PickingOrderDelivered
• PickingOrderCanceled

are exported when a Reserve&Collect order is paid or canceled in POS.

Improved function for repairing PLU lists definitions (RTP-30501

The button for repairing PLU lists definitions in the visual editor in POS configuration has been improved to handle error in the XML definitions. Previously, an error in a xml node would throw an exception while repairing and the PLU list definition would not be repaired.

Create Excel file from "Ikke fakturerte kredittsalg" (RTC-40791)

Creating an Excel file from the report "Ikke fakturerte kredittsalg" is now supported.

Settlement - daily report (RTC-39983)

Fix for incorrect pay out values in 1806_subCashBalance subreport.

Cashier statistics (RTC-39588)

Changes in report: 0904_CashierStatistics. Fix for failing reports with alphanumerical cashier numbers.

Balance permissions

Store users without "Administer balance" permission are able to create balance for cash registers (BalanceTransactionType = Workstation).

Team users and cashiers  (RTC-44432)

Team users with correct permissions are allowed to assign/create cashiers for other users.
In addition, an issue where team users could not see cashiers in Cashier management, has been fixed.

Original net cost price when returning items (RTC-41706)

The sales price in the return is fetched from the original sale, as well as the net cost price.

Improved function for repairing PLU lists definitions (RTP-30501

The button for repairing PLU lists definitions in the visual editor in POS configuration has been improved to handle error in the XML definitions. Previously, an error in a xml node would throw an exception while repairing and the PLU list definition would not be repaired.

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. 

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.

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.

Extend Tracking link logic to support full URL in dispatch order details grid (RTC-40419)

A clickable link informing about the shipment status is present in the dispatch order details grid in the Tracking Number column.

New trigger for picking orders: Order fully paid (RTC-38919)

When customer order has StorePrepaidDispatchDelivery variant then export generates only for fully paid web order:

• Order created is skipped for orders containing CustomerOrderVariant: StorePrepaidDispatchDelivery.
• Order paid is only sent for orders containing CustomerOrderVariant: StorePrepaidDispatchDelivery.

Picking order export counter (RTC-40406)

The Picking order export contract is extended with "pickingOrderExportCount".Everytime a change is made to an order, it results in a new export of a picking order and the pickingOrderExportCount is +1. What is more, picking order export contract is extended with "deliveryPointName". That means, DeliveryPointName is filled with store name when ExternalId in OrderDeliveryDetails is not null.

Extend PickingOrderExport job with external store and external order numbers (RTC-40482)

The PickingOrder job contracts :CustomerOrder.Export.PickingCancelled, CustomerOrder.Export.PickingDelivered, CustomerOrder.Export.PickingStarted and CustomerOrder.Export.PickingCompleted was extended with:

• externalOrderStoreNumber 
• externalOrderNumber 

and the PickingOrder job contract CustomerOrder.Export.PickingOrder was extended with:

• externalPickingStoreNumber
• externalOrderStoreNumber 

Customer order - structured note (RTC-40479)

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

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.

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

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. 

Errors in OrderMessageIntegration - GenerateMessage job (RTC-37721)

GenerateMessage job executes properly with completed status and message of generated and published order confirmation for order number and receipt id.

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. 

PAC.CW Doesn't Assign/Reassign to Central Warehouse (RTC-39399)

PAC and PAC.CW are assigned and reassigned correctly to Centrale Warehouse which is fetched from Dispatch Rule -> Stores View -> Centrale Warehouse Column.

Do not send "order sent" e-mail after picking a PAC order (RTC-39338)

Only the Ready for Pickup email is sent after picking up PAC orders in the InStore App.

Add receipt PDF to PAC "Ready for pickup" template (RTC-39188)

The receipt PDF is attached to the "Ready for Pickup" email template.

Extend picking order export with price and currency code on line item (RTC-39111)

The total amount to pay for each order line as well as the currency code is part of the picking order JSON.

Show Gift Card as payment method on receipt attachment (RTC-39093)

Klarna and Gift Card payment method is presented on the receipts attached to the Shipping order email template. What is more, the Order Date text is updated with Swedish "Orderdatum".

Allow changing from PAC to PAC.CW delivery method (RTC-39059)

Rejecting PAC orders in InStore App changes automatically the delivery method to PAC.CW and reassigns picking orders to the Central warehouse. As a result, these orders follow the PAC.CW flow.

GenerateMessage job throws exception when sending an order (RTC-39043)

The Generate Message job prepares Receipt message template successfully. Email is delivered/received properly after sending a dispatch order in Chain Web.

Errors in OrderMessageIntegration - GenerateMessage job (RTC-37721)

GenerateMessage job executes properly with completed status and message of generated and published order confirmation for order number and receipt id.

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.

Improvement in Create stocktaking (RTC-40086)

To prevent the creation of a new stocktaking getting stuck in the status "Creating", improvements have been made to close the connections to Chain Classic.

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. 

Fix: Duplicated order lines (RTC-31068)

There is a button in customer order details view called "Regenerate". After clicking, order should be re-fetched (from POSWCF, based on latest related receipt state) and duplicated order lines should be removed. No data will be lost (incl. discounts, online returns) - It will not work for payed and delivered lines,  as it is mainly implemented for active orders. This functionality is available for admin users and the users with new role "Regenerate order" assigned.

Fix: Filter with customer number fails when returning from an order (RTC-31569)

Filtering is working correctly and error does not occur anymore.

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.

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.

Creating new dispatch rule with defined name (RTC-32853)

User receives the right communicate if all required fields will not be filled (all confirmation messages and Central warehouse). Before adding Central warehouse and saving it, it is impossible to edit stores - edit button will be unavailable.

Before adding Central warehouse and saving:

After adding Central warehouse and saving:

Communicate for user if all required fields will not be filled:

Refreshing Screen After Back to Previous Page (RTC-32895)

The Dispatch Orders main grid is active and not faded after returning from the dispatch order details view with an opened pop-up. 

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. 

Improvements after acceptance tests of product series are implemented (RTP-23303)

1. Configuration is changed so the following arguments in ButtonConfig can be configured: Type: Product Series or Model, Number.
2. Nothing happens after clicking the button on an item without model or product series.
3. Default value is changed to "All" instead of "In stock" after clicking the button on an item with some product series.
4. While switching back to "In stock" view if there are no items in selected product series in stock, the item details from "All"-view is no longer shown.

Sales report with excluded item groups (RTC-30576)

Improved selection in reports containing excluded groups. This to make sure report will not fail when selection does not include excluded groups.

Improvement in Create stocktaking (RTC-40086)

To prevent the creation of a new stocktaking getting stuck in the status "Creating", improvements have been made to close the connections to Chain Classic.

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.

File name

0757_MixSales

Data source

Lindbak POS Reporting Cube (OLAP)

Selections 

Comment

EAN

Item name

Department

Item area

Item group

% of total sales

Items sold 

% items sold 

Discount ex. VAT

Receipts with mix

Share mix receipts 

Amount in mix receipts ex. VAT

Avg. sales customer

Gr. prof. % mix

Gr. prof. % total

Gross profit

Clarifications: Report has a star explanation for a few columns. It means that summary values for particular mix are calculated including all transactions in store. As an example '% Items sold' is calculating by taking quantity and dividing it by whole store quantity. For whole mix it will be store quantity of all items in store. For particular article in that mix '% Items sold', quantity of that product in mix will be divided by all articles in that mix. Summary for mix (grey grouped row) takes whole statistics about store, even if it is not mix.

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.

Customer Service Integration (RTC-32580)

Empty lists of "Contacts" and "Adresses" (except for "General Address") are supported during importing customers from CustomerService

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

Extend POSLog processing with shipment details (RTC-22515)

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

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.

Searching or filtering by scanning barcode (RTP-22179)

Searching or filtering receipts in receipt journal in POS can now be done by scanning an item's barcode.

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.

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)

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.

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.

Set system parameters back to blank (RTC-29801)

User is able to set system parameters to blank value.

Improvement in Stocktaking (RTC-40086)

To prevent the creation of a new stocktaking getting stuck in the status "Creating", improvements have been made to close the connections to Chain Classic.

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.

File name

0757_MixSales

Data source

Lindbak POS Reporting Cube (OLAP)

Selections 

Comment

EAN

Item name

Department

Item area

Item group

% of total sales

Items sold 

% items sold 

Discount ex. VAT

Receipts with mix

Share mix receipts 

Amount in mix receipts ex. VAT

Avg. sales customer

Gr. prof. % mix

Gr. prof. % total

Gross profit

Clarifications: Report has a star explanation for a few columns. It means that summary values for particular mix are calculated including all transactions in store. As an example '% Items sold' is calculating by taking quantity and dividing it by whole store quantity. For whole mix it will be store quantity of all items in store. For particular article in that mix '% Items sold', quantity of that product in mix will be divided by all articles in that mix. Summary for mix (grey grouped row) takes whole statistics about store, even if it is not mix.

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. 

File name

Data source

Selections:

Loyalty id

Date from 

Date to 

Store

Output: 

Bonus checks overview. For each store sum of issued, redeemed, spent, expired and balance bonus checks with number of sales and members who got/used bonus. Next table with issued amount and member with bonus independent of chosen period. Total sum of each column for all selected stores.

Columns: 

File name

Data source

Selections:

Loyalty program

Output: 

One page per store. For each month sum of issued, redeemed, balance and expired bonus checks. One sum for manual issued checks, checks issued from sales and total. First page of report is total for all stores.

Columns: 

Expiring

File name

Data source

Selections:

Date from 

Date to 

Store

Transaction type

Reason code

Default all available codes. List shows only reason codes linked to selected transaction types. NB! Depending on Chain Web version. When you select transaction type, only first available reason code will be selected. Workaround for this is to de-select all reason codes before selecting transaction type(s).

Absolute values

Relevant parameters: 

pTransactionTypesToExclude

pShowAbsoluteValues

pGrouping

Output: 

List of item transactions with reason codes.

Columns: 

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. 

File name

Data source

Relevant parameters: 

pTransactionTypesToExclude 

pShowAbsoluteValues

pGrouping

Selections:

Date from 

Date to 

Store

Transaction type

Reason code

Absolute values 

Grouping

Department

Columns (sum for store and each level of hierarchy. Sum total on last row):

EAN

EAN of item.

Item name

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.

Discount (RTC-25643)

Correction on visibility of customer discount when adding discount from Arts XML. After changes, the discount now shows on the customer card in Chain Web. 

Refund and return (RTP-16124)

Providing correct refund/return of discounted items from Customer order regarding Aera payments. 

Adding order to Project (RTC-23876)

Small change in how the system add customer orders to projects. 

Automatic Reassign Job - Rework (RTC-25150)

Previously assigned store is excluded from possible dispatch locations. That means automatic reassign does not assign orders to a store from which they have been previously rejected.

Reassign order lines (RTC-23733)

• Non-sale lines are not considered for removal when performing automatic reassign from the dummy store.
• Normal automatic reassign doesn't handle picking orders owned by a fake store.
• Removal of a line from dispatch order results in the line being removed from the previous picking order.
• After removing the unavailable items when reassigning them, the order is successfully delivered.

Chain Web Capture ShippingCSID to improve nShift integration (RTC-24728)

Chain Web now pulls data from DispatchService when picking order is finished with additional attribute shippingCSID. After finishing picking order, a new field called shippingCSID is created in the table, and the value is save in customerOrder.pickingOrder table.

Export to Myhrvold scales (RTC-24620)

Item and price information (Labels) that are exported and sent to a blob are converted to Myhrvold format and put on a specified (configurable) folder. Every MyhrvoldXml file is named after StoreID, by which labels inside XML are grouped.

Fix: Export to Myhrvold (RTC-26255)

Convert label to Myhrvold On-Premise  job is correctly processed when there is no value in UnitPriceFactor field in the label.

Sale per hour and cashier (RTC-25988)

New report is optimized to use in cash register. Report shows graphic sales per hour and sales per cashier.
See documentation in confluence: 0540_SalesPerHourAndCashier_std.

Missing translation (RTC-25860)

Added missing Swedish translations for subscription of report 0457. 

Support for Liter15 (RTC-25711)

In report for Wet Stock and Daily Wet Stock support for new unit of measure, Liter15 was added.
When dippings are registered in Liter15 this will be shown with and * on the day for the dipping.

Changed reports: 0750_WetStock and 0751_DailyWetStock.

Subgroups sales (RTC-25486)

Report 0611: sorting of item groups changed from alphanumeric to numeric.

New parameters in Top sales per item (RTC-25474)

To do the follow up on item sales better, two new parameters are added to existing report 0459_TopSalesPerItem:

• Brand - Filters result based on selected brand,
• Campaign - Filters result based on selected campaign.

Not able to edit all settlements with status "Ready for balance" ( RTP-18165)

It's possible to create balance for every shift settlement with status "Ready for balance". 
Correction on filtering of balances where user was not able to edit all settlements "Ready for balance" is done.  

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.

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.

Translation correction (RTP-18999)

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

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.

Refund and return (RTP-16124)

Providing correct refund/return of discounted items from Customer order regarding Aera payments. 

Subscriptions (RTC-26043)

Correction on bug that occurred when user select option "Upcoming week" and after that change default value in "Apply date filter to". Now subscription is properly created.

Missing translation (RTC-25860)

Added missing Swedish translations for subscription of report 0457. 

Receipt Journal Log - New data lines (RTC-23833)

New data lines are available in receipt journal log:

• Cancellation of the receipt;
• Manually registered deposit;
• Scanned deposit refund;
• Currency in payments logs;
• Article discounts - contains type (percent/amount), reason of the discount and the amount that is subtracted from the price of the item.

Reassign order lines (RTC-23733)

• Non-sale lines are not considered for removal when performing automatic reassign from the dummy store.
• Normal automatic reassign doesn't handle picking orders owned by a fake store.
• Removal of a line from dispatch order results in the line being removed from the previous picking order.
• After removing the unavailable items when reassigning them, the order is successfully delivered.

New parameters in Top sales per item (RTC-25474)

To do the follow up on item sales better, two new parameters are added to existing report 0459_TopSalesPerItem:

• Brand - Filters result based on selected brand,
• Campaign - Filters result based on selected campaign.

Resend button is removed (RTC-24071)

Resend option is not visible for credit notes, since it is not supported.

Missing item lines (RTC-24465)

Correction on invoice creation for consolidation invoice where invoices lines would appear missing on the PDF created. 
Issue was found between Customer order and Project where there was blank reference on both order and project. 

Correction on price calculation for invoice from internal transfers (RTC-24095)

VAT is now properly added to the item price while sending internal transfer to credit.

Missing buttons in POS Replication dialog (RTP-17154)

POS Replication dialog for acknowledging activation/deactivation of replication subscriber displays "Cancel" and "Confirm" buttons now.

Subgroup sales (RTC-25043)

A copy of report 0610 is created with new parameters for selecting store and latest EOBD. Selection of latest EOBD makes it possible to set up subscription of report to get latest EOBD.

Sales statistics (RTC-25472)

Changes made in the report for sales statistics (0752) to more efficiently report on stores and totals.
Page 1 of the report is always total for all selected stores, next pages are per store. This is same behavior as in report 0714.
New columns added to Gross profit section: % exc. campaign, campaign and campaign %. This is the same data as shown in report 0714.

Updating PIN for Cashier from Cloud User Management (RTC-25294)

New user that is a cashier has PIN (the same value as CashierNumber). PIN doesn't change when user is updated or cashier is removed from user. If new user is not a cashier, then PIN stays NULL.

Refund (RTC-24163)

Prices on a customer order lines will be frozen at the time of customer order creation. Order lines will not be affected by any other discount than line, during the refund process. Only line discount will be added on the order after refund process.

Reference ID (RTC-23795)

There is no need to fill field ReferenceId when the user has changed the delivery method on Customer order/ offer to one that has Custom type defined in system parameter CustomerOrderDeliveryMethod. 

Now field ReferenceId isn't mandatory for this setting and customer offer or order is properly created without it. 

Adjustments to the invoice standard V3 (RTC-22650)

Logo has 50px height and the width adapted to its' format. Section with customer details is placed below logo aligned with the invoice details on the right side. Margins are 20px. Reference text and number are moved to top section. When there is no reference text/ number added to the order, this fields are invisible on the invoice. Additionally, color and size are removed from receipt lines. 

Subtotal rounding on Invoice (RTC-19153)

Correction to how amount on receipt line is set to rounded value from POSLog which is adjusted to deal with rounding issues.
Total amount on the invoice has been rounded correctly, regardless of the type of rounding up and down and kind of set discount (% or new amount). Additionally, rounding prices in the summary on Customer order has been fixed.

Count lists (RTC-11439)

When assigning count list fails, detailed exceptions are shown to the user and logged in BackOffice logs.

Fix: All order lines is picked, but order is not completed, and picking order gets reassigned (RTC-22639)

Automatic reassign of dispatch order (DispatchOrderReassign job) package does not create empty picking orders when no order lines can be reassigned.

Subscription options on Report 0457_CampaignStatistics (RTC-24237)

Adding option "Upcoming week" in subscription when report 0457_CampaignStatistics is renamed. Providing support for Custom name on the report .
Now renaming of the report  0457_CampaignStatistics doesn't make option "Upcoming week" unavailable. The report distribution follows defined time intervals and settings during subscriptions.

Correction of bug in saving/editing User Roles (RTC-24343)

Providing proper creation of a new user role and edition of the existing without error message.

Occurrence of this bug is related to new version of web browser.

DispatchServiceRule parameter (RTP-17551)

New DispatchServiceRule parameter has been implemented with the default value set to "WebOrdersFromPhysicalStores" under the filter CustomerOrder.

Discount (RTC-25643)

Correction on visibility of customer discount when adding discount from Arts XML. After changes, the discount now shows on the customer card in Chain Web. 

Subscription options on Report 0457_CampaignStatistics (RTC-24237)

Adding option "Upcoming week" in subscription when report 0457_CampaignStatistics is renamed. Providing support for Custom name on the report .
Now renaming of the report  0457_CampaignStatistics doesn't make option "Upcoming week" unavailable. The report distribution follows defined time intervals and settings during subscriptions.

User maintenance of customer (RTC-24540)

Correction on customer creation and edition while changing parameters: "Store Access" or "Customer Type".

Correction of bug in saving/editing User Roles (RTC-24343)

Providing proper creation of a new user role and edition of the existing without error message.

Occurrence of this bug is related to new version of web browser.

File name

0088_BonusRolloutPerStore

Data source

Analysis services (Cube)

Selection

Year from

Default last year.

Year to

Default current year.

Bonus rollout name 

Default all - shows available rollouts within period.

Loyalty program

Columns - One row per store with issued bonus checks for store.