Actual Behavior When getting a return request, there a ~5 additional endpoints to get further data. I do miss the endpoint to get approvals because this is what I may do next, after creating an approval. HTTP-201 and the location of the new resource indicate that there are real resources. But when calling

Actual Behavior When sending, f.e., the body to create a return request to the endpoint for approval creation, the HTTP-400 response indicates, that I wanted to decline the approval. Additionally, it says, that a comment is required, but a comment is given. null Bug null New New null Major AdoWorkItem

Actual Behavior This example found in https://intranet.intershop.com/kb/index.php/Display/2F9406 contradicts itself. When accepting a request, you can't comment that it's not acceptable. {"status": "APPROVED", "comment": "The return request reasons are not convincing." } null Bug null New New null Minor

Description Calls of the ViewProduct_52-Edit Pipeline in the back-office will go into a loop that ends with a PipelineCallStackException: [2022-07-19 17:27:26.372 +0200] ERROR localhost ES1 appserver0 [TestEnterprise-Site] [TestSalesChannel] com.intershop.beehive.core.internal.request.RequestHandlerServlet

Description Product Attribute Groups export/import has problems with decimal definition and domain assignments The exported file is invalid and cannot be re-imported again. Repro Steps - setup ICM 7.10.38.9 with german lead locale inside \eserver\share\system\config\cluster\localization.properties american

Description Some customers migrate from ICM 7.10.32.13-LTS/7.10.32.6-LTS to 7.10.38.11. dbprepare throws the following errors related to the bts TablesPreparer/DatabaseTablesPreparer: [2022-07-07 15:15:51.769 +0200] ERROR NL-EVI-CCKHFB3 ES2 dbmigrate [] [[migrate]bts:Class0_BasketPO TablePreparer [com

Download - TechTalk 2 2022 ENFDEVDOC doc_access_contract doc_status_final doc_type_techtalk 4 144cd7d31f62b71c5ea06f600ab50bd1 ConfluenceCloud 48059678721 /spaces/ENFDEVDOC/pages/48059678721 1844226834

Description The case is as follows: There exists a base product at organization level with MinOrderQuantity, MaxOrderQuantity, StepQuantity and Unit. Now we import at channel level a product with only the online flag: <product sku="4934090" import-mode=”UPDATE”> <sku>4934090</sku> <online>1</online>

Description Getting HTTP 500 instead of 400, when trying to create return-request via REST, which is not of the type (RETURN | PICKUP). These 2 types can be checked with simple validators before querying any other data. Copied from Repro Steps when changed from Escalation to Bug Use the Postman collection

Actual Behavior The RMA REST API spec is mixing type RETURN + pickupAddress in the examples, which is not usefull when copying it to play around. A RETURN does not store pickupAddress. Expected Behavior Examples in the spec should fit together. null Bug null Verified Closed null Major AdoWorkItem 78213