The purpose of this article is to explain the necessary steps to configure Full Text Search in your final application.
You have several properties to help you with this configuration:
At generator level, you have these properties you can configure to get Full Text Search in your application.
If the
Searchable property is set to TRUE, all the
Business Component of the
KB are made searchable. You can change this locally for certain Business Components (see Transaction defined as Business Component section below).
It specifies the search Engine to be used. This property is only displayed if the Searchable property is set to True.
It specifies the directory where the index files will be stored only if the Searchable property is set to True.
They are several properties available in a Transaction object that was defined as a Business Component to configure Full Text Search.
If it is set to True, it means that this Transaction will be searchable.
Sets a GeneXus object, which has to receive the key of the Transaction as a parameter. This property is only offered if the Searchable Transaction Property is set to True. See more information at: Search viewer property.
Note: In order to use Full Text Search functions for files, you don't need to set any property, just use the functions explained in the See Also section.
Full Text Search Data Types
Full Text Search Examples
Full Text Search Examples - Indexing