Description The method ShopDO.getEventRegistryEntryList() will modify the shops field eventRegistryEntryList in a non-thread-safe way. This leads to ConcurrentModificationExceptions. Repro Steps You will need a shop structure that has child and parent shop(s). Setup an event configuration such as email

Description There is a problem while trying to fetch property group information from the new(est) payment framework API. This is caused by the fact that the associated PaymentServiceBO extension doesn't handle dependency injectio. null Bug null Verified Closed fenego Major AdoWorkItem 78493 Products

Description Customer has trouble with this default punchout configuration. Open the punchoutconfiguration.properties and check the following line. # oci | field NEW_ITEM-LEADTIME configuration oci.ver5.punchout.configuration.NEW_ITEM-LEADTIME.fieldname=NEW_ITEM-LEADTIME oci.ver5.punchout.configuration

Description Copied from Repro Steps when changed from Escalation to Bug When trying to map an order to latest version com.theberlinbakery.types.v1_2.StoreOrder during order transmission, I get a parse exception, because the offered JNDI-path points to a bean that returns version 1.0. As the bean that

Table of Contents Intershop PWA 2.4 - Feature List (EN) Experience Management Intershop Progressive Web Application Functional Scope Intershop PWA 2.4 - Feature List (EN) Release 2.4 of the Intershop Progressive Web App comes with basic B2C and B2B e-commerce features and – more importantly – it is

Table of Contents Operating System Web Server Node.JS Node Package Manager Git Intershop Commerce Management Browser Docker Operating System Operating System (not included in the product) Any operating system running Node.js Web Server Web Server (not included in the product) Any web server running

Table of Contents Introduction What's New? Features References Fixed Defects Performance Improvements Documentation Code Refactoring Chores Breaking Changes Introduction Welcome to Intershop Progressive Web App 2.4. This public release note contains information about the latest features of the Intershop

Description Partner found a REST call include for the order call using the PWA: payments_paymentMethod. It seems like this include isn't documented as in the swagger documentation and also not part off the "all" include Repro Steps order call with payments_paymentMethod compare to order call with all

Actual Behavior When rejecting/declining a return request, and no comment is given I get HTTP-400, but the spec does not document this constraint. The response message does not match correctly, because I wanted to reject it, but the message tells me that this is already done."A comment is required f

Actual Behavior When sending a second (or more) approvals/rejections, the API does not respond, that the approval is still closed. The first (successful) approval never changes. The API always responds with HTTP-201, which is ok, but the status of the return request can't be changed after the first approval