Ryan Bare
Ryan Bare  -  CMS
Mar 25, 2019
visibility 3949
star star star star star
(2 votes)

Marking notifications as read automatically

Users often have a large number of unread notifications displayed in their notification icon badge. While opening the window temporarily clears the badge, the number returns on a page reload. This has been discouraging users from utilizing notifications, as they are not using the "Mark all as read" button.

In CMS 11.19.0, all notifications will now automatically be marked as read when the notification window is closed. The notifications will retain their yellow "unread" background until either the notification is clicked, or upon a page reload. This means the "Mark all as read" button and the context menu with the "Mark as read" option are no longer necessary and have been removed. 

Mar 25, 2019

Comments

error Please login to comment.
Latest blogs
Composition Over Inheritance: Why Your Content Contract Is Not a Base Class

Inside the structural conformance pattern in SaaS CMS — from server-side inheritance to pipeline governance. A contract in Optimizely SaaS CMS is...

Vipin Banka | Sep 19, 2026

Optimizely Opti ID Integration: Why the API Key Was Missing from the DXP Management Portal

While working on an Optimizely CMS 12 Opti ID integration recently, we ran into an issue that initially appeared to be related to SSO authenticatio...

Madhu | Sep 18, 2026 |

Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |