Description Larger import processes runs in to "maximum open cursors exceeded". Mostly customers are not involved, the specific code was delivered via custom fixes only. 2024-01-15T16:37:45.4205299Z at com.intershop.beehive.core.internal.impex.BulkerThread.handleElement(BulkerThread.java:93) 2024-01-15T16:37:45

Description Due to a missing product validation / handling when the <availability-status> tag is empty in combination with a <valid-to> / <valid-from> tag in the product import file, the product data in the database is not correct and leads to not listed products in the advanced product search when filtering

Description The allowlisting of classes for the global cache reset event logging have no effect, due to retrieval of the StackTraceElement class itself instead of the affected class from the stack trace. E.g. com.intershop.beehive.core.pipelet.database.RefreshCache is allowlisted, still it's logged:

Description String or binary data would be truncated in table 'xxx.dbo.AUDITITEM', column 'TRANSACTIONID'. Truncated value: '3a1c1abe-bea6-4977-b551-6673 core_review null Bug null Verified Closed ede Critical AdoWorkItem 92811 Infrastructure Products Products ICM 0 Fixed in Commit 92916 Parent as/11

Description When the article fact data (A and N import files) are defined in a higher level than the stocks within the shop hierarchy, then reserved and blocked quantities may be overseen. The issue does not affect installation using reseved stocks. (see doc on Shop2SupplierDO.allowParentStock) Steps

Table of Contents Introduction What's New? Features References Fixed Defects Documentation Breaking Changes Changes That Require More Recent ICM Versions Introduction Welcome to Intershop Progressive Web App 5.0. This public release note contains information about the latest features of the Intershop

null Bug null Verified Closed null Blocker AdoWorkItem 92728 Products Products 0 Pull Request 92734 Parent 7.30.0

Description Currently it's not possible for projects to generate a sitemap for the PWA because the domainsplitting configuration can't be adapted/replaced by projects (customizations). The domainsplitting configuration as part of the URLRewriting is necessary to rewrite the ICM URLs in the sitemap. In

Description When importing products in UPDATE mode, but specifying REPLACE mode for "category-links", the default category does not change. During the import process, the following warning is thrown: WARN c.i.b.core.internal.impex.FileLogger - Impex Warning message: There was no explicit default category

Description If a Pod fails unexpectedly e.g. killed by OOM or by deleting the Pod currently running processes and the resource locks that the processes have acquired are not released when Pod restarts. Previously this was covered by the execution of ReleaseAllProcesses preparer or by ProcessMgrImpl.

Description It is possible to use special characters as subcategory ID if changing the ID after creation Actual Behavior Create a new subcategory for any catalog (on master or channel level)try to use special characters for the ID. You will get the following message: "Category could not be created: The

Description When PWA sitemap is generated as described in problem (see parent issue) the host name is replaced with the maintained external PWA url from the application. Since the sitemap has its own protocol definition (http, https, but ootb-only https for PWA Sitemap - see screenshot) and there's only

Description The entries in the table TRANSPORTCONFIG stay in the table after a domain is deleted and the job DeleteDomainReferences finished. The job does not throw an error. hotfix_required null Bug null Verified Closed null Major AdoWorkItem 92641 SMC and Operations Products Products 0 Pull Request

Description Precondition ICM 11.7 The REST Request: OPTIONS /customers/{CustomerKey}/users/{CustomerItemUserKey}/wishlists/{CustomerWishlistKey}/share returns always an empty result. There is no possibility to get the available payment options for a customer to show them on the myAccount payment page

Description When creating new return requests via the RMA API, the request has to include a customAttributes field on header level, otherwise a 500 server error code is returned. The field is not marked as required in the API definition and should therefore not be mandatory. Failing request example:

Issue Description Custom Fix Issue Description An increase in Solr search index build times and a slower ICM Back Office product search has been detected in our latest releases, ICM 7.10.38.28-LTS and ICM 7.10.40.5. This behavior is intensified with an increasing number of products in the system. Customers

Description The WishListRO does not contain a method for setting the creationDate. Without this method, it is not possible to set the creationDate for an object that was created with the default constructor. Note: getCreationDate could throw a NPE if creationDate is null. A check should be implemented

Description During deletion a SQLIntegrityConstraintViolationException occurs. Original Description: The customer has a huge DELETEDUSER (>10.000 entries) table and the DeleteUserReferences seem to only delete about 200 entries. So it takes several attempts to delete all user references. Is it possible

Description see task number in code null Bug null New New null Major AdoWorkItem 92460 Products Products iom/5.0.0

null Bug null New New null Major AdoWorkItem 92464 Products Products iom/5.0.0