The first time a user performs a search, the add-on indexes configured tables. The add-on updates the index each time a record is inserted, updated, or deleted. The following describes additional details on how the add-on handles indexing:
If the process runs out of memory, the JVM can remove indexed data. The next search performed triggers the indexing process.
When a user updates a record, indexed data is updated if a field configured for search is modified.
If searched fields contain a foreign key field and this field doesn't have a programmatic label rule, a cache will be built for the target table—the table the FK points to. The following also applies:
If a record in the target table updates a field that participates in defining the record's label, the cache will be updated.
If a record in target table is deleted, the cache will be updated.
If the table being searched and the target table are in the same dataspace, the update process will be performed real-time. If those tables are in different dataspaces, the update process will be performed at the next search.