Validate & Approve Population Data

Overview

The Population Data Validation and Approval screen is designed for population data approvers to ensure the accuracy and consistency of population data submitted for villages. This screen allows approvers to validate, correct, and approve data, ensuring the integrity of the data used for resource planning.

User Roles

Roles	Description	Role Code
Population Data Approver	Responsible for validating the population data, ensuring its accuracy, including the ability to edit data, approve, or send data back for correction.	POPULATION_DATA_APPROVER
Root Population Data Approver	Responsible for validating the population data, ensuring its accuracy, including the ability to edit data, approve, or send data back for correction.Has additional permissions, including the ability to finalize population data.	ROOT_POPULATION_DATA_APPROVER

Interface Elements

Header Section

• Microplan Name: Displays the name of the current microplan being reviewed.

• Logged-in User: Indicates the user role and account.

Population Data Summary (KPIs)

• All values are dynamically updated based on the real-time census data.

• These values are sourced directly from microplan-specific KPIs, which reflect any actions taken by data approvers.

• As census data is reviewed, corrected, or approved, the values will change accordingly.

Filters and Search

• Administrative Hierarchy and Area Selection: Dropdown menus for selecting specific administrative areas (e.g., district and village).

• Search and Filter Options:

  • Workflow Status Filters:

    • Pending validation

    • Pending approval

    • Validated

  • Assigned to Filters:

    • Assigned to me

    • Assigned to all

  • Buttons: Apply Filter, Clear

Population Data Table

Column	Description
Village Name	Name of the village under review
Uploaded Target Population	Target population submitted for the village
Confirmed Target Population	Approved target population for the village
Uploaded Total Population	Total population submitted for the village
Confirmed Total Population	Approved total population for the village
Action Buttons	Includes View Logs for historical data and other validation actions

Action Buttons

• View Logs: Displays historical changes and logs related to a specific village's data

---

Population Data Validation Workflow

4.1. Role-Based Permissions and Actions

Population Data Approver (PDA)

The Population Data Approver is responsible for validating population and editing data. Their responsibilities include:

Validating Data:

• Cross-check the uploaded data with the confirmed population to ensure accuracy.

Editing Data:

• Modify the village population data if discrepancies are found, with a reason logged for each change and the data is sent back for approval.

When No Data Is Assigned:

• If no data is assigned to the PDA, a "Back" button is shown, allowing them to return to the previous screen.

---

Root Population Data Approver (RPDA)

The Root Population Data Approver has all the functionalities of a PDA and additional capabilities to finalise population data. Their responsibilities include:

Editing Data:

• Modify the village population data if discrepancies are found, with a reason logged for each change.

Approving or Sending Data for Correction:

• Once the population data is validated, the RPDA can either approve it or send it back for correction if further issues are identified.

Approval Workflow:

• If someone from the hierarchy below modifies and sends the data for approval, the RPDA can approve it. For example, if a province-level user sends the data back for approval, the RPDA will receive the application for approval and validation.

Finalising Actions:

• If all the villages within the selected microplan have been validated and no further changes are required, the RPDA will see a "Finalise Actions" button at the footer of the page.

• The "Finalise Actions" button will lock the data and prevent further modifications once clicked, marking the end of the validation process for the selected microplan population data.

• After finalising the population data, a success screen will be shown, indicating that the population data is finalised.

---

Additional Notes

• Once the population data reaches the national-level data approver and the validation is finalised, the system will disable all action buttons. The status will be set to "CENSUS_APPROVED", and no further changes can be made. At this point, users can only view the details of the data but will not be able to perform any additional actions, such as editing or approving the data.

• Population supervisors will only see the boundaries in their inbox that fall under their jurisdiction.

API End Points

Purpose	Endpoint URL	Method	Payload
Get chart data for a specific visualization	dashboard-analytics/dashboard/getChartV2	POST	{ "aggregationRequestDto": { "visualizationType": "METRIC", "visualizationCode": "censusUploadedTargetPopulation", "filters": { "COUNTRY": ["MICROPLAN_MO"], "status": ["PENDING_FOR_VALIDATION"], "planConfigurationId": ["246cfc95-b4b0-43e8-b375-dd44333cc881"], "tenantId": ["mz"] }, "moduleLevel": "CENSUS" }, "headers": { "tenantId": "mz" } }
Search census data	census-service/_search	POST	{ "CensusSearchCriteria": { "tenantId": "mz", "source": "246cfc95-b4b0-43e8-b375-dd44333cc881", "status": "PENDING_FOR_VALIDATION", "assignee": "a7431b92-5db5-46b1-9b5b-33272ba8dbfc", "jurisdiction": ["MICROPLAN_MO"], "limit": 50, "offset": 0 } }
Search business services	egov-workflow-v2/egov-wf/businessservice/_search	POST	SearchParams{ tenantId=mz, businessServices=CENSUS }
Search plan employees	plan-service/employee/_search	POST	{ "PlanEmployeeAssignmentSearchCriteria": { "tenantId": "mz", "active": true, "planConfigurationId": "246cfc95-b4b0-43e8-b375-dd44333cc881", "role": ["POPULATION_DATA_APPROVER", "ROOT_POPULATION_DATA_APPROVER"], "employeeId": ["a7431b92-5db5-46b1-9b5b-33272ba8dbfc"], "limit": 5, "offset": 0 } }
Search project type by campaign ID	project-factory/v1/project-type/search	POST	{ "CampaignDetails": { "tenantId": "mz", "ids": ["5b5a49ca-584c-4226-bbd6-98cddd95ef78"] } }
Search plan configuration details	plan-service/config/_search	POST	{ "PlanConfigurationSearchCriteria": { "tenantId": "mz", "id": "246cfc95-b4b0-43e8-b375-dd44333cc881" } }