Add force_manual_search to request for case search validation #33905
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.
Support Ticket: USH-4011
Product Description
Help performance for vase search validation (has reached 10+ seconds on production)
Technical Summary
Suggested by Shubham, based on the problematic app: "This is because the default_search is set to true for the module (Skip to ES search results) and even though Web Apps passes execute as false , FP perform ES search for modules with default_search set. To override the default_search Web Apps also need to pass the force_manual_search as true for requests where we don’t want to do the search. "
Feature Flag
Case Search
Safety Assurance
Safety story
This will be tested on staging to ensure it does not break workflow
Automated test coverage
Not too many in this area
QA Plan
I am not requesting QA
Rollback instructions
Labels & Review