top of page

Introducing Email Scrubber 7.3 — Has Archive Record and Case Activity Feed Posts


You asked for more flexibility... and with Email Scrubber 7.3, we're delivering exactly that.


This release is all about one theme... archiving your email data without losing the context around it. 


We are delivering two new features.

  • A Case-level archive indicator

  • Feed items for archived emails


Feature 1: The "Has Archived Records" Case Flag

Here's a question your support agents ask all the time: "Is this everything, or is there more history somewhere?"


Until now, there was no at-a-glance way to know whether a Case had archived email history. Agents either checked the archive related list on every Case, or worse... assumed the visible emails were the whole story.


Email Scrubber 7.3 introduces an automatic Case flag. When archive records exist for a Case, Email Scrubber sets a checkbox field so your users, reports, and automation all know there's more to see.


What you can do with it:

  • Add the flag to your Case page layout so agents see it instantly

  • Show your archive viewer component only on Cases that actually have archived history

  • Build reports and list views like "Closed Cases with archived email"

  • Drive automation and validation off the presence of archived data


Flexible by design. Out of the box, the flag is the Has Archived Records field Email Scrubber provides on the Case. Prefer your own field? Point the configuration at any checkbox field on the Case object and Email Scrubber will maintain that one instead.


Built for scale. The update runs as a batch process, designed to stay out of your users' way. Turn on the automatic option and it runs right after each archive batch completes... or leave it inactive and schedule it on your own terms. Either way, it processes only the Cases that need updating.


No wasted cycles, no locked records during business hours.



Feature 2: Feed Items for Archived Emails

If your org runs Enhanced Email, your agents live in the Case activity feed. Every email is an entry in Recent Activities... and when an email is archived, that entry disappears with it.


With 7.3, it doesn't have to.


When Email Scrubber archives an email, it can now create a feed post in its place... a breadcrumb that references the new archive record, right where the original email used to be. Your storage goes down. Your Case history stays complete.


The details that make it work:

  • Your title, your content. The post title comes from your configuration, and the post body is driven by a formula field on the EmailMessage. Summarize the sender, subject, and date however your team wants to see it. Because it's evaluated at archive time, the text is captured while the email still exists and preserved after it's gone.

  • Chronology preserved. Here's our favorite part: if the running user has the Set Audit Fields upon Record Creation permission, Email Scrubber backdates each feed post to the original email's message date. The post doesn't land at the top of the feed on archive day. It sits exactly where the email sat, keeping your activity timeline in true order.

  • One click to the archive. Each post links directly to the archived email record, so "where did that email go?" is answered in a single click.



Shipped Safe

Both features arrive inactive by default. Your current archive processes continue exactly as they run today. Nothing changes until you decide it should. When you're ready, each feature is a single configuration option on the Declutter Setup metadata record, documented step by step in the user guide.


The Bigger Picture

Email messages are the largest data storage consumer in most Salesforce instances — and archiving them shouldn't mean amputating your Case history. Version 7.3 is about having both: the storage savings of aggressive archiving and the context your team needs to serve customers.


Because one size does not fit all... and now, neither does your archive.


Email Scrubber 7.3 is available now on the AppExchange. Questions about enabling these features in your org? Reach out. We're happy to walk through the configuration with you.

 
 
 

Comments


bottom of page