Steps to Repeat ICM backoffice: - select channel inSPIRED - go to Orders > Shipping Configuration - create a region without a (display) name, e.g. - by import <region> <id>ATestWithoutDisplayName</id> <address-type>Regular</address-type> <active>true</active> </region> - or select user preferred language

Description When the database is not (yet) available during startup and the retryOnError property is enabled then a retry fails with exceptions. A connection to the database can't be established by the Appserver, the startup fails Steps to Repeat 1. set the properties intershop.startup.retryOnError=true

Table of Contents Introduction References Category Import Data Category Loop Steps to repeat Impact How Can This Inconsistency Be Detected? Can I Mend the Situation? How Can This Inconsistency Be Prevented? Category trees without a root category Steps to Repeat Impact How Can This Inconsistency Be Detected

Expected Behavior Shipping address has to belong to the positions in that invoice Business Impact Wrong documents are created. This probably has some legal implications. Domain Order Management Bug Order Management Fixed and verified Closed null Major AdoWorkItem 85085 Products IOM Invoicing Payment

Description Temporary workaround for #61509 causes a test failure and has to be reverted since it's obsolete now. Actual Behavior Temporary workaround causes a test failure and has to be reverted since it's obsolete now. Expected Behavior No test failures. konsum-starter release-as11-merge-skipped Konsum

Description Note: This is an intermediate fix, ensuring that a shipping address belonging to one of the invoice positions is assigned to the invoice. There will be a subsequent release for order documents "v2" including proper shipping bucket support in invoice documents. Actual Behavior a random shipping

Description According to the API, a name for the deliveryDate is only required for the type EXPRESS, and ignored in other cases. A name mismatch between the STANDARD and EXPRESS types can lead to a wrong type assignement. Steps to Repeat Define a name mapping for the STANDARD type in "Shop2DeliveryTypeDefDO"

Description Removal of outdated (invalid) baskets in the database should be different for ORACLE and MS SQL Server, because current Storage Procedure sp_basket_observer might cause a so-called Lock Escalation on MS SQL Server in case of a large amount of entries in the table BASKET or basket related

Description Release notes: This release improve the product import performances. Beside stored procedure changes, and small changes in the definition of some DOs in java, the fillfactor of 4 tables have been modified to reduce bloat issues. It is recommended to fully vacuum these tables as part of the

Description These attributes were apparently forgotten in a previous removal of the order merge feature. ReturnPosDO.subReturnRef DispatchPosDO.subDispatchRef (this one was not even tagged as deprecated ) OrderPosCancelDO.subOrderCancelRef ResponsePosDO.subResponseRef RemovalNote Domain Order Management