Chain Web  2.10.341 - 2.10.274

Prev Next

Chain Web v. 2.10.341 

Released 11th of February 2025

Version requirements can be found in the Release Notes tab in this Jira: (RTC-46896)

Improvements

Balance

Balance permissions (RTC-45009)

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

Modifying shift settlement without submitting settlement, resets settlement (RTC-44386)

Values displayed in the shift balance edit view are always fetched from previously submitted settlement and editing the settlement without submit does not longer affect displayed values.

Users

Create users with special characters (RTC-47349)

In user management, users can be created with "/", "\" and space in the username.
Note that in some cases, the user might not be exported to Chain correctly.

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.


Chain Web v. 2.10.340

Released 11th of November 2024

Improvements

Batch Import

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.

Customer

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.

Customer order

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.

Gift card module

Regive (RTC-44329)

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

Order dispatch

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.

Order picking

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.

Reports

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.

Stocktaking

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.


Chain Web v. 2.10.331 

Released 18th September 2024

Improvements

Area

Description

Cashier

Cashier and user improvements (RTC-43142)

  • Cashier cannot be created with a nonpositive cashier number.

  • The user name cannot contain "/", "\" or space characters.

Count groups

Modifying count groups (RTC-43184)
Count groups created by HQ users can no longer be modified by non-HQ users.

Customer order

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.

