DIGIT Docs
Microplanning 0.2
  • DIGIT Knowledge Base
  • Local Governance
Microplanning 0.2
  • Introducing Microplanning
    • Release Notes
      • v0.2 Release Notes
        • Release Checklist
        • Technical Release Summary
        • Master Data Management Service (MDMS) and Configuration updates
        • Service Builds
        • UI/UX Audit
  • PRODUCT SPECIFICATION
    • User Manual
    • Product Requirement Document
      • SOPs
        • Guidelines
  • TECHNOLOGY
    • Architecture
      • High Level Design
      • Low Level Design
        • Plan Management
        • Census Management
        • Microplanning UI
          • System Admin Flow
          • Population Data Approval
          • Facility Catchment Mapping
          • Microplan Estimation Approval
      • Services
        • HCM Microplan Web
          • User Interface Design
          • Set Up Microplan
            • Microplan Details
            • Boundary Selection
            • Data Management
            • Data for Assumptions and Formulae
            • Microplan Assumptions
            • Formula Configuration
            • User Tagging
            • Summary Screen
          • User Management
            • Bulk User Create
            • Download Users Credentials
          • Supervisor Flows
            • User Interface Design
            • My Microplan
            • Select Activity
            • Validate And Approve Population Data
              • Village Details
            • Assign Facility To Villages
              • Village Assignment And Unassignment to Facility
            • Validate And Approve Microplan Estimation
          • Open Microplans: System Admin
            • Draft Flow
    • Specification
      • Plan Service
      • Resource Generator Service
      • Census Service
  • SETUP
    • Installation
    • Configuration
      • Advanced Configurations
    • QA Test Cases
    • Performance Testing
Powered by GitBook

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

On this page
  • Flow of Uploading
  • Template generation:
  • Validations in excel template:
  • Browsing and Uploading file
  • Validation of xlsx files
  • On Submit:
  • Delete File:

Was this helpful?

Export as PDF
  1. TECHNOLOGY
  2. Architecture
  3. Services
  4. HCM Microplan Web
  5. User Management

Bulk User Create

The Bulk Upload Users functionality allows the System Administrator to create multiple users with various roles in the Microplan by uploading an Excel template containing user details.

PreviousUser ManagementNextDownload Users Credentials

Was this helpful?

Flow of Uploading

  1. Template generation

  2. Editing template

  3. Browsing and Uploading

  4. Validating File

  5. Submitting file

Template generation:

To fill up the details in excel sheet a template is downloadable. The template is created by using the api call to /project-factory/v1/data/_generate

The user fills up the template and making sure to fill it in a valid manner.

Validations in excel template:

  • Fill in user details (Name, contact number, and email) in each sheet according to the role.

  • Do not assign the same user to both the Microplan Estimation Approver and National Microplan Estimation Approver roles.

  • Do not assign the same user to both the Facility Boundary Assigner and National Facility Boundary Assigner roles.

  • Do not assign the same user to both the Population Data Approver and National Population Data Approver roles.

Browsing and Uploading file

When the user clicks on Browse in My Files, they can select a file of type .xlsx, .xls and only the downloaded template can be uploaded. Once the file is selected, the validation of the Excel file begins. This validation is performed using the following hook:

The file is then set in the state and validated through the below hook.

Digit.Hooks.campaign.useResourceData( uploadedFile, state?.hierarchyType, type, tenantId, id, baseTimeOut?.["HCM-ADMIN-CONSOLE"], { source: "microplan" } );

Once the status from the validation is "Completed", the processedFileStoreis extracted from the response and sent to the following hook.
Digit.UploadServices.Filefetch([processedFileStore], tenantId)

This hook returns fileUrl, which contains the URL attribute. For example, the URL might look like:

https://unified-qa-filestore.s3-ap-south-1.amazonaws.com/mz/HCM-ADMIN-CONSOLE-CLIENT/December/4/1733307220857RYETclexTL.xlsx?...

This is a pre-signed URL generated by Amazon S3 (Simple Storage Service), which provides temporary access to a specific file stored in an S3 bucket.

When the fileUrl is set, the file can be downloaded by clicking a button that uses the following hook:

Digit.Utils.campaign.downloadExcelWithCustomName({ fileStoreId: file?.filestoreId, customName: fileNameWithoutExtension }); 

When the files are selected, the following api calls are being made.

Actions is set to validate when the file is first selected its sent for payload for /project-factory/v1/data/_create

End Point

Method

/project-factory/v1/data/_create

MICROPLAN_ADMIN

/project-factory/v1/data/_search

MICROPLAN_ADMIN

Validation of xlsx files

This hook does the validation of the xlsx file uploaded.

Digit.Hooks.campaign.useResourceData( uploadedFile, state?.hierarchyType, type, tenantId, id, baseTimeOut?.["HCM-ADMIN-CONSOLE"], { source: "microplan" } );

The error description is shown in error details.

On Submit:

The action is set to create for the payload for /project-factory/v1/data/_create

The page goes

End Point

Roles

/project-factory/v1/data/_create

MICROPLAN_ADMIN

Delete File:

When the delete button is clicked, the uploaded file is deleted.

DIGIT-Frontend/health/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/hooks/useResourceData.js at console · egovernments/DIGIT-FrontendGitHub
Logo