Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Search for | Example | Results |
---|---|---|
A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Search for | Operator | Example |
---|---|---|
Two or more words in the same topic |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
- Knowledge Management migration
- Import documents into Service Manager
- XML file specification for Knowledge Management migration
- Sample import record migration file
- General considerations for importing documents into Service Manager
- XML source document considerations for importing
- Document import considerations for attachments
- Configure the wsdl2java.bat file
- Configure the wsdl2java.sh file
- Running the wsdl2java command file
- Configure the runDocumentImport.bat file
- Configure the runDocumentImport.sh file
- Running the runDocumentImport command file
- Reconciling unresolved links
- Using the knowledgecreator.log file
- KMSCCoreImport utility
- KMDocumentExport utility
Document import considerations for attachments
Before importing documents into Service Manager, consider the following regarding attachments.
- All attachments should be in an attachments folder under the XML source directory.
- Shared Content attachments should have the file name prefixed with
"shared_" followed by a unique string used as the legacyid for attachments followed by an underscore and the file name.
shared_<legacyId>_<filename>
Example:shared_1234567890_Logo.jpg
. - Attachment links (shared or owned) in the source XML should have the
format
href=/answers/attachments/1234567890
where 1234567890 is the legacyid of the attachment. Embedded attachments should usesrc=
instead ofhref=
. - Document owned attachments (that is, documents not shared) should have the file name prefixed with a unique string used as the legacyid for attachments followed by an underscore and the file name.
<legacyId>_<filename>
Example:1234567890_Logo.jpg
Related topics
Knowledge Management migration
General considerations for importing documents