Sanitation
PlatformDomainsAcademyDesign SystemFeedback
v1.3.1
v1.3.1
  • Introducing DIGIT Sanitation
    • Roadmap
    • Who can use DIGIT Sanitation?
      • Field Research
  • Platform
    • Features
    • Release Notes
      • Test Cases
      • Service Build Update
        • Release Builds for DIGIT 2.8
      • MDMS Configuration Updates
      • Test Cases for Urban-Rural Convergence
      • Localisation
      • Impel Release Notes
    • Architecture
    • Installation
    • Setup
      • On AWS
    • Operations Guide
    • Development Guide
      • Backend Developer Guide
      • UI Developer Guide
    • Source Code
  • Product
    • Faecal Sludge Management (FSM)
      • Features
      • Sanitation Actors & Interactions
      • User Interface Design
      • FSM Core Service Configuration
        • FSM Implementation Configuration
        • FSM Calculator
        • FSM Vendor Registry
          • Workflow Service
            • Configuring Workflows For New Product/Entity
            • Setting Up Workflows
            • Workflow 2.0 Configuration
          • User Service
            • User Data Encryption Promotion
            • Encryption Client Library
          • API Contract
        • FSM Vehicle Registry
        • Legacy/Re-Indexing the FSM Data
        • FSM UI Docs
          • FSM Citizen UI
          • FSM Employee UI
          • FSM DSO UI
          • FSM FSTPO UI
        • FSM-DSS Technical Documentation
      • FSM User Manual
        • FSM Citizen User Manual
        • FSM Employee User Manual
          • Manage Vendor, Driver and Vehicle Details
        • DSO User Manual
        • Septage Treatment Plant Operator User Manual
      • Test Cases
      • FSM UI/UX Audit
      • FSM Functional Specification
      • FSM Technical Specification
        • Vehicle Technical Specification
        • Vendor Technical Specification
        • Calculator Technical Specification
      • FSM Release Notes
      • Training
  • Programme
    • Functional Customisation
      • Urban-Rural Convergence
    • Technical Customisation
    • Technical Specification: Urban-Rural Convergence
    • Standard Operating Procedure (SOP)
    • Program Rollout Plan
    • Adoption Metrics
    • Implementation Plan
    • Implementation Guide
      • General FSM Implementation Activities
    • Implementation Checklist
  • COMMUNITY
    • Contribute
    • Issues
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
  • Stepper Information
  • Service Request Screen

Was this helpful?

Export as PDF
  1. Product
  2. Faecal Sludge Management (FSM)
  3. FSM Core Service Configuration
  4. FSM UI Docs

FSM Citizen UI

Last updated 1 year ago

Was this helpful?

There are two new updates introduced in FSM v1.2.1 while creating a new application - Stepper Information and Vehicle Capacity Selection in the Service Request Screen.

Stepper Information

We are introducing stepper information in FSM while creating an application from the citizen side so that they have visibility on how many steps they need to go over to submit details regarding their tank.

Technical Implementations Details:

TLTimelineInFSM.js file is the common component and used for rendering the stepper information. The path of the file is:

frontend/micro-ui/web/micro-ui-internals/packages/modules/fsm/src/components/TLTimelineInFSM.js

The code snippets for defining the steps present in FSM application under case “APPLY”:

The code snippets to render the stepper information in each screen using the timeline component:

Service Request Screen

Citizens can now select vehicle capacity along with the number of trips required while creating an application. If nothing is selected, we will proceed by taking the minimum vehicle capacity available with the number of trips.

Technical Implementation Details:

Code path: frontend/micro-ui/web/micro-ui-internals/packages/modules/fsm/src/pageComponents/SelectTripNo.js

The code snippet for rendering the Vehicle Capacity field in Service Request screen:

<CardText> {t("ES_VEHICLE CAPACITY")} </CardText>
 <RadioOrSelect
    options={vehicleMenu?.map((vehicle) => ({ ...vehicle, label: vehicle.capacity }))}
    selectedOption={vehicleCapacity}
    optionKey="capacity"
    onSelect={selectVehicle}
    optionCardStyles={{ zIndex: "60" }}
    t={t}
    isMandatory={config.isMandatory}isDropDown={true}
/>

The code snippet for fetching the vehicles available under all DSO:

const allVehicles = dsoData.reduce((acc, curr) => {
  return curr.vehicles && curr.vehicles.length ? acc.concat(curr.vehicles) : acc;
}, []);
const cpacityMenu = Array.from(new Set(allVehicles.map((a) => a.capacity)))
    .map((capacity) => allVehicles.find((a) => a.capacity === capacity));

The code snippet for setting the default vehicle capacity to minimum:

using Timeline component to render the stepper Information in each screen provided with step number in currentStep.