LIP wrongly marks batch as ProcessedOK/2 when timeout due to FlatBatchJson lock (RTC-41283)

When there occurs a timeout MemberIdentityMerger job finished with Faulted status and empty batch has proper 0 - unprocessed status.

Issues with creation of new customer when no IsDefaultSuggestedGroup CustomerGroup is defined (RTC-44309)

Error is no longer occurring and customer is correctly created, even if default group is not defined.

Job to delete old customer orders (RTC-34855)

The CustomerOrderCleanup job removes order offers and customer orders, which:

• have "Active" status, and are older than 5 years and were expired over 5 years ago;
• have "Draft" or "Completed" status and are older than 5 years.
• have "Cancelled" status and are older than 3 months.

The job is configured in the Integration Management Platform.

Regive (RTC-44329)

The Regive operation in version 1 of Gift card Service API supports Swedish and/or Norwegian characters in the custom message. 

PickingOrderProcessor job should handle Create before Update (RTC-43160)

PickingOrderProcessor job handle multiple operations for given customer order in order of creation. Operations for given customer order are not processed if previous operation (for this order) in the same execution have failed.

Emails/SMS with Receipt are not sent after removing undelivered lines (RTC-42608)

When a picking order is closed (delivered) by deleting the last item (partial delivery), confirmation Emails/SMS are sent. Messages are not sent for PAC and PAC.CW methods. The exports are working correctly.

Weird error message and confusing article grid in Dispatch on refund (RTC-41585)

Warning message is no longer appear at the bottom of the site. After successful refund of not locked order user is redirect to the dispatch order details view, moreover at the bottom of the site appears green successful message.

Export picking status blobs when picked in external system (RTC-43794)

Now the status of picking from an external order picking system like AutoStore will be updated in external systems (via Picking status blobs), So that  that the information we see in the picking order is correct, and  the external systems will get the correct status.

Export PickingOrderCanceled blob when Reserve&Collect Order is canceled in Chain Web (RTC-44070)

When user cancels Click & Collect orders in Chain Web the PickingOrder job is triggered and exports PickingOrderCanceled blob.

Shift balance (RTC-44692)

New report showing key number for shifts in a specified period.

Report name: Shift balance report

Filename: 0791_ShiftBalanceReport.rdl

Full information about report can be found in confluence: List of reports - EG Retail Chain - Confluence EG A/S.

Cashier statistics with fuel (RTC-44550)

New report similar to 0019_CashierStatisticsWithDiscount_std but added extra column to split regular and fuel sale.

Report name: 0781_CashierStatisticsWithDiscount

Detailed information in confluence: List of reports - EG Retail Chain - Confluence EG A/S.

Items not counted (RTC-44136)

For stocktakings with type "Items Not Counted", a count group is created automatically with "All items" option set. All required items are linked to it.

Cashier and user improvements (RTC-43142)

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

Modifying count groups (RTC-43184)

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

Set original net cost price when returning items (RTC-41706)

Net cost price in the return is the same as used in the original order.

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

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

Removing last line does not cancel dispatch order (RTC-42467)

Dispatch order is cancelled after last normal item is removed from whole order in picking order. Rejected order is not visible in dispatch orders view in Chain Web.

No validation of failed refund due to locked order (RTC-42012)

When trying to refund order which has locked status, the user interface displays a validation message at the bottom of the site about the failed refund.

Product description differs on templates (RTC-41100)

Product description does not differ between OrderConfirmation and CreditNote templates. 

Orders don't close automatically when there is no more items to deliver (RTC-40707)

Orders are closed automatically when all items have been delivered, also after items have been removed manually. Statuses in database are also updated properly.

SKU for Click&Collect (Reserved&Collect) orders (RTC-40091)

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

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

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

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

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

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

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

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

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

Delay of picking order creation for specific order types (RTC-41290)

The delay of picking order creation, by the PickingOrderProcessor job, only applies to the order types 
StorePrepaidWarehouseDelivery and StorePrepaidDispatchDelivery.

Picking order processor job saves partially modified data for picking order despite of exception (RTC-42952)

