- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-20-2021 11:04 AM
Users are using the wrong template for certain knowledge bases. It seems the templates are available for every knowledge base (going by interceptor).
A good example is the Known Error KB which should only contain articles using the Known Error template. Conversely, we don't want the known error template used the the standard Knowledge base.
Any way to restrict this?
Solved! Go to Solution.
- Labels:
-
Knowledge Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2021 03:04 PM
There is an OOB way to configure specific Templates to a KB. Check step 5 > Article Templates
https://docs.servicenow.com/bundle/quebec-servicenow-platform/page/product/knowledge-management/task/create-a-knowledgebase.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2021 12:33 AM
As each template is a child table of kb_knowledge, you can modify reference qualifier for Knowledge base field on Template table. This way when user select a template and populate knowledge base they will have limited/correct knowledge base options.
If this helps, please mark this correct/helpful as applicable.
Thanks,
Pushpa
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2021 03:04 PM
There is an OOB way to configure specific Templates to a KB. Check step 5 > Article Templates
https://docs.servicenow.com/bundle/quebec-servicenow-platform/page/product/knowledge-management/task/create-a-knowledgebase.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2021 11:46 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-15-2022 01:03 PM
We too would like for "Standard" to not be a removable option. @Sarup Paul if you or anyone else at ServiceNow can take this into consideration as a future enhancement that would be greatly appreciated.