The template generated to event/Tracker program will contain different tab:
Instructions: Contain information how to use the template excel.
TEAs: Contain the Program Tracked Entity Attributes management.
Stages: These tabs are going to be generated depending on the program stages, a tab is generated for every program stage.
Release notes: This tab is for reference only, you cannot edit it. Please refer to this tab for latest features and fixes
Mapping: This tab is for reference only, you cannot edit it. This tab will list all the option sets /Health are / Legend etc. Used in the Excel spreadsheet.
Keep in mind:
Changing the tab order in the Excel template will not change the DHIS2 configurations
This template can only be used to edit existing DHIS2 program, program creation is not supported
The instructions tab
This tab provides brief information related to the Excel sheet. You can go through this tab to have a thorough understanding of all the fields in the sheet.
All cells are protected in the spreadsheet, the instruction tab contains the program setting for the selected tracker or event, also the instruction tab contain a section for the server info about server from the template was downloaded.
The TEAs tab
This tab contains the Tracked Entity Attributes assigned to the current program.
Managing sections
To add another section, the user only will have to add a new row (it is very important to remark that an entire row needs to be added) right below the previous section’s last TEAs.
For a new section, the user has to select "Section" on the Structure (A) column.
Then type a name on (C) column that will be displayed for the new section.
If the newly added row is selected as a section, the entire row will be highlighted in a light blue color
Managing TEA
Adding new TEAs:
To add a new TEA, you have to find the right position where you want it and add a new entire row right below. The following cell should be filled in:
Structure (Column A): In this cell, the user will have to select TEA in the options. Once you have selected TEA the following columns must be highlighted in red to show that are mandatories:
UID
Name
Short Name
Value type
Aggregation type
UID (Column B): This cell should be automatically filled in once the user enters the TEA name.
Name (Column C): The user must enter TEA name and the following column should be automatically filled in:
UID
Short name
Value type
Aggregation type
Short Name (Column D):This cell should be automatically filled in once the user enters the TEA name.
Value Type (Column E): This cell should be automatically filled in once the user enters the TEA name.
Aggregation Type (Column F): This cell should be automatically filled in once the user enters the TEA name.
Mandatory (Column G): The user will be able to select between yes and no. If the user selects “Yes”. The TEA must be filled to complete the event.
Searchable (Column H): The user will be able to select between yes and no. If the user selects “Yes”, allows the TEA to be used as a search filter in the Tracked Entity Instance list.
Display in List (Column I): The user will be able to select between yes and no. If the user selects “Yes”, the value of the selected TEA will be displayed in the Tracked Entity Instances list.
Allow Future Date (Column J): The user will be able to select between yes and no. If the user selects “Yes”, the TEA will allow selecting a future date.
Error/Warning/Info (Column M): The template will show detail regarding the cell highlighting on each row.
The UID, Short name, Value Type and Aggregation Type are used to verify that the TEA exists in the server, in case the TEA doesn’t exit, the cells will display a “Not found” message.
If the expected cells are not automatically filled in, then drag the formula from another cell in the same column.
For columns from I to L, if the cell remains blank, the default value is “No”.
Removing a TEA:
To remove an existing Tracked Entity Attribute from the current program, simply delete the entire corresponding row. Importing this template into the Program Configuration App will interpret missing rows as elements to be removed from the Program's current configuration.
0 Comments