Partially modified data is not saved by the PickingOrderProcessor job.

PickingOrderProcessor job improvement (RTC-42482)

The PickingOrderProcessor job does not stop processing pending events when one of them fails.
It continues processing consecutive events in the same execution, and if at least one of the events fails, the status of the job execution is set to faulted.

PickingOrderProcessor job does not export picking orders when one of events processing fails (RTC-42291)

PickingOrderProcessor job exports picking order to other systems instantly after processing each event, so it is done even if some of the events failed in the same job execution.
When event fails with exception CartIsCancelledFault, then job execution is no longer stopped - job carries on processing consecutive events in the same execution.
If processing of scheduled event fails, then the configurable on job level delay will be added to the next reprocessing of this event.

PickingOrderProcessing job contains RIS orders that are trying to delete delivered order (RTC-41842)

When user try to delete Click and Collect (RIS) order with picking order status set to delivered then Picking Order Processor job execute it properly with completed status including reject order message.

PickingOrderProcessor job automatically reprocessing failed events (RTC-41492)

PickingOrderProcessor job processes failed events with status "RetryPending", if no other pending events were found.
The default configurable in the job retry count is 10. At 10 retries, it will sets the status to error.

Create balance popup (RTC-40920)

A "Create balance" popup is displayed when the user is creating shift balance.

Image Added

Hide shift balance difference (RTC-40857)

With the system parameter ShowBalanceDifferenceInRegistrationView, the shift balance difference can be hidden. If the parameter is set to false, the balance difference is not shown in the Edit shift balance view.

Balance improvement (RTC-39885)

To prevent different time zone problems, the BalanceDate datetime now contains 12:00:00, instead of 00:00:00.

Customer creation (RTC-40679)

Multiple clicks on the Save button will not trigger duplicated customers during the customer creation. The Save button is locked after the first click.

Deleting count groups (RTC-39839)

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

Deleting a count list (RTC-41188)

Deleting a count list can be done Stocktaking overview.
Image Added

Possible Memory Leak (RTC-39477)

OrderMessageIntegration does not overuse memory and memory leak is patched. 

Modifying count groups (RTC-43184)

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

Cashier and user improvements (RTC-43142)

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

PickingOrderProcessor job should handle Create before Update (RTC-43160)

PickingOrderProcessor job handle multiple operations for given customer order in order of creation. Operations for given customer order are not processed if previous operation (for this order) in the same execution have failed.

Export picking status blobs when picked in external system (RTC-43794)

Now the status of picking from an external order picking system like AutoStore will be updated in external systems (via Picking status blobs), So that  that the information we see in the picking order is correct, and  the external systems will get the correct status.

Emails/SMS with Receipt are not sent after removing undelivered lines (RTC-42608)

When a picking order is closed (delivered) by deleting the last item (partial delivery), confirmation Emails/SMS are sent. Messages are not sent for PAC and PAC.CW methods. The exports are working correctly.

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

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

Email send out is triggered before db transaction is committed (RTC-42873)

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

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

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

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

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

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

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

Export picking status blobs when picked in external system (RTC-43794)

Now the status of picking from an external order picking system like AutoStore will be updated in external systems (via Picking status blobs), So that  that the information we see in the picking order is correct, and  the external systems will get the correct status.

Removing last line does not cancel dispatch order (RTC-42467)

Dispatch order is cancelled after last normal item is removed from whole order in picking order. Rejected order is not visible in dispatch orders view in Chain Web.

Picking order processor job saves partially modified data for picking order despite of exception (RTC-42952)

Partially modified data is not saved by the PickingOrderProcessor job.

Product description differs on templates (RTC-41100)

Product description does not differ between OrderConfirmation and CreditNote templates. 

SKU for Click&Collect (Reserved&Collect) orders (RTC-40091)

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

Orders don't close automatically when there is no more items to deliver (RTC-40707)

Orders are closed automatically when all items have been delivered, also after items have been removed manually. Statuses in database are also updated properly.

No validation of failed refund due to locked order (RTC-42012)

When trying to refund order which has locked status, the user interface displays a validation message at the bottom of the site about the failed refund.

