Releases: dhis2/dhis2-android-capture-app
Android Capture App for DHIS 2 (v2.8.1.1) - Hotfix
This is a patch version of the DHIS2 Android App It builds upon the last version including bug fixes that couldn't wait to the next version. It includes no functional improvements neither changes in the User Interface. It means that yours users can update without experiencing any change in the UI. | |
Bugs fixed
Bug fixing: You can find the list of bugs fixed here. |
Android Capture App for DHIS 2 (v2.8.1) - Patch version
This is a patch version of the DHIS2 Android App It builds upon the last version including bug fixes that couldn't wait to the next version. It includes no functional improvements neither changes in the User Interface. It means that yours users can update without experiencing any change in the UI. | |
Bugs fixed
Bug fixing: You can find the list of bugs fixed here. |
Android Capture App for DHIS 2 (v2.8)
The new DHIS2 Android App allows offline data capture across all DHIS2 data models. Data and metadata are automatically synchronized whenever there is internet access, always keeping the most relevant data for the logged user in the device. The app is compatible and we support 2.40, 2.39, 2.38. And has no breaking changes with 2.37, 2.36, 2.35 and 2.34. | |
USER EXPERIENCEResized dataset tables: This feature allows users to resize the columns in datasets, making it easier to view and work with larger tables. Now it is possible to resize all columns by clicking on the header of the column. The resizing can be done through drag and drop. A maximum and minimum size limit is given for the columns that can be resized to ensure a good layout. Users can resize all columns at once by clicking on the top left of the table. Jira | Screenshot New sync error navigation: This version of the app improves the navigation of sync errors on the user interface. The app will display the sync errors in a simple and clean manner allowing the user to navigate from the home screen to the exact field that is causing the error inside the event or data set. Jira | Screenshot Collected handwritten signatures for image Data Elements: This feature allows users to collect handwritten signatures from the device. The signatures will be saved as an image data elements in the app. Jira | Screenshot Made phone number and email Data Elements actionable in the form and allowed external actions for phone number, email and URL value types: This feature enables users to take action on phone numbers, email addresses, and URLs directly from the app, such as dialing a phone number or opening a web page from the event or enrollment data entry form. Jira | Screenshot Improved visual configuration and rendering of option sets: This feature improves the way option sets are displayed and configured when configured visualy by enabling render option sets with any value type as Radio buttons or check box and supporting other value types for visual data entry. Jira | Jira2 | Screenshot Added loading banners when actions take a long time to improve user experience: This feature provides visual annimations to users when they perform actions that take longer than usual to complete, such loading maps or searching, so that they know that the system is processing their request. Jira | Screenshot Improved user experience for better functionality when offline: This feature enhances the functionality of the app when it is used offline, ensuring that menus are disabled when the online actions are not available. Jira Improved management of long texts: This feature enables users to view long text in fields that are limited in size, such as a stage names or datasets headers. Jira | Jira SUPPORT MOBILE IMPLEMENTATIONSProvided support for Android app version control from DHIS2 user interface: This feature enables implementation administrators to manage and control the version of the Android app from the DHIS2 user web interface, making it easier to manage app updates and ensure compatibility with the DHIS2 system. Managers will be able to upload the desired version and users will get a prompt message to update when they are not in the last updated version. The management of versions is made through a new Web App. Jira | Screenshot Removed the maximum number of offline accounts: This feature removes the limitation on the number of offline accounts that users can create, allowing them to work with as many offline accounts as needed. Jira WEB PARITYSupported file value type: This feature adds support for file value type in the Android app, allowing users to attach files to their data elements or attributes. Jira | Screenshot Supported new tracker working lists (filter by DE): This feature adds support for new tracker working lists that allow users to filter by data elements. The working lists need to be configured in web using the web Capture App. The Android app will download the working lists that are configured and saved on the server side. Jira LMISIntegrated a new module for real stock monitoring use case: This feature adds a new module for real stock monitoring use case to the app, enabling users to manage and monitor their stock levels in real-time. Integrating a module implies that the app will open a completely new and different user interface and experience to respond to a different data entry flow. To use this modules the program will need to be configured using the new web app for program use case configuration. Jira | Screenshot MAINTENANCEBug fixing: You can find the list of bugs fixed here. |
Android Capture App for DHIS 2 (v2.7.1.1) - Hotfix version
This is a patch version of the DHIS2 Android App It builds upon the last version including bug fixes that couldn't wait to the next version. It includes no functional improvements neither changes in the User Interface. It means that yours users can update without experiencing any change in the UI. | |
Bugs fixed
You can find in Jira details on the bugs fixed in this version. Remember to check the documentation for detailed Please create a Jira Issue if you find a bug or |
Android Capture App for DHIS 2 (v2.7.1) - Patch version
This is a patch version of the DHIS2 Android App It builds upon the last version including bug fixes that couldn't wait to the next version. It includes no functional improvements neither changes in the User Interface. It means that yours users can update without experiencing any change in the UI. | |
Bugs fixed
You can find in Jira details on the bugs fixed in this version. Remember to check the documentation for detailed Please create a Jira Issue if you find a bug or |
Android Capture App for DHIS 2 (v2.7)
The new DHIS2 Android App allows offline data capture across all DHIS2 data models. Data and metadata are automatically synchronized whenever there is internet access, always keeping the most relevant data for the logged user in the device. The app is compatible and we support 2.39, 2.38, 2.37. And has no breaking changes with 2.36, 2.35, 2.34 and 2.33. | |
USER EXPERIENCEIncrease tappable areas in icons and buttons: Some buttons or tappable labels of the Android App had small sensitive areas for the user to tap. The whole user interface was reviewed and the tappable areas has been increased. For example the "+" button to create a new stage or the "˅" icon to open TEI details or expand a section. Clean Data Entry forms: The input fields had a hint message saying "Insert value here" which remained there after the values was entered. We have kept the hints when the field is empty, but they dissapear now once the value is entered by the user. Jira | Screenshot | Documentation Simplify steps to create program stage: When the user groups the events per program stage in a tracker program, the option to create a stage was only visible when the events of the specific program stage where expanded. In this version, the option to create a new event is always visible. When the user taps on the button, that program stage will unfold showing to the user all the already existing events of that particular program stage. In addition to this, when there is only one option based on the program configuration, the available program stage is selected automatically and program stage selection step is skipped.Jira 1 | Jira 2 | Screenshot | Documentation Move Share button in TEI Dashbaord to a secondary menu: The TEI Dashboard had a black "Share" button which was using a significant space on the screen and not align with the visual design of the app while the function is very marginally used. The button has been removed and the functioanlity to share a TEI through QR code has been located on the three vertical dot menu, at the top right corner of the screen. Jira | Screenshot | Documentation More intuitive Navigation for event sections: The accordion navigation of form sections was confusing for some some users and the next action after completing the last field of one section was not intuitive. This version of the App includes a "Next" button at the end of each section which calls the user to action. The funtion of the button is to close the current section and open the new one. Jira | Screenshot | Documentation New input dialog for datasets: When the user in entering data in a dataset, the keyboard opens overlaping most of the screen and the dataset table. The new text input dialog opens an input field above the keyboard which shows the Data Element name, and category options of the field being selected, ensuring the user does not lose context when navigating the tables during data entry. Jira | Screenshot | Documentation LOCAL ANALITICSNew legend style on tables: The style for legends in tables has a new design which ensures good contrast and visibility independently from the selected colour for the legend. Jira | Screenshot | Documentation Implement missing aggregation functions: The following aggreagation functions are supported now in local analytics: LAST, FIRST, AVERAGE_SUM_ORG_UNIT, LAST_AVERAGE_ORG_UNIT, LAST_IN_PERIOD, LAST_IN_PERIOD_AVERAGE_ORG_UNIT, FIRST_AVERAGE_ORG_UNIT [Jira](Implement missing aggregation functions) | Documentation SYNC PROCESSOpen home after syncing metadata: When a user logs in to the Android App for the first time, the App needs to download all the metadata and data, including the file resources. Depending on the server and user configuration, on the server resources and on the internet connection, this process can be very long. Until this version, all these happened on the splash screen and the user had to wait during all this time on the same screen. We cannot change that process or waiting time, however we can make it more interactive and informative. In this new version the app will remain in the splash screen during the metadata download and will open the home screen once the metadata is in the device. In the home screen, the app will inform with a loading spinner on each program when the data is downloading and when is ready. The user will be able to see how many programs are downloading data, or completed, making the waiting process more transparent and informative about its progress. Jira | Screenshot | Documentation Do not make full sync when opening the App: Before this version, everytime a user opened the DHIS2 Capture App, the application would launch a sync process for data and metadata, to ensure the app was in sync with the server. In most cases and locations this process was very slow. In order to facilitate the work in the most difficult cases, we have removed that sync process. When the user opens the app, even if s/he logs out and logs in again, the app will open without performing a full sync. Users have the option to sync with the server through the Refresh button any time they wish. Jira | Documentation TRACKER FEATURESManage ownership in permanent referrals: Since 2.7, when a user makes a permanent referral of a TEI, the ownership will be updated accordingly. Jira | Documentation MOBILE IMPLEMENTATION SUPPORTUpload SMS APK: From this version, the app available in Google Play includes the SMS functionality. In previous versions, this functionality was only available on an apk available in Github. Jira | Documentation QUALITY, PERFORMANCE AND STABILITYData sets
Sync process Forms You can find in Jira details on the new features in this version. Remember to check the documentation for detailed information of the features included in the App and how to configure DHIS2 to use it. Please create a Jira Issue if you find a bug or you want to propose a new functionality. [Project: Android App for DHIS2 | Component: AndroidApp]. |
Android Capture App for DHIS 2 (v2.6.2) - Patch version
This is a patch version of the DHIS2 Android App It builds upon the last version including bug fixes that couldn't wait to the next version. It includes no functional improvements neither changes in the User Interface. It means that yours users can update without experiencing any change in the UI. | |
Bugs fixed
You can find in Jira details on the bugs fixed in this version. Remember to check the documentation for detailed Please create a Jira Issue if you find a bug or |
Android Capture App for DHIS 2 (v2.6.1) - Patch version
This is a patch version of the DHIS2 Android App It builds upon the last version including bug fixes that couldn't wait to the next version. It includes no functional improvements neither changes in the User Interface. It means that yours users can update without experiencing any change in the UI. | |
Bugs fixed
You can find in Jira details on the bugs fixed in this version. Remember to check the documentation for detailed Please create a Jira Issue if you find a bug or |
DHIS2 Android App version 2.6 Release Notes
The new DHIS2 Android App allows offline data capture across all DHIS2 data models. Data and metadata are automatically synchronized whenever there is internet access, always keeping the most relevant data for the logged user in the device. The app is compatible and we support 2.38, 2.37, 2.36. And has no breaking changes with 2.35, 2.34, 2.33, 2.32, 2.31 and 2.30. | |
IMPLEMENTATION SUPPORT FEATURESSupport multiple users offline: The Android app can now work with up to 3 different users while being offline. The users will need to have access to the internet for the first login of each account and will be able to switch accounts after without requiring access to the Internet. The users will be able to manage the user accounts and delete accounts if needed. When the maximum number of accounts is reached, it will be necessary to delete one of the existing accounts to log in to a new one. Jira | Screenshot | Screenshot 2 | Documentation Configuration troubleshooting: This feature is for administrators. The Android App incorporates an option in the settings screen for verifying some aspects of the DHIS2 configuration.
Jira | Screenshot | Screenshot 2 | Documentation OFFLINE ANALYTICSSupport legends for tables in analytics: Legends are displayed in pivot tables by enabling the feature "Use legends for chart color" in the Data Visualizer App. The Android app will color the cells using either the pre-defined legend per data item or a single legend for the entire pivot table, depending on the settings in Web. Jira | Screenshot | Documentation TRACKER FEATURESBreak the glass: If the program is configured with an access level of "Protected" and a search is done outside the user scope, a dialog requesting a reason for access will be displayed for the user to temporarily override the ownership privilege of the program. This means, the user will gain access to the program related data. Jira | Screenshot | Documentation Make mandatory TEI search configurable: Searching TEIs before creating is not mandatory now. Using the Android Settings App (v2.2.0) it is possible to configure the user flow for creating TEIs. If the feature is enabled, the Android App will display a "create new" button after opening a program and a search will be optional. Jira | Screenshot | Documentation Separate offline/online search flows: To improve the response time in the search results, the Android App now searches offline first and displays the results while making an online search as a second step, transparent to the user. Searching outside the program is offered as a second step when the attributes used in the search contain at least one Tracked Entity Type (TET) attribute Jira | Screenshot | Documentation DATA ENTRY AND SYNC FEATURESScan and display GS1 Data matrix QR codes: If an attribute or data element rendering type is configured as QR code, the Android App will be able to read and process the string as GS1 Data Matrix codes. Combined with the use of d2 functions in program rules, the different fields of a GS1 code can be saved into different data elements or attributes (d2:extractDataMatrixValue(key, dataMatrixText)). Jira | Screenshot | Documentation Allow the user to "refresh data" to get last updated data from server: Users can now retrieve the latest data from the server before entering new data. A refresh button is now located to trigger a granular synchronization in the following screens:
Jira | Screenshot | Documentation Render Icons in enrollment forms: The icon based data entry can now be used in enrollment forms. When an enrollment section contains one or more Tracked Entity Attributes with option sets and icons assigned, the app is able to display them as a matrix or sequence based on the section rendering type. In previous sections of the App this feature was only available for Data elements. Jira | Screenshot | Documentation Improve Save and Complete flow in events: New dialog boxes are displayed when saving an enrollment or event. The 'Re-open' button is now located in the details screen and it will be available only if the user has the correct authority (‘Uncomplete events’) to reopen a completed event. The "completion" concept and dialog is now more intuitive and user friendly. Jira | Screenshot | Documentation New design for warnings/errors and completion dialogs: Error and Warning messages have been improved to provide the user more and better information. The new dialogues when saving, allow the user to discard changes, save and correct later or keep editing the form to correct the values depending on the configuration. Jira | Screenshot | Documentation Improve design fo datasets columns span: The redimensioning arrows are now fixed at the upper-left corner of the screen . Jira | Screenshot | Documentation Show hint of OU selected when opening the OU hierarchy: If an organisation unit is selected, when the hierarchy is displayed, all the ascending (parent) OUs will be in bold to help the user navigate the previous selection. Jira | [Screenshot](https://s3.eu-west-1.amazonaws.com/content.dhis2.org/dhis2-android/release+no... |
Android Capture App for DHIS 2 (v2.5.2) - Patch version
This is a patch version of the DHIS2 Android App It builds upon the last version including bug fixes that couldn't wait to the next version. It includes no functional improvements neither changes in the User Interface. It means that yours users can update without experiencing any change in the UI. | |||||||||||||||||
Bugs fixed
You can find in Jira details on the bugs fixed in this version. Remember to check the documentation for detailed Please create a Jira Issue if you find a bug or RELEASE INFO
|