The template generated to for event/Tracker program will contain different tabtracker programs contains different tabs:
Instructions:
...
This section contains comprehensive guidelines on how to
...
effectively utilize the Excel template
...
.
TEAs
...
(Program Tracked Entity Attributes
...
): Within this tab, you can manage the attributes associated with the tracked entities in the program.
Stages: These tabs
...
dynamically correspond to the program stages, generating a tab
...
for
...
each individual stage.
Release
...
Notes: Please note that this tab is provided solely for reference
...
purposes and is not editable. For the latest features and fixes, kindly refer to this section.
Mapping: This tab is also designed for reference
...
purposes and is non-editable. It enumerates various components such as option sets, health areas, legends, etc., employed within the Excel spreadsheet.
| Note |
|---|
Keep in mind:
|
...
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 (See Image 1).
...
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 (See Image 2).
...
Managing sections
Adding a new section:
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.
| Info |
|---|
If the newly added row is selected as a section, the entire row will be highlighted in a light blue color |
Removing a section:
To remove a Section 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.
Managing TEA
Adding new TEAs:
...
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.
...
A Tab is generated for every Program Stage available. Each Tab is used for the corresponding Program Stage management.
...
(See Image 3).
...
Please note the following points:
New Program Stages: This template is designed solely for the purpose of editing pre-existing program stages. It does not support the creation of new Program Stages.
Stages Name Modification: The modification of stage names is not supported using the template. Kindly refrain from altering tab names. Should such modifications be necessary, you can use the PCA (Program Stage Configuration App).
Managing sections
Adding a new section:
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
...
data element.
For a new section, the user has to select "Section" on the Structure (A) column.
Then type a name on (
CD) column that will be displayed for the new section.
Removing a section:
To remove a Section from the current stage, 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.
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 colorcolour.
If the user select “No”, the users must enter the full name, short name and code. These cells should be highlighted in red colorcolour.
Form Name (Column D):This cell should be automatically filled in once the user enters the TEA name.Value Type The user should enter between 2 and 200 characters.
Full name (Column E): This The user should enter between 2 and 200 characters. If the user selected auto naming, this cell should be automatically filled in once the user enters the TEA nameblocked.
Aggregation Type Short name (Column F): This The user should less than 50 characters. If the user selected auto naming, this cell should be automatically filled in once the user enters the TEA nameblocked.
Mandatory Code (Column G): The user will be able to select between yes and noshould enter less than 50 characters. If the user selects “Yes”. The TEA must be filled to complete the event.Searchable selected auto naming, this cell should be blocked.
Description (Column H): The user will be able to enter helper text that will be displayed to the user during data entry.
Compulsory (Column I): The user should select between yes “Yes” and no“No”.
If the user selects “Yes”
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 data element must be answered to complete and event.
If the user selects "No" the data element should be optional, this option will be the default answer.
Agg Operator (Column J): The Aggregation Type is for analytical objectives, prompting users to select an option from the available choices, with "None" as the default response.
Option Set (Column M): Defines the available answer that will be displayed for the current data element.
Legend set (Column N): Legends that will appear to the current data element.
Parent Data Element (Column O): The user must enter the correlative of the Data Element that will act as parent for the current Data Element.
Answer Value (Column P): Value that will trigger the “show” rule of the Data Element.
Error/Warnings/Info (Column Q): Details regarding the cell highlighting on each row.
Stage ID (Column R): This cell will display the ID of the current stage, and it will remain in read-only mode.
Stage Name (Column S): This cell will display the name of the current stage, and it will remain in read-only mode.
| Info |
|---|
Adding existing Data elements:
|
Removing a data element:
To remove a Data Element from the current stage, 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.