If you use Creatio cloud, you will always have the latest version of the global search service.
If you use Creatio on-site, run the following console command:
This will open the list of all containers. The global search version number will be available in the image column.
For global search version 2.0 and later:
Execute the PUT request in this format:
For global search versions earlier than 2.0:
Open gs-mysql container via the following command:
docker exec -it gs-mysql bash
Run the following command in the opened gs-mysql container:
mysql -p1665017 use gs; UPDATE GlobalSearchIndexingEntity SET LastIndexedOn = NULL, InProcess = 0;
By default, the service logs only errors. To enable logging of all events, locate the following string in the docker-compose.yaml file:
Replace the string with the following string:
Execute the following request:
Where GS-WEB-API is the server address, and SITE_NAME is your Creatio website name.
You can restrict access to ElasticSearch using Haproxy, which supports base64 authentification. Use the x-pack plugin to set up access to ElasticSearch via a login and a password.
How do I add a new object to the ElasticSearch indexing, or change the settings for the indexed fields of existing objects?
You can enable and configure indexing of specific sections using Creatio in-app tools. By default, ElasticSearch will index only sections, regardless of their author, as well as lookup columns (with a few exceptions). The attached *.pdf file contains the list of exceptions.
This information is available in the Elastic service documentation.
Check if the “Deduplication service api address” (“DeduplicationWebApiUrl” code) system setting is populated and whether the following features are enabled in “FeatureToggle:”
Learn more about how to enable additional functionality in the following developer documentation article: Feature toggle. Mechanism of enabling and disabling functions.
Can I use the global search and bulk duplicate search services in two Creatio applications simultaneously?
If you are using two Creatio applications, for example, production and developer environments, you can set up the global search and bulk duplicate search services for each of them independently. Use the following guides to set up the services:
The display order of the search results mainly depends on their relevance. The following factors affect relevance:
- The volume of text in the document.
- The frequency of the the search query in the document.
- The frequency of the search query in the index.
- Other, less important, parameters.
The following system settings affect the display order of search results as well:
- “Global search default entity weight” (“GlobalSearchDefaultEntityWeight” code) – increases the display priority of section records where the search was performed. For example, if you enter a search query from the Contacts section, the records of this section will appear first in the list.
- “Global search default primary column weight” (“GlobalSearchDefaultPrimaryColumnWeight” code) – increases the display priority of specific search results. It applies to records whose primary column value matches the search query. For example, Full name is a primary column for the contact and Name is a primary column for the account. If the search query matches the value in the record's primary column, this record will be displayed at the top of the search results.
While these system settings affect relevance, they do not guarantee the exact display order of search results as the other factors affect the order as well.
Since you must deploy the global search and deduplication service using Docker, microservices do not support Windows authentication.