Bartosz Sekula
Nov 20, 2018
visibility 4313
star star star star star
(4 votes)

Delayed approval email notifications

Up to this point, if you had SMTP configured, your editors would receive immediate emails about every approval step that the content went into.

In cases when a page goes through a long approval sequence - is reviewed at few steps, declined, marked as ready for review once again, approved, etc. it would cause the editors to be flooded with emails.

Version 11.13.0 of EPiServer.CMS.UI brings an improvement to our Content Approval email notifications. 

The frequency of incoming emails is now just dependent on the Notification Dispatcher scheduled job interval setting (configured in the admin mode, nothing changed about it) which means that a single editor will only receive a single email with a batch of all Approval related notifications.

An example email that contains 4 notifications about two different content items is presented below:

By adding the following module:

[ModuleDependency(typeof(FrameworkInitialization))]
[InitializableModule]
public class ApprovalNotificationInitialization : IConfigurableModule
{
	public void ConfigureContainer(ServiceConfigurationContext context)
	{
		context.Services.Configure<ApprovalNotificationOptions>(options => options.Immediate = true);
	}

	public void Initialize(InitializationEngine context)
	{
	}

	public void Uninitialize(InitializationEngine context)
	{
	}
}

you can turn this feature off and not have the emails bundled.

Nov 20, 2018

Comments

Aria Zanganeh
Aria Zanganeh Nov 21, 2018 11:53 PM

For one of customer there were looking for this for a long time :) 

error Please login to comment.
Latest blogs
Automated Search & Navigation to Graph Migration with Claude Code

A Claude Code plugin that scans your S&N codebase, applies Graph SDK transformations, and validates the result. Install once, run one command. CMS ...

Connor Fortin | Jun 24, 2026

Migrating from Find to Graph: Lessons Learned from a Real CMS 13 Project

While migrating a search solution from Optimizely Search & Navigation (Find) to Optimizely Graph in CMS 13, I encountered several issues that were...

Binh Nguyen Thi | Jun 24, 2026

Optimizely: Upgrade Opti-ID and .NET 10 in CMS 12

Many Optimizely customers are planning their roadmap around a future migration to Optimizely CMS 13. As a result, upgrades such as Opti ID adoption...

Madhu | Jun 23, 2026 |

Understanding Optimizely Graph: Caching, Webhooks & Avoiding Stale Content (Optimizely SaaS CMS)

📌 Scope: This post covers Optimizely CMS (SaaS) only — using the official @optimizely/cms-sdk and @optimizely/cms-cli packages with Next.js 15. If...

Kiran Patil | Jun 23, 2026 |