Description Dover reported an increasing order value difference with a rising number of products when a promotion line item is used. In case that this wont be treated as defect could you please provide some hints how to improve the precision for the calculation to keep differences on a minimal level

Description WA log: [2022-05-10 14:50:45 +0200] server [26892/25532/DGkCAGJ6X6QGsqjA-33-35] ERROR request: BhvSubRequestProcessIncludes(): max. recursion level (include.maxdepth=32) for <wainclude>s exceeded while processing /INTERSHOP/web/WFS/inSPIRED-inTRONICS-Site/en_US/-/USD/IncludeBranding-StyleSheetHook

Description A new REST interface is necessary to allow PWAs to trigger GDPR action "delete" and "send information" after user followed link in GDPR response email. Steps to Repeat Copied from Description when changed from Task to Bug A new REST interface is necessary to allow PWAs to trigger GDPR action

Description If you compare the OMT search forms between the orders and the products, no shops nor suppliers are selected for the orders, whereas they are all selected in the product form. The behaviour should be the same in both cases whereas the order search way is the better one: it is faseter to select

Description IOM has the possibility to automatically deduct inventory from a supplier's stock level when the order is commissioned. This logic currently works with the originally ordered quantity of a line item only. It should however also consider any canceled units as these will not need to be fulfilled

Table of Contents Introduction References Glossary Activation Implementation ICM Cookie Handling Configuration Hint for Customization Pipeline Calls / Log in and Out Introduction This document is valid from ICM 7.10.32.16-LTS and 7.10.38-9-LTS to 12.0. For previous versions, refer to Concept - Integration

Description The export configurations of: ORDEREXPORT_STANDARD_BAKERY_V1 ORDEREXPORT_IDEAL have been removed. This has been done without deprecation cycle because both implementation classes have actually been removed a long time ago. RemovalNote null Task null Completed Closed null Major AdoWorkItem

Description OrderExportConfigBeanDefDO.RETURN_ANNOUNCEMENT_EXPORT has been deprecated. Projects should migrate to ReturnAnnouncementTransmissionDOs instead. DeprecationNote null Task null Completed Closed null Major AdoWorkItem 76444 Return RMA-Process Products Products iom/4.1.0

Description After running dbprepare on 7.10.38.5-LTS, the replication of tables from the staginggroup PRICING_PriceScale fails. ERROR - Error preparing staging table PRICEDEFINITIONPRODUCTBINDING com.microsoft.sqlserver.jdbc.SQLServerException: There is already an object named 'PKPRICEDEFINITIONPROD

Description In case of a return announcement, it is possible to activate exports as transmissions. In that case, one config is needed per supplier to get one export per supplier. However, there is a bug in case the order has multiple suppliers: an export is generated even though there is no article in