Hey @sbritt - Any ideas on how I can achieve this with what is already OOTB? Or, should I start to design something from scratch to trigger a notification that grabs the current author, regardless if it has changed?

Thanks,

-Rob

We are also currently workshopping this scenario. We have a user who has moved teams and is no longer working on knowledge articles but is Author/Revisor on just under 100 articles.

We managed to remove his subscriptions to the articles and update our notifications to only go to Ownership group members and unhide the author field to manually update to the Ownership Group Manager but the 'Articles expiring' notification is still going to the user as they are the revisor of previous article versions. Such a pain.

If you find a good process for this, please do share.

Hey Lesley, (sorry for the delay)

I received some help on this and am taking a different route.

We designed a Flow Designer workflow to handle the process now. I am still in testing mode, but it will certainly take care of sending the notification to the current author which was a huge deal.

We are in talks with the rest of the teams that use this process, to make sure all who receive the notification via OOTB process, still want to receive these.

Author is the main person who should, manager of the group is another main person (maybe). A person who revises an article does not need this notification. We have some people who may help out authors and change one small thing to an article. After that, they do not need to know when it is expiring.

So, I am looking to retire (no pun intended - haha) the OOTB process and use the Flow Designer workflow created instead.

Thanks,

-Rob

Haha great "retire" pun.

This sounds very interesting, Rob. Would love to hear what kind of worklfow you're thinking of if you're willing to share and testing is successful.