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.
Step-by-step guide to add the service
- In Studio add a custom service named AQ_Aggregate_Index_Migrate
- The service definition looks like this:
- The aggregateId is always required.
The aggregate version is optional. In case this is not specified, the latest version of an aggregate will be indexed.
We need a service that is able to update an aggregate. This service has following parameters:
Parameter Direction Value Data Type Description Fill AggregateType Input Module Element Aggregate Select the aggregate that you want to update. Required AggregateID Input Expression Integer Please provide the attribute containing the ID of the aggregate entry to index. Required AggregateVersion Input Expression Integer If a specific version of the aggregate needs to be updated. If not provided then the latest one is updated. StoreInstances Input Expression Entity Event Name Event Type Description AppException Cancel The service takes this exit if indexing failed for some reason.
The service you defined can be use in a flow like this:
- A project that wants to index the aggregates has to create an exposed migration flow.
- In this flow you first call the
AQ_AggregateRead
to load the existing aggregates into the profile. - The next step is to use the
AQ_Aggregate_Index_Migrate
service to add the aggregate index. - The flow must be exposed, and should be called for every aggregate Id in the database. It can be passed as a parameter in the URL, and retrieved from there with the
BB_SetRequestParameters
service.
Related articles appear here based on the labels you select. Click to edit the macro and add or change labels. Note: the article itself also appears as related article, this is a known limitation.
Unable to render {include} The included page could not be found.
Overview
Content Tools