Description Supplier may theoretically be allowed to see only part of the position, but currently they get a permission denied when they try to access/view positions from such orders. ticket 65515 has fix a 'permission leak'; before it user could have more permission then actually defined: The old trigger

This API specification is available for download as an Open API 3.0 YAML file: icm-b2b-promotion-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:

This API specification is available for download as an Open API 3.0 YAML file: icm-b2b-product-1x3x0.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:

Description Based on the original issue. We have found out that the prefix for the namespace http://www.intershop.com/xml/ns/intershop/order/2.0 is not constant: most of the times it's ns2 (e.g.: <ns2:orders xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ns2="http://www.intershop.com/xml/ns/intershop/order/2

Description After product imports there may be duplicate attributes when inadvertently leading or trailing spaces surround the entered attribute names. It is possible to enter attribute names in the back office as well, that have leading or trailing spaces in the name, both for XML based attributes (Product)

Actual Behavior The Contact Center REST API contains a REST endpoint to get details on an application. Included there's a Storefront URL which is used for the Co-Browsing feature. Currently the Storefront URL is based on the property "intershop.WebServerURL/intershop.WebServerSecureURL" globally maintained

Description when there is no default category in the product import file for a product, then the import will automatically set one (previously the validator did it but that was removed with #69937) Now the import sets a default category automatically: assigned classification categories are skipped and

Description When a job takes a lot of time, bakery.control.job.Timer is stuck in a blocking call awaiting the job to finish. Due to the singleton pattern / EJB scheduler the Timer is not fired anymore which basically prevents all other jobs from firing until the blocking call has finished. Repro Steps

Table of Contents Introduction References Version Information and Dependencies Supported Application Types Feature Overview Payment Management Options Webhooks General Information Webhook Validation Receiving a Webhook Experience Profiles Setup Precondition Setting Up the Assembly Option 1 Option 2

Table of Contents Introduction Version Information and Dependencies Preconditions Supported Application Types Feature Overview Payment Methods Payment Management Options Setup Precondition Setting Up the Assembly Defining File-Based Configuration Deploying the Assembly Configuration Adjusting Firewall