> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/health/v2.0/deploy/configuration/microplan-service-configuration/microplan-web-service-configuration/supervisor-workflows/select-activity.md). # Select Activity ## **Overview** The Select Activity screen helps supervisors manage and track microplans. It shows role-based activity cards that guide them through tasks like validating population data, assigning facilities, and approving estimations. The activities displayed depend on the user’s role (Root or Normal) and the current microplan status, so supervisors only see actions relevant to their responsibilities at each stage. ## **Interface Elements** **Microplan Name Display:** A prominently displayed label at the top of the interface that shows the name of the selected microplan. **Activity Options:** Displays a list of activities as clickable items. Selecting an activity navigates the user to the corresponding detailed workflow.
## Available Activities **1. Validate & Approve Population Data** * **Purpose**:\ Ensures the population data associated with the microplan is accurate and approved for further processing. * **Steps**: * Review uploaded population data for completeness and correctness. * Approve or flag data for revision as needed. * **Roles Involved**: * ROOT\_POPULATION\_DATA\_APPROVER: Can review, approve, or send back population data, as well as finalised population data. * POPULATION\_DATA\_APPROVER: Can review, approve, or send back population data. * **Role-Based Access**: * This card is visible based on the user role and the `wfStatus` that aligns with the data validation stage. **2. Assign Facilities to Villages** * **Purpose**:\ Assign healthcare or distribution facilities to specific villages or areas within the campaign's scope. * **Steps**: * Map villages to designated facilities. * Confirm assignments to ensure logistical accuracy. * **Roles Involved**: * ROOT\_FACILITY\_CATCHMENT\_MAPPER: Assign and unassign facilities to villages, and finalise facility assignments. * FACILITY\_CATCHMENT\_MAPPER: Assign and unassign facility to villages. * **Role-Based Access**: * This card appears only when the `wfStatus` indicates that facility assignment is the next step. **3. Validate & Approve Microplan Estimations** * **Purpose**:\ Review and finalise the estimated resources, population coverage, and other metrics calculated for the microplan. * **Steps**: * Check estimations for accuracy and alignment with campaign objectives. * Approve or request adjustments as necessary. * **Roles Involved**: * ROOT\_PLAN\_ESTIMATION\_APPROVER: Can approve or request adjustments for microplan estimations, also finalized microplan estimation. * PLAN\_ESTIMATION\_APPROVER: Can approve or request adjustments for microplan estimations. * **Role-Based Access**: * The card is displayed based on `wfStatus` of the plan configuration, indicating readiness for estimation validation. ## **User Actions Flow** 1. **Select an Activity:**\ Choose one of the available activities depending on the current stage of the microplan. 2. **Proceed to the Next Screen:**\ Click the activity to access its detailed workflow interface. ### **Notes** * **Role-based Permissions:** Certain activities might be restricted based on user roles and permissions. * **Sequential Workflow:** Activities must be completed in sequence for effective campaign execution: 1. Validate Population Data 2. Assign Facilities 3. Approve Microplan Estimations * **Progress Tracking:** Ensure tasks are not repeated and assignments remain aligned with campaign objectives. ## **API Endpoints**
End PointsPurposeRole
/egov-workflow-v2/egov-wf/process/_searchSearch process history for this planROOT_POPULATION_DATA_APPROVER,
POPULATION_DATA_APPROVER,
ROOT_PLAN_ESTIMATION_APPROVER,
PLAN_ESTIMATION_APPROVER,
ROOT_FACILITY_CATCHMENT_MAPPER,
FACILITY_CATCHMENT_MAPPER,
MICROPLAN_VIEWER
/egov-workflow-v2/egov-wf/businessservice/_searchSearch workflow business services by tenant ID and planROOT_POPULATION_DATA_APPROVER,
POPULATION_DATA_APPROVER,
ROOT_PLAN_ESTIMATION_APPROVER,
PLAN_ESTIMATION_APPROVER,
ROOT_FACILITY_CATCHMENT_MAPPER,
FACILITY_CATCHMENT_MAPPER,
MICROPLAN_VIEWER
/plan-service/config/_searchRetrieve plan configuration details by configuration IDSUPERUSER,
MICROPLAN_ADMIN,
MICROPLAN_CAMPAIGN_INTEGRATOR,
ROOT_POPULATION_DATA_APPROVER,
POPULATION_DATA_APPROVER,
ROOT_PLAN_ESTIMATION_APPROVER,
PLAN_ESTIMATION_APPROVER,
ROOT_FACILITY_CATCHMENT_MAPPER,
FACILITY_CATCHMENT_MAPPER,
MICROPLAN_VIEWER
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.digit.org/health/v2.0/deploy/configuration/microplan-service-configuration/microplan-web-service-configuration/supervisor-workflows/select-activity.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.