EUREKA full-text search

With the EUREKA search, you can perform a full-text search across the entire database, including the content of all types of documents. The data is prepared by indexing all objects, for example at night with the “Update Eureka index” job (UPD_FUL_IDX).

For purposeful results, you can limit the query to selected objects, e.g., only service calls and FAQs.

Attention

Attention: A search with EUREKA can produce a large number of hits as it searches for the beginnings of words, which makes the search much faster than a general substring search, but usually returns more hits than expected.

Note: If you are searching for a substring (if you do not know how the term you are looking for was written in full), it may help to enter a % sign in front of the search term.

Document folders are not indexed and therefore cannot appear in search results.

Full text search with Elasticsearch

JustRelate CRM supports the intelligent Elasticsearch technology (Elasticsearch Inc.). Its algorithms significantly improve the performance of the EUREKA search. In particular, it also supports high availability for distributed architectures (cloud, clusters, nodes, etc.).

Thanks to downstream analysis and formatting, search strings can be sent to Elasticsearch as specified in the field (with a dot). This means, for example, that companies are found that have a dot in their company name, such as “S.I.S. Süd-Industrie-Anlagen Service GmbH”.

Elasticsearch is an open source search engine based on Lucene. It works with indexes consisting of JSON documents in NoSQL format. The search engine is very fast and ideal for searching large amounts of data (big data).

If you operate Elasticsearch in your distributed architecture, the CRM can be configured accordingly to manage and use the CRM indices in Elasticsearch. A tool for EUREKA index management is available, especially for administration in cluster operation, which also manages the indexes of an Elasticsearch configuration.

Notes about Elasticsearch for the administrator

  • JustRelate CRM integrates the technology for indexing. The Elasticsearch software must be purchased or hosted individually.
  • Information on setting up the Elasticsearch server and managing Eureka indexes can be found in the documentation "Eleasticsearch Setup" [D-20-227426].
  • The Elasticsearch server is started on the corporate network or a cloud, and then manages all search indexes as a central index management. Multiple indexes for multiple applications can be hosted simultaneously. Several applications can access the server in parallel, with both read and write operations. Compared to Lucene, Elasticsearch is very comfortable to use, flexibly adaptable, and low-maintenance. Indexes are synchronized automatically in an encapsulated environment.
  • Elasticsearch supports all important algorithms and patterns for evaluating umlauts, numbers, e-mail addresses, etc. and can be easily configured and extended in this respect.

Note: The variable PSA_FUL_IDX_PLN_FLD_CHR (search for numbers with special characters) is set to $NONE when using Elasticsearch in the CRM. There are better methods for this in Elasticsearch (pattern, tokenizing). If Elasticsearch is not used, this variable can be used as before for special serial and model numbers.

Pure EUREKA search for numbers with special characters, e.g. serial or model numbers

EUREKA can search for numbers with special characters (e.g. service objects by serial or model numbers), because not only strings are indexed.

Info

Admin: In the Unmodified fields tab of the Administration/Tools/Search and Find/EUREKA Search: Objects menu, you can specify per object the fields that should not be resolved during indexing.

In the variable PSA_FUL_IDX_PLN_FLD_CHR, you can specify which characters should be removed during indexing so that no resolving takes place. These characters are then also removed during searches so that the entry is found. By default, the period character is removed. Hyphens and underscores are valid parts of words already.

This change makes it possible in the JustRelate standard to search for serial or model numbers like A.123-456. The procedure is also suitable if CRM number fields are supplied from ERP or other systems via interfaces.