BAH-3479 | Backend changes for dateless appointments #145

kavitha-sundararajan · 2024-01-19T14:01:04Z

…ges for priority (#104) * add database column and api changes for priority Co-authored-by: Umair Fayaz <[email protected]> * add priority to appointment audit Co-authored-by: Umair Fayaz <[email protected]> * fixed test failure for priority * add tests for code coverage --------- Co-authored-by: Umair Fayaz <[email protected]>

…ests (#106) * removed invalid priority and related tests * added testcase for invalid priority

…ges for priority (#104) * add database column and api changes for priority * add priority to appointment audit * fixed test failure for priority * add tests for code coverage --------- Co-authored-by: Umair Fayaz <[email protected]>

…ests (#106) * removed invalid priority and related tests * added testcase for invalid priority

gsluthra · 2024-01-25T04:48:04Z

As @angshu had mentioned yesterday, please ensure that an appointment should show in "Waitlist" based on status and not based on whether a date is set/no step. Can you verify code for this, and maybe add a test to ensure that even if a data is set on an appointment, it shows in waitlist if its status is waitlist.

gsluthra · 2024-02-26T06:16:27Z

api/src/test/java/org/openmrs/module/appointments/dao/impl/AppointmentDaoImplIT.java

@@ -243,27 +239,13 @@ public void shouldReturnAppointmentsForProvider() {
        assertEquals(1, appointments.size());
    }

-    @Test
-    public void shouldReturnAppointmentsForPatientBetweenGivenDatesForASpecificStatus() throws ParseException {


Why is this test removed?

Apologies, since it has been added later, it was removed while cherry picking by mistake. Added it back

api/src/test/java/org/openmrs/module/appointments/dao/impl/AppointmentDaoImplIT.java

omod/src/main/java/org/openmrs/module/appointments/web/contract/AppointmentRequest.java

omod/src/main/java/org/openmrs/module/appointments/web/contract/AppointmentDefaultResponse.java

gsluthra · 2024-02-26T06:21:41Z

omod/src/test/java/org/openmrs/module/appointments/web/mapper/AppointmentMapperTest.java

+    @Test
+    public void shouldMapExistingAppointmentWhenPayloadHasAppointmentPriority() throws ParseException {
+        AppointmentRequest appointmentRequest = createAppointmentRequest();
+        appointmentRequest.setPriority("Routine");


Why are getters/setters for Appointment Priority using String, instead of Enum?

Since we referred appointment status, we followed the same for priority as well

See comments above

gsluthra · 2024-02-26T06:30:20Z

api/src/main/resources/liquibase.xml

+        </preConditions>
+        <comment>Update start and end date time of patient appointment table to be nullable</comment>
+        <sql>
+            ALTER TABLE patient_appointment MODIFY start_date_time datetime;


I think its better to be explicit about default as null using DEFAULT NULL.

https://fedingo.com/how-to-modify-mysql-column-to-allow-null/

default value is set to NULL now

gsluthra · 2024-02-26T06:45:18Z

What is the default priority assumed, if no priority is set (for backward compatibility)? Where is that code? I am guessing default is "routine" priority. thanks!

kavitha-sundararajan · 2024-02-26T06:58:01Z

What is the default priority assumed, if no priority is set (for backward compatibility)? Where is that code? I am guessing default is "routine" priority. thanks!

Currently, default is not set, because showing it in the UI itself is behind a toggle. https://github.com/Bahmni/openmrs-module-appointments/pull/145/files#diff-0c4429900b456f54d785391170847fccd1f3e8f0fcb322d5ee296670318c2affR111
It'll be NULL only if we didn't pass any priority.

angshu · 2024-02-26T06:36:27Z

api/src/main/java/org/openmrs/module/appointments/dao/impl/AppointmentDaoImpl.java

+        if (appointmentSearchRequest.getStartDate() != null) {
+            criteria.addOrder(Order.asc("startDateTime"));
+        } else {
+            criteria.addOrder(Order.asc("dateCreated"));


is there any reason to order by date created. An appt maybe created well ahead in advance for later dated appointments. If this is done for for waitlisted appointment, then this can be combined with the status - e.g. if status = waitlist, order by dateCreated if not specifically asked for "startDateTime"

refactored to combine both criteria

I am little confused. We seem to be ordering by startdate (ascending) if its part of the search parameter. I can still want to search by status but order by startdate, no? If you want to sort based on request, then the request must send it as sort parameter, not search parameter

yeah I agree. reverted it back to the existing way since that'll still sort the appointments irrespective of status

angshu · 2024-02-26T06:37:07Z

api/src/main/java/org/openmrs/module/appointments/dao/impl/AppointmentDaoImpl.java

        setDateCriteria(appointmentSearchRequest, criteria);
        setPatientCriteria(appointmentSearchRequest, criteria);
        setLimitCriteria(appointmentSearchRequest, criteria);
        setProviderCriteria(appointmentSearchRequest, criteria);
        setStatusCriteria(appointmentSearchRequest, criteria);

+        String limit = Context.getAdministrationService().getGlobalProperty("webservices.rest.maxResultsDefault");


You don't make a service call from Dao. if you need it, pass it from the service. Not here!

moved it to service method

api/src/main/java/org/openmrs/module/appointments/model/AppointmentPriority.java

angshu · 2024-02-26T06:52:01Z

omod/src/main/java/org/openmrs/module/appointments/web/contract/AppointmentQuery.java

@@ -12,6 +12,7 @@ public class AppointmentQuery {
    private String patientUuid;
    private String status;
    private String appointmentKind;
+    private Boolean isDatelessAppointments = false;


am assuming this comes from frontend API call. Why should we call the parameter as "isDateLessAppointments"? if your intent is to search by waitlisted appointment, then "status" should be enough. or if you really want to search appointments without dates - atleast call the parameter as "withoutDates" or "unassingedDates". Javabeans properties for booleans do not require fields to be prefixed with "Is" - boolean fields getter can be "IsWithoutDates" or "hasUnassignedDates". An appointment is not a valid one without dates - so "isDateLessAppointments" do not make sense

renamed to withoutDates

"isDatelessAppointments" attribute still exists. Have you refactored the code to search by status instead of relying on "datelessAppointment" as part of search?

api/src/main/java/org/openmrs/module/appointments/dao/impl/AppointmentDaoImpl.java

omod/src/main/java/org/openmrs/module/appointments/web/contract/AppointmentRequest.java

angshu · 2024-02-26T07:01:30Z

omod/src/main/java/org/openmrs/module/appointments/web/controller/AppointmentController.java

@@ -60,6 +60,10 @@ public List<AppointmentDefaultResponse> getAllAppointments(@RequestParam(value =
    @RequestMapping( method = RequestMethod.POST, value = "search")
    @ResponseBody
    public List<AppointmentDefaultResponse> searchAppointments( @Valid @RequestBody AppointmentQuery searchQuery) throws IOException {
+        if(searchQuery.getIsDatelessAppointments()) {


Also you are expecting a searchquery but fetching only date-less appointment?
Does it mean

if appointment without dates, rest of criteria do not apply? That does not seem right. I can look for an appointment with a certain priority or service for which dates have not been assinged yet - right?

please don't call service method as "searchDatelessAppointment". Call it "appointmentWithoutDatesAssigned" or something that makes more sense. DatelessAppt seems very much a technical internal thing.

renamed getter as isWithoutDates() , service method as searchAppointmentsWithoutDates() and dao method as getAppointmentsWithoutDates()

same question above is relevant here as well. Why not leverage status if you are looking for "waitlisted" appointments? Unless you want to return all appointments without dates?

angshu · 2024-02-26T07:01:56Z

omod/src/test/java/org/openmrs/module/appointments/web/mapper/AppointmentMapperTest.java

+    @Test
+    public void shouldMapExistingAppointmentWhenPayloadHasAppointmentPriority() throws ParseException {
+        AppointmentRequest appointmentRequest = createAppointmentRequest();
+        appointmentRequest.setPriority("Routine");


See comments above

gsluthra · 2024-02-26T07:34:53Z

What is the default priority assumed, if no priority is set (for backward compatibility)? Where is that code? I am guessing default is "routine" priority. thanks!

Currently, default is not set, because showing it in the UI itself is behind a toggle. https://github.com/Bahmni/openmrs-module-appointments/pull/145/files#diff-0c4429900b456f54d785391170847fccd1f3e8f0fcb322d5ee296670318c2affR111 It'll be NULL only if we didn't pass any priority.

I am trying to determine, if an existing adopter of Bahmni, that already has appointments in their database, uses this new module, with wait-list enabled, how will previously created appointments show up (if they have null in priority). Is that something we need to worry, or the new feature/UI will work fine, if it has older created appointments (for future dates)?

kavitha-sundararajan · 2024-02-27T08:07:26Z

What is the default priority assumed, if no priority is set (for backward compatibility)? Where is that code? I am guessing default is "routine" priority. thanks!

Currently, default is not set, because showing it in the UI itself is behind a toggle. https://github.com/Bahmni/openmrs-module-appointments/pull/145/files#diff-0c4429900b456f54d785391170847fccd1f3e8f0fcb322d5ee296670318c2affR111 It'll be NULL only if we didn't pass any priority.

I am trying to determine, if an existing adopter of Bahmni, that already has appointments in their database, uses this new module, with wait-list enabled, how will previously created appointments show up (if they have null in priority). Is that something we need to worry, or the new feature/UI will work fine, if it has older created appointments (for future dates)?

Yeah right, the new UI will work fine for the older appointments irrespective of priority. If they want to add priority for older appointments, they can edit the appointment and capture it from the dropdown

angshu · 2024-02-29T05:27:17Z

api/src/main/java/org/openmrs/module/appointments/dao/impl/AppointmentDaoImpl.java

+        if (appointmentSearchRequest.getStartDate() != null) {
+            criteria.addOrder(Order.asc("startDateTime"));
+        } else {
+            criteria.addOrder(Order.asc("dateCreated"));


I am little confused. We seem to be ordering by startdate (ascending) if its part of the search parameter. I can still want to search by status but order by startdate, no? If you want to sort based on request, then the request must send it as sort parameter, not search parameter

angshu · 2024-02-29T05:34:27Z

api/src/main/java/org/openmrs/module/appointments/helper/AppointmentServiceHelper.java

-        appointmentJson.put("endDateTime", appointment.getEndDateTime().toInstant().toString());
+        String startDate = (appointment.getStatus() == AppointmentStatus.WaitList && appointment.getStartDateTime() == null) ? null : appointment.getStartDateTime().toInstant().toString();
+        appointmentJson.put("startDateTime", startDate);
+        String endDate = (appointment.getStatus() == AppointmentStatus.WaitList && appointment.getStartDateTime() == null) ? null : appointment.getEndDateTime().toInstant().toString();


this will negate one of the criterias that a waitlisted appointment can have a date. This assumes that waitlist status appointment can not have a date. Why do we have to do this check against waitlist status. Why not simply just check if the dates are null, alternatively just get the time instant from the date?

I am assuming the method "getAppointmentAsJsonString" is used for audit purpose, and since it has the appointment object - you have all the info.

yeah, this method is used for audit purpose only. This will still allow waitlist appointments with dates by falling to the else part but there is no need of this check against waitlist. I'll remove the status check here

angshu · 2024-02-29T05:48:09Z

omod/src/main/java/org/openmrs/module/appointments/web/contract/AppointmentQuery.java

@@ -12,6 +12,7 @@ public class AppointmentQuery {
    private String patientUuid;
    private String status;
    private String appointmentKind;
+    private Boolean isDatelessAppointments = false;


"isDatelessAppointments" attribute still exists. Have you refactored the code to search by status instead of relying on "datelessAppointment" as part of search?

angshu · 2024-02-29T05:49:43Z

omod/src/main/java/org/openmrs/module/appointments/web/contract/AppointmentQuery.java

@@ -68,4 +69,12 @@ public String getServiceTypeUuid() {
    public void setServiceTypeUuid(String serviceTypeUuid) {
        this.serviceTypeUuid = serviceTypeUuid;
    }
+
+    public Boolean getIsDatelessAppointments() {


Why do we need this attribute "isDatelessAppointment"? if your idea is to search for waitlisted appointment - do it by "status" not this unnecessary attribute. Unless within a particular status, you also want to search the appointments without dates, which I believe is not your requirement.

this attribute was renamed to "withoutDates", not sure how it is showing "isDatelessAppointment". can we try refreshing the page once ?

angshu · 2024-02-29T05:51:43Z

omod/src/main/java/org/openmrs/module/appointments/web/controller/AppointmentController.java

@@ -60,6 +60,10 @@ public List<AppointmentDefaultResponse> getAllAppointments(@RequestParam(value =
    @RequestMapping( method = RequestMethod.POST, value = "search")
    @ResponseBody
    public List<AppointmentDefaultResponse> searchAppointments( @Valid @RequestBody AppointmentQuery searchQuery) throws IOException {
+        if(searchQuery.getIsDatelessAppointments()) {


same question above is relevant here as well. Why not leverage status if you are looking for "waitlisted" appointments? Unless you want to return all appointments without dates?

kavitha-sundararajan

Few comments to be implemented are being tracked in this card BAH-3637 and will be taken up later

* Kavitha, Umair | A-1204370983916597| add database column and api changes for priority (#104) * add database column and api changes for priority Co-authored-by: Umair Fayaz <[email protected]> * add priority to appointment audit Co-authored-by: Umair Fayaz <[email protected]> * fixed test failure for priority * add tests for code coverage --------- Co-authored-by: Umair Fayaz <[email protected]> * Kavitha | A-1204361352115416 | removed invalid priority and related tests (#106) * removed invalid priority and related tests * added testcase for invalid priority * Backend migration to create dateless appointments (#105) * allow dateless appointments if status is waitlist (#108) * Kavitha, Umair | A-1204370983916597| add database column and api changes for priority (#104) * add database column and api changes for priority * add priority to appointment audit * fixed test failure for priority * add tests for code coverage --------- Co-authored-by: Umair Fayaz <[email protected]> * Kavitha | A-1204361352115416 | removed invalid priority and related tests (#106) * removed invalid priority and related tests * added testcase for invalid priority * Backend migration to create dateless appointments (#105) * allow dateless appointments if status is waitlist (#108) * Add logic to filter DateLess Appointments * add. appointment creation date in response (#109) * Add tests to filter DateLess Appointments * Update POM files * Fix failing Tests for Search appointments * Kavitha | add date check and tests for waitlist appointments * Kavitha | removed Invalid priority * Kavitha | added missed tests from master branch * Kavitha | rename datelessAppointments to appointmentsWithoutDates * Kavitha | add default null value to date columns in appt * Kavitha | removed status check in appointment json * Kavitha | removed sorting based on status * Kavitha | removed unused imports --------- Co-authored-by: Umair Fayaz <[email protected]> Co-authored-by: Phanindra-tw <[email protected]> Co-authored-by: Arjun G <[email protected]>

* BAH-3479 | Backend changes for dateless appointments (#145) * Kavitha, Umair | A-1204370983916597| add database column and api changes for priority (#104) * add database column and api changes for priority Co-authored-by: Umair Fayaz <[email protected]> * add priority to appointment audit Co-authored-by: Umair Fayaz <[email protected]> * fixed test failure for priority * add tests for code coverage --------- Co-authored-by: Umair Fayaz <[email protected]> * Kavitha | A-1204361352115416 | removed invalid priority and related tests (#106) * removed invalid priority and related tests * added testcase for invalid priority * Backend migration to create dateless appointments (#105) * allow dateless appointments if status is waitlist (#108) * Kavitha, Umair | A-1204370983916597| add database column and api changes for priority (#104) * add database column and api changes for priority * add priority to appointment audit * fixed test failure for priority * add tests for code coverage --------- Co-authored-by: Umair Fayaz <[email protected]> * Kavitha | A-1204361352115416 | removed invalid priority and related tests (#106) * removed invalid priority and related tests * added testcase for invalid priority * Backend migration to create dateless appointments (#105) * allow dateless appointments if status is waitlist (#108) * Add logic to filter DateLess Appointments * add. appointment creation date in response (#109) * Add tests to filter DateLess Appointments * Update POM files * Fix failing Tests for Search appointments * Kavitha | add date check and tests for waitlist appointments * Kavitha | removed Invalid priority * Kavitha | added missed tests from master branch * Kavitha | rename datelessAppointments to appointmentsWithoutDates * Kavitha | add default null value to date columns in appt * Kavitha | removed status check in appointment json * Kavitha | removed sorting based on status * Kavitha | removed unused imports --------- Co-authored-by: Umair Fayaz <[email protected]> Co-authored-by: Phanindra-tw <[email protected]> Co-authored-by: Arjun G <[email protected]> * Kavitha | refactor search API for appointments without dates * Kavitha|lowered test coverage ratio * add specific imports --------- Co-authored-by: Umair Fayaz <[email protected]> Co-authored-by: Phanindra-tw <[email protected]> Co-authored-by: Arjun G <[email protected]>

* BAH-3350: Appointments: search endpoint stack traces when a patient has more than one identifier of the same time (#142) * Ability to Filter on Appointments with multi-value support for search keys Ability to Filter on Awaiting Appointments with multiple values for same keys * Added test cases to increase branch coverage & set threshold to 0.60 (#152) Added test cases to increase branch coverage & set threshold to 0.60 (#152) * Kavitha|Awaiting appointments code refactor (#151) * BAH-3479 | Backend changes for dateless appointments (#145) * Kavitha, Umair | A-1204370983916597| add database column and api changes for priority (#104) * add database column and api changes for priority Co-authored-by: Umair Fayaz <[email protected]> * add priority to appointment audit Co-authored-by: Umair Fayaz <[email protected]> * fixed test failure for priority * add tests for code coverage --------- Co-authored-by: Umair Fayaz <[email protected]> * Kavitha | A-1204361352115416 | removed invalid priority and related tests (#106) * removed invalid priority and related tests * added testcase for invalid priority * Backend migration to create dateless appointments (#105) * allow dateless appointments if status is waitlist (#108) * Kavitha, Umair | A-1204370983916597| add database column and api changes for priority (#104) * add database column and api changes for priority * add priority to appointment audit * fixed test failure for priority * add tests for code coverage --------- Co-authored-by: Umair Fayaz <[email protected]> * Kavitha | A-1204361352115416 | removed invalid priority and related tests (#106) * removed invalid priority and related tests * added testcase for invalid priority * Backend migration to create dateless appointments (#105) * allow dateless appointments if status is waitlist (#108) * Add logic to filter DateLess Appointments * add. appointment creation date in response (#109) * Add tests to filter DateLess Appointments * Update POM files * Fix failing Tests for Search appointments * Kavitha | add date check and tests for waitlist appointments * Kavitha | removed Invalid priority * Kavitha | added missed tests from master branch * Kavitha | rename datelessAppointments to appointmentsWithoutDates * Kavitha | add default null value to date columns in appt * Kavitha | removed status check in appointment json * Kavitha | removed sorting based on status * Kavitha | removed unused imports --------- Co-authored-by: Umair Fayaz <[email protected]> Co-authored-by: Phanindra-tw <[email protected]> Co-authored-by: Arjun G <[email protected]> * Kavitha | refactor search API for appointments without dates * Kavitha|lowered test coverage ratio * add specific imports --------- Co-authored-by: Umair Fayaz <[email protected]> Co-authored-by: Phanindra-tw <[email protected]> Co-authored-by: Arjun G <[email protected]> * BAH-3860 | repeated imports in tests * BAH-3860 | fix. tests in AppointmentMapper --------- Co-authored-by: Mark Goodrich <[email protected]> Co-authored-by: Umair Fayaz <[email protected]> Co-authored-by: kalai-tw <[email protected]> Co-authored-by: kavitha-sundararajan <[email protected]> Co-authored-by: Umair Fayaz <[email protected]> Co-authored-by: Phanindra-tw <[email protected]>

kavitha-sundararajan and others added 13 commits December 28, 2023 00:58

Kavitha | A-1204361352115416 | removed invalid priority and related t…

3beec8d

…ests (#106) * removed invalid priority and related tests * added testcase for invalid priority

Backend migration to create dateless appointments (#105)

c9d95cc

allow dateless appointments if status is waitlist (#108)

2576208

Kavitha | A-1204361352115416 | removed invalid priority and related t…

ba0193b

…ests (#106) * removed invalid priority and related tests * added testcase for invalid priority

Backend migration to create dateless appointments (#105)

1239ada

allow dateless appointments if status is waitlist (#108)

d464910

Add logic to filter DateLess Appointments

ae9cbbd

add. appointment creation date in response (#109)

d088a9a

Add tests to filter DateLess Appointments

ceadfce

Update POM files

f931918

Fix failing Tests for Search appointments

c121103

This was referenced Jan 24, 2024

BAH-3103 | Appointment Priority and Dateless Appointments #120

Closed

BAH-3010 | Ability to view awaiting appointment list #114

Closed

kavitha-sundararajan requested a review from a team January 25, 2024 04:28

Kavitha | add date check and tests for waitlist appointments

63f7c4e

kavitha-sundararajan force-pushed the BAH-3479 branch from 4e2d730 to 63f7c4e Compare February 26, 2024 05:59

gsluthra reviewed Feb 26, 2024

View reviewed changes

api/src/test/java/org/openmrs/module/appointments/dao/impl/AppointmentDaoImplIT.java Show resolved Hide resolved

gsluthra reviewed Feb 26, 2024

View reviewed changes

omod/src/main/java/org/openmrs/module/appointments/web/contract/AppointmentRequest.java Show resolved Hide resolved

gsluthra reviewed Feb 26, 2024

View reviewed changes

omod/src/main/java/org/openmrs/module/appointments/web/contract/AppointmentDefaultResponse.java Show resolved Hide resolved

gsluthra reviewed Feb 26, 2024

View reviewed changes

Kavitha | removed Invalid priority

4fad218

angshu requested changes Feb 26, 2024

View reviewed changes

kavitha-sundararajan added 3 commits February 26, 2024 13:19

Kavitha | added missed tests from master branch

02a7993

Kavitha | rename datelessAppointments to appointmentsWithoutDates

207916b

Kavitha | add default null value to date columns in appt

ff9dc4e

kavitha-sundararajan requested review from angshu and gsluthra February 27, 2024 13:29

angshu reviewed Feb 29, 2024

View reviewed changes

kavitha-sundararajan added 3 commits February 29, 2024 12:46

Kavitha | removed status check in appointment json

591b78b

Kavitha | removed sorting based on status

a9778b7

Kavitha | removed unused imports

41a0262

kavitha-sundararajan requested a review from angshu March 1, 2024 13:11

angshu approved these changes Mar 4, 2024

View reviewed changes

kavitha-sundararajan commented Mar 4, 2024

View reviewed changes

kavitha-sundararajan merged commit b98e7ea into master Mar 4, 2024
2 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

BAH-3479 | Backend changes for dateless appointments #145

BAH-3479 | Backend changes for dateless appointments #145

kavitha-sundararajan commented Jan 19, 2024

gsluthra commented Jan 25, 2024

gsluthra Feb 26, 2024

kavitha-sundararajan Feb 26, 2024

gsluthra Feb 26, 2024

kavitha-sundararajan Feb 26, 2024

angshu Feb 26, 2024

gsluthra Feb 26, 2024

kavitha-sundararajan Feb 27, 2024

gsluthra commented Feb 26, 2024

kavitha-sundararajan commented Feb 26, 2024

angshu Feb 26, 2024

kavitha-sundararajan Feb 27, 2024

angshu Feb 29, 2024

kavitha-sundararajan Mar 1, 2024

angshu Feb 26, 2024

kavitha-sundararajan Feb 27, 2024

angshu Feb 26, 2024

kavitha-sundararajan Feb 27, 2024

angshu Feb 29, 2024

angshu Feb 26, 2024

kavitha-sundararajan Feb 27, 2024

angshu Feb 29, 2024

angshu Feb 26, 2024

gsluthra commented Feb 26, 2024

kavitha-sundararajan commented Feb 27, 2024

angshu Feb 29, 2024

angshu Feb 29, 2024

kavitha-sundararajan Feb 29, 2024

angshu Feb 29, 2024

angshu Feb 29, 2024

kavitha-sundararajan Feb 29, 2024

angshu Feb 29, 2024

kavitha-sundararajan left a comment

BAH-3479 | Backend changes for dateless appointments #145

BAH-3479 | Backend changes for dateless appointments #145

Conversation

kavitha-sundararajan commented Jan 19, 2024

gsluthra commented Jan 25, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

gsluthra commented Feb 26, 2024

kavitha-sundararajan commented Feb 26, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

gsluthra commented Feb 26, 2024

kavitha-sundararajan commented Feb 27, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

kavitha-sundararajan left a comment

Choose a reason for hiding this comment