|
Siebel Search Administration Guide > Configuring Siebel Search Using Siebel Tools > Siebel Tools Search Object Reference >
Table 10. Properties of the Search Result Field Object
|
|
|
|
Column |
Required |
The name of the physical column in the search index that varies with the vendor of your database software. |
These columns may contain a column name or a function. |
Create Column Flag |
Optional |
A flag that denotes which columns will be actually created in the Search Table. |
Some fields defined are system columns that need not be explicitly created. They are automatically created by the search engine. |
Data Type |
Optional |
Specifies the data type of the column. Valid values are Varchar, Char, and ApVarchar. |
Required only for fields that are flagged TRUE in the Create column. |
Index Mode |
Optional |
Specifies the index mode of the column. Valid values are literal, none, and normal. |
The index mode specifies the type of indexing that is applied to the values. |
Name |
Required |
The logical name of the field. |
|
Text Length |
Optional |
The amount of storage, in bytes, allocated to a field. |
|
Type |
Required |
A picklist with valid values displayed. |
Attribute Type can take the following values: System, Data (Public), Data (Private). None of the predefined fields can be deleted. Additionally, Data (private) fields cannot be customized. |
The Search Index Object
A default set of search indices are set up at the time you install the Siebel application. If you want to create additional indices, the rules, assumptions, and properties of the search index object are listed below. The Search Index object is a logical name for a group of search engine specific entities. For example, the Search Index for Hummingbird will be a Hummingbird index table. Thus, the search index, Solution will map to an index table called FUL_SOLN. Rules and Assumptions of the Search Index Object
- It is a good practice to index only master data (also called referential data), and not transactional data, because transactional data changes very often, and your index may not reflect the current data.
- Search engines are most powerful when used to search for text and keywords in voluminous documents and attachments in the database. The perfect candidates for Search are Literature, Solution, Product, FAQ, and Resolution documents. Your Siebel application includes preconfigured search indices, such as Product Literature, SmartScripts, Service Requests, and so on.
- Search supports Access Control and Organization visibility rules. The business component that you plan to index should support one of these visibility rules. It is also acceptable to index business components that have no visibility rules enforced. In such cases, all business component records will be visible to all users. For more information, see About Visibility Control Enforcement.
Search Index Object Properties
Table 11 lists the properties for the Search Index object.
Table 11. Search Index Object Properties
|
|
|
Name |
Required |
Logical name for the search index. |
Index BusComp |
Optional |
Business Component that the index maps to. This field can be null if it is based on an external directory. |
DB Table |
Optional |
Flag indicates if the object maps to a database table or not. If the search index is based on an external file system, this field should not be checked. In its default state, this flag is checked. |
|
