Products
Packages [expand] [collapse]
Services
Released in version
3.2.17
3.0.7
3.0.6
2.1.2
2.1.0
2.0.0
1.0.0

Release notes for Episerver updates

This overview lists the latest changes included in Episerver updates delivered as NuGet packages and services. You can filter the information for products and versions, bug fixes and features. As a developer working with Episerver solutions, use the information to decide which updates to apply to your project. See Installing Episerver updates for information on how to install.

Note: New NuGet packages listed here may not be immediately available in the Episerver NuGet feed.

Changes in EPiServer.Personalization.Commerce

Item type
From date
To date
Items/Page
Id Type Title Released
COM-11549
  [Perform] Introduce new setting for forcing variants to be exported as individual items

Several customers have reported that they want to be able to ignore the products in their catalog and export all variants as separate items instead.

To do this, use the abstractions and structure map interceptor pattern. Partners need to write their own implementation of an interface method whose default implementation is ~500 lines of code with private sub-methods. The source code is provided to the partners for this purpose.

Version/s: EPiServer.Personalization.Commerce 3.2.17;
Jul 02, 2020
COM-9177
  [Personalization] Serialization of CommerceTrackingData gives unexpected results when using scoped configuration

https://github.com/JamesNK/Newtonsoft.Json/issues/830

We use a custom contract resolver inheriting CamelCasePropertyNamesContractResolver to serialize tracking data to JSON. Even though we use different instances of our contract resolver the CamelCasePropertyNamesContractResolver uses an internal static cache of resolved JsonContracts and shares them between resolver instances.

When a contract for a tracking type is resolved the Site and ClientToken values for the current scope are used in the JSON data and, because of the cache, in all future tracking data of that type. If the site consists of more than one web app the web apps may have cached values from different scopes leading to a, from the outside, seemingly random behavior in regards to what values are included in the JSON.

The Newtonsoft team have chosen not to “fix” it (it’s not really a bug, it’s inconsistent behavior) in later versions because that would be a major breaking change. Therefore, upgrading the Newtonsoft.Json version is not a viable workaround.

Version/s: EPiServer.Personalization.Commerce 3.0.6;
Mar 19, 2019
COM-9021
  Personalization: Add better logging in the export feed process.

There should be info-level logging for successful exports and warning/error-level logging for failed exports.

The scheduled job log should mention how many blobs are in the DB. Something like:
"Created X catalog feeds. There are now Y feeds awaiting export.

If there are more feeds awaiting export than were created by the latest job execution it indicates that earlier exports have not been successful.

Version/s: EPiServer.Personalization.Commerce 3.0.7;
Mar 19, 2019
COM-8156
  Catalog feed does not include products in secondary catalog

Steps to reproduce
Precondition: There is a multi-site commerce solution where products are kept in a master catalog (primarey category relation for each product links to the master catalog) and then linked to categories site-specific catalogs.

1. Configure personalization for each of the sites, including configuration of the catalog to export for each site.
2. Run the catalog feed export.

Expected: The products linked to each site specific catalog are included in the export.
Actual: The products are not included in the catalog they are linked to.

Version/s: EPiServer.Personalization.Commerce 2.1.2;
Nov 01, 2018
COM-8161
  Catalog feed category outlines can be incorrect in multi-catalog scenario

Steps to reproduce
Precondition: There is a multi-site commerce solution where products are kept in a master catalog (primary category relation for each product links to the master catalog) and then linked to categories site-specific catalogs.

1. Configure personalization for each of the sites, including configuration of the catalog to export for each site.
2. Run the catalog feed export.

Expected: The category outline for each product refers only to categories in the exported catalog. If the product is linked to multiple categories in the same catalog, all these outlines are included.
Actual: All outlines in all catalogs are included.

Version/s: EPiServer.Personalization.Commerce 2.1.2;
Nov 01, 2018
COM-7319
  Rework client side tracking API

The client-side JS tracking API has been rewritten to use an asynchronous web api controller as a proxy that handles tracking requests from JS API in the client, and forwards the requests to the Recommendation Service. The tracking response returns from the Recommendation Server and renders to the client through the proxy.

Version/s: EPiServer.Personalization.Commerce 2.1.0;
Oct 07, 2018
COM-7429
  Catalog feed categories should not include catalog name

Since only one catalog can be exported in each catalog feed, and with the new multi-site support there is no indication there will ever be multiple catalogs in one feed, the catalog name in the category hierarchy in the feed only adds noise.

Remove the catalog level from the hierarchy.

NOTE: This must be matched by adjusting the category tracking in the same way.

Version/s: EPiServer.Personalization.Commerce 2.0.0;
Jul 22, 2018
COM-7123
  Support multiple accounts for Perform native integration packages

The previous native integration only supported one account per installation. This feature now enables one web application to host multiple sites and allows tracking for each of them individually using configuration settings.
For further documentation, see https://world.episerver.com/documentation/developer-guides/commerce/personalization/recommendations/multiple-scopes/, https://world.episerver.com/blogs/Magnus-Rahl/Dates/2018/7/personalization-2-0-commerce-native-integration-multi-site-support/ and https://world.episerver.com/documentation/upgrading/episerver_personalization/episerver-personalization-commerce-2-0/.

Version/s: EPiServer.Personalization.Commerce 2.0.0;
Jul 22, 2018
COM-5626
  [Recommendations] Product description is not generated in Catalog Feed

Steps to reproduce

  1. Create a catalog in the English and Svenska (Swedish) languages.
  2. Create a product with an active variant.
  3. Update the product description in both languages.
  4. Export the catalog feed.

Expected:
The product description in Svenska can be exported to catalog feed via <p:description location="sv"/> property.

Actual:
Product description in Svenska cannot be exported.

Version/s: EPiServer.Personalization.Commerce 1.0.0;
Oct 31, 2017
COM-4988
  [Recommendations] Refactor packages to use Episerver.Tracking.Core

This story rewrites the Episerver Personalization integration to use the common API from EPiServer.Tracking.Core, streamlining and integrating the tracking process with other Episerver products like Profile Store and Advance. This also makes it possible to use the same APIs in Commerce for tracking to one or more services with or without Perform product recommendations.

Version/s: EPiServer.Personalization.Commerce 1.0.0;
Oct 31, 2017