John-Philip Johansson
Feb 7, 2017
  4238
(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
A First Look at Optimizely Remote MCP Server for Experimentation

Optimizely just released a Remote MCP Server for Experimentation and I've been trying it out to see what it can do. If you don't know, MCP (Model...

Jacob Pretorius | May 1, 2026

Promoted and Certified

What a busy week

Andy Blyth | May 1, 2026 |

Announcing new library: SettingsManager

When you run .net app, there have been a few ways to store settings. Those can be set via appSettings.json, or via Azure Portal AppService...

Quan Mai | Apr 30, 2026

From Prompting to Production: Optimizely Opal University Cohort and the Future of Agentic MarTech

Most organizations today are still playing with AI. They experiment with prompts, test ideas in isolated chats, and occasionally automate a task or...

Augusto Davalos | Apr 28, 2026

Six Compelling Reasons for Upgrading to CMS 13

Most software updates ask you to keep up. Optimizely CMS 13 asks something different — it asks whether your digital strategy is built for a world...

Muhammad Talha | Apr 28, 2026

Optimizely CMS 13 breaking changes: GetContentTypePropertyDisplayName

When upgrading from CMS 12 to 13, resolving property display names may not work as before. Here’s what changed.

Tomas Hensrud Gulla | Apr 27, 2026 |