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:
|
...
A Tab is generated for every Program Stage available. Each Tab is used for the corresponding Program Stage management.
...
| Note |
|---|
Please note the following points:
|
Managing sections
Adding a new section:
...
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):The user should enter between 2 and 200 characters.
Full name (Column E): The user should enter between 2 and 200 characters. If the user selected auto naming, this cell should be blocked.
Short name (Column F): The user should less than 50 characters. If the user selected auto naming, this cell should be blocked.
Code (Column G): The user should enter less than 50 characters. If the user 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” and “No”.
If the user selects “Yes” 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.
| Note |
|---|
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.