Announcing the release of 4.10.0 of the CHT Core Framework

Product Releases
1

We’re excited to announce the release of 4.10.0 of CHT Core Framework

See below for some highlights, read the release notes for full details.

Following our support policy, versions 4.6.x are no longer supported. Projects running these versions should start planning to upgrade in the near future. For more details read our software support documentation.

Check out our roadmap to see what else is currently being working on.

4.10.0 Highlights

Aggregate Targets can now be viewed for the previous month

The CHT now supports viewing Aggregate Targets for the previous month. All users who have access to Aggregate Targets will see a Filter option that allows them to choose between the current month and previous month. This affects both “monthly” and “all time” widgets. Viewing the previous month’s data for an “all time” widget (which is cumulative) will show the data as it were at the end of the previous month. When “Previous Month” is selected, a visual cue (the month name) will be displayed both in the list view (as a breadcrumb) and the detail view (as the column header).

Details
  • “Current month” will always be shown by default
  • The “Reporting Period” label in the filter sidebar uses the analytics.target.aggregates.reporting_period translation key
  • This filter is shown for all users who have access to aggregate targets, you don’t need to do anything to enable it (and there is no way to disable it)

image
image801×539 79.9 KB

Aggregate Targets for users assigned to multiple places

The CHT also now supports Aggregate Targets for users that are assigned to multiple places. If a user has multiple places (added in 4.9.0), they will see an additional filter option that allows them to choose which place they want to view. There is also a visual cue on each Target to clearly indicate which place is being viewed.

NOTE: Users who are assigned only one place will not see the additional place filter option, but they will continue to see the new Reporting Period filter option.

Details
  • The list of places will be shown alphabetically
  • The first place in the list will be selected by default
  • Only one place can be selected at a time (it’s not a multi-select)
  • The label / heading for the list of places in the filter sidebar is the name_key of the place contact type as set in app_settings
  • This filter is shown for all users who have access to aggregate targets and are configured with multiple places, you don’t need to do anything to enable it (and there is no way to disable it)

image
image858×574 110 KB

Form validation for Luhn identifiers

Luhn numbers are used in a range of identification schemes and include a check digit to allow validation so they can be checked for common mistakes like typos. Including this in xpath means this can be checked while the form is being filled out to detect mistakes before the form is completed. More information is available in the xpath documentation.

#9227: Include xpath function for validation of Luhn identifiers

And more…

We’ve also implemented loads of other improvements and fixed a heap of bugs.

3 Likes