knowledge base selecting topics

tim_houlston
Kilo Contributor

Hi, i am trying to use knowledge base across a domain separated environment, however i notice that knowledge categories are effectlively useless as they cannot be selected by any article author or admin when creating an article.

i.e If i create one or several categories in the appropriate tab in the   knowledgebase i can never select them as an author.

When i create an article the category is linked to a   "topic" and there seems to be no place to define a topic or link a category to a topic, so i have no ability to link the newly defined categories in the categories tab in the knowledgebase to be selectable because they are all linked to topics which i can not seem to select define or link.

has anyone else experienced this or know of any solution?

5 REPLIES 5

Michael Fry1
Kilo Patron

Ran into that in the past. Figured out I had to change the domain on the categories in order for the child domain to see and use it:



Screen Shot 2017-08-30 at 8.09.01 AM.png


HI Michael,



Thank you very much for your response, unfortunately i have tried that and still cant set the custom category or even see the custom category at the point of creating a new article.



if the global domain solution did work (and it was some other issue preventing me from seeing it) would that mean that knowledgebase would not really be domain separated, as any knowledge user would be able to see any knowledgebase category as they would have to reside in global rather than their own domain.



Thanks


We used 1 knowledge base with several categories and set the domain on the categories to the child domain that it should belong too. That solution worked for us, and allowed our customers the ability to see and search the kbase.


Gilbert Jimenez
ServiceNow Employee
ServiceNow Employee

HI Micheal,



By default, the Topic and Category fields no longer appear due to knowledge v3 category changes.



With knowledge v3, all knowledge articles are organized by category and subcategory within knowledge bases.



Knowledge v2 KB uses the legacy category structure; where knowledge articles are organized by topics and categories.



Before migrate articles, a category structure should have been created for these articles in the destination knowledge bases. This structure can reproduce your legacy topic and category structure or can be extended to take advantage of the knowledge v3 category functionality.



The above information can be found i the wiki articles below:


http://wiki.servicenow.com/index.php?title=Migrating_to_Knowledge_Management_v3#gsc.tab=0


http://wiki.servicenow.com/index.php?title=Migrating_to_Knowledge_Management_v3#Define_a_Category_St...



Can you ensure that the KB you are implementing categories for is a V3 Knowledge base and not V2.



You can verify this by showing the XML of the KB by right clicking header and clicking "Show XML" and scrolling down to "Release Version".



+Best Regards,


Gilbert