chore: added "Non Data Contact" toggle behavior to Generalized Search [CHI-2933] #737
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is related to techmatters/flex-plugins#2512
Description
This PR adds support for it's UI counterpart, to add "Non Data Contact" toggle behavior to Generalized Search. To do so:
isDataContact
boolean property (ElasticSearch).rawJson.callType
.onlyDataContacts
is present in the query, we add a filter clause to match only contacts that haveisDataContact
field set to true.IMPORTANT‼️
This changes require a complete reindex of all the documents.
Checklist
Verification steps
true
.isDataContact
field.AFTER YOU MERGE
You are responsible for ensuring the above steps are completed. If you move a ticket into QA without advising what version to test, the QA team will assume the latest tag has the changes. If it does not, the following confusion is on you! :-P