Adding Parent or Problem field to a Knowledge Document
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2017 01:50 PM
Hi.
We are newer to creating a knowledge base within ServiceNow.
When we create a Knowledge Document, how do we get the field to appear where I can enter the Parent Incident or the Problem record number so that if the KD is accepted, the Parent/Problem is automatically pulled into the Incident?
I have a similar question related to other fields as well. How do we get into our Knowledge Document Template, the ability to define within the KD itself, the Assignment Group, Category, TYPE, Urgency, and other related fields?
Lastly, and I can post separately if needed, do we need to be concerned about profiling? For example we are building out 2 KB's, Public and ITIL.
If I can add the fields we need to the KD so that if accepted it pulls them back into the Incident, do we need to be thinking about how it will work with KD's in the Public KB vs. ITIL KB? I ask because in the Public KB, we would not want or need our users to see things such as TYPE, Category, Assignment Group, etc.
I hope this has enough information and that I'm posting in the right area.
Thanks
Walt
- Labels:
-
Knowledge Management
-
Workflow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2017 12:08 PM
This is OOB behavior when the target (or one of the target fields) is a reference in the property "glide.knowman.attach.fields".
In other words, add a field (reference to kb_knowledge) to your form, then specify that field in the property value, and you'll get your reference.