3.3.0 Release Candidate Bugs

Uncaught TypeError: (0 , i.getPatientChartStore) is not a function when launching patient chart

This is because one of the frontend modules that have the dependency `patient-common-lib` is not up to date. It's most likely the billing module.

We have removed the billing module in this PR.

It's weird that we made a new patch release since the PR was made, and the deploy build has happened but the changes are not reflected in test3.

Blocker

FIXED

Vero

Ward app visible

Same as row 1

Same as row 1

Blocker

FIXED BUT NOT DEPLOYED

Grace

O3-4488 - Getting issue details... STATUS

Lost the ability to scroll on a Tablet in test3, but it's fine in dev3

An issue with how the REST module handles http requests.
Ian’s aware and planning to work on a fix.

Blocker

NOT STARTED

Grace

The Billing Home App is unable to fetch data, resulting in a 404 error, and continuously making requests in an infinite loop in test3.

Same as row 2, its because the backend dependency kenyaemr is not present.

Same as row 1

Same as row 1

Blocker

FIXED

Praneeth

Some modules have unresolved backend dependencies. Check the Backend Modules tab in the Implementer Tools for more details after logging in

Because the billing module has a dependency which is “kenyaemr”

Same as above

Same as above

Blocker

FIXED

Vero

Appointment date (in the appointment module) appears distorted while using a tablet.

Blocker

NOT STARTED

Vero

Can’t see the translated form labels for the Adult Return visit form when my locale is set to French, for example

There was a module name that wasn't updated

Replace occurrences of form-engine-lib namespace in favor of form-engine-app to handle form translations

A new e2e test pending to cover this flow in the future - https://github.com/openmrs/openmrs-esm-patient-chart/pull/2266

Blocker

FIXED

by Pius

Dennis

Add config so new order types show: Imaging, Procedures.

the new order types can be added via Configuration. Currently, the refApp only supports 2 order types. Eg in Ozone: order types Imaging and Procedures are added via configuration

Nice-to-have; Not blocker

NOT STARTED

Grace

O3-4482 - Getting issue details... STATUS

Siderail buttons are out of order

This order is defined by the this configuration here. The Network calls how that the config is not being fetched by the server, and hence the order seems incorrect.

Nice-to-have; Not blocker

NOT STARTED

Grace

The Error Console is really noisy with this alert whenever I am testing the Global Nav bar: An extension slot with the name 'patient-banner-tags-slot' already exists. Refusing to register the same slot name twice (in "registerExtensionSlot"). The existing one is from module @openmrs/esm-patient-banner-app.

Per Dennis: this happens because the patient-banner-tags-slot extension slot exists in a reusable component. This means that each instance of the slot that gets rendered will have the same slot name. That violates a fundamental principle of the extension system - that slot names should be unique across the app.

This is, in fact, the system working as intended in the sense that the extension system isn’t really set up for the same extension slot name to be used by multiple application, so this warning message is generated for the benefit of developers who may not realize they chose a name already in place.

Not blocker

NOT STARTED

Grace

Photos do not render in patient chart Header on physical Tablet (ok on desktop and using dev tools

Seems unique to only Grace’s tablet

Fine on 3 other tablets, android and ipads.

CANCELLED

Grace