Update Person when case outcome date of death is changed

[SORMAS-JanBoehme]

Problem Description

See Epic #13208

Proposed Change

See Epic #13208

Added Value/Benefit

See Epic #13208

Acceptance Criteria

• Popup behaves as described in "implementation details"

Implementation Details

When a user is changing the "Date of outcome" of a case while "Outcome of Case" is "Deceased", a popup appears that shows the consequences of their actions. See Mockup for information about how the popup looks and the shown text (new localization IDs need to be added if required, otherwise reuse the current localization IDs where possible)

Placeholders are marked with Curly Brackets:

Firstname = Person.firstname of the person attached to this case
LASTNAME = Person.lastname of the person attached to this case as uppercase
UUID of Person = person.uuid of the person attached to this case
DiseaseOfCaseToBechanged = The string value of case.disease of the case that the user wants to change

Behaviour:
Date of Death:
Date field where the user can (but does not have to) select a date. This date must be either today or in the past. If the user selects a date in the future, the field is marked in red with an error message (same behaviour as for the field CaseData.outcomeDate) and the popup can not be saved. The field is prefilled with the value selected by the user when the popup has been triggered.

Click on "Discard":

• No changes are made to either the case or the person.
• The value of "Date of outcome" in the UI is reset to the value that it had before changing it and triggering the popup
• The pop up closes

Click on "Save":

• Values of person are updated in the database according to the shown data
• Value of "Date of outcome" of the case is updated in the database according to the selected date in the popup
• the pop up closes

Additional information:
The described behaviour means that data of the person will be updated even if it already is set to "Dead". While this may seem redundant, it is by design to avoid having to perform multiple checks before if the data already matches, etc. and as a failsafe in case the data of the person does not match the expected values.

Mockups

Additional Information

No response

[SORMAS-JanBoehme]

Consolidated this issue with #13209 to make the process more streamlined and user friendly.