Description The CEC "Find Customer" button does not execute an action in case of mouse click. Steps to Repeat Open the Customer Engagement Center. Navigate to the customer search. Enter a search term. Click the "Find customer" button. Actual Behavior When clicking on the "Find customer" button to trigger

Description Project team tested some demo cases for xxx and stumbled over some unexpected behavior in Wrapper. When requesting Wrapper (all endpoints) then parameters with whitespace (also if it is URL encoded with %20) the parameter is not passed to Sparque as expected. Actual Behavior As an example

Description Affect the IOM REST API - Inventory Service 2.0 (https://knowledge.intershop.com/kb/2940Y3) When inventory data are requested for a list of products, the service return a 400 status without any inventory information when a single SKU from the list is invalid. Inventory of existing products

Description The ICM AS SMC job scheduler overview list throws sometimes exceptions about DetermineAllSchedules Steps to Repeat Within a project there was a need to execute long running SMC schedule job "CleanUpImpexJobs" to remove old jobs and related process entries ( about 13k ) By using the SMC list

Description Spelling mistake found in Customer REST API 1.6.0 (and earlier versions): "preffered" instead of "preferred c3po_documentation null Bug null Fixed and verified Closed null Major AdoWorkItem 104524 Products null Pull Request as/13.1.0

Description adds init/migration preparers that allow to: change the managed-schema with the Schema API (https://solr.apache.org/guide/solr/latest/indexing-guide/schema-api.html#modify-the-schema ) e.g. replace-field-type and rollout this change to all config sets of the cluster upload other configset

Description The Stripe Checkout API expects the value in the smallest currency unit to be an integer. Under the assumption that money values are always represented with decimal places from the used currency, the implementation converted the data by moving the decimal point and interpreting it as integer

Description OCI configuration punchout options rest request does return status code 204 Steps to Repeat - setup ICM 11.11.4-LTS within K8s cluster - execute a (PWA) REST options requests to determine OCI configuration from a channel, example URL https://{hostname}/INTERSHOP/rest/WFS/{Channel}-Site/-

Description Requests to the policy enforcer that contain an encoded % character and that should be directed directly to the sparque desk (prefix /sparque/) generate a 500 error from the policy enforcer. Such requests are nor redirected to sparque desk. example: https://policy-enforcer.search.sparque

Description When search index builds or other locking processes are in progress there is currently a message at the backoffice page: "Currently search index operations..." but the index configurations are editable. This can cause inconsistencies at the synchronization of index configuration with the