Table of Contents Introduction View and Edit Interactive Prototype Responsive Design Page Notes Widget Style Manager Feedback Wireframes Introduction The wireframes described here contain interaction designs for storefront pages. Elements and functionality of the Intershop Progressive Web App are displayed

Actual Behavior In a live ICM installation and a Solr Cluster with multiple Zookeeper/Solr Nodes and Replicas for each index the search sometimes returns correct results after a successful replication of the indexes, and sometimes no results for the same search request. Expected Behavior The search returns

Description Actual behavior: The Error log is too often used for printing out error responses from PAYONE. For instance when a payment connector reports back that the authorization was declined a notice is written into the Error log. But that's a normal business case. Expected behavior: Only error scenarios

Description Actual behavior: The Error log is too often used for printing out error responses from Cybersource. For instance in CyberSourceCreditCardAuthorize when Cybersource reports back that the authorization of a credit card was declined a notice is written into the Error log. But that's a normal

Description In the storefront context if you submit a quote request you get 2 entries for table ProductListEvent. If you set a new price and submit the quote in the back office then no ProductListEvent will be written. Expected is there also a new entry for the new price. Steps to Repeat - Create a quote

Description In the Order Export Service configuration the path for exported orders files must be set. But, it is necessary to use the absolute path, something like /var/intershop/share/... But, the absolute path is not necessarily known to the business user, especially when running ICM in a CaaS system

Description The customer maintains additional ad-hoc Customer Segments in the Live system of a Staging environment. A replication of Customer Segments removes these Customer Segments from the Live system - what is the expected behavior in this case. However, the following attempt to create such a Customer

Description The price lists import in UPDATE mode creates a new price entry if the price unit for the product is changed. Repro Steps - Create a price list - Add a price entry (quantity=10, value=100) for a product - Export a price list (see 1TestPriceList.xml) - Change the unit of the fixed price entry

Repro Steps 1. Create a new SOLR index on EDIT OR - DELETE an existent index on LIVE system 2. Replicate at least the search indexes The first replication leads to displaying the replicated index in the LIVE back office with N/A products, in the SOLRCloud console the (new) collection is NOT listed. System

Description When you try to GET or DELETE a non-existing lineitem this shows up in the error log, causing cluttering of this log file. [2021-09-24 12:10:57.805 +0200] ERROR localhost ES1 appserver0 [####-Site] [-] com.intershop.component.basket.orm.internal.BasketBOImpl [] [Unknown] [Q10KAAIPLbUAAAF8HWJRsxdJ]

Repro Steps 1) can be reproduced by adding a custom job with a long runtime (Thread.sleep) 2) can be reproduced by stopping the database or terminating the connections Actual Behavior 1) When a scheduled job runs longer than the time configured at "expectedRuntime", JobHandlerBean will log warnings and

Description When trying to import "fixed" product data after importing "wrong" product data, these updates may lead to completely inconsistent product data when said products are delivered by multiple suppliers. Repro Steps Products: First batch PROPER_PRODUCT_SUPPLIER_A: manufacturerArticleNo = 'MAN_A'

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

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