A friend of mine came to me with a problem he had. He created a record producer and from there he wanted to have field which would be connected to the contextual search. And of course he wanted this to search in a specific knowledge base, but OOB it search in all of the knowledge bases. I agree that If I had a record producer that is used to report IT incidents, I don't want it to search the HR knowledge base.
And of course you can do this, just takes a bit of digging and looking
Some of you know my gigantic amount of imagination, so In this example I will create a record producer for reporting Email incidents and I want to limit the contextual search for only the email knowledge base.
1. First I created a knowledge base and put in one article in it
2. Now lets create the record producer
I just created a simple RP which was going to create an incident record and threw in two variables.
- Short desc: This is just a simple Single Line Text which I will connect the search context to
- Who: This is just a reference field to the sys_user. I just felt I wanted to have two fields
Then I just felt to put in the script where this was going to be put in the incident. Just for fun, no needed for this demo. And it could have been done slimmer
But bare with me, it's Saturday and I just lost a game of Monopoly.
3. Now lets create the search context and connect it to the Record Producer
First I created the search context.
You can see that I only wanted to search in knowledge so I put "Knowledge only" in the field Searcher.
Here are a few choices and depending on what you choose, the related list "Resource Configuration" will
have different records. I will tell you more about that later.
Then I pressed the "new" button on the related list, I chose my variable "Short desc" to be the one it uses for search
and connect it to the search context by hitting submit.
Now you got the Record producer connected to the search context and you can also see under Resource Configuration
that knowledge is ready to rock and roll as well.
4. Let try the record producer!
As you can see when I typed "email" in the field I get a lot of results and I since my created Knowledge base
only has one article, I know that I get stuff that I don't want.
5. Time to filter
Now let's make so it will only look for records in my knowledge base. To do this we need to get an encoded query to use
as a filter. So let's head to kb_knowledge.list and get that first.
So Now I got my encoded query in my clipboard. Next stop is the search context record.
Click on the related list Resource Configuration and then click on the record "Knowledge".
And that will take you to this:
As you can see the "condition" record has no value. It is totally empty.
So I clicked on "Condition" and paste in my encoded query in the value field. And it looked like this:
Submitted the record and ready for test nr.2.
6. FInal test
Back to my record producer and hit "try it". Now when I filled in "email" I only got one result and it is the
article from my own knowledge base.
Over and out, now back to watch some Olympics
22 Comments
