Automation workflow for inactive page

[sshakya]

I am using Inactive page notification from Confluence that helps us keep content up to date. But users have been complaining about this and asking for few improvements. I wanted to know if below requirements are possible

- Send summary email of all the pages that's expiring, not a single email per page.

- Customize the notification so that there is more info in the email. 

[Brant Schroeder]

@sshakya if you are using Confluence automation for this I do not know of a way to compile a list of pages but you can customize the notification.  If you are using better content arching then you would have to contact their support and see if that is something you can do on cloud.

[Levente Szabo _Midori_]

@sshakya What you mention are known limitations to A4C, and this is why it's not a viable tool for Confluence content lifecycle management. Notably, you can't customize what is considered "inactive", you will get as many emails as many pages you report, and branch rule execution cuts off at 150 pages. Meaning that if you ever need to report more than 150 pages, some people would never get an email.

Better Content Archiving brings a flexible, automated notification mechanism that covers your pain points:

1. You can trigger emails by automatically refreshing page statuses
2. It sends page lists, not individual emails
3. You can send different emails for different purposes (expired pages, not viewed pages, archivable pages, etc)
4. You can customize the content of emails
5. You can select different recipients for your emails
6. You can even recreate and fix the Confluence daily digest email experience

Watch this tutorial video for a better idea and give it a try for free in your instance:

(Please note that I'm part of the team developing Better Content Archiving for Confluence)

[Danja Karenko]

EDIT:

I retract my previous statement since I finally understood that you were referring to the definition of inactive (=not having been viewed), not the duration of the inactivity. My apologies for not grasping that earlier! =)