PickingOrderProcessor job does not export picking orders when one of events processing fails (RTC-42291)

PickingOrderProcessor job exports picking order to other systems instantly after processing each event, so it is done even if some of the events failed in the same job execution.
When event fails with exception CartIsCancelledFault, then job execution is no longer stopped - job carries on processing consecutive events in the same execution.
If processing of scheduled event fails, then the configurable on job level delay will be added to the next reprocessing of this event.

Convert scales to atte.dat files (RTC-35873)

Exported from Item Management Strongpoint scales are now converted to atte.dat files on on premise server. Job to convert scale labels was renamed to LabelImport and can be configured to support both Strongpoint and Myhrvold scales. 

For Strongpoint scales, files are created per store and can contain more than one scale label and more than one item. Files are named atte.StoreNumber.TimeStamp and are saved in a configured folder.

In first row, there are stored all required information from item-scale: if the scale label is new or removed, PLU, retail price, promotion price, status (0 if price is per Kg , 1 in all other cases), best before, tare, item group, storage temperature and origin. Next rows contain information on font size and weight declaration text. When  scale is removed from label, created file contains only first row (with numeric data), which starts with letter R. If some of exported values from item have more digits than expected in file, then job finishes with status 'CompletedWithWarninigs' with clear warning message and file is not created. However, If more item-labels are exported in the same time, files will be created, but will not include scales from incorrect item.

Fix for: Import of user fails when long user name + update CashierNo{} (RTC-40630)

StoreGroup with type CloudPermission is correctly created in the database and the job UserMerger is correctly executed when the username has more than 50 characters. 
Users with CasihierNo in BackOffice other than in the cloud user management are updated correctly, along with their cashierNo.

PickingOrderProcessor job automatically reprocessing failed events (RTC-41492)

PickingOrderProcessor job processes failed events with status "RetryPending", if no other pending events were found.
The default configurable in the job retry count is 10. At 10 retries, it will sets the status to error.

Weird error message and confusing article grid in Dispatch on refund (RTC-41585)

Warning message is no longer appear at the bottom of the site. After successful refund of not locked order user is redirect to the dispatch order details view, moreover at the bottom of the site appears green successful message.

Delay of picking order creation for specific order types (RTC-41290)

The delay of picking order creation, by the PickingOrderProcessor job, only applies to the order types 
StorePrepaidWarehouseDelivery and StorePrepaidDispatchDelivery.

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.

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.

Split order when it is partially delivered (RTC-41154)

When an order is partially delivered (some order lines), a split is created and non-delivered items are assigned to a dummy store and waiting for reassignment to another store (with available stock) that can handle and deliver the rest of the order. 

Freight items is always reassigned to the store that can handle picking orders first.

Deleting count groups (RTC-39839)

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

Create balance popup (RTC-40920)

A "Create balance" popup is displayed when the user is creating shift balance.

Image Added

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.

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. 

Cashier registration (RTC-39129)

When creating a cashier on a user, the Default cashier role is automatically selected.

The cashier username is automatically generated based on the selected store number and cashier number, if the AdditionalLabelForCashierPassword system parameter is set. 

To display a custom text above the password field, the system parameter AdditionalLabelForCashierPassword must be filled with the text to display.

Search for customer orders by external order number (RTC-39224)
When the SearchOrdersByExternalNumber system parameter is set to True, customer orders can be found by searching for the external order number in POS.

When the SearchOrdersByExternalNumber system parameter is set to False, customer orders can be searched for by order number.

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.

Possible Memory Leak (RTC-39477)

OrderMessageIntegration does not overuse memory and memory leak is patched. 

Improvement in Create stocktaking (RTC-35464)

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.

Deactivated customer is Customer service (RTC-37068)

Customers with status Deactivated in the Customer Service export, are imported to Chain Web and their status is updated in Chain.

Customer order service (RTC-38284)

The GetCustomerOrder3 method from Customer Order service returns the delivery and customer information based on what is saved on the order, rather than on the linked customer. If there is no customer data in the order, then the delivery and customer information from the linked customer is returned.

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

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

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.

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.

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

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

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.

