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.)
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.
See also Bartosz Sekuła's blog post.
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 TinyMCE editor has been moved to a separate NuGet package with its own versioning.
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.
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.
When a visitor submits a Salesforce 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.
It is now possible to create segments based on filter definitions and historical data in the Episerver Insight user interface.
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.