4.11.0 release notes

Known issues

Check the repository for the latest known issues.

Upgrade notes

Breaking changes

None.

UI/UX changes

None.

Highlights

The CHT-Datasource API now supports querying persons

The CHT datasource API has been expanded to allow querying places and persons by contact type.

Details

See more details in the api docs.

Phone numbers are not required to be checked for duplicates

Phone number fields can now be used without automatically checking for duplicates. This can be useful for workflows where users may share a phone or for any workflow where having duplicate phones is possible, and it’s undesirable to check for duplicates.

Duplicate checking is still available if desired.

Details
  • Previously, the phone widget was configured in an xlsxform field by setting type: tel. By default, the phone widget both validates the phone number value and checks for existing contacts that have the same number.
  • With these new changes, the existing (now deprecated) functionality stays the same, but going forward, phone number fields should be configured in an xlsxform by setting type: string with appearance: number tel.
  • Fields with this new configuration will always validate the phone number value, but by default they will not check for existing contacts with the same number.
  • To enforce a unique phone number with the new style of field, you should add a new column with instance::cht:unique_tel: true.

The logged in users contact summary contains more target documents

The contact-summary function now receives the last three target documents of the contact, available through the CHT API. Additionally, the logged in user’s target documents are passed to the contact-summary function when generating the contact summary of one of the logged in user’s facilities. More details in the contact page docs

And more…

Features

  • #9241: Create API endpoint for getting people
  • #9269: Expose the user’s target documents into the contact summary

Improvements

  • #6390: Allow for phone number validation but also allow for duplicate phone numbers
  • #8551: Convert Python Invoke code in the cht-deploy to its JS/TS equivalent
  • #9389: Update api/v1/person endpoint to not use camel-case personType query parameter
  • #9413: Deprecated mutation event

Security fixes

None.

Performance improvements

None.

Bug fixes

  • #8225: Cannot use db-object-widget to load contact data in non-relevant inputs group
  • #8947: Outbound push cron config error
  • #9294: No feedback document recorded on PouchDb crash
  • #9341: Strip invisible characters from the fields bsYear, bsMonth, bsDay
  • #9429: Only 50 reports are passed to the contact summary which is passed to enketo
  • #9433: REST Endpoint /api/v1/users/{{username}} throwing Server error when updating contact

Technical improvements

  • #8604: Catch missing values file in k3d script
  • #8605: Show URL when done running k3d script
  • #8608: add a “get all logs” script for k3d deployments
  • #9097: K3D suites are failing for external contributors
  • #9328: Generated docs are published when building dev branches

Contributors

Thanks to all who committed changes for this release!



Last modified 26.09.2024: release: add 4.11.0 release notes (#1524) (c24e0997)
Edit this page Create documentation issue Create project issue