Description Description: Using the newly introduced search rule Concept - URL Rewriting (from 7.10.5) - 5.11 Search https://support.intershop.com/kb/index.php/Display/2Q8070 may break some links in the storefront (e.g. brand links on product detail pages). Steps to repeat: 1. Enable the mentioned rule

Description Actual behavior Calling rest api for CMS can lead to NPE if a pagelet in the composition tree is pretending to have a slot which in fact it hasn't. Expected behavior Calling rest api for CMS can cope with situations where a slot object is missing. Even though the pagelet definition is including

Description Current behavior In Master, create a new local catalog with name and ID Drilldown in the catalog, click "Edit Properties" edit any property, e.g. "Description" or try to assign products dynamically Click Apply after the changes switch to any other tab, e.g. "Content" and back >> The change

Description Description: If the product brand on the PDP or "Brands" page contains certain special characters (e.g. &,"), the link results in a 0 search result page. Steps to repeat: 1) create product with a manufacturer name that contains the special character "&" 2) rebuild the search index 3) open

Description Description: The AS preference PasswordUpdateSkipOldPasswordValidation has no related dbMigrate preparer call Steps to repeat: Customer did install 7.10.15.3 version and found no related dbmigrate preparer call/code for the new introduced preference "PasswordUpdateSkipOldPasswordValidation"

Description Description: Since version 7.10 the COMPUTEDITEMS field of the BASKET and the ISORDER table contain compressed data. So they are not directly readable anymore. Would it be possible just to log the ComputedItems field into the debug log one time after every calculation? Are there security/privacy

Description Description: The GetCustomersREST.query will fail on LISTAGG function because of a lot basicprpofile customer table domain records Steps to repeat: Customer scenario has a lot of basicpofile customer records for specifc domain. In case of a REST call which does execute GetCustomersREST.query

Description Description: Master Products with only a product link set on a channel, can not be removed by the bulk import. It only happens with the bulk import and under some conditions. -The product is shared to a channel. -in a channel only a productlink is created Then the product can not be removed

Description Description: When importing a customer XML in UPDATE mode while the XML "user" section in the file uses REPLACE mode, the CGs and IGs of the customer are "toggled". Steps to repeat: 1. In B2B channel backoffice export customer OilCorp (see attached _orig XML) 2. In BO create 2 new CG_ customer

Description REST calls b2c: post /customers put /customers/- b2b: post /customers/-/users put /customers/-/users/<userid> the attribute preferredLanguage should not be mandatory in this calls, instead the application default language should be set Repro Steps REST calls b2c: post /customers put /customers/-

Description Description: When a product is updated via BMECat import this update should be a REPLACE mode import for all attributes of the import language provided in the HEADER and for non-localised attributes of the product. Attributes of other languages however should not be affected. Situation: A

Description Description: in tracking.js a "encodeURI" should be added, else IE 11 produces „Invalid URL“for searches like „Fußball“ Repro Steps Description: in tracking.js a "encodeURI" should be added, else IE 11 produces „Invalid URL“for searches like „Fußball“ Fix_with_next_patch ilmSPIRIT Bug Commerce

Description Description: Disabling a campaign with an attached promotion and re-enabling promotion causes an invalid basket checkout message. Steps to repeat: 1. In B2B channel create a campaign with Everyone customer segment 2. In campaign, create an order percent off promotion, assigned to the campaign

Description Current Situation It is not possible any more to sort components in the design view (version 7.10.15.2): It was possible in 7.9: Desired Situation It should be possible to sort components in the design view. Steps to reproduce login to the BO go to the channel or the application open the

Description The dictionary inspector handles several collection types. Iterators will be iterated over so that in fact they are unusable afterwards. This is not problematic in cases were the iterator is created by a method like com.intershop.beehive.core.capi.domain.Domain.createUnitsIterator() but ccause

Description Description: When searching in backoffice advanced search within an attribute with a name containing an apostrophe sign then an error is thrown. Steps to repeat: 1. In backoffice (master or channel) edit any product, add a new custom attribute with name "Aantal accu's" and a value "body"

Description Object clicked = 0, although the test object was clicked several times in control group and test group. Test (See screenshots for result): Overview Statistics Control Group (50%) Test Group (50%) Test Object Viewed (max 1 per Session) 11 10 Test Object Clicked 6 5 Total Values Statistics

Description Problem: DBInit fails (deployed a f_business 'intershop7' assembly only) with an error: [2020-02-11 23:51:19.683 +0100] --------------------------------------------------------- [2020-02-11 23:51:19.683 +0100] -------------------- preparation summary ---------------- [2020-02-11 23:51:19

Description Actual behavior: [2020-02-11 12:13:07.837 +0100] Startup finished in 22s [2020-02-11 12:13:08.024 +0100] [2020-02-11 12:13:08.025 +0100] --------------------------------------------------------- [2020-02-11 12:13:08.025 +0100] -------------------- pre-processing --------------------- [2020-02-11

Description REST Call get customers/-/wishlists/<wishlistId> Expected behaviour wishlistId is part of the response Why is this important? The REST call get customers/-/wishlists returns a link list. If this link list is automatically resolved the id is only available in the link url and it is cumbersome