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.
Words and Phrases
| 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. |
Using Boolean Operators
| 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
XML source document considerations for importing
The XML source documents processed by the KMImport utility must meet the following requirements:
- Root element must be <rKmDocument>.
- The source document may contain elements only at one level under the root element. Elements containing child elements cause the import to fail.
- Source documents must contain a <Title> element.
- Source documents must contain a valid <DocType> element. Valid means the DocType value must match an existing DocType (name field) in Service Manager.
- Source documents must contain a <Categories> element with a semicolon delimited string of published (approved) categories. Categories to publish to are specified using XPATH format. For example a document to be published to the "Incident Management" subcategory of the "Service Manager" category
would appear as follows:
<Categories> Service Manager/Incident Management</Categories>
Additional categories are appended and preceded by a semicolon;.<Categories> Service Manager/Incident Management ;anothercategory;</Categories> - Elements with data containing HTML markup or any special characters that are illegal in XML should be CDATA wrapped to prevent the XML parser from throwing an exception.
- XML source documents that contain meta data for an "external" DocType must also contain a <ExternalDocumentName> element that contains the file name of the external document used as the document body. This file must reside in the same directory as the XML file that references it.
- When using the
kmimportutility to reimport an external document, the external document name must remain the same as the original. Also, any attachments must keep the same name. -
If you have tailored the kmdocument dbdict, be sure to not include your tailored Array fields, Structure fields, and Arrayed Structures fields in the source XML documents; otherwise the import will fail.
Related topics
