A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

John-Philip Johansson
Feb 7, 2017
  4050
(9 votes)

Introducing Tasks in Content Approvals (Beta)

This feature is released as a Beta feature in CMS UI 10.5.0 and is still under development.

You can read more about how you enable Beta features in Fredrik Tjärnberg’s blog post.

What are Tasks?

The Tasks pane is a useful tool for editors to monitor content creation. You can filter out content depending on their status,  for example, select Drafts in the Tasks drop-down to get a list with content items in status Draft only.

Image blog-tasks-tasks-menu-original.PNG

Tasks with Content Approvals

The Tasks drop-down list can now be used to display content in a certain stage of an approval sequence, in a way that helps the editor to know what to focus on.

For example, Alfred has sent two pages for review, and the approval sequence is set up to allow either Lina or Emil to approve. Lina uses the Tasks pane and Received Review Requests > Awaiting Your Review to see what content she has to review and do some work:

Image blog-tasks-lina--optimized.gif

Bonus feature: Categorized Tasks Queries

As part of this release, we added grouping support to the Tasks menu. As you can see in the screenshot below that there are three main categories: "Status", "Sent for Review", and "Received Review Requests".

Any other query will end up in a category labelled "Other", and you can easily put them in an existing or a new custom category.

Image blog-tasks-tasks-menu-new--awaiting-review.png

Bonus feature: Optional Localization Support with IContentQuery and IContentQueryCategory  

Often you might end up implementing the query’s DisplayName using the LocalizationService. Like this:

// No need for this anymore
public override string DisplayName => _localizationService.GetString("/awesomequeries/super/label");

It’s so common that we made it simpler by allowing DisplayName to be a key and it will be used with the ILocalizationService to return the localized display name.

// Do this instead, if you use the LocalizationService
public override string DisplayName => "/awesomequeries/super/label";
Feb 07, 2017

Comments

Please login to comment.
Latest blogs
Building simple Opal tools for product search and content creation

Optimizely Opal tools make it easy for AI agents to call your APIs – in this post we’ll build a small ASP.NET host that exposes two of them: one fo...

Pär Wissmark | Dec 13, 2025 |

CMS Audiences - check all usage

Sometimes you want to check if an Audience from your CMS (former Visitor Group) has been used by which page(and which version of that page) Then yo...

Tuan Anh Hoang | Dec 12, 2025

Data Imports in Optimizely: Part 2 - Query data efficiently

One of the more time consuming parts of an import is looking up data to update. Naively, it is possible to use the PageCriteriaQueryService to quer...

Matt FitzGerald-Chamberlain | Dec 11, 2025 |

Beginner's Guide for Optimizely Backend Developers

Developing with Optimizely (formerly Episerver) requires more than just technical know‑how. It’s about respecting the editor’s perspective, ensurin...

MilosR | Dec 10, 2025