Episerver CMS

This story enables you to:

• know where blocks added to the TinyMCE editor are located
• easily navigate to them by clicking a Go to Block button

See Grzegorz Wiecheć' blog post and TinyMCE plug-ins for more information.

You can now drag and drop an image (bmp, jpg, gif, and png) directly from your computer into the TinyMCE editor. The image is automatically stored in the local For This Page or For This Block folder. See Nicklas Israelsson's blog post, Customizing the TinyMce (v2) in the Episerver CMS Developer Guide, and also Adding and editing images in the Episerver User Guide.

Select an image in the TinyMCE editor to display a Go to media button. Click the button to open the image or hover over it to see where the image is stored. See Customizing the TinyMCE editor (v2) in the Episerver CMS Developer Guide, and also Adding and editing images in the Episerver User Guide.

The release of the TinyMce package version 2.0.0 includes an updated TinyMCE editor. From this release, it is no longer possible to configure the TinyMCE editor from the admin view; all changes are done through code. See Ben McKernan's blog post< and Configuring the TinyMCE editor (v. 2.x).

When using rich text (with placeholders) elements, the placeholders are often replaced with real form data in confirmation steps. In some cases, this can cause performance issues. Select the new option Disable placeholders replacement in the Settings tab of rich-text form elements to not replace placeholders with entered data in a following step. Instead, the default placeholder text will be displayed.

The Rich Text and Submit button elements can now be dependent on other fields in the same manner as Image choice, Number, Range, etc. See The Dependencies tab documentation in the Episerver User Guide.

You can now configure validation error messages on form elements, see Form element types in the Episerver User Guide.

This story makes forms more user-friendly and accessible, specifically level AA of WCAG compliance.

You can now control how long form submissions are stored in Episerver by setting up retention policies. The retention policy is set on the form so you can have different retention policies for different forms. You can also have different settings for finalized form submissions and for partially submitted form data. For more information, see Customizing retention policies in the Episerver Forms Developer Guide and Managing form submissions in the Episerver User Guide.

You can now choose one of the registered systems as connected data source in the user interface. See Multiple external systems in the Episerver Forms Developer Guide.

You can now hide or show a field based on input to another form field. You create rules for field elements on a new Dependencies  tab in the element properties.

You can use this feature to create a customer satisfaction survey that displays additional questions depending on how a visitor answers. So, if a visitor answers "Food" to the question "What's your favorite thing about the Coffee House?", an additional question is displayed, "Which food do you like in particular?". That question is not displayed if the visitor picks any of the other options for the first question. To set up a survey like this, see Creating a customer satisfaction survey in the Episerver User Guide.

You can now search inside a select column in the form submissions.

When a form is deleted (and removed from Trash as well), a scheduled job deletes all form submissions related to the form. 

A scheduled job checks for partially filled-in form data and deletes it after a specified number of days after the visitor submitted the data. The default time is 30 days.

When you deleted submitted form data, any related uploaded files are also deleted.

Previously, if the submission of form data to a marketing automation connector to create/update an entity was unsuccessful, an error was logged but a success message was still displayed in the UI. Also, the form submission was recorded in the Episerver database. Now there is an option in the admin settings to choose a different behavior, such that the error is displayed in the UI, and the form submission is not recorded in the database.

A checkbox 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 not stored in the mai cookie. Therefore, auto-fill and personalization based on Salesforce fields will not work.

When a visitor submits a Salesforce/Pardot/Marketo/MS Dynamics form multiple times, you can now either update the visitor's existing information, or you can create a new entity (lead, contact, and so on).

It is now possible to create additional connector instances with different credentials and names.

First public release of Episerver Insight - an add-on for organizing and storing data based on visitor behavior and preferences, to provide segmented input for omnichannel marketing campaigns.

See the Episerver Insight and Episerver Profile Store developer guides, and Episerver Insight in the Episerver User Guide.

It is now possible to create segments based on filter definitions and historical data in the Episerver Insight user interface.

The Change approvals add-on now supports CMS 11. See Change approvals in the Episerver User Guide and Impact of Change Approvals on other addons and its limitations for details.

By selecting the Prevent users from approving their own changes check box, the person who made a change is not allowed to approve, even if that person is assigned as an approver.

This new feature lets editors and marketers configure strategies for Advance content recommendations directly from the Episerver CMS edit view.

Episerver Content Delivery API is a new headless API for collecting and updating content. With this REST-based API you can create your own integrations, and pull content from the CMS content repository, bypassing the presentation layer, and publish it to any application. See the Episerver Content Delivery API developer guide.

Episerver Content Delivery API can now retrieve Commerce catalog content in JSON format. See the developer guide topic Content Delivery API and Commerce for more information.