Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automate Case Details and Fields Preselection for Influenza Cases #13184 #13200

Merged
merged 4 commits into from
Dec 10, 2024
+10 −0
Merged

Automate Case Details and Fields Preselection for Influenza Cases #13184 #13200

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
d79fbfa
Automate Case Details and Fields Preselection for Influenza Cases #13184
Dec 3, 2024
4694a90
Merge branch 'development' into change-#13184-automate-case-details-a…
Dec 9, 2024
0bb1fc5
Automate Case Details and Fields Preselection for Influenza Cases #13…
Dec 10, 2024
206e1ea
Automate Case Details and Fields Preselection for Influenza Cases #13…
Dec 10, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion sormas-api/src/main/java/de/symeda/sormas/api/caze/CaseDataDto.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -638,7 +638,7 @@ public static CaseDataDto build(PersonReferenceDto person, Disease disease, Heal
caze.setPortHealthInfo(PortHealthInfoDto.build());
caze.setDisease(disease);
caze.setInvestigationStatus(InvestigationStatus.PENDING);
caze.setCaseClassification(CaseClassification.NOT_CLASSIFIED);
caze.setCaseClassification(CaseClassification.CONFIRMED);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the changes required in the ticket should be only for Influenza cases

caze.setOutcome(CaseOutcome.NO_OUTCOME);
caze.setCaseOrigin(CaseOrigin.IN_COUNTRY);
// TODO This is a workaround for transferring the followup comment while converting a contact to a case. This can be removed if the followup for cases is implemented in the mobile app
Expand Down
2 changes: 2 additions & 0 deletions sormas-ui/src/main/java/de/symeda/sormas/ui/caze/CaseCreateForm.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -282,6 +282,7 @@ protected void addFields() {
facilityOrHome.setId("facilityOrHome");
facilityOrHome.setWidth(100, Unit.PERCENTAGE);
CssStyles.style(facilityOrHome, ValoTheme.OPTIONGROUP_HORIZONTAL);
facilityOrHome.setValue(Sets.newHashSet(TypeOfPlace.HOME));
facilityTypeGroup = ComboBoxHelper.createComboBoxV7();
facilityTypeGroup.setId("typeGroup");
facilityTypeGroup.setCaption(I18nProperties.getCaption(Captions.Facility_typeGroup));
Expand Down Expand Up @@ -550,6 +551,7 @@ private void setNoneFacility() {
FacilityReferenceDto noFacilityRef = FacadeProvider.getFacilityFacade().getByUuid(FacilityDto.NONE_FACILITY_UUID).toReference();
facilityCombo.addItem(noFacilityRef);
facilityCombo.setValue(noFacilityRef);
facilityType.setRequired(false);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is this needed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Without this line, this field will be set as required for validation. It happens only from code change. And in this case, in Validation Form, even if Place of Stay is set to Home, app will ask us to introduce the Facility Type(as Required).

}

private void updateFacility() {
Expand Down
Loading