Disable sending of OrderHasChanged messages (RTC-37214)

The 'OrderHasChangedEnabled' system parameter was implemented. It allows disabling OrderHasChanged calls when there are changes (as e.g. replace or remove items) performed on the order.

Extend "Deliver package" in Chain Web to support multiple picking orders (RTC-35972)

The "Package delivery" functionality in Chain Web was extended to support delivering (Deliver to Customer) PAC.CW orders with multiple picking orders.

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.

EHF invoice (RTC-35695)

The reference texts and reference numbers of each receipt are contained in the EHF invoice.

Signatures in receipts (RTP-27866)

The Receipts Journal displays the signature on receipts, for users that have access to see it.
To see the signatures, the user role needs to have access to "View receipt signatures".

Image Added

The signatures' images are cached in the browser.

Stocktaking Excel export (RTP-26651)

• The column names in the stocktaking Excel exports match the displayed data in the stocktaking grid.
• The "Count group completed" column shows if the count group is completed or not

Adyen Checkout (RTP-26647)

Adyen is available as a payment terminal in POS API. It is possible to pay for an order with an authorized Adyen payment. After the transaction, the payment can be captured by using PaymentService to contact Adyen itself. 

Balance improvement (RTC-39885)

To prevent different time zone problems, the BalanceDate datetime now contains 12:00:00, instead of 00:00:00.

Customer order service (RTC-38284)

The GetCustomerOrder3 method from Customer Order service returns the delivery and customer information based on what is saved on the order, rather than on the linked customer. If there is no customer data in the order, then the delivery and customer information from the linked customer is returned.

Deactivated customer is Customer service (RTC-37068)

Customers with status Deactivated in the Customer Service export, are imported to Chain Web and their status is updated in Chain.

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.

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

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

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.

Extend "Deliver package" in Chain Web to support multiple picking orders (RTC-35972)

The "Package delivery" functionality in Chain Web was extended to support delivering (Deliver to Customer) PAC.CW orders with multiple picking orders.

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.

Adyen Checkout (RTP-26647)

Adyen is available as a payment terminal in POS API. It is possible to pay for an order with an authorized Adyen payment. After the transaction, the payment can be captured by using PaymentService to contact Adyen itself. 

Stocktaking Excel export (RTP-26651)

• The column names in the stocktaking Excel exports match the displayed data in the stocktaking grid.
• The "Count group completed" column shows if the count group is completed or not.

Credit invoice export (RTC-36580)

The credit invoices are exported for the date they were created on, regardless of time.

Default credit limit (RTC-36203)

The default credit limit for credit customers is defined in the system parameter DefaultCustomerCreditLimit. If the value in the parameter is set to 0 (zero), the credit limit will default to 50,000. The highest possible value is 9999999,99.

Do not set picking store twice (RTC-36460)

BackOffice does not update the picking store through POSAPI multiple times in a single automatic reassign from the dummy store.

Support Excluding Order Placed Stores From Dispatching (RTC-36705)

The 'OrderStoreNumbersExcludedFromDispatch' system parameter allows for excluding stores from dispatching meaning no orders will be placed at the excluded store.

Block Automatic Reassign for Orders with Delivery Method PAC.CW (RTC-35975)

The automatic reassign does not take into account orders with delivery method PAC.CW.

Support PAC.CW order method in order details view (RTC-35974)

Dispatch details view supports new delivery method PAC.CW - manual edition of this method is disabled and only applicable actions are available.

Extend Communication Logic for PAC.CW Dispatch Order Type (RTC-35973)

When using delivery method PAC.CW only Order confirmation, Receipt and Order delivered is communicated to the recipient. 

Disable sending of OrderHasChanged messages (RTC-37214)

The 'OrderHasChangedEnabled' system parameter was implemented. It allows disabling OrderHasChanged calls when there are changes (as e.g. replace or remove items) performed on the order.

Create Picking Orders for PAC.CW (RTC-35969)

Creating picking orders for delivery method PAC.CW was enabled:

