Skip to content

v2.0.4

Choose a tag to compare

@Marlpzg Marlpzg released this 04 Jun 03:02
· 82 commits to main since this release

Release date: June 3rd, 2024

Key Features

  • New Android Settings added to HNQIS 2.0 Programs configuration.
  • New Global Score Program Indicator in HNQIS 2.0 Programs.
  • HNQIS2 Metadata Package v1.1.4
  • Bugfixes.

Detailed Features

  • A new section in the New/Edit Program form has been added to include Android Setings in HNQIS 2.0 Programs. Now, the TEI download limit can be defined for each HNQIS 2.0 Program (used by the Android Capture App). This feature requires the Android Settings DHIS2 App to be installed in the server to apply the configurations during the "Set Up Program" process.
  • A new Global Score Program Indicator has replaced the Global Score Attribute in HNQIS 2.0 Programs. this change improves the usage and update of Analytics. Updating old HNQIS 2.0 Programs (by using the "Set Up Program" feature) is critical to ensure the correct operation of the Programs.
  • A new HNQIS 2.0 Metadata Package has been released to remove the Global Score Program Attribute. Installing the new package is required to use HNQIS 2.0 features.

Bug Fixes

  • Fixed a bug where applying Sharing Settings "too quickly" resulted in an error. The "apply" button is now disabled until all the metadata has been loaded.

Known Issues

  • Searching for Users and User Groups in the Sharing Settings dialog still remains an issue.
  • Sometimes, changes in the contents of a Program Stage may not be reflected in the PCA. Reloading the page should fix this issue.
  • After transferring HNQIS 1.X Assessments to HNQIS 2.0, some Action Plan Events may display a conflict if the Event Date is set in a future date. This issue resolves itself once the Event Date has passed.
  • Modifying the Line Listing that is generated automatically for the Dashboard in HNQIS2 Programs will cause the "Set Up Program" process to fail. This is a bug related to DHIS2 and will be addressed in a future version. A workaround is to delete the Line List manually to re-generate the analytics again.