Page Comparison

indexsuffix

No

““

Suffix of all Hawksearch indexes

shouldprintignoredfields

No

false

If enabled, it will print the fields which have no correspondent in the Hawksearch engine, but were attempted to be indexed anyway. These ignored fields can be seen in the scheduled job’s message and logs

indexingenvironment

Yes

““

API Endpoint for Indexing

(provided by Hawksearch)

searchenvironment

Yes

““

API Endpoint for Searching

(provided by Hawksearch)

dashboardenvironment

Yes

““

Location of the dashboard

(provided by Hawksearch)

trackingenvironment

No

““

API Endpoint for Event Tracking

(provided by Hawksearch)

recommendationsenvironment

No

““

API Endpoint for Recommendations

(provided by Hawksearch)

contentreadpagesize

No

600

Minimum value: 1
The number of items from the IndexingQueue table being read/processed at once

itemindexingapilimit

No

125

Minimum value: 1

Maximum value: 125

Hawksearch upper limit when indexing items

hierarchyindexingapilimit

No

125

Minimum value: 1

Maximum value: 125

Hawksearch upper limit when indexing hierarchies

ignoretracking

No

false

X-HawkSearch-IgnoreTracking
Header value for search requests

variantindexingstrategy

No

“VariantAttributesRollUp“

Available values:

• “VariantAttributesRollUp“

• “SeparateDocuments“

• “VariantAsChildOfParent“

Determines the indexing strategy for product-variant relationships

eventedindexingenabled

No

true

If enabled, it will add any (specified) change to content (both CMS and Commerce) in the IndexingQueue table in order to be processed later by the Incremental Indexing Job. Note that incremental (delta) indexing will not be available if this is set to “false”.

enablepriceindexing

No

false

If enabled, it will index the prices for entries that support pricing (such as variants or packages).

For Variant as Separate Document indexing strategy, both variants and packages have their prices indexed out of the box.
For other strategies, only packages will have their prices indexed out of the box. To index variant prices in these strategies, custom code must be written to extend the indexing pipeline. Check How to Extend Handlers and How To Extend Pipes.

It will also add event handlers to register changes for prices in the IndexingQueue table

enableinventoryindexing

No

false

If enabled, it will index the inventories for entries that have inventories (such as variants or packages).
For Variant as Separate Document indexing strategy, both variants and packages have their inventories indexed out of the box.
For other strategies, only packages will have their inventories indexed out of the box. To index variant inventories in these strategies, custom code must be written to extend the indexing pipeline. Check How to Extend Handlers and How To Extend Pipes.
It will also add event handlers to register changes for inventories in the IndexingQueue table

hidefindadminscreens

No

false

If enabled, it will hide the “Search & Navigation” menu item from the global menu. This menu item is visible if Optimizely Find (former EpiFind) is installed in the project

dbconnectionstringname

No

“EPiServerDB“

The target database where the IndexingQueue table will be created. The table contains changes for content later picked up by the Incremental Indexing Job. If nothing is specified, the default CMS database will host this table