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:
Rearranging the tab order in the Excel template will not impact the DHIS2 configurations.
This template is designed solely for the modification of existing DHIS2 programs; it does not support the creation of new programs.
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 within the spreadsheet are protected. The "Instruction" tab encompasses program settings for the chosen tracker or event, alongside a section detailing server information pertinent to the template's download source.
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, users should select Tracked Entity Attribute (TEA) from the provided options. Upon has been selected TEA, the subsequent columns must be highlighted in red to indicate their mandatory status:
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.
In case the expected cells aren't automatically populated, you can resolve this by dragging the formula from another cell within the same column.
Columns I to L will default to "No" if the cells are left blank.
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.
The Stages tab
A Tab is generated for every Program Stage available. Each Tab is used for the corresponding Program Stage management.
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 stage.
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.
Managing Data elements
Adding new data elements:
Structure (Column A): In this cell, users should select Data Elements from the provided options. Upon has been selected Data element, the subsequent columns must be highlighted in red to indicate their mandatory status:
Form name
Correlative (Column B): This cell should be automatically filled in once the user selecting Data Element in the structure column.
Use auto Naming (Column C): The use can select between “yes” and “no”.
If the user selects “Yes”, the full name, short name and code must not be entered by the user. These cells should be highlighted in gray color.
If the user select “No”, the users must enter the full name, short name and code. These cells should be highlighted in red color.
Form 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.
0 Comments