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 |
|
HTML Editor
The HTML Editor control allows users to type in and format multiple lines of text for display in an HTML Viewer control. Unlike other text input controls, if you do not want users to change the HTML text, you must display it in an HTML Viewer control.
The benefits of an HTML Editor control are listed below.
- Users can format multiple lines of text for display with the built-in editing tools or with HTML tags.
- Users can spell check the text.
- RDBMS tools can typically query HTML Editor control fields as long as you map the HTML Editor's input field to a multi-row array table. See Multi-row array table.
- Third-party reporting tools can typically read HTML Editor control fields as long as you map the HTML Editor's input field to a multi-row array table. See Multi-row array table.
- Users can update the text value at any time.
The costs of an HTML Editor are listed below.
- You must use a separate HTML Viewer control to display a read-only version of data you do not want users to change, such as an approved knowledge article.
- You must choose RDBMS mapping that has sufficient space for potentially large HTML input. Typically, an array mapping strategy is best for storing HTML Editor control data as there is no risk of data truncation when users type large amounts of text. See Array mapping options.
- The control uses the character encoding of the back-end RDBMS to determine how to store character data. If users type in text using a character encoding that your system does not support, the data will likely become corrupted.
- It is difficult to validate that users type in meaningful values into the control.
- You must use a separate HTML Viewer control to provide a read-only version of the text.
- The longer the width of the HTML Viewer control the more form space the control requires.
In general, an HTML Editor control is best used in the following circumstances.
- The user needs to type in and format multiple lines of text. For example, the text is a knowledge document.
- You want the option to spell check the text.
If you do not want users to format the text, use either a Text or Text Area control instead. Likewise, if you need to display the value of another text field in the system, use either a Text or Text Area control.
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to ovdoc-ITSM@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: