Knowledge Article Template articles do not launch a workflow context.

Sam190
Giga Expert

Hi all,

I activated Article Templates in order to use at the same time with an Interceptor for when a user has to create a knowledge article. The article templates are for example "KCS Article", "How To", "FAQ" and so on... The interceptor and the article templates work, as I attached templates to the knowledge bases.

When I create an article using one of the templates that is not "Standard", it goes to draft mode but it doesn't launch any workflow (OOTB) despite the knowledge base having workflows on it. I read somewhere that they don't get launched because the templates are based on child tables of kb_knowledge and only articles that are directly on the kb_knowledge table launch knowledge workflows. 

How can I get around that so I can have the full knowledge process by using article templates? I can't find anything about it online... 

All the necessary plugins have been installed. 

1 ACCEPTED SOLUTION

sachin_namjoshi
Kilo Patron
Kilo Patron

This is happening since your KB article workflows are configured on kb_knowledge_base table and KB article templates are configured on different tables like below

find_real_file.png

 

You will have to configure workflows on above tables as per your instance configuration so that you can see workflow context.

 

Regards,

Sachin

View solution in original post

6 REPLIES 6

Tony K
Kilo Sage
Kilo Sage

We're setting up knowledge right now as well using templates and skipping standard. If I remember right approvals/workflow were not working on the other templates because they were missing info in fields that would trigger the next steps in the workflow. 

Also do you have multiple knowledgebases? For each one you have to configure which workflows you are using.

 

Sarup Paul
ServiceNow Employee
ServiceNow Employee

The workflow associated with the Knowledge Base in which these articles are being created (irrespective of standard, or templates) should kick in. If it doesn't then probably there is customization / configuration that is causing this. Please do check by creating a HI ticket.