• Picking orders are created for the picking stores only, when the entire order can be picked at the picking stores.
• Multiple picking orders are created when some items are available at the picking stores and some have to be sent to the picking store from Central Wearhouse
• Empty picking orders are created for the picking stores when none of the items in the orders are available to be picked at the picking stores. 

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.

Count list with apostrophe (RTC-36351)

Count lists with apostrophe in the count list name can be deleted.

Possible Memory Leak (RTC-39477)

OrderMessageIntegration does not overuse memory and memory leak is patched. 

Customer order service (RTC-38284)

The GetCustomerOrder3 method from Customer Order service returns the delivery and customer information based on what is saved on the order, rather than on the linked customer. If there is no customer data in the order, then the delivery and customer information from the linked customer is returned.

Deactivated customer is Customer service (RTC-37068)

Customers with status Deactivated in the Customer Service export, are imported to Chain Web and their status is updated in Chain.

Disable sending of OrderHasChanged messages (RTC-37214)

The 'OrderHasChangedEnabled' system parameter was implemented. It allows disabling OrderHasChanged calls when there are changes (as e.g. replace or remove items) performed on the order.

Extend Communication Logic for PAC.CW Dispatch Order Type (RTC-35973)

When using delivery method PAC.CW only Order confirmation, Receipt and Order delivered is communicated to the recipient. 

Extend "Deliver package" in Chain Web to support multiple picking orders (RTC-35972)

The "Package delivery" functionality in CW was extended to support delivering (Deliver to Customer) PAC.CW orders with multiple picking orders.

Create Picking Orders for PAC.CW (RTC-35969)

Creating picking orders for delivery method PAC.CW was enabled:

• Picking orders are created for the picking stores only, when the entire order can be picked at the picking stores.
• Multiple picking orders are created when some items are available at the picking stores and some have to be sent to the picking store from Central Wearhouse
• Empty picking orders are created for the picking stores when none of the items in the orders are available to be picked at the picking stores. 

Recipient's data (RTP-27150)

When creating a Web Order/Reserve & Collect Order in POS, the recipients name is shown correctly in receipts with customer information, picking lists, order confirmations, Dispatch Order screen in Chain Web, and in orders in POS. Information such as customer name, address, phone Number, and e-mail corresponds to the recipient's data.

Default credit limit (RTC-36203)

The default credit limit for credit customers is defined in the system parameter DefaultCustomerCreditLimit. If the value in the parameter is set to 0 (zero), the credit limit will default to 50,000. The highest possible value is 9999999,99.

Do not set picking store twice (RTC-36460)

BackOffice does not update the picking store through POSAPI multiple times in a single automatic reassign from the dummy store.

Block Automatic Reassign for Orders with Delivery Method PAC.CW (RTC-35975)

The automatic reassign does not take into account orders with delivery method PAC.CW.

Support PAC.CW order method in order details view (RTC-35974)

Dispatch details view supports new delivery method PAC.CW - manual edition of this method is disabled and only applicable actions are available.

Support Excluding Order Placed Stores From Dispatching (RTC-36705)

The 'OrderStoreNumbersExcludedFromDispatch' system parameter allows for excluding stores from dispatching meaning no orders will be placed at the excluded store.

