Description The AddPreferenceDefinitionsPreparer step does not create an entry for DefaultPaymentMethodRecurringOrders ( uuid in PreferenceDefinitionUUIDs.properties is missing ) Repro Steps Customer does migrate db schema from previous ICM version to latest 7.10.37.1 Due to missing PreferenceGroupUUIDs

Description during the import of 10k price-list entries the following error occurred: [2022-02-07 17:35:37.277 +0100] [BulkerThread-0] [impex.inSPIRED-inTRONICS.1] ERROR com.intershop.beehive.core.internal.impex.FileLogger  - Impex Error message: ORMException occurred while removing price scale tables

Description The Javadoc of "ORMCatalogCategoryBOImpl::getString(...)" states that it returns: "the value of a custom attibute. If the category is a root category, a fallback to the catalog is done." but there is no check for root category at all. Fix_with_next_patch null Bug null Verified Closed Stadtwerke

Description Customer noticed, that there are some issues in the Payload they are receiving from IOM for RMA: Payload looks like this, and it is missing the county field: Also there is a NULL in the Addition address field: <ns2:Addition>Principala nr 145 null</ns2:Addition> <?xml version="1.0" encodi

Actual Behavior Multiple implementations are levaraging ForkJoinPool#commonPool for async computations in the following apps: order-app transmission-app schedule-app e.g. CompletableFuture&lt;List&lt;OrderState&gt;&gt; future1 = CompletableFuture                            .supplyAsync the

Description ICM Version of the client: 7.10.24.2 The customer has noticed that new system pages are missing on the Prod Edit and Live system. During the analysis, we found a SQLServerException in the error log which was thrown during application server start only! [%date{yyyy-MM-dd HH:mm:ss.SSS Z}] %-5level

Description When using non-numeric characters in shipping bucket identifiers, sending customer mails will fail with an exception. Error at ShopCustomerMailMessageAcceptorMDBean : caused by: class java.lang.NumberFormatException: For input string: "76157166-001" java.base/java.lang.NumberFormatException

Description Publication switches synonyms on tables that are members of a staging group included in the replication. STAGING$switch_synonyms & friends use the current entries in STAGINGTABLE (column LIVETABLENAMESUFFIX, in particular) to figure out where to point the synonym to (if suffix is currently

Description The customer noticed loads of error messages in their edit system, like this: [2022-01-25 17:40:38.001 +0100] ERROR localhost ES17 appserver0 [inSPIRED-Site] [inTRONICS] com.intershop.component.image.pipelet.CreateImageBOThumbnail [] [Storefront] [tQtxVGDvVbJwVAEfrzI8bGDlECJgMcXGpG7UfXGK]

Description ticket should wait: [24.8.2022 10:11] Philipp Borchert ich würde das ticket erstmal parken, wir haben letztens schonmal kurzfristig drüber elaboriert das health check geraffel nach microprofile-health zu migrieren weil das im wildfly integriert ist Actual Behavior In case IOM instances are

Repro Steps - setup ICM replication - inside the edit system create some SMC schedule jobs for channel inTRONICS - inside the edit execute execute some business object replication for below items by using list views or object related properties views - after the business object replication the batch

Actual Behavior HTTP-201 is incorrectly documented a the return code for update transmissions endpoint The specification lists 201 and 207 for a successfull call, but just 207 should be documented. 201 will never be returned. null Bug null Verified Closed null Major AdoWorkItem 73604 Products Products

Description The class ContactXML contains wrong setEMail method naming Repro Steps Customer is using com.intershop.adapter.orderexport.xml.binding.impl.ContactXML with method setEMail inside custom code to read an ICM exported order.xml file. ( this is by default not our standard - we do not read order

Actual Behavior REST-calls from OMT using ShopDO.name instead of ShopDO.shopName as expected by API. If different, the OMT notifies an error. Expected Behavior REST-calls from OMT are working with with correct parameters. null Bug null Verified Closed null Major AdoWorkItem 72901 Products Products 0

Description Since 7.10.38 the amount query parameter for product list calls in the REST API has a hard limit of 200. This should be configurable. Actual Behavior /products?amount=1000 will lead to "bad request" Expected Behavior A project should be able to override this limit, e.g., because there is

Description The Job ProcessProductPriceRefresh removes to many objects in PRODUCTPRICECHANGEEVENT table which could lead to OCAException when changing or importing price lists. [2022-01-18 16:29:00.706 +0100] ERROR localhost ES1 appserver0 [] [] com.intershop.beehive.core.internal.job.JobExecutor []

Description The Payone cartridge logs several sensitive banking data in different logs, at least, when "Sofortüberweisung" is used, example (anonymized): - warn log (Request Parameters) [2022-01-17 08:26:13.998 +0000] WARN ...prod-lv-app000000.internal.cloudapp.net ES1 appserver0 [....-Site] [-] com

Description Getting a PriceListPO through the Query Framework will not call injectMembers as expected. This can lead to NPEs when trying to access a non-instantiated Mgr class. [2022-01-10 10:10:56.093 +0100] ERROR localhost ES1 appserver0 [] [] com.incentro.intershop.impex.pipelet.CleanPriceLists []

Actual Behavior REST-calls from OMT using ShopDO.name instead of ShopDO.shopName as expected by API. If different, the OMT notifies an error. Expected Behavior REST-calls from OMT are working with with correct parameters. null Bug null Verified Closed null Major AdoWorkItem 72857 Products Products 0

Description There is a follow up issue with the bug fix Bug 70155. If the database contains old price scale entries with an unit and only delta pricelist imports are performed, the following error may occur: Caused by: java.lang.IllegalArgumentException: The quantity is of invalid unit. Should be: but