People choose searchable fields and then find the records those fields describe. The examples connect provisioning, indexing, repair and dialog behavior while leaving provider publication limits visible.
First lookup creates work that settings inspection can explain. The combined example checks the dependent outcome after another capability changes its source or authority. The lifecycle and regression examples revisit retained state after a later change rather than repeating individual rule rows.
A record type is unprovisioned and an administrator can read settings.
Steps
Read defaults, request lookup access twice and inspect the type’s target and owed work.
Expected
Default inspection writes nothing; first lookup provisions the type and repeated lookup does not create another configuration version.
Data
Use an isolated workspace, named fixture records and the caller grants described by the prerequisites.
Source
services-platform:modules/quick-search/tests/e2e/quick-search-access.e2e.spec.js#provisioned the record type the tenant had never searched,services-platform:modules/quick-search/tests/e2e/quick-search-configurations.e2e.spec.js#answers version 0, which is the version no tenant ever wrote,services-platform:modules/quick-search/tests/e2e/quick-search-configurations.e2e.spec.js#moves the index target to the generation and version the indexer must write
03Field retirement remains visible while repair convergeslifecycleproposed
A custom field is configured and a contact is indexed with its value.
Steps
Archive the field, inspect degraded settings, let repair rebuild and repeat a lookup using current credentials.
Expected
Settings retain the unavailable field for explanation, repair owes the replacement and eventual lookup no longer relies on the retired field.
Data
Use an isolated workspace, named fixture records and the caller grants described by the prerequisites.
Source
services-platform:modules/quick-search/tests/e2e/quick-search-configurations.e2e.spec.js#answers the archived field in place, as unavailable with the reason a screen shows,services-platform:modules/quick-search/tests/integration/services/maintenance/resubmit-targets.integration.spec.js#submits nothing on a second pass in the same hour,services-platform:modules/quick-search/tests/integration/services/indexing/discoverable-attribute.integration.spec.js#says a record of each status the rule does not offer is not discoverable
04Configuration powers do not substitute for lookup powerspermissionnegativeproposed
The dialog has visible results and its index remains readable during a delayed request.
Steps
Type a new term, change inactive inclusion and complete two search responses in reverse order.
Expected
The latest term and filter determine displayed results; retained results remain during loading and another workspace’s indexing failure does not widen access.
Data
Use an isolated workspace, named fixture records and the caller grants described by the prerequisites.
Source
react-console:lib/quick-search/__tests__/controller.test.ts#searches once for a word typed in one go,services-platform:modules/quick-search/tests/integration/services/indexing/handle-change-events.integration.spec.js#fails every event of the tenant whose write was refused, so CRM redelivers exactly those