The Order IOM Extension REST API works only with the IOM Connector enabled. This API specification is available for download as an Open API 3.0 YAML file: icm-order-iom-extension-1x0x1.yaml References The following page lists available REST APIs for ICM 11 and their version dependencies: Reference -

Description In case of a successfully exported order, status matches IOM (mostly). If the exact same order is then exported again from ICM (user error, other reasons) the result is that the order is flagged as export failed and the correct status can no longer be seen in ICM. Steps to Repeat Copied from

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

Description The order history (my account) gets very slow when there are more and more orders. In our case 17 orders led to a 6s load time. ICM 7.10.30.2 / IOMConnector 6.5.1/2 We use the RSS Repro Steps Have an account with roughly 20 orders and navigate to the order history. Observe long loading times

Description Description: lower case in Order List should be adjusted. inSPIRED > Orders > Order List Steps to Repeat In the backoffice: Open inSPIRED > Orders > Order List Actual Behavior Description: lower case in Order List should be adjusted. Expected Behavior All items need to be in Sentence Case

Description The OrderPositionState information from the IOM is assigned to the corresponding ICM OrderProductLineItem via the article identifier ( IOM#articleID <–> ICM#productSKU ). This mapping is no longer unique, as the IOM Order REST API now also supports multiple shipping-buckets and a product

Description ICM 7.10.30.2 IOM 3.4.3.0 IOMCONN 6.5 During our testing of the IOMConnector migration, we've observed that the are sometimes unexpected product names visible in IOM after export. The reason is the product mapper, that does not use the orders locale: product.setName(productBO.getDisplayName()

Description Description: The system tried to export an order, terminating with the following exception: "Value too long for Field "Name" in com.theberlinbakery.types.v1_0.Article" Is the ICM and also the IOM supports at this place the same attribute length (1000 chars) this mapping-error should not be

Description Actual behavior ICM defines an enumeration TaxClass in ac_iomconnector_common that is hardcoded to three tax classes: NoTax, ReducedTax, FullTax if you are not using the exact same tax types in your product data, you have to implement and override TaxClassResolver via the Component Framework

Description Bug description During the yesterdays demo an order export to IOM failed. The product in the order included surcharge product. For product without surcharge was the order export to IOM successful. Where (Environment & Channel) ICM: https://iom29demo.intershop.de:8443/INTERSHOP/web/WFS/SLDSystem/