Description Description: A java.lang.IllegalAccessError occurs in In a patched class from <IS_LOCAL>/lib when calling a protected/default method from a class of the same package. Example: I want to patch the class com/intershop/sellside/pmc/internal/rendering/PipelineDictionaryProvider.java. In this

Description Problem: The ORM persistence manager locks the whole cache manager implementation in: com.intershop.beehive.orm.internal.common.PersistenceManagerImpl.createObject(ORMObjectKey, ClassDescription) com.intershop.beehive.orm.internal.common.PersistenceManagerImpl.getObjectByQueryResult(QueryResult)

Description Description: The Localization domain of a partner application is not deleted when the partner is deleted. Steps to repeat: login as admin to inSPIRED select "Reseller Channel" create a new partner PartnerSupport login as admin to PartnerSupport create a new sales channel PartnerSupportChannel

Description Description: The GetUserGroupsByCustomerSegments pipelet does throw an exception in case of an invalid live system USERGROUPASSIGNMENT table entry Steps to repeat: In case of special replication scenario steps: create promotion in editing system replicate to live assign promotion to users

Description REST call: post baskets/<basketId>/merges The baskets could not be merged. Authentication token contains syntactic errors. code: basket.merges.authentication_token_syntax_failure.error Further Investigations it seems the problem occur if the authentication token comtains the prefix 'encryption'

Description REST request: post basket/<basketId>/items Current behavior if you add a product to basket with a quantity that exceeds the maximum quantity per line item limit there are 2 info messages: "This product has limited inventory. We have adjusted the quantity to reflect the number of products

Description In basket REST request answers the client needs information of the lineItemId in the info section. Only the paths section is not convinient at all. Example: Maximum Quantity per Product in Cart will be exceeded by the following operations post: /basket/<basketId/items (Add a product with

Description Description: The GetUserGroupsByCustomerSegments pipelet does throw an exception in case of an invalid live system USERGROUPASSIGNMENT table entry Steps to repeat: In case of special replication scenario steps: create promotion in editing system replicate to live assign promotion to users

Description Description: In the web adapter agent log the number of invalidated pages for a search word are logged for the site. In this message the search word is logged after pages= and the number of invalidated pages is logged after searchword= In this example look at the second line: [2019-11-04

Description The promotion conditions are always styled like they are in edit mode even if they aren't. Seems that the issue was introduced with rework of template during Cashback implementation. Steps to Repeat The promotion conditions are always styled like they are in edit mode even if they aren't