Try our conversational search powered by Generative AI!
AI OnAI Off
Episerver CMS
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.)
Expand All Collapse All
CMS 10
Edit view
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:
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.
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.
You can also configure your system to send out email notifications. See Configuring your email server.
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.
You can also configure your system to send out email notifications. See Configuring your email server.
"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.
You can now add or edit query strings on internal links using the Remaining Url field in the Edit link dialog box. See Linking to a page on the same website in the Episerver User Guide for more information.
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.
