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.
Revamped order statistics boosts performance in Marketing UI
Fixed in: EPiServer.Commerce 13.16.0 [ID: COM-10446]
While there are no visible changes with this update, Episerver has optimized how data is retrieved when order statistics are displayed in the ‘Campaign’ and ‘Discounts’ sections of Episerver Commerce.
To compensate for improved performance, this optimization update ignores inactive and expired campaigns and promotions. Marketers can still look at historical data by using the “commerce.ReportForInactivePromotionItems” app setting to add to a report.
This update does require Episerver Commerce 13.16 or higher and that the scheduled job “Collect Order Per Statistics” is running on a regular basis.
Order Details screen gets Episerver Design System and new functionality
Fixed in: EPiServer.Commerce 13.16.0 [ID: COM-10279]
The Order Management screen within the Customer Service Representative [beta] UI received a makeover from the recently rolled out Episerver Design System. Based on Google’s Material Design System, these changes are both structural and visual with intentions of optimizing the customer service representative experience.
The Order detail page now uses a tab-based structure broken out into Summary Detail, Payments, and introduces Returns & Exchanges. Other updates include sorting by shipment number for shipping and item data, and the ability to edit both shipments and line items in a new modal experience.
Visitor Intelligence (formerly Insight) gets Epi Navigation UI rollout
Fixed in: EPiServer.Profiles.Client 1.14.0 [ID: PROF-5397]
Visitor Intelligence (Insights) is the latest product in Epi’s portfolio to receive the recently rolled out visuals and navigation updates to its UI. Visitor intelligence is an add on for Episerver that allows for filtering visitor profiles and creating customer segments that can be used in marketing campaigns, to target users based off their online behavior on your site.
[Beta] Support for running editing site without CLR content models
Fixed in: EPiServer.CMS.Core 11.15.0 [ID: CMS-15547]
Episerver is beta testing the ability to have a site that is not built with the use of content models defined in the code. So, what exactly does that mean?
Currently, when Episerver delivers a web page to a site visitor, the content for the page is retrieved from the database. Then, content models format the content and present it for display on the web page.
In this release, Episerver is testing its ability to deliver data straight to a web page without doing any type of formatting of the data. While this is primarily an architecture change, this will allow for sites to load faster and enable marketers with the freedom to use content stored in Episerver in new ways online and more efficiently.
This isn’t available to all Episerver users, but if you’re interested in learning how to take advantage of this and other beta features, contact The C2 Group here.
Beta goes live: Content Saved event, DOM updated event, and Epi Ready event
This month Episerver has released three key events from beta testing. These events are now available for anyone to use.
Content Saved event
Fixed in: EPiServer.CMS.UI 11.24.0 [ID: CMS-15463]
This event is utilized by customers that want to handle the page edit view on the client side rather than server side. It is a simple way to check, using Java script, if an item was being edited.
DOM Updated event
Fixed in: EPiServer.CMS.UI 11.24.0 [ID: CMS-15464]
This event allows for better support for editing overlays when using the on-page editing features within the Experience Editor. Originally this event was triggered manually. After its update and beta release, the event was updated to trigger automatically.
Epi Ready event
Fixed in: EPiServer.CMS.Core 11.24.0 [ID: CMS-15465]
This event supports knowing when the current content is editable. It allows customers to handle the page edit view on the client side rather than server side.
Along with this, the epiReady event introduced a beta object which was added to window.epi.
This object contains three properties:
- isEditable, true in edit mode and false in preview mode.
- inEditMode, true in both edit mode and preview mode if content is being edited.
- Ready, true if the property isEditable and has been initialized.