Dispatch order

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 trigged before db transaction is comitted (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.

Picking orders

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

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.

Receipt journal

Improved search performance (RTC-41230)
The performance when searching in the Receipt Journal has been significantly improved, and reduced the timeout occurrence.

Vat rate with decimals on Receipt details (RTC-43255)
VAT can be displayed with one decimal number in the receipt details in The Receipt journal view.

POS Services 7.90.94.0 or higher is required!

Scale labels

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.

Users/ Cashiers

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.


Chain Web v. 2.10.322

Released 22nd of August 2024

Improvement

Improved search performance (RTC-41230)

The performance when searching in the Receipt Journal has been significantly  improved, and reduced the timeout occurrence.


Chain Web v. 2.10.321

Released 18th of June 2024

Improvements

Area

Description

Balance

Create balance popup (RTC-40920)

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


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

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.

Dispatch orders

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 Chain Web, 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 Chain Web are sent to the Central warehouse, order lines not in stock at Chain Web 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 Chain Web.

Picking orders

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.

Picking orders export

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.

POS Configuration

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.

Reports

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.

Stocktaking

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.


Chain Web v. 2.10.317 - coming next release

Planned

Improvement

SAF-T receipt export locking (RTP-37478)

Fix for locking in encountered when SAF-T receipt export is triggered.

Required: SAFTReceiptExport 1.1.2 or higher.


Chain Web v. 2.10.316

Released 10th of December 2024

Improvement

Balance permissions

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


Chain Web v. 2.10.315

Released 13th of November 2024

Improvement

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.


Chain Web v. 2.10.313

Released 27th of August 2024

Improvement

Customer order

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.


Chain Web v. 2.10.311

Released 23rd of May 2024

Improvement

POS Configuration 

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.


Chain Web v. 2.10.310

Released 2nd of May 2024

Improved handling of PLU List config for POS

(RTP-27604)

Configuration of PLU Lists for POS has been changed in Chain Web to prevent XML parsing issues and 'System.OutOfMemoryException' in POS. Chain Web will no longer add redundant 'FunctionSet' nodes in the PLU Lists XML definitions when editing the lists or adding new pages to the list. 

In addition, a new function button called 'Repair PLU' has been added to the PLU List visual editor in Chain Web to repair PLU List definitions where redundant XML nodes has been created. This reduces the size of the PLU list definition significantly making it much easier for POS to process the PLU Lists without the risk of throwing a 'System.OutOfMemoryException'.

Flight data in receipt header

(RTP-28679)

Parameter to configure which flight data to show in receipt header - FlightHeaderInSaleView - has been implemented. More flight data is shown in receipt header if configured.

POS Configuration

FlightHeaderInSaleView parameter (default value: <?xml version="1.0" encoding="utf-16"?><StringListConfigBE xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><stringList><string>Flight</string><string>Destination</string><string>FlightCode</string><string>FinalDestination</string><string>NorwegianTollQuota</string></stringList></StringListConfigBE>)

Allows to set visible fields in flight header in sales view.

Improvements

Area

Description

Customer order

Customer order - structured note (RTC-40479)

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

Customer
OrderService

Search for customer orders by external order number (RTC-40201)

Customer orders can be found by searching for the external order number in POS.

Order dispatch

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.

OrderMessageIntegration

Possible Memory Leak (RTC-39477)
OrderMessageIntegration does not overuse memory and memory leak is patched.

Users/
Cashiers

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.


Chain Web v. 2.10.309991

Released 19th of March 2025

Improvements

Dispatch order

PickingOrderProcessor should skip orders based on order number - store number combination (RTC-48174)

PickingOrderProcessor job are using combination of order number and store number when handling processing of orders.

Stocktaking

Deleting a count list (RTC-45741)

Deleting a count list can be done from "Overview" under Stocktaking in the Menu.


Chain Web v. 2.10.30999

Released 13th of November 2024

Improvements

Dispatch orders

Payment method missing/incorrect in Email templates (RTC-44436)

Payment methods used for particular order are properly displayed in the email templates:

  • Payment methods with amount less or equal to 0 are not displayed in templates and receipt pdfs.

  • Payment methods are properly fetched from database tables.

  • Order paid with multiple payment methods contains all methods in all templates displaying payment method (e.g Payment method: Klarna,Giftcard).

  • There is no difference in how payment method is displayed on the email templates for orders created in Webshop and orders created in Physical store.

Gift card

Redirect for Gift card in Cloud or Chain Web (RTC-44967)

The system parameter RedirectToGiftCardManagement defines if the user should be sent to Gift cards in Chain Web or Gift Card management in Cloud.
If the parameter is set to True, and the "CloudChainUrl" parameter is not empty, the user will be redirected to GiftCard management in Cloud from the navigation menu.
If the parameter is set to False, the user will always be directed to Gift Cards view in Chain Web.

Order picking

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

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

Users

Create users with special characters (RTC-44999)

In user management, users can be created with "/", "\" and space in the username.
Note that in some cases, the user might not be exported to Chain correctly.
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.


Chain Web v. 2.10.30998

Released 10th of October 2024

Improvement

Count groups

Modifying count groups (RTC-43184)

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


Chain Web v. 2.10.30997

Released 25th of September 2024

Improvements

Cashier

Cashier and user improvements (RTC-43142)

  • Cashier cannot be created with a nonpositive cashier number.

  • The user name cannot contain "/", "\" or space characters.

Order dispatch

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.

Order picking

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.


Chain Web v. 2.10.30996

Released 16th of September 2024

 Improvements

Customer orders

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.

Order dispatch

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.

Order picking

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.


Chain Web v. 2.10.30995

Released 23rd of August 2024

Improvement

Order dispatch

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.


Chain Web v. 2.10.30994

Released 16th of August 2024

Improvement

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.


Chain Web v. 2.10.30993

Released 14th of August 2024

 Improvements

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.

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.


Chain Web v. 2.10.30992

Released 22nd of July 2024

Improvements

Order dispatch

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.

PickingOrder
Processor job

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.

Scale labels

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.

Users/Cashiers

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.


Chain Web v. 2.10.30991

Released 3rd of July 2024

Improvement

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.


Chain Web v. 2.10.3099

Released 28th of June 2024

 Improvements

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.


Chain Web v. 2.10.3097

Released 18th of June 2024

Improvements

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


Chain Web v. 2.10.3096

Released 14th of June 2024

Improvement

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.


Chain Web v. 2.10.3093

Released 03rd of June 2024

 Improvements

Order dispatch

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.

Stocktaking

Deleting count groups (RTC-39839)

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


Chain Web v. 2.10.3092

Released 31th of May 2024

Improvements

Balance

Create balance popup (RTC-40920)

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

Picking orders

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.


Chain Web v. 2.10.309

Released 17th of May 2024

Improvements

Dispatch orders

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.


Chain Web v. 2.10.308

Released 06th of May 2024

Improvement

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.


Chain Web v. 2.10.307

Released 29th of April 2024

Improvement

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


Chain Web v. 2.10.306

Released 25th of April 2024

Version Requirements is located on the menu to the left. 

Improvement

Customer order - structured note (RTC-40479)

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


Chain Web v. 2.10.305

Released 19th of April 2024

Improvement

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.


Chain Web v. 2.10.304

Released 16th of April 2024

Improvements

Customer
Order
Service

Search for customer orders by external order number (RTC-40201)

Customer orders can be found by searching for the external order number in POS.

Order dispatch

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


Chain Web v. 2.10.303

Released 10th of April 2024

Improvement

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.


Chain Web v. 2.10.302

Released 28th of March 2024

Improvement

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.


Chain Web v. 2.10.301

Released 15th of March 2024

Improvements

Cashier management

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.

Customer
Order
Service

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.

Dispatch orders

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.

Order
Message
Integration

Possible memory leak (RTC-39477)

OrderMessageIntegration does not overuse memory and memory leak is patched. 

Stocktaking

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.


Chain Web v. 2.10.300

Released 6th of March 2024

Improvements

Customer

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.

Dispatch orders

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

Invoices

EHF invoice (RTC-35695)

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

Order Message Integration

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.

Receipt journal

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

The signatures' images are cached in the browser.

Stocktaking export

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

POS  API

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. 


Chain Web v. 2.10.294

Released 30th of April 2024

Improvement

Balance improvement (RTC-39885)

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


Chain Web v. 2.10.293

Released 16th of February 2024

Improvements

Customer

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.

Dispatch orders

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

Order Message Integration

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.

POS API

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 export

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.


Chain Web v. 2.10.292

Released 26th of January 2024

Improvements

Credit invoice

Credit invoice export (RTC-36580)

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

Customer

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.

Dispatch orders

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. 

Reports

Stock list (RTC-37811)

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

Stocktaking

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.


Chain Web v. 2.10.2891

Released 5th of April 2024

 
Improved handling of PLU List config for POS

(RTP-27604)

Configuration of PLU Lists for POS has been changed in Chain Web to prevent XML parsing issues and 'System.OutOfMemoryException' in POS. Chain Web will no longer add redundant 'FunctionSet' nodes in the PLU Lists XML definitions when editing the lists or adding new pages to the list. 

In addition, a new function button called 'Repair PLU' has been added to the PLU List visual editor in Chain Web to repair PLU List definitions where redundant XML nodes has been created. This reduces the size of the PLU list definition significantly making it much easier for POS to process the PLU Lists without the risk of throwing a 'System.OutOfMemoryException'.


Chain Web v. 2.10.289

Released 20th of March 2024

Improvements

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.


Possible Memory Leak (RTC-39477)

OrderMessageIntegration does not overuse memory and memory leak is patched.


Chain Web v. 2.10.288

Released 26th of February 2024

Improvements

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.


Chain Web v. 2.10.287

Released 8th of March 2024

Improvement

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

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


Chain Web v. 2.10.286

Released 26th of February 2024

Improvements

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

Order Message Integration

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.


2.10.285

Released 14th of February 2024

Improvements

Dispatch orders

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


Chain Web v. 2.10.284

Released 6th of February 2024

Improvements

Customer

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.

Dispatch orders

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. 

Orders

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.

Required

Chain Web v. 2.10.284 or higher!

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.

Required

Chain Web v. 2.10.284


Chain Web v. 2.10.283

Released 25th of January 2024  

Improvement

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


Chain Web v. 2.10.282 

Released 5th of January 2024

Improvements

Dispatch orders

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.

POS Configuration

Configuration for which services and integrations to be shown in System info  (RTP-26500)

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.

Required

POS Master v. 3.0.0.141

Stocktaking

Count list with apostrophe (RTC-36351)

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


Chain Web v. 2.10.280 

Released 6th of December 2023

Improvements

Dispatch orders

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.

POS Configuration

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.


Chain Web v. 2.10.274

Released 21st of May 2024

Improvement

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.