Search button enabled without filling all required location fields (Country, Province, and District) in Advanced Search

[taohidkhan22]

NB: The issue also exists for the death advanced search.

Bug description:

In the Advanced Search section, the Location of Birth field group consists of three dependent fields — Country, Province, and District. These fields are grouped together and should collectively be treated as a single required field group for enabling the Search button.

However, the system currently enables the Search button even when only Place of Birth and Country are filled in, without selecting Province and District.

Steps to reproduce:

1. Log in as Hospital Clerk/ reg/ RO
2. Navigate to the Birth advanced search
3. Select the place of delivery
4. Select country
5. Observe the search button

Actual result:

• The Search button becomes enabled after entering Place of Birth and Country only, even though Province and District are not selected.

Expected result:

• The Search button should remain disabled until all three fields (Country, Province, and District) under Location of Birth are filled in. Only when all required fields are completed should the Search button become active.

Screenshot/Recording:

• Screenshot 1

• Screenshot 2

• Videos:

Search.button.faulty.mp4

Tested on:
https://register.v19-beta-prod.opencrvs.dev/

[euanmillar]

We shouldnt hardcode any validation to province or district as each country has a custom hierarchy. Does that need to be mentioned @taohidkhan22

[taohidkhan22]

Understood. However, in our Farajaland configuration, the Country, Province, and District fields are all mandatory in the form. So, we expect the same validation and dependency to apply in the advanced search options as well. But, if district and province are not Required fields in the advanced search, they shouldn't be shown as 'required'.
@euanmillar

[rikukissa]

For "required", the use case is a bit different in the form and in advanced search: in form we want to ensure user fills out all fields that are mandatory by law, in the search view it's more about narrowing down search results as much as we can to limit visibility to records.

In that sense there should be enough flexibility to configure required differently for each use case.
I do agree with the bug report tho - if a field is set to required then it must be filled for the search button to be enabled