Last updated: Sep 10 2018

Episerver - update 231

New release of Episerver CMS Core, Episrever CMS UI, Episerver Campaign, Episerver Forms, the Marketing Automation connector for MS Dynamics, and the Avensia Storefront Connector. Bug fixes for Episerver Commerce and the Marketing Automation connector for Exact Target.

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 Core

New feature:

    • CMS-10481: API: Configurable if person who requested approval can approve the change
      API support for four-eyes principle in content approvals. See CMS-9772.

Episerver CMS UI

New feature:

Episerver Commerce

Episerver Campaign

  • Episerver Campaign 7.11

New feature:

    • BM-38241: Insight Segment Support for Smart Campaigns
      A segment from Episerver Insight can be added to the Smart Campaign graph, to add Insight-based filtering to a campaign. Campaign events (like mailing sent, opened, clicked) can be tracked into Profile Store.

Episerver Forms

New features:

    • AFORM-1775: Line added to clarify Form view modes distinction
      The forms view drop-down now has a line to separate edit view modes (On-Page Editing and All Properties) from other view modes. The line indicates differences between Form Submissions and other view modes. The line also increases consistency between the Forms user interface and the Commerce Catalog user interface.

    • AFORM-1778: Handle submission actor's result

      Previously, Episerver Forms did not handle submission actor’s result (actors returned results but they were not used).
      This feature allows actors to:

      • Return a signal to cancel form submission in case actor running fails
      • Return an error message which can be displayed to visitors


      For more information, see Implementing actors in the Episerver Forms Developer Guide.

Episerver add-ons

Third-party add-ons

  • Avensia Storefront Connector 5.1.0

Important notifications

Related topics