Page History
...
- In case you are upgrading to version 9.7 or higher and want to benefit from the full text search the aggregates that you already have stored in database must be indexed.
- In case that all your aggregates already are indexed and a new version of the model is published to production wit new business logic, you want to re-index all aggregates so that changed derived values can be found during the search.
This article describes a strategy that allows you to manually index aggregates.
As it is important that also system set attributes are indexed, this cannot be a database operation, and a filled runtime profile is needed. We have created a special service that allows you to just index aggregates without updating them in the database. The first step is to create the service definition in studio, and then call it in an appropriate flow. This service is useful for aggregates for which versioning is used. The new service marks the aggregate as changed, without actually creating a new version. You could use
| UI Text Box | ||
|---|---|---|
| ||
This service is not a standard service, and it is not part of the AquimaLibrary. You have to ask for the code at support@blueriq.com and add the definition to the globals manually. |
...
Overview
Content Tools