Allow conditional logic to make a mandatory fields optional

[jpye-finch]

Description

Often not all the details about someone are known but not all. This causes issues as a field can only by mandatory or optional.

There are some use cases where a mandatory field will need to be optional.

For example. We don't fully support the registration of an unknown deceased. As we have mandatory fields. The purpose of the registration is to record the event. The death. Not the identity of the deceased

This ticket is to allow conditional logic:

• Make any mandatory field optional
• Make an optional field mandatory

Example 1:
Add a checkbox on the deceased page. 'Deceased identity is unknown'

IF Deceased identity is unknown is true
THEN then all mandatory fields are optional on the Deceased details page

Example 2:
Foundling

If child is a foundling
THEN then all mandatory fields are optional on the Child's details page

ACs

GIVEN I select an option from a dropdown, of a checkbox
WHEN their is conditional logic on that field to make other fields optional
THEN The it changes

[euanmillar]

In form config this is possible, but the backend e.g search will throw an error. Use cases need defined clearly e.g. around John Doe death. We could use hidden fields to store default created temporary name and date of birth etc.

[rikukissa]

Echoing Euan and pasting some my thoughts here:

Making mandatory fields optional is very case-by-case. Effectively these cases require extensive testing first.

Best to:

• Only implement new core-level flexibility when we know requirements
• Use explicit selects or other inputs to state an unknown value "Deceased's details are unknown [ X ]"
• Use clear "JOHN DOE" type default values in hidden fields for required fields that want to be made empty

Quick exploration to some items

Deceased details

• Tested: making all deceased details optional and left them empty. Registration, view and printing seems to work ok. Patient object is created but with almost no information as expected.

Child's details

• Tested empty child section and got

Invalid person section found for given code: child-details

• Child section was completely left unwritten. Client did send

details:
  child: {identifier: []}

To think

• Long term – Is it better to use conditional hide / show for the full input or allow eval string in required?

[euanmillar]

@rikukissa wouldnt your gist here make this possible in configuration? opencrvs/opencrvs-farajaland@3ec801a.

@jpye-finch see: #7950

So I think we can close this