Bartosz Sekula
Nov 20, 2018
visibility 4353
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
Finding Thomas Part 4 - The Intelligence Layer

I've been finding Thomas for four weeks now. Bear with me — we're almost at the full picture. Quick catch-up : Thomas is the returning visitor who...

Ritu Madan | Jul 14, 2026

The Silent Success: When Your Optimizely SaaS CMS Config Push Succeeds with "0" Changes

  Picture this frustratingly common scenario in headless, code-first development with Optimizely SaaS CMS: You’ve defined a brilliant new element,...

Vipin Banka | Jul 13, 2026

Architecting an Enterprise-Grade Development Pipeline in Optimizely SaaS CMS

Most enterprise teams show up to Optimizely SaaS CMS with a clear roadmap for their release pipeline: DEV → QA → Stage → Prod. Four logical...

Vipin Banka | Jul 12, 2026

Bynder DAM Connector for Optimizely SaaS CMS: Improved Metadata Property Synchronization

While working with the Bynder DAM Connector for Optimizely SaaS CMS , one of the key areas I explored was how Bynder asset metadata is synchronized...

Vipin Banka | Jul 11, 2026