World is now on Opti ID! Learn more

John-Philip Johansson
Dec 27, 2016
  2248
(0 votes)

Introducing Notifications in Content Approvals (Beta)

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

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

You can also read more about Content Approvals in my previous blog post.

Notifications require WebSockets and configuring your email server.

What are Notifications?

Notifications were released as public beta in CMS 9.4.0 and is used by CMS UI 9.4.0 to show notifications related to Projects. A notification is sent instantly to the recipient and shows up in the UI in the "bell icon". Any unread messages will later be emailed out to the user. In CMS 10.3.0, emails can also be sent out instantly instead of waiting for the Notification dispatcher scheduled job.

Notifications on Content Approval events

In CMS UI 10.3.0 notifications are also used to send Content Approval-related messages, and it uses the new instant emails as well.

In the screenshot below, Lina has received a notification that Alfred has sent a page to be reviewed, and she is one of the approvers that should approve or decline the change.

Image blog-notifications-lina-ui.PNG

Lina also receives an email about this, as seen below.

Image blog-notifications-lina-email.PNG

Lina decides to approve the changes and since this scenario only has one step, the page is now ready to be published. In the screenshot below, Alfred is notified about this.

Image blog-notifications-alfred.PNG

Notifications are sent when content is awaiting approval, has been approved, declined, or aborted. Those events are available on the ApprovalEngineEvents which can be hooked into.

Dec 27, 2016

Comments

Please login to comment.
Latest blogs
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |