Query

Property

Description

Name of generic query

Name displayed in the generic query (Query builder) form of the WebOffice client.

Example 'My airports generic query' for Name of generic query

Example 'My airports generic query' for Name of generic query - WebOffice html client

Default query

Default query used for this Layer. The Default query property is used if the Layer is activated (set to active/selected).

Query builder enabled?

Specifies whether generic query (Query builder) functionality is available or not. See figure above for details. The Query builder form gets displayed if the user presses the right mouse button with the mouse pointer over the Predefined Query in the Query form.

Query builder button in compact search form layout

For configuration of the query builder see chapter Options.

Note: Query builder queries may be even more powerful than queries defined in the project configuration. You may specify brackets as well as the operators "is NULL" and "is not NULL" to review the consistency of your data.

Note: By default with the query builder it is possible to search in the current map extent only. If you want to provide this function for predefined queries as well, see chapter Predefined Queries.

Access control ID:

Access control ID needed for access control based on usermanagment module.

If an ID is configured here (eg 'QUERYBUILDER_OWNER') and WebOffice usermanagement module is used then the user role is checked whether it provides the necessary application right or not (according to the example the application right would be 'QUERYBUILDER_OWNER'). If the necessary application right is not available then the query builder will not be available in WebOffice for the correspodning layer/table.

Default search result

Default Search result used for displaying results of search requests submitted by the user in the Query builder form.

Search category (query builder)

Display group if Query builder is enabled.

Max hits

Specifies the maximum count of hits shown in the Search result. If the search request exceeds the configured Max hits count then the search request is canceled. A notification is shown to the user.

Create index for global full-text search

Specifies whether this search configuration shall be considered

for the creation of the global full-text search index. See chapter Configure a Full-Text Search for details.

Note: Full-text search is currently available for Layers, but not for Tables.

Result weighting (FTS)

Defines the weighting of features of this layer, when they appear as results of a full-text search. For each found result of a full-text search, a result-score that indicates how well the results corresponds to the search text is calculated by Solr. In the suggestions, results with a high result-score appear on the top. The result-score of a feature is multiplied with the weighting factor that can be defined here.

For weighting, only values > 0.0 are allowed, values > 10.0 are not recommended. The default value is 1.0 (no weighting). A weighting between 0.0 and 1.0 lowers the result-score of features of this layer. A weighting > 1.0 increases the result-score of features of this layer. Examples of meaningful values are 0.5, 1.0, 2.5 or 5.0.

Note: After changing the result weighting, the corresponding full-text search subindices must be recalculated.

Note: Full-text search is currently available for Layers, but not for Tables.

External Layer ID

The specified External Layer ID is used to provide a unique identifier (to be used as values for parameters LayerID or query) for external search requests on this Layer. See chapter WebOffice URL call interface for details.

Check consistency?

Specifies whether to check the count of passed object keys with the count of found object keys when using external parametrized calls to WebOffice (URL Call Interface). If the two counts are not conform, the passed but not found object keys will be listed in a notification in the client.

Notification in the client if consistency is checked

Search values in cache?

Could the lists of possible values be cached? If 'false', then search form value lists are to be built for each user session. If 'true', then WebOffice can cache the values of search fields, that do not depend on user values (not in any hierarchie)