Table of Contents Introduction References Migration Introduction Note This migration guide applies for 7.10.26.4, 7.10.27.1 and 7.10.28.0. 7.10.27.0 is not included, refer to Cookbook - Single Sign-On (SSO) | Recipe: Configure Redirect URI | Solution 2 for the original redirect URI pattern. When using

Description Description: Customer gets a NPE in com.intershop.adapter.productprice.service.internal.provider.ProductPriceServiceProductPriceProviderImpl.getPrices because the user object is null. Caused by: java.lang.NullPointerException: null at com.intershop.adapter.productprice.service.internal.provider

Description Steps to repeat: Clear the application cache via the cache REST API Make a call to the ShopPersistenceService.getShopDOList() All shops will be put into the cache without lazy fetching In a different transaction (e.g. new API call or new schedule run), get the list again via the mentioned

Description Current Behavior REST API returns (under very rare and specific conditions) values like "java.util.ArrayList$Itr@92ab940" Expected Behavior A REST API should not return such terms. Steps to Repeat create product A no specific attributes create product B with one custom attribute of type "multiple

Description Current Behaviour: The promotion.id has no maximum length documented, but the database has a length restriction. When using an id with length 500 i.g., the request will fail. Expected Behaviour: Documented constraints. Note: As all customers currently respecting this constraint and a breaking

Description Installed Solr Cloud Adapter 2.3.1 and Solr 8.6.3 or Solr 8.7 An initial search index build fails with: org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error from server at http://localhost:8983/solr: Can't create a configset with an unauthenticated request from a trusted

This API specification is available for download as an Open API 3.0 YAML file: icm-b2b-product-1x2x0.yaml References The following page lists available REST APIs for ICM 7.10 and their version dependencies: Reference - Intershop Commerce Management 7.10 REST API API Specification openapi: 3.0.1 info:

Table of Contents Time Zone of Docker Images Helm Charts Time Zone of Docker Images This step is required when migrating a system from IOM 2.x to 3.2 Make sure that both database and IOM-images are set to the same time zone. IOM-images now always use the time zone "Etc/UTC". Before starting the migration

Table of Contents Introduction Feature List Order Management Central Order Repository for Orders from Different Channels and Touch Points Including (Data-Centric) Business Processes Individually Configurable per Sales Channel and Supplier (Process-Centric) User Interface to Manage Orders Including (OMT-Centric)

Table of Contents Introduction Glossary General Information Additional References New Features and Enhancements Enhancements in Setup and Operations On/Off for Access Log Update of Java to Version 11.0.9.1 Customization Allow Usage of a Docker-Proxy, When Building Project Images Timeout for Test-data