What is the best practice for connecting a Knowledge Database to a custom scoped app?

[raking08]

We have a scoped application that is a large, detailed structured knowledge repository on specific data standards. While the knowledge ther eis not appropriate to be in a KB DataBase, discussion and ongoing improvement to it is a great application of a SNOW KM Module.

Technically we need to add a new "List field" to the KM side that will allow for a dropdowm list of preconfigured links to the custom repository.

My 2 questions are:

1. My idea of an approach is to add a field to KB_KNOWLEDGE table ( I think) I would do that by:
   1. creating an extension table in the scoped application
   2. Adding the custom list field referencing the main table in the scoped application
   3. This way the links, and data are only available and manageable by the Custom Application Steward.
   4. I plan on creating that under the scoped application with access by KM (vs creating it as a global table).  
2. is this the right approach at all ? is there something pre-built in SNOW that does this that I am missing? This approach is only "semi automated". Is there a standard way to add in a semantic layer that can further automate this?

All feedback is appreciated

Richard

[raking08]

I have confirmed that :

• a list field will not work, but a series of reference fields using a table with the name and links will work if added directly to the KB_Knowledge table as a new reference field. This feels like the wrong approach however. Also it seems impossible to add the new column(s) to an extension table of KB_Knowledge into the scoped app.
• Has anyone extended KB_Knowledge into a scoped application in order to be under the scoped custom app security etc? Extended the table for other reasons?

[saptashwa_chakr]

Hi ranking,

I have just gone through your statement.

So would you like to add the reference of OOTB "KB_KNOWLEDGE" table or you want to make a new knowledge base in your custom application?

Please share your views.

Thanks,

Saptashwa

[raking08 · Accepted solution]

Hello Saptashwa,

We initially were going to add a new field to the corporate knowledge base to use with a new (non-scoped) KB. But quickly realized this would neither migrate well if we were to commercialize the main scoped application, nor would it get past corporate governance.

We took a different route for adding links between multiple records in our scoped app and the WIKI page for any given knowledge article. This new approach is faster and will serve the same function for non Service now documents as well. Plus its more user friendly.

Short answer is the new approach is preferred

Many thanks

Richard