Episerver features - September 2020

To enable on-page edit (OPE) when a site is split up between a delivery application and a management application, the applications need to share the same parent domain.

Additionally, the document.domain needs to be set to the same domain on both the delivery site and the management site. This feature enables support to do that.

Provided a script to be used in the tag helper. It re-renders properties after they have been saved, so that on-page editing always shows the latest changes.

Blocks inside content areas can be rendered with guid-based identifiers instead of the traditional integer-based identifiers. This feature enables overlays for individual blocks rendered with guid-based identifiers when using on-page editing.

• Clickable project names in the notification bar.
• Information about what projects the content is part of.
  

This is a new Episerver Labs add-on, see Grzegorz Wiecheć blog post and Episerver Labs for more information.

On the Order Management screen, you can add a new shipping address to a customer's order without editing an existing address or adding a new address to the customer's address book.

In the Form Details tab, under Shipments, you can view the recipient name to have a better overview of shipping information.

Build-in payment methods that require credit card input are disabled. Credit card payments are done externally to the Order Management screen.

You can use a CSV file with the source code of the mailing that contains field functions. When the mailing is rendered, the nested field functions of the content CSV file are replaced by the specified content.
See Field functions in the Episerver User Guide.

For performance reasons, the limit of parallel REST API connections per client has been reduced to 25 as for the SOAP API.
See REST API in the Campaign Developer Guide.

You can upload and use images with a size of up to 50MP for campaigns.

You can assign roles to users only; not individual permissions. Only customer support can assign or revoke individual permissions. Assigning permissions via roles keeps the user management clear. You can create roles with exactly the permissions the user needs. It is easier and safer to revoke a role instead of revoking permissions one-by-one.
See Users in the Episerver User Guide.

In the recipient history, you can irrevocably delete recipient data. According to Article 17 of the General Data Protection Regulation (GDPR), the right to be forgotten, every person has the right to have personal data deleted.
See Recipient history in the Episerver User Guide.

When you create, edit, or start an opt-in process and the mailing dispatch is suspended in the client, you receive a notification that the opt-in process will not start. (Usually, opt-in processes automatically start after creation.)
See Opt-in processes in the Episerver User Guide.

There are several changes to the MsDynamicsClosedLoopWebserviceJobTemplate such as changing the recipient list ID field for closed loop lists from email to dynamics_id. Background: When configuring the MS Dynamics CRM integration, the closed loop interface is configured in the customer’s client using the MsDynamicsClosedLoopWebserviceJobTemplate.
See Microsoft Dynamics CRM integration In the Episerver user Guide.

The handling of automatic blacklist entries based on a feedback loop supports the new providers web.de, gmx.net and mail.com.

Opt-in emails (registration confirmations) contain an unsubscribe link that is also rendered in the email header as it already is for regular mailings and transactional mails.
See Opt-in processes in the Episerver User Guide.

When defining a target group and creating an action-based condition for soft or hard bounces, you can use the new Period filters Before and After an exact time stamp. This lets you filter bounces by excluding time periods as it is already possible for the actions clicked a link, opened mailing and received mailing.
See Defining a target group in the Episerver User Guide.

When creating a new target group, you can use an existing target group from any client that you can access as a template. This is easier than creating from scratch, for example, if you have a complex target group definition with a lot of rules and you only want to change one rule or condition.
See Target groups in the Episerver User Guide.

When creating a new client, personalized tracking is disabled by default due to data protection. Customers need to request customer support to enable personalized tracking during onboarding. When you create a new client based on an existing one, the client inherits the setting.

If you use unsubscribe lists based on recipient lists, you can choose whether to export global unsubscribers that are not assigned to any particular recipient list or unsubscribers that are assigned to one or more particular recipient lists.
See Exporting recipients in the Episerver User Guide.

For analyzing bounces, only unique bounces are counted. The bounce counter that is used, for example, in the campaign analysis in Smart Campaigns and in the recipient history shows unique bounces and the unique bounce rate.

If you previously exported recipients into a .csv file using the MultiRecipientCsvExporter scheduled job, but did not pull the file, the next export job overwrote the file. The new behavior appends additional parameters to the new file name instead of overwriting the previous file.
See Multiple recipients export job on Episerver World.

In Deep Analytics, you can display the ID instead of the name for the mailing, client and recipient list dimensions.
See Creating a report template in the Episerver User Guide

When using a Velocity field function for displaying a date, the date is returned as string value. To extract the date and use only some parts of it for further processing (for example, day or time), a date object is required. The new behavior creates date objects from string values.
See Field functions in the Episerver User Guide

When loading coupon codes, a pre-filter checks for valid tracking links. The new validation reduces the loading time and improves the performance.

A new validation for the scheduled jobs CsvImportFiles and MultiRecipientListCsvImporter checks if the used recipient list is part of the client hierarchy. This avoids importing recipients into wrong clients.

This allows for recommendations in a similar fashion to the current product email recommendations. See the Episerver User Guide.

Hand-pick rule in merchandising is extended and now it is possible to configure hand-picked recommendations from selected category.

Changes to allow for the extension of tracking to better enable B2B businesses to integrate with our recommendation platform. Enabling segmentation of products and clients.

Output cache features have been added for Content Delivery API:

• ETag and Cache-Control header added to the response of each endpoint.
• New option to configure output cache expiration time added.

• All internal content links are returned as absolute URLs using the canonical schema, host, and path configured for the site and branch of the linked content.
• Content located outside of any site uses the default CMS logic to determine the current site.
• Resolving the canonical URL is language-aware.

REST API previously exposed absolute URLs with the incorrect host. Media URLs now use the management host. Use fetchable URL for images in XHTML properties, link item, collections, URL properties.

Auto translate function updated to work with new Text Translator API from Microsoft.

Member fields shown by their display names in form mappings and visitor group user interfaces.