Configuration for which services and integrations to be shown in System info (

The services and integrations to be shown in Services/Integration in POS can be controlled by using 'ServicesToShowInSystemPanel' POS Configuration parameter. By default, this parameter is empty and there will be no services/integrations shown.

Count list with apostrophe (RTC-36351)

Count lists with apostrophe in the count list name can be deleted.

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.

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.

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. 

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.

ReconcileConfiguration parameter (RTP-25654)

"ReconcileConfiguration" parameter is added in POS Configuration, wherein a list of items (EANs) can be added (separated by comma) and also the line sales they correspond to.

New balance wizard improvements (RTC-34593)

• After registering a balance and turning back, the cash register can no longer be changed in both the old and new balance registration wizard.
• The balance registration for all cashiers message is not longer shown on entering the new balance registration wizard.

Customer Service Integration (RTC-34286)

Import of business customers from CustomerService contains optional field called "name".

Import localization (RTC-34430)

The Norwegian translation of instruction text in Import Excel modal properly lists required columns.

Fix: "Create" button in New Customer order window (RTC-33532)

"Create" button is available, when customer or customer and project are selected

Fix: EHF invoices (RTC-35288)

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

Consolidate EHF invoices (RTC-31388)

User is able to set on true for "consolidated invoice" and "electronic invoicing" flags at the same time in the "invoicing" tab in customer's details and it is now possible to create consolidated EHF invoices.

Invoices for receipts for the same customer but from different projects are consolidated in project scope - one consolidated invoice for each project.

Extend Dispatch Order Details View With Gift Card and Payment Info (RTC-35070)

The Dispatch Order details view has been extended with the Customer Order and Payment tabs. It is possible to see the payment transactions when an order is paid with a gift card. What is more, the Payment grid contains link to Gift card data.

Extend Picking Order JSON With Order Placement Store (RTC-34847)

The Customer Order contract for the Picking Order is extended with info about which store the order was placed in and which store the order should be picked in.  

Change order delivery methods (RTC-34676)

A new section called delivery method has been added to the dispatch order details view. It shows which delivery method the order has been placed with, and if the status of the order is "New" its possible to change delivery method by clicking on the "Edit" button. It is not possible to change to or from delivery method Pay&Collect(Code = PAC).

Show What Store has Placed the Order (RTC-34671)

The "Placed at store" field informing what store (Number and Store Name) the order was originally placed in is visible in the order dispatch details view in the "Order information" section.

Hide "send order" button when UseDispatchServiceForShipments = True (RTC-32835)

When the system parameter UseDispatchServiceForShipments = True, the "send order" button is hidden.

Improved performance when activating configuration changes for POS (RTC-30703

Changes were done in [Chain].[udf_StoreGroupConfigurationSet] function to improve performance when activating configuration changes in POS.

Performance improvements (RTC-34269)

To avoid report timing out, improvements in the queries for two reports have been made:

• Customer frequency - 0801_CustomerFrequence
• Sales per assortment - 0803_SalesPerAssortment

Count list grid view (RTC-35052)

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

Import localization (RTC-34430)

The Norwegian translation of instruction text in Import Excel modal properly lists required columns.

Fix: "Create" button in New Customer order window (RTC-33532)

"Create" button is available, when customer or customer and project are selected

Improved performance when activating configuration changes for POS (RTC-30703

Changes were done in [Chain].[udf_StoreGroupConfigurationSet] function to improve performance when activating configuration changes in POS.

Performance improvements (RTC-34269)

To avoid report timing out, improvements in the queries for two reports have been made:

• Customer frequency - 0801_CustomerFrequence
• Sales per assortment - 0803_SalesPerAssortment

Count list grid view (RTC-35052)

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

Customer Service Integration (RTC-32580)

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

Shipping details (RTC-20057)

Shipping details are available in Order lines tab in customer order details view.
New column "Package no", that is hidden by default, displays Package Tracking Number.
In order line details view are available shipping details like:

• Package Tracking Number,
• Shipment Tracking Number,
• Shipment Provider.

If for Shipment Provider is set up TrackingUrl in CustomerOrderDeliveryMethod system parameter, then the link to the tracking package is available in Shipping Details under "Trace order" label.
Package number in "Package no" column is also available as link when this condition is met.

Image Added

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.

Content-security-Policy Errors (RTC-22193)

Errors related to Content-Security-Policy are not thrown when entering Dispatch Rule in the Dispatch Rules view. 

Resend EHF (RTC-33534)

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

LindbakRetailIntegration (SSIS packages) (RTC-33091)

The email related/ processed column 'AD_username' was renamed to 'Email' in CashierStaging package.

PLU Board setup (RTP-18732)

Maximum size for image upload in PLU Board setup in POS Configuration is 100kb now.

Export functionality for PLU Boards (RTC-30610)

It is now possible to export PLU Board details to a .csv file.

Hidden parameter value in POS Configuration (RTP-23137)

'CoopayBackupSeed' parameter's value is hidden in POS Configuration view.

Image Added