Description Pipeline ProcessBasket-AdjustBasketByInventoryStatus contains a second Transaction-Begin instead of a Transaction-Commit transition. Repro Steps Pipeline ProcessBasket-AdjustBasketByInventoryStatus contains a second Transaction-Begin instead of a Transaction-Commit transition. Konsum (CM

Description The following Import or Export references are missing at the overview Reference - XML Import and Export Specifications: ac_order_status_import_xml.xsd: no reference for this xsd linked Standard Order Export: Full Entry missing (xsd not linked, reference at Reference - Order Export) As far

Description Description: The methods com.intershop.tool.common.Main.getPreparationStep(PreparerConfig) and com.intershop.tool.common.Main.storePreparationStep(PreparerResult result, String toolName) in ICM 7.8.x (and newer versions) have a crude error handling. Here from the source code: catch(Exception

Description Description: In the B2B Storefront if you add a product with a minimum order quantity > 1 from the compare page to the basket there will be one more product added than the quantity is set to. Steps to repeat: in inTRONICS Business channel select a product in the attributes tab set the step

Description Description: In the order approval workflow sometimes e-mails will use OrderNotificationEmailFrom values from the domain preferences and sometimes from the application preferences. The customers expects that only the value from the domain preferences ( channel preferences -> Order Notification)

Description Description: Currently, in the product detail page the complete REST details incl. authentication-token are printed in Browser's page source. These information can be misused. We should hide these information. Steps to repeat: click on PDP, e.g. http://jxdemoserver6.intershop.de/INTERSHO

Description Description: The customer compared a fresh installed 7.10.14.0 with a 7.8.4,0 and found much longer response times in the newer version for example for a simple trial to retrieve the current basket. We requested a performance log and found that for every request to a pipeline after the first

Description Problem: Customers face sometime the error message 'Invalid jump target' after a deployment and server start. This requires at least one server restart. The application server does not work otherwise. Expected behavior: error does not occur, server restart not necessary extended logging,

Description Problem: The shop does not response to customer requests for a long time. The customer restarts all web servers if this problem happen to fix the problem. Investigation: The default installation of the customer consists of 6 application servers. 6 new application servers (including new VMs)

Description Description: The project team found a ListNavigationVO initialization in f_business/a_storefront/sld_ch_sf_base/src/main/java/com/intershop/sellside/storefront/base/pipelet/CreateSearchIndexSearchResultNavigationList.java that circumvents the component framework based wiring of ListNavigationVO