Last updated: Mar 21 2017

Episerver - update 155

New releases of Episerver Commerce, Episerver Forms and A/B Testing. Bug fixes for Marketing Automation Integration connectors.

The update applies to Episerver projects version 7.5 and higher, and contains finalized work items included in the latest iteration. Continuous release updates are cumulative to include previous updates. Episerver supports all platform updates and strongly recommends that you keep ongoing projects up-to-date. You can install the updates from the Episerver NuGet feed.

Main packages
This release information lists updated main package versions for the Episerver platform. When a release is built, other dependent packages also may be bumped to new versions, although they contain no publicly visible changes. This is done to avoid dependency errors. When you upgrade, NuGet alerts you to upgrade related packages to the required versions. For Commerce, it is important to ensure that you are running the same version of CMS and Commerce, both in the front-end and back-end applications.

Updated main packages

Click a package in the list to see work item details.

Episerver CMS UI

New features:

    • MAR-424 As a developer, I want a KPI type that can be used to evaluate client side conversions.
      Introduces a framework for creating, injecting, executing, and converting javascript based KPIs to use in A/B tests and beyond.
    • MAR-457 As a CMS user, I want a KPI type that lets me convert if a user remains on a target page for a specified amount of time.
      A client side KPI that turns an A/B test view into a conversion if a site visitor included in an AB test remains on an A/B tested page for a user-specified amount of time.

Episerver Commerce

New feature:

    • COM-3932 [Recommendations] Create sample code to update widget configuration
      New API for enabling default recommendations settings. This API is used in the Quicksilver reference site.

Episerver Forms

New feature:

    • AFORM-895 Ability to fallback to a non-Js version per visitor (Beta)

      New WorkingModeService  service class determines whether the Forms add-on is working in non-js mode. Default implementation returns a setting from Forms.config. You can override the IsWorkingInNonJSMode method to decide when the Forms should work in non-js mode for each and every request.

Episerver add-ons

Important notifications

Related topics