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 |
|
Subform
The Subform control displays a separate form containing data from a different table than the table associated with the main form. A Subform control allows any controls on the subordinate form to use the link record data to perform a virtual join.For example, a text control or table control on the subordinate form can display related data from another table. You determine what related data to display by creating a link record entry for the Subform control's Input field and specifying the related database field whose values you want to display in link record line entry.
Example Subform control on the open interaction form
Example Subform control Input value
Example link record line entry for the callback.contact field
The benefits of a Subform control are listed below.
- You can display related record data from any other source in the system.
- You can display related records that have one to many relationships. For example, from one input, the contact name, you can use a Subform control to display many related fields such as the contact's location, address, or telephone number.
- You can provide link record data to controls that do not normally have link records such as Text or Table controls.
- Any information on a Subform control is automatically read-only when it is part of a virtual join.
The costs of a Subform control are listed below.
- You must create a separate link line entry and a query for each Subform control.
- You must create and maintain a subordinate form for the linked controls.
- You cannot use the virtual join option if you want users to interact with the controls on the subordinate form. This typically requires using either global lists or hard-coded values for any Combo Box controls on the subordinate form.
Since Subform controls depend upon link queries, any inefficiencies in the underlying query will negatively affect your system performance. Following the best practices in How do I write a good query? will reduce this performance impact. In addition, you must be very familiar with the Service Manager data model to create the necessary queries.
In general, a Subform control is best used in the following circumstances.
- You need to display data from a different table than the one associated with the main form
- You want the related information to be displayed in read only controls
If you want users to be able to select or interact with the related data, either use a Comfill control or do not enable the Virtual Join option for the Subform control. See Comfill for a description of Comfill costs and benefits.
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: