1. Go to the knowledgbases and enter the name of the new knowledgebase record (eg. Change_Library), the Display Name (eg. Changes), Type (sclib) and the Search Server Name. Click Add.
2. On the Type Information tab, set the table name, query (for which changes should be indexed) and the unique key. The scripts will already be added as this is done when adding the new knowledgebase.
3. In the Fields Definition tab, you need to set up the fields which the customer would like to be indexed.
Look at some of the other records to get a feel of what is needed here.
Remember the Hitlist column enables the field to be available to be used in the hitlist (Search Results) if set to true. The Doc Body column enables the field to be searched from a simple search (not an advanced search) if set to true.
4. Back on the Status tab, set the Refresh Interval as appropriate (eg. 2 means to index every 10 mins). Save.
5. Click Full Reindex.
6. Once the KMUpdate background process has run, and the kmknowledgebaseupdates table has flushed, changes will be indexed and can be used in Knowledge Management.
7. To display the change from the knowledge search results, you need to set up a new format to display it. I suggest copying "SD.view.interaction.km" and call it "CM.view.change.km" - and update this format with the appropriate fields from the change.
i.e . cmd line > fd > SD.view.interaction.km > more option > copy > CM.view.change.km > save > ok
Note: Design the form according to the requirement
else if(vars.$L_linktable == "cm3r")
//vars.$L_modetouse = "KMbrowse"; //see ess.determine.EdtFmt process record
vars.$L_formattouse=" CM.view.change.km ";
9. Go to Search Knowledgebase and search for changes: