Episerver features - May 2019

Administrators can require editors to add a comment when sending content for review.

To avoid confusion, all scheduler dates are displayed as UTC in admin view, since the Scheduler uses this internally. Labels are added to clarify this.

In Project Overview, the Show comments icon is changed to the same one used for the Comments pane shown outside of projects.

Notifications are now automatically marked as read when the notification window is closed. This removes the Mark all as read button and the Mark as read context menu on the notifications. See Ryan Bare's blog post.

Improves performance and reduces the number of calls that some Commerce systems make to third-party tax calculators.

See Sending tracking cart with changes information.

• Introduced a new API that converts the currency of a Money type and returns full precision value:

  Mediachase.Commerce.Shared.CurrencyFormatter.ConvertCurrencyWithFullPrecision(money, currency)
  

• Removed intermediate rounding from the default implementation of calculators. So, it rounds only at the highest level (order group calculator). CalculateXXX() methods in the default implementation of calculators, which are protected, now return full precision values.

• Stored full precision values for discount amounts on line items and shipments. This behavior is a breaking change.

• Added a new global configuration on the promotion engine: a Boolean setting, named ApplyPromotionUnitIndividually. You can change this setting in the appSettings. 

  • If set to true, the promotion engine takes the percentage discount for an individual unit and, from then on, works like an “amount off” discount.

  • If set to false, the setting works as it does currently in Commerce 12. That is, the promotion engine does not take the percentage discount for an individual unit, but for a whole line item (so it takes the quantity of line item into account).

Since they were converted from enums to classes, they can now be extended.

• API to get the parent IOrderGroup of an IOrderForm

This story provides support for StringDictionary in strongly typed catalog content types at API level. For more information, see Quan Mai's blog post.

The CSR user interface has been rebranded with new colors and components.

When working on the CSR UI screen, you can now select a shipping method.

The CSR UI is improved with a more responsive layout that makes it display better and provides support for mobile device use.

On the Order Management screen, you can select an customer's existing shipping address or create a new one.

On the Edit Discount screen, you can exclude certain catalogs, categories, and catalog items from a specific promotion. You can also do this programmatically; see Excluding catalog items from a promotion.

The Strategy Container block retrieves content recommendation data from the Advance API and displays content suggestions based on a strategy, such as popular content or what other users read.

A service that enables customers to export all third-party ID entries of a client into a CSV file has been added.

You can use REST API OptInProcesses for accessing opt-in processes in Episerver Campaign (retrieval, creation and modification). For more information, see Configuring MS Dynamics CRM integration (under "Connect the advertising consent to an opt-in process") in the Episerver Campaign User Guide.

You can stop a running target group analysis in Smart Campaigns by clicking the new cancel button.

• Split the D365 into Online and On Premise Versions, due to differences in the form structure.
• Switch base language to English, so other CRM language settings get EN as plug-in replacement.
• Expanded DOI configuration: Configure XML-value to use CRM user data for DOI mailings.
• Trigger transaction emails from entities other than contact, lead, and account by using lookup workflows.
  For more information, see Send transactional emails in the Episerver Campaign User Guide.

Previously, MS Dynamics could not address more than 100,000 recipients in one campaign. An external Windows service removes this restriction and manages campaigns and the transmission of marketing lists with more than 100,000 recipients. The customer must install this service.

Previously, the connector supported only standard fields of entities. This story adds support for custom fields.

API methods has been added in the service and connector to determine the membership of a lead in a list.

Re-introduce code that allowed customers to customize email templates into Silverpop 5.x connector.

Currently, multiple form submissions in the same session update the prospect created on the first submission. This story lets you change this behavior to create a new prospect on every submission, similar to the way that the Salesforce and Marketo connectors work. Use the drop-down box (see below) on the admin settings screen to choose the desired behavior.

A check box has been added to the admin settings screen to allow for asynchronous submission of form data to Salesforce.
If this option is enabled, data submission is a "fire and forget" operation. That is, the entityId is not received and stored in the MAI cookie. Therefore, auto-fill and personalization based on Salesforce fields does not work.

• InRiver Product Marketing Cloud (PMC) support

• D365 v 10 (Retail server 9.10) support

• Three new configuration properties to the <retailServer/> configuration element in storefront.config

• Updated Episerver Commerce version: supports 12.3.0 to less than 14.0.0

• Updated minimum supported version of Newtonsoft.Json to 11.0.1

• More logging

• Added IRecordDto as a base interface on all DTOs

• Support for sort order on IMediaDto

• More options on how to host Avensia.Storefront.Staging database on DXC.

  For more information and upgrade instructions, see release notes on the Avensia website.