Is it possible to have a task for knowledge article?

[Community Alums]

My requirement is to have an Assignment Group field on Knowledge Articles and assign a task to that group a month to valid date.

I started with the workflow on Kb_knowledge and I don't see and Task activity. Is it possible to have a task for knowledge articles or, would you suggest some other way to do this?

[Jeff Currier]

You could add a related link for "Attached to task", which would allow you to associate any task with a specific knowledge article.

But I think the only task types associated to knowledge articles out of the box are KB Submission tasks and Feedback tasks.

[Mwatkins]

Hi Rajinis,

It Sounds like you want to have some kind of task automatically created for every knowledge article every month. Is that right?

Here's some of the things that I thought should be mentioned about deciding to use the task table:

• If you have 1,000 KB articles that's 12,000 tasks a year, right? Not a big deal. If you had 100,000 kb articles then this would generate enough task records to have some impact on performance and you should think about System Archiving the old closed task records. How many records do you expect to create?
• Extending the base task table is a very common and useful thing to do and many customers have done it extensively. However, it is not a 0 cost design decision. Do you need all the bells and whistles of the task table or could a simple custom table that does not extend from task do the trick - workflows, flow designer, business rules, notifications and many other "engines" can all be run on non-task tables? State Management, Approval Rules and SLA's are probably the biggest functionality loss when deciding not to use a table extending task.

Ok. So, let's assume you've thought it through and you want to use task.

• Every month make a new task for every KB article
• The task should be assigned to the group in the Assignment Group field.

There is no assignment group field on the KB knowledge table out of the box, so you'd need to make one and ensure that it is correctly populated somehow.

Options for task creation:

• You could create a scheduled job that runs once a month, loops through each KB article and creates a task via GlideRecord.
• You could create a Flow Designer that fires on a monthly basis and use the built in task creation behavior and loops to make one task for each KB article. https://docs.servicenow.com/bundle/paris-servicenow-platform/page/administer/flow-designer/reference...

Good luck!

Please ✅ Correct if this solves your issue and/or  👍 if Helpful

[SanjivMeher]

So there is no OOB solution to review a knowledge on a periodic basis.

So you have few options.

1. Set up a monthly or quarterly scheduled job to move all the articles to review state again where last updated date is before 1 month or a 1 quarter respectively. This will cause the knowledge article to be reviewed and then approved.

2. Create one task using a scheduled job to review all the knowledge article where last updated date is before 1 month or a 1 quarter respectively. If you have a HTML description field, add the link to the articles there, or in the worknotes.

[Community Alums]

It is just one task to be created 30 days before the valid date, that will go to the assignment group. I think just extending the base task table should work. Any advice to this route?