Bartosz Sekula
Nov 20, 2018
visibility 4490
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
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 |