4.9.0 release notes

Known issues

Check the repository for the latest known issues.

Upgrade notes

Breaking changes

None.

UI/UX changes

This release adds support for assigning multiple places to users. Users who are configured to have multiple places will see some subtle UI changes as described in the Highlights section. For a video walkthrough of the changes, check out the June 2024 CHT Round-up call and this forum post.

Highlights

Allow multiple places to be assigned to users

To better support Supervisors who manage CHWs across multiple areas, it is now possible to assign more than one “Place” (ie Community Health Unit, Health Center, etc…) to a user. To enable this feature, simply assign the can_have_multiple_places permission to the relevant user role(s) and add the desired “Place(s)” to the user.

Setup

If the User’s Role has the appropriate permission, it will be possible to assign multiple Places. Note: Selected Places must be at the same level in the hierarchy.

IMPORTANT: When removing a Place that was previously assigned to a user, app storage needs to be cleared on the physical device. When adding a Place to an existing user, that user will sync the new Place and associated data automatically the next time they sync.

User Experience

Users who are assigned multiple Places will see a few changes in the CHT’s User Interface. These changes are summarized below, and are discussed in detail in this forum post.

Contacts Page: The List View will show all assigned Places (ie CHUs) but will not show the list of child places (ie CHW Areas).

Contact Detail: The list of child places (ie CHW Areas) can be viewed on this page.

Messages, Tasks, and Reports Pages: Data for all assigned Places will show up together in the List View. An additional level of lineage has been added to the Breadcrumbs to clarify which Place each item (Message, Task, or Report) is associated to.

Targets: Personal Targets will look the same. Aggregate Targets will not be shown for users with multiple assigned places, even if the user has the permission. Support for Aggregate Targets for users associated to multiple places will potentially be supported in a later release.

Signature widget

For some time now there has been interest in having the CHT support the ability for a CHT to collect a hand drawn signature from a patient. With this release, app developers may now implement the draw widget in “signature” mode. Here is an example of both the draw widget and signature widget on a demo app in the CHT:

And more…

Features

  • #6543: Allow for multiple places to be assigned to users
  • #9116: Update the user form to allow assigning multiple places to users.
  • #8308: Add support for Signature Widget in forms

Improvements

None.

Security fixes

None.

Performance improvements

None.

Bug fixes

  • #7530: Can’t edit forms that have empty “binary” fields
  • #8072: Error when saving form with repeated upload inputs
  • #9203: Ensure backward compatibility of facility_id in Admin app

Technical improvements

  • #9065: Add cht-datasource to support get person by uuid
  • #8557: Investigate using shellcheck for script linting
  • #9134: Upgrade e2e test fails on betas
  • #9153: Update the release notes generation script to add a list of contributors
  • #9155: Permissions to show reports and tasks test is failing often
  • #9173: Add Gaze cwd with path.resolve to watch.js
  • #9179: Integration tests broken on master
  • #9187: Haproxy unit tests are failing due to haproxy patch release

Contributors

Thanks to all who committed changes for this release!