Episerver Release Notes — June. By The C2 Group
By: The Group
Tags: Cms Development, CMS, Web Development, Episerver, Release Notes

By The C2 Group | Originally posted at c2experience.com

Episerver’s continuous release cycle provides new features and bug fixes on a bi-weekly cadence. Each month, C2 will aggregate and highlight some of the bigger updates to Epi software. To learn more, or if you have specific questions, you can contact The C2 Group, an Episerver Gold Partner, here.

Omit unpublished and expired content

Fixed in: EPiServer.ContentDeliveryApi 2.6.0 [ID: HAPI-316]

Previously when calling for content from the Content Delivery API, CMS users would have to manually skip over or omit any content expired or unpublished. This update ensure that any unpublished or expired content is excluded, saving teams time from having to manually do it and saving bandwidth by omitting extra data.

Forms available for SPAs

Release: EPiServer.ContentDeliveryApi 2.6.0 [ID: HAPI-11]

With this release, there is now the added ability to use forms in single page apps (SPA). To learn more about SPA forms capabilities,including limitations, see Episerver’s release note details here.

Added Dependencies Tab Options: Rich Text, Submit Button Elements

Fixed in: EPiServer.Forms 4.25.0 [ID: AFORM-2236]

The form elements Rich Text and Submit button can now be dependent on other fields in the same manner as Image choice, Number, Range, Multiple or single choice, etc. For example, let’s say you have a customer satisfaction survey where the respondent rates you 1–5. The next question surfaced will depend on their response rating. To learn more about implementing the Dependencies tab (example shown below), see Episerver’s documentation here.

Episerver Form Dependencies tab (Source: Episerver)

Upcoming CMS UI Refresh

Originally released in: EPiServer.CMS.UI 11.21.0 [ID: CMS-13766]

Epi’s CMS will be receiving a face lift to the UI,including a new navigation and modern styling. This was released in CMS UI 11.21.0 but has since been removed from Episerver’s nuget feed due to unintended semantic breaking changes. To those early adopters who installed 11.21.0 while it was available, Episerver recommends downgrading to 11.20.x for the time being.

The navigation menu at the top of the editor is the only thing that is functionally different; the rest is just eye candy. Really really sweet eye candy. The menu is intended to be an opt-in change, and there will be some code changes required for add-ins to utilize this new menu. This will be the thing to watch. We are eagerly anticipating the next release of this CMS UI refresh.

Episerver CMS UI 11.21.0 preview (Source: Episerver)

‍

Delete profile and related events

Fixed in: EPiServer.Profiles.Client 1.9.0 [ID: PROF-1308]

The Episerver Profile Store is used to store site visitors’ profile and track behavioral data. In return, this data can then be analyzed with Profile Store and used for personalization and omnichannel marketing. This update will allow for CDP admin users to better manage information with, more specifically, deleting profiles and behavior-related events. As GDPR approaches its first full year in regulation, this feature will be useful in the case a user requests their personal information be deleted from a company’s database.