Setting up Workflow for Valid To Date

[StephanieM34173]

We are currently creating a workflow for the Valid To expiration for KB articles.
We are using Ownership Groups.
We would like to create a notification to the ownership group  at 30 days (one notification email with all articles listed with links to open the article, edit the KB and Valid to Date). At 7 days if the article has not been updated, a Task (or Service Request) is created and assigned to the ownership group with SLAs.

We are currently on Vancover (upgrading to DC soon). 
I was told that we should use Feedback Tasks instead of  Tasks, however, with the Dashboards we have in place, I am afraid that we are unable to add in the Feedback Tasks and the groups would have to go to another location to see them all (and forget about them all together).

What is the workflow with Valid To expiration worked for your company? I hate to do everything manually (as I have been doing in the past) and now we have a team that can create these workflows for us.

Thank you!

[Kim27]

Hi Stephanie, here's a link you will find useful. It walks through the process for what you describe above—hat tip to @Logan Poynter . 

I have not found a way to create a KFT other than as a result of a flag/rating/knowledge not found. I wish there was a way to manually create a KFT (through a catalog item or via clicking a "New" button"). It would make tracking tasks generated outside of SN easier and allow us focus on a single work queue. If anyone has figured this out, please share! 

P.S., I created this idea to generate a KFT from a catalog item. If you are so inclined, please go and upvote it: https://support.servicenow.com/now?id=view_idea&sysparm_idea_id=022ff20a9364d214080af35d6cba102f&sys...

[StephanieM34173]

Thank you for your response. 
We are using ownership groups as authors/SMEs tend to leave and this way we may the whole application team accountable for the KBs. We have the email down but I wanted to make an additional flow where either a Service Request or Task is created if the Valid To date has not been modified  and expires in 7 days. This way its trackable and SLAs are applied. I was told by the company that is assisting us that Feedback Task was the only way to achieve this but they have to be created at the onset when the email gets sent. I really dont want Feedback Tasks as we dont have that in our main dashboard and you have to kinda dig to find them (if you dont know where it is at). If it was a Task, Catalog Request, Service Request or Incident those are added to our Dashboard. 

Just wanted to see if anyone else does something similar and what type of item worked for you (Task, Request, Incident, etc.)

[laura_p]

Our developers created a workflow that 30 days before the Valid to date the system creates a KFT. From there the approved publishers in that group receive an initial email and several reminders so they don't forget. You mentioned you don't want it going into KFTs but just mentioning that it does work for us if you find that there is no other way.