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.)
Part of another project notification When you have a project (for example 'Project 1') enabled and open a page that has another draft belonging to another project ('Project 2'), you will get a notification: Hopefully, this notification prevents you from creating multiple drafts in different projects by mistake.
Projects in the notification are clickable Projects in the notification are clickable: By clicking a project name, you switch project and the project overview opens. Thanks to this, you can quickly access projects related to the current content.
Version gadget displays project name When the content version belongs to a project, the name of the project is displayed in the Versions gadget: Especially when working with multiple projects, the Versions gadget is very useful to get a good overview of the different versions and which projects they belong to.
In Project Overview, the Show comments icon is changed to the same one used for the Comments pane shown outside of projects.
Notifications in the user interface are now automatically marked as read when the notification window is closed. This improves the notification feature as the notification counter in the bell icon is reset after you open and close the notification window and will only display new notifications after that. Previously, the counter was cleared when you closed the window but the number was displayed again when the page was reloaded, unless you manually marked them as read.
The following improvements have been added to the date/time picker:
The image property now comes with a thumbnail that makes it easier for you to see which image is actually used. You can also drag and drop images from the assets pane or from your computer straight into the image property.
To make content collaboration and communication easier, you can now add and view comments on content items, even if they are not associated with a project. The commenting functionality is accessed via a new commenting pane in the user interface. Toggle the pane with a toolbar button.
In the Select Image dialog box, you can now upload an image (by the context menu or by drag and drop) and then insert it on your page without having to leave the dialog. In this dialog box, you can also move images between folders, copy, and rename images, etc.
Episerver World will occasionally publish RSS notifications on new Episerver features or other useful information. You will get a notification in the user interface (in the bell icon) whenever a new post has been published. Clicking on the notification will take you to an article on World.
The "beta/domUpdated" message introduced in CMS UI 11.2.0 is no longer needed. The On-Page Editing (OPE) overlays are now updated automatically. See John-Philip Johansson's blog post and Editing user interface in the Episerver CMS Developer Guide.
A newProperty Value Listthat allows the editors to input multiple primitive values has been introduced. Available types are:
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.
Content approval email notifications were previously sent instantly. Now, they are grouped into summaries and sent at regular intervals instead. The intervals are controled by the Notification Dispatcher scheduled job. You can configure notifications to be sent instantly, see Configuring email notifications for content approvals.
This feature introduces an API which lets you disable personalized content for a specific user across all visitor groups. See Disabling visitor group personalization for more information.
BLOBs that are no longer used are now deleted.
Explicit log messages from CMS Core no longer contain Personally Identifiable Information (PII) like user name or IP addresses.
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.
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.
You can add a group to a content approval sequence. Groups have a special group icon in the list of suggestions and you can also see how many users are included in the user group. Hover over the group to see a list of included users.
A new appSetting, episerver:ui:ApprovalStepRoleUserLimit, has also been introduced in the web.config file, which triggers a warning when an administrator adds a group larger than the defined value in the appSetting. It also limits the amount of notifications sent to the users in the group. See John-Philip Johansson's blog post and Configuring CMS user interface.
When setting up an approval sequence, administrators can now require reviewers to add a comment when approving and/or declining an approval step.
The person who started the approval sequence will see this comment as a notification in the user interface:
The Beta flag has now been removed from the content approvals feature.
Content approvals can be used for blocks and media in the assets pane. The setting up of approval sequences for blocks and media works in the same way as for pages. However, there are some differences in functionality. For example, you cannot define an approval sequence for individual assets, only on folders in the assets pane. Also, local assets folders always inherit the approval sequence from the page they are associated with. For more information on content approvals on blocks and media, see the Episerver User Guide.
You can now use the Tasks pane to filter on content you have sent for review and on content you are requested to review. See John-Philip Johansson's blog post: Introducing Tasks in Content Approvals (Beta). This release also adds category support to the Tasks dropdown, to help with grouping different queries together for the user. See Extending the Tasks pane with custom queries in the CMS Developer Guide.
Users who have started a content approval sequence by setting an item to Ready for Review, or are set as approvers, now receive notifications in the user interface. The bell icon in the toolbar displays the number of new notifications a user has; click the icon to display a list of notifications. From the notification list, you can go to the item that needs to be reviewed.
If the notifications should be displayed instantaneously, you need to enable WebSocket support on your web server; otherwise the user interface must be refreshed to display the notifications.
This is the first release of the Content Approvals feature, which enables administrators to set up approval sequences containing a number of steps that editors have to collaborate on and approve to be able to publish the content. This feature is currently in beta, meaning that users need to be in the EPiBetaUsers group in order to use the new feature. See the documentation in the the Episerver User Guide for details.
Developers can now build rich clients using JavaScript and control the DOM with their chosen JavaScript framework. This lets you edit content processed by JavaScript in the on-page edit view without breaking the view. See John-Philip Johansson's blog post and Editing user interface.
"Sticky view" means that the you can select a view (for example, on-page edit or all properties view) and the selection stays when opening another content item. The sticky view functionality is enabled for every content item by default. For more details, see Describing content in the user interface and Grzegorz Wiecheć's blog post.
When working with multiple languages, it is possible to filter the navigation pane, Blocks gadget, and Versions gadget to display content in the currently selected language only. The Show Content in Current Language Only setting is now sticky and does not have to be reset after each page reload. See also Bartosz Sekuła's blog post "Persist "Show Content in Current Language Only" settings" for more information.
You can drag and drop multiple folders and items within the assets pane, and delete, cut or copy and paste them, either from the context menu or using standard keyboard shortcuts. Any unselected children folders are also moved, copied or deleted.
You can also drag and drop multiple folders or items from the assets pane to the content area.
The projects feature is now enabled by default (unless it was explicitly turned off in the admin view). The feature is no longer disabled/enabled in the admin view, but in an app setting, episerver:ui:IsProjectModeEnabled, in the web.config file.
The Change Log API is deprecated so the use of it has been removed. The Change Log admin page has been moved to Tools and gotten a minor update. See Activity logging in the CMS Developer Guide.
It is now possible to define that a job is restartable. If the IIS crashes or is recycled when a job is running, the scheduler runs the job on the next scheduled time by default. A restartable job is started again to make sure it can run to completion (assuming the job can continue where it was stopped). The job can restart on any available instance/server. See Scheduled jobs in the CMS Developer Guide.
From Episerver CMS UI 10.6.0, the GadgetAttribute is marked as obsolete and will be removed in an upcoming major version release. Instead, you should use CompontentAttribute when creating components. All jQuery-based libraries are also now marked as deprecated and should not be referenced because they will be removed in the future. See Grzegorz Wiecheć's blog post for more information.
The telemetry of scheduled jobs has been improved. Among other things, the job history now includes more detailed information, the log size has been increased, and executing a job manually does not change the execution date and time for the next scheduled job. You can also assign a GUID to your job, making it possible to change the name or namespace of the job at a later time. See Scheduled jobs.
The import and export functionality in the admin view has been improved. Among other things, you can now select only one item to export without exporting its sub items as well. You can also import only one language version of an item. See Johan Björnfot's blog post for more details.
The import and export functionality in the admin view has been improved. Among other things, you can now select only one item to export without exporting its sub items as well. You can also import only one language version of an item. See Johan Björnfot's blog post for more details.
As a part of the content approvals feature, Episerver has added plug-in areas at common extension points to make it easy for developers to extend the Episerver user interface. See Plug-in areas in the Episerver Developer Guide for details.
Running the database with local date and time is no longer be supported (CMS-1449). A database that is not converted to UTC will throw an exception to avoid any data loss caused by mixing local and UTC date and time. Conversion can be done before upgrading for versions 9.1 or later, for example using the provided PowerShell scripts, see Storing UTC date and time in the database for more details. A setting can be added to the appSettings section of web.config to disable the exception if the site temporarily have to be started without doing the conversion, add episerver:DisableDateTimeKindValidation with value true.
It is now possible to sort form submissions, to make it easier to navigate large amounts of submissions.
New WorkingModeService service class determines whether the Forms add-on is working in non-js mode. Default implementation returns a setting from Forms.config. You can override the IsWorkingInNonJSMode method to decide when the Forms should work in non-js mode for each and every request.
You now can drag and drop form elements into the FormArea in All Properties view.
Support for validation of multiple elements at once
The Episerver Social platform is a collection of extensible services for defining and collecting community-generated content.
Comments-manage and deliver hierarchical, user-generated content
Ratings-allow users to quantify the value of your content and products
Groups- aggregate users and content to build digital communities
Moderation-review and control user contributions
Activity Streams-broadcast your audience's engagement with your application
This is a new Episerver UGC add-on, powered by Stackla, that enables you to display user-generated content on your website, commerce site and other channels.
A key performance indicator (KPI) records when a website visitor performs a desired action, such as clicking an add button, or completing a sale. You can create custom KPIs, using goal objects in the KPI framework, for use with Episerver A/B testing or any other package that relies on creating instance-based goal objects. See also: Key performance indicators.
Time on Page A client side KPI that turns an A/B test view into a conversion if a site visitor included in an AB test remains on an A/B tested page for a user-specified amount of time.
Site stickiness This new KPI, Site Stickiness, allows a CMS editor to select a target page and a timeout period (1-60 minutes). The A/B test counts a conversion if a visitor goes from the target page to any other page on the website during the set time period. If the visitor closes the browser and then opens the target page again within the specified time period, a new page view is not counted. However, a conversion is counted if the visitor goes from the target page to another page during the second visit.
Landing Page
A new gadget, Archived Tests, has been added to the A/B testing feature. The gadget displays all archived tests run on the currently displayed page. It can be added either to the navigation pane or the assets pane.
A/B testing now works on sites with multiple languages.
You can now add up to five conversion goals when creating an A/B test. You can also decide if one of the conversion goals should be more important, or less important, than the others when determining a winning version. When viewing the A/B test details screen and using multiple conversion goals, the test results show how the test versions are performing against the selected conversion goals. See the Episerver User Guide for more information on how to create an A/B test with multiple conversion goals.
Introduces a framework for creating, injecting, executing, and converting javascript based KPIs to use in A/B tests and beyond.
An A/B test winner can now be automatically published when the test duration has ended and the results are statistically significant.
The winner will be the version that has the higher conversion rate. If the conversion rates are equal, the editor must pick a winner manually.
This feature is set in the admin view under Admin>Config>AB Testing Configuration. If it is enabled (set totrue), it affects all A/B tests on the site. The default setting isfalse.
An option has been added to the MAI Admin screen to allow admins to turn off the auto-fill feature for forms mapped to MAI connectors.
Support added for lists.
On the Admin screen, a dropdown has been added listing all folders in the ExactTarget instance. So, a marketer can choose one to filter the Data Extensions.
Associate new leads with campaigns.
An option has been added to submit data from an Episerver form directly to an Eloqua form. So, the site activities of visitors submitting forms can be tracked in Eloqua.
Support for custom fields
New add-on for Episerver CMS 10. Episerver Connect for Campaign is an add-on which connects Episerver CMS, Episerver Forms, and Episerver Campaign. With this add-on, you can collect visitor data and pass that on to Episerver Campaign.
If another user has tagged you, made a comment on one of your actions or replied to one of your comments, you are notified of this in the user interface. The bell icon in the toolbar displays the number of new notifications you have. Click the icon to display a list of notifications. From the notification list, you can go to the project overview to read the comment.
Adds a comment form to the project item activity feed. This allows messages to be created as part of the activity feed in order to facilitate collaboration on project items. Additionally, it is possible to reply to these messages or comment on other activities in the activity feed.
The project overview lets editors collaborate on a project. They can comment on project items from the Items tab and comment on the project itself or on project actions from the Project comments tab. Editors also can tag other users when commenting.
A tagged user receives an email with an excerpt of the comment and a link to the project. Users also receive emails if someone replies to their comments or comments on one of their project actions, and so on.
Projects lets editors work on multiple content items and release them at the same time, and increases content collaboration between editors by including a commenting and email notification feature.
Adds real time updates to the activities feed in the project overview so that new activities and associated comments are instantly shown without the need to refresh the view.
When you load the navigation or assets pane, the last selected tab is selected by default, as long as the same browser is used.
If the system goes into ReadOnly mode while an editor is working in edit view, the editor is redirected to a read-only page. See Database mode on how to provide your own customized read-only page.
The Episerver log-in screen, global menu and quick access menu have been rebranded.
Episerver CMS is now set up to display comments and changes to projects in the user interface immediately. When using the projects feature, the WebSocket protocol is used to check for new or updated comments and project items from other users. As soon as another user adds a comment or project item, Episerver automatically updates your user interface and displays the comment or item (assuming you have the projects interface open). Note: This feature is enabled by default and requires WebSocket support on the web server, see WebSocket Support in the CMS Developer Guide for more information.
By default, EPiServer CMS uses the local time zone for storing date and time in the database. It is possible to switch to use UTC time as default in the database. See Storing UTC date and time in the database.
It is possible to work in server-side mode, that is, JavaScript is not required.
Forms 3.1 uses a plugin-approach by populating the appropriate exporter based on mimeType each exporter provides.
To use the new DataExporter, use theForms.UIpackage, then subclassDataExporterBase. A new Item is added to the drop-down list inView Form Submission.
The sample pack is extended with several new form elements (Date Time, Range, Rich Text, and URL). See the Episerver User Guide.
Beta flag has been removed.
The newForms marketing automation connectorlets you use the Episerver marketing automation connectors with Episerver Forms 3.
To use Episerver Forms with your existing installation of a marketing automation connector, upgrade to the latest version of that connector and install the Forms marketing automation connector. See also Configuring the Forms marketing automation connector.
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.
Assign a specific host in admin view for edit links such as quick navigator and the sites tab in edit view. The setting is found under admin view > Config > Manage Websites.
Makes it possible to disable visitor group criteria; the disabled criteria will not be displayed in the user interface. This feature is mainly used internally to support market automation add-ons.
Set allowed roles on UI components
Support for SEO alternative languages
Permanent links and friendly URLs replace classic links
The Eloqua® add-on automatically exports form data from your website to your Eloqua account database by mapping EPiServer form fields to Eloqua database fields. For more information, see Configuring Eloqua and the Using Eloquasection of the EPiServer User Guide.
The ExactTarget® add-on automatically exports form data from your website to your ExactTarget account database by mapping EPiServer form fields to ExactTarget database fields. For more information, see Configuring ExactTarget and the Using ExactTarget section of the EPiServer User Guide.
The HubSpot® add-on automatically exports form data from your website to your HubSpot account database by mapping EPiServer form fields to HubSpot database fields. For more information, see Configuring HubSpot and the Using HubSpot section of the EPiServer User Guide.
The Microsoft Dynamics CRM® add-on automatically exports form data from your website to your Microsoft Dynamics CRM account database by mapping EPiServer form fields to Microsoft Dynamics CRM database fields. For more information, see Configuring Microsoft Dynamics CRM and the Using Microsoft Dynamics CRM section of the EPiServer User Guide.
The Pardot® add-on automatically exports form data from your website to your Pardot account database by mapping EPiServer form fields to Pardot database fields. For more information, see Configuring Pardot and the Using Pardotsection of the EPiServer User Guide.
The Salesforce® add-on automatically exports form data from your website to your Salesforce account database by mapping EPiServer form fields to Salesforce database fields. For more information, see Configuring Salesforce and the Using Salesforce section of the EPiServer User Guide.
Change default OPE editors to be floating instead of flyout. Refer to Object editing and UI wrapper types for more information.
Scheduled publishing for projectsadds additional functionality to the Projects (beta) feature, allowing editors to set a point in time for publishing multiple content items. For more information about the usage, see user guide.
Search in link dialog
With this feature you can view and navigate a project with a set of pages and other content as if it was published. Use this to check that links work and all content items look as they should before publishing the project. Refer to update 31 for more information about the Projects feature in beta version.
Globalization support in link dialog: Currently the support is limited to the link item collection and the link tool in TinyMCE. The support is not yet implemented for the property URL due to a related bug which is not yet fixed.
Multi-publishing of projects (Beta)
Support for auto suggestion editor
Contains a feature in CMS that makes it possible to report links to other content in custom properties.
Extensible Permissions for functions adds extended possibilities to assign users and roles to permissions. Refer to Permission to functions in the Episerver Platform User Guide for more information.
