This page is no longer maintained. To see a list with all new user interface features, go to the release notes feed and use the filters to filter out UI features for a specific product and for a specific time period.
Are you on an earlier version Episerver CMS and don't know if you should upgrade or not? Have a look at the below content and see all the nice features you're missing if you don't.
(Hover over a feature to see in which version it was released.)
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.
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 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.
The XForms functionality has been moved to a separate NuGet package with its own versioning.
The Search functionality has been moved to a separate NuGet package with its own versioning.
The Dynamic content functionality has been moved to a separate NuGet package with its own versioning.
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.
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.
First release of Episerver Advance.
This new feature lets editors and marketers configure strategies for Advance content recommendations directly from the Episerver CMS edit view.
Support for Episerver CMS 11.
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.
This feature lets you drag different content type items into a property. Use this when you want to add pages and images to create a carousel switching between content items to display. This feature is also used in Commerce to add products, variants, packages and bundles when creating discounts. See Restricting content types in properties and Built-in property types for more information.
New project feature
The first release of the new project mode feature. Project mode is a feature where, when enabled, all changes done to content are automatically associated with a project.
The second release of the new project mode feature, the first was released in update 68. Project mode is a feature where, when enabled, all changes done to content are automatically associated with a project. This release includes a new project overview where it is possible to examine which content items that are part of a project and to control publishing of the items. The overview is accessible from the project bar.
Project preview (Beta)
A new Project Items navigation pane was added to give editors an overview of the content items in the project.
This list displays items included in the project and their status. You can select multiple items and set them to Ready to Publish with the check mark button. Each item has a context menu that is displayed when you hover over it. From the context menu, you can set the items as Ready to Publish, remove them from the project, or open an item for editing.
Select multiple items in the Project Items navigation pane and in the project overview, and set them to Ready to Publish or remove them from the project all at the same time. The multi-select feature has both mouse and keyboard support.
This feature lets the editor compare properties between different versions.
Select the Compare different versions button in the toolbar to turn the compare view on and off. A Select compare mode button is displayed which lets you switch between comparing content and properties. When comparing properties, the two compared versions are displayed side-by-side in the All Properties view. Tabs that contain changes between versions are highlighted with a digit, which identifies the number of changes. The latest version of the property is shown first, either to the left or above the older version. All properties that differ between the two versions are highlighted with a yellow background.