Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
From the FSM Registry screen, an admin can create the sanitation worker page using the add option.
Admins can fill the "Add Sanitation Worker" form to create sanitation workers in the system.
Admins can fill details such as Mobile Number, Name, Date of Birth, Photograph, Address, Skills, etc.
The mobile number has to be unique, otherwise a validation error will be shown and the user will not be able to submit the form.
There is a role details section at the bottom which is non-mandatory.
Using this role details section, an admin can specify the functional roles that this worker has, such as driver, helper, etc.
By default, all workers will have a generic SANITATION_WORKER role.
The functional roles have been mapped to the system roles using this master.
Currently, driver and helper functional roles are present in the system. Both are created as citizens.
Sanitation workers can have multiple functional roles, that is, they can be a driver as well as a helper.
Employer has two options: ULB and private vendor. This specifies the current employer of this worker. This can be changed in Edit Sanitation Worker.
Sanitation workers can also be tagged to vendors on this page based on whether the employer type is a ULB or a private vendor. This implies that the vendor select dropdown is populated based on the employer type.
Vendors can be a ULB or a private vendor. This is specified in this master.
After submitting the necessary details, an admin can click on submit and a response page is shown.
We will hit the "/individual/v1/_create" endpoint to create sanitation workers
The curl is given below:
If a vendor is selected while creating a sanitation worker, we are calling this endpoint "/vendor/v1/_update" to tag this worker to a vendor after the individual create has responded with success.
The curl is given below:
Role-action mapping is done for the above two API endpoints for the following role:
This section includes the following:
Sanitation Worker UI Documentation
As part of FSM v1.4, sanitation worker related features/screens have been added to the FSM UI. These screens are accessible with current FSM related roles such as FSM_Admin, Creator, Editor, Collector, etc.
The following screens are available for the sanitation worker UI:
From the FSM card in the home screen, there is a link to the "FSM Registry". FSM admins have access to manage the FSM Registry.
The FSM Registry is multi-tabbed search screen.
Using the FSM Registry, FSM admins can manage vehicles, vendors, and sanitation workers in the system.
There are three tabs available, that is, Vendor, Vehicle, Sanitation Worker.
Vendor and vehicle were already there in FSM 1.3. The Sanitation Worker tab have now been added.
This tab shows a list of sanitation workers in the system.
Admins can search for sanitation workers with the sanitation worker ID, name, and mobile number.
Admins can disable/enable sanitation workers.
There is a vendor dropdown available to each sanitation worker which shows a list of vendors that they can be tagged to. An admin can tag a sanitation worker to a vendor using that dropdown.
Vendors are listed based on agency type. Currently, there are two types of agency: ULB and private vendor.
If a sanitation worker is employed by the ULB, then the dropdown will show vendors whose agency type is ULB, and likewise for private vendors.
We are using the individual registry to create, update, and disable sanitation workers.
If an admin disables a sanitation worker already tagged to a vendor, then that vendor tagging is also disabled. This implies that the if an admin enables that user, we need to tag the vendor again.
There is an 'Add' option at the top right of this screen using which admins can create vehicle, vendor, and sanitation worker.
Note: There is a SANITATION_WORKER role in the system. All sanitation workers created through the system will have this role.
We will hit hit the individual search API to get a list of sanitation workers using the SANITATION_WORKER system role.
The curl is given below:
We will hit the "vendor/v1/_search" endpoint to get a list of vendors.
The curl is given below:
We will hit the "/vendor/v1/_update" to update tagging of sanitation workers to vendors.
The curl is given below:
We will utilise the individual update API for disabling/enabling sanitation workers.
The curl is given below:
Role-action mapping is done for the above mentioned API endpoints for FSM admin users with the following role code:
From the Screen Admin can search for Sanitation worker and go to it's .
From the , admin can click on "Edit" action
Admin will be redirected to the edit sanitation worker page
This page contains the same form as . The only difference is all the fields are auto populated based on the worker that we are updating
Admin can update all the details except Sanitation Worker Id and Name
Clicking on Submit will show a response screen saying Sanitation Worker details updated successfully
We are hitting Individual Update endpoint "/individual/v1/_update" to update the details of a Sanitation worker
Refer the curl below:
If during update, vendor details are changed then along with individual update we are calling vendor update "/vendor/v1/_update"
Refer the curl below
Role action mapping is done for the above 2 endpoints for "FSM_ADMIN" role
Clicking on a particular ID takes the user to the .
The employer selection of a sanitation worker can be done while .
In FSM 1.3 EDITOR users could take workflow actions and assign drivers to FSM Applications now we have changed that assignment. Now EDITOR users can assign a driver and multiple helpers to an FSM Application. And both driver and helper are Sanitation workers now.
EDITOR User role code:
Login with EDITOR user and go to FSM Inbox
From Inbox choose any application whose status is pending for DSO assignment
Go to the application details page from inbox
From the Action bar options click on "Assign Vehicle and Sanitation Workers"
A Popup window will open which looks like the following
We have two new options here, Assign Driver and Assign Sanitation Worker
Assign Driver is single select and mandatory
Assign Sanitation worker is multi-select and we can assign multiple Sanitation workers. Assigning worker is non mandatory though
Both these dropdowns are searchable i.e., EDITOR can search by name and Sanitation worker ID
These dropdowns are populated based on the vendor that is tagged to the current FSM Application.
User can click on Assign to take this action. A toast message is displayed showing the update is successful.
After this action, added Sanitation workers are displayed on the Application Details screen under DSO Details Section
To fetch FSM application details we are hitting this endpoint "/fsm/v1/_search"
Refer the below curl:
To update FSM application we are hitting this endpoint "/fsm/v1/_update"
Refer to the below curl:
To get a particular vendor data tagged to the current application we are hitting this endpoint "/vendor/v1/_search"
Refer to the below curl
Role action mapping for the above three endpoints is done for this role
From the FSM Registry page Admins can Search for a Sanitation Worker and go to it's details page by clicking on Sanitation Worker Id
This page shows all the details about a Sanitation worker
Sample Page Screenshot is given below for reference
Admin users will get an action bar at the bottom of the page which has two actions
Edit -> This takes the user to Edit Sanitation worker Page
Delete -> This calls the update Individual API and disables this user ( Soft delete)
A corresponding toast message is shown
After taking delete action page is automatically redirected to the FSM Registry
We are hitting this endpoint "/individual/v1/_search" to fetch Sanitation Worker Details
Refer the curl below:
When individual is deleted we are making use of individual update "/individual/v1/_update"
Refer to the curl below
When we delete a Sanitation worker who is tagged to a vendor we are updating the worker - vendor tagging to inactive.
Refer to the curl below:
Role Action mapping is done for the above three endpoints for FSM_ADMIN role
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.
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.
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:
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.
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:
The code snippet for fetching the vehicles available under all DSO:
The code snippet for setting the default vehicle capacity to minimum:
In FSTP, we are trying to decouple the vehicle dispose from the FSM application. Whether vehicle is attached to any FSM application or not, we allow the vehicle to dispose in the FSTP plant.
After logging as a FSTP user, we have now the home button option:
Code changes path are:
DIGIT-Dev/frontend/micro-ui/web/micro-ui-internals/packages/modules/fsm/src/components/FsmCard.js
After moving into “home” option, an FSTP user can choose from the following options:
FSTP can choose Add Vehicle Log option if he/she wants to check whether a vehicle is linked to any application and dispose.
FSTP can choose Inbox if he/she wants to check all the applications that are is ready to dispose.
The path for code:
frontend/micro-ui/web/micro-ui-internals/packages/modules/fsm/src/pages/employee/FstpOperations.js
The code snippet for populating the options:
The code snippet for rendering the icon:
ULBHomeCard.js is the common component used to populate options in the screen.
The paths:
frontend/micro-ui/web/micro-ui-internals/packages/react-components/src/atoms/ULBHomeCard.js
FSTP can add vehicle log using vehicle number (in proper format with spaces, e.g. AB 00 CD 1234). An improper format will throw an error.
The path for the code:
frontend/micro-ui/web/micro-ui-internals/packages/modules/fsm/src/pages/employee/FstpAddVehicle.js
The code snippet for populating the add vehicle log field and its validation:
The code snippet for rendering the screen:
After entering the vehicle number in the add vehicle log screen, we are fetching the FSM application, which is linked to that specific vehicle number. The data is rendered as shown below:
The path for the code:
frontend/micro-ui/web/micro-ui-internals/packages/modules/fsm/src/pages/employee/FstpServiceRequest.js
The code snippets for fetching the FSM application linked to vehicle number:
Fetching the vehicle Id using vehicle number
Fetching the vehicle log using vehicle Id
Extracting out the FSM application number from vehicle log:
Fetching the FSM application details using FSM application number
The code snippets to render the data:
Mobile view
Desktop view
After selecting the application, FSTPO can dispose the vehicle log in the vehicle log screen.
Additional details and attachment fields are introduced in new updates in FSM v1.2.1 .
The screen for the existing vehicle log:
The screen for new vehicle log if no application is found for vehicle is shown below. FSTPO can dispose the new vehicle log by providing all the details below.
The path for the code:
frontend/micro-ui/web/micro-ui-internals/packages/modules/fsm/src/pages/employee/FstpOperatorDetails.js
The code snippet for additional details and attachments field:
For new vehicle log:
The code snippets to render input field for new vehicle log:
There are three main updates in FSM v1.2.1 for employee UI:
Application timeline
Photo viewed by employee/DSO
Payment mode while completing request
An employee can see the application status in application timeline with provider details.
The path for the code:
frontend/micro-ui/web/micro-ui-internals/packages/modules/fsm/src/pages/employee/ApplicationDetails/index.js
The code snippet to render application timeline:
The code snippet for extracting the provider info for each status:
An employee/DSO can view the photo uploaded by the employee/DSO in complete request action.
The path for the code:
frontend/micro-ui/web/micro-ui-internals/packages/modules/fsm/src/pages/employee/ApplicationDetails/index.js
The code snippets to render the field:
ViewImages.js are the common component used to fetch and render the Image file id. The path is shown below:
frontend/micro-ui/web/micro-ui-internals/packages/modules/fsm/src/components/ViewImages.js
An employee has to select the payment mode while completing the request.
File path:
frontend/micro-ui/web/micro-ui-internals/packages/modules/fsm/src/pages/employee/ApplicationDetails/config/CompleteApplication.js
The code snippet to render the field.
MDMS file fetch for payment mode:
Desludging operators (DSO) can be registered via a user interface (UI) available to the urban local body (ULB) admin. Once created, multiple vehicles and drivers can be mapped to a DSO. DSOs can also be enabled/disabled in the system.
Desludging operators will have the following details:
Drivers can be registered via a UI available to the ULB admin. Once created, a driver can be mapped to a DSO. Drivers can also be enabled/disabled in the system.
Driver operators will have the following details:
Vehicles can be registered via a UI available to the ULB admin. Once created, a vehicle can be mapped to a DSO. Vehicles can also be enabled/disabled in the system.
Vehicles operators will have the following details:
The citizen or the ULB official can apply for a desludging request.
Application Channel
Citizens can apply online using the web application.
Citizens can walk into a ULB and submit a request to the counter operator, who then creates an application on behalf of the citizen online.
Citizens can call the ULB and request for a desludging operation, which can then be transformed into an online application by the ULB official.
Application Submission
Desludging applications can be created by a citizen.
Desludging application requests can be created by a ULB official on behalf of a citizen.
- If the application is created by a ULB official, then capture the channel in which the request was received. It will be an additional field in the UI to capture the channel.
Service Request Fee
Service request fee is calculated as a multiplier of the amount per trip defined in the billing slab table (based on property type, sub-type, whether it is a slum, vehicle capacity) and the number of trips.
For certain combinations with the above parameters, the pricing can be set at zero. In such cases, demand will not be generated.
ULBs can configure a minimum advance payment to be collected before starting a request. This can either be a fixed value (starting from 0) or a percentage (ranging from 0-100). Citizens will be able to make a payment above the minimum advance amount, and below the total trip amount as an advance payment.
Payment: Online/Cash Counter
Citizens can make both the advance and balance payments online.
Citizens can make both the advance and balance payments at the ULB counter.
Payment receipts will be generated and sent across via SMS. They can be downloaded at the citizen and ULB interfaces.
When a service request is received by a ULB official, he/she can do the following:
- Search and assign a DSO to the application request.
- Cancel the application with remarks.
- Update the application request with the number of trips required to empty the septic tank or Pit and the vehicle details.
- Change the DSO from an application request if the assigned DSO is not available.
- Update the status of the request as completed, post desludging.
- View past records of requests and service delivery.
Cancellation of application
A citizen or a ULB official can cancel the application online.
Citizens can cancel it only if the DSO is not assigned to the service request.
Application cannot be cancelled if the payment is made already.
ULB officials can cancel it only if the service is not completed by the DSO.
SMS and Email Updates
SMS and email updates are sent on every necessary process of the entire process flow.
A DSO should get notified about the request that is assigned to him/her. On receiving the request, the following actions can be taken:
- View the request.
- Assign requests to a vehicle.
- Update the number of trips.
- Flag a request ready for disposal.
- Close the request post desludging.
One DSO cannot see the details of the other DSO or the request assigned to the other DSOs.
Citizens can provide feedback on the desludging request:
There will be an option to rate the service provided with comments.
There will be an option for citizens to update whether safety equipment is used by the sanitary workers during the operation.
Plant operators can do the following:
View the list of desludging operations for a day. Since an application may have multiple trips, the plant operator will view multiple line items against an application in the inbox.
Update the Vehicle entry log against an application request with the details like:
- Date and time of entry.
- Volume of sludge dumped at the plant.
If a vehicle without a corresponding request arrives at the FSTP, the FSTP can record the vehicle entry.
The DSO can also decline an incoming vehicle.
Citizens can provide feedback on the desludging request:
Rate the service provided (1-5 stars).
Multi-select to update whether safety equipment is used by the sanitary workers during the operation.
List of PDFs
Acknowledgement Recepit: Confirming receipt of desludging receipts.
Payment receipts: Multiple payment receipts based on the payments made.
Search criteria
Search result
Search criteria
Search result
Search criteria
Search result
Filter criteria
Selection criteria
Other functionalities:
Share via:
a. Image: Downloads image
b. Whatsapp: Image shared via Whatsapp
Download:
a. Image format
Advance Balance Workflow
Pay Later Workflow
Zero Price Workflow
Fetching data from the MDMS
The config can be found at CompleteApplication.js
File Path: frontend/micro-ui/web/micro-ui-internals/packages/modules/fsm/src/pages/employee/ApplicationDetails/config/CompleteApplication.js
UploadPitPhoto.js molecule is available within the molecules folder in react-components.
File Path: frontend/micro-ui/web/micro-ui-internals/packages/react-components/src/molecules/UploadPitPhoto.js
Saving Image fileId in FSM service
The link for the MDMS changes made is given below.
RoleStatusMappping.json
Schedule Action is added for post-pay applications where DSOs can schedule the trip by entering the number of trips.
Code snippet for schedule window:
ScheduleDso.js is the file responsible for the schedule window pop up.
File path: frontend/micro-ui/web/micro-ui-internals/packages/modules/fsm/src/pages/employee/ApplicationDetails/config/ScheduleDso.js
| Type | Estimation (in hours) | Assignee | Comment | Status | Reviewed by PM | Gaps (if any) | Reviewed by Antriksh |
|---|
Field Name | Type | Mandatory | Editable (Y/N) | Unique within a ULB (Y/N) |
Vendor name | Free text | Y | N | N |
Gender | Array | Y | N | N |
DOB | Date | N | Y | N |
Email address | Free text (Email format) | N | Y | N |
Mobile number | Number | Y | N | Y |
Door number | Free text | N | Y | N |
Plot number | Free text | N | Y | N |
Building name | Free text | N | Y | N |
Street | Free text | N | Y | N |
Pincode | Free text | N | Y | N |
City | Array | Y | N | N |
Locality/mohalla | Array | Y | N | N |
Landmark | Free text | N | Y | N |
Additional Details | Free text | N | Y | N |
Status | Binary | Y | Y | N |
Field name | Type | Mandatory | Editable (Y/N) | Unique within a ULB (Y/N) |
Driver name | Free text | Y | N | N |
Driver license number | Free text (Validation on the license format) | Y | Y | N |
Gender | Array | N | Y | N |
DOB | Date | N | Y | N |
Email address | Free text (Email format) | N | Y | N |
Driver phone number | Number | Y | N | N |
Field name | Type | Mandatory | Editable (Y/N) | Unique within a ULB (Y/N) |
Registration number | Free Text | Y | N | Y |
Vehicle model | Array | Y | Y | N |
Vehicle type | Array | Y | Y | N |
Tank capacity | Array | Y | Y | N |
Pollution certificate valid till | Date | N | Y | N |
Insurance valid till | Date | N | Y | N |
Road tax paid till | Date | N | Y | N |
Fitness certificate valid till | Date | N | Y | N |
Vehicle owner name | Free text | Y | N | N |
Vehicle owner phone number | Number | Y | N | N |
Field name | Type | Mandatory | Editable | Comments |
Applicant name | Text | Y | N |
|
Mobile number | Numeric | Y | N |
|
Gender | Dropdown | Y | N |
|
City | Dropdown | Y
| N | As per the boundary data defined. |
Locality | Dropdown | Y | N | As per the boundary data defined. |
Whether property is in a slum | Binary | Y | N |
|
Slum name | Dropdown | Y | N | Only if the above selection is yes. List of slums per ULB to be uploaded in the system. |
Street name | Text | N | N |
|
Door house number | Text | N | N |
|
Landmark | Text | N | N |
|
Geo location | Lat-Long | N | N | As per DIGIT standards. |
Onsite sanitation type | Dropdown | N | Y | Select one from the list. |
PIT size | L*B*D in feet (This UOM might change from state to state) | N | Y | Numeric |
Property type | Dropdown | Y | N | Use the same ontology as defined in DIGIT Property Tax. |
Property sub-type | Dropdown | Y | N | Use the same ontology as defined in DIGIT Property Tax. |
Number of trips required | Numeric | Y | Y | Editable by ULB and DSO. |
Vehicle capacity | Dropdown | Y | N | Populated as per the vehicle capacities available in the particular ULB. |
Application channel | Dropdown | Y |
| Required only if the creator is a ULB official. |
Total amount | Numeric, display only | Y | N | Calculated based on the billing slabs. |
Minimum amount payable | Numeric, display only | Y | N | Displayed as per the configuration in the backend. |
Advance amount | Numeric | Y | Y |
|
Field name | Type | Required | Comments |
Volume of waste collected | Numeric | Y |
|
Field name | Type | Required | Comments |
Vehicle in-time | Time | Y |
|
Vehicle out-time | Time | Y |
|
Volume of sludge dumped | Numeric | Y |
|
Additional details | Text | N |
|
Attachments | Document/Image | N |
|
Field name | Type | Required | Comments |
Vehicle number | Alphanumeric | Y | Only unregistered vehicles in the system.
|
DSO name | Text | Y |
|
Locality | Text | Y |
|
Vehicle in-time | Time | Y |
|
Vehicle out-time | Time | Y |
|
Volume of sludge dumped | Numeric | Y |
|
Additional details | Text | N |
|
Attachments | Document/Image | N |
|
Attribute | Type | Required? | Comments |
Vehicle | UUID | Y |
|
Trip Number | Numeric | Y |
|
Volume | Numeric | Y |
|
Desludging request | UUID | Y |
|
Reason for declining | String | Y | [ “Septage Source”, “Outside operational hours”, “Under Maintenance”] |
Field name | Type | Required |
ULB name | Default | Internally pass the ULB name (Y) |
From date | Date | Y |
To date | Date | Y |
DSO name | Search | N - Auto-populate on typing a few letters. |
Application number | Application date | Current Status | DSO Name | Amount (Rs) | Date of completion |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Field name | Type | Required |
ULB name | Dropdown | Internally pass this info. |
Mohalla | Dropdown | N |
DSO | Search | N - Auto-populate on typing few characters. |
From date | Date | Y |
To date | Date | Y |
Application number/Date | Mohalla | DSO Name | Status | SLA compliance | Volume of waste collected |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Field name | Type | Comments |
ULB name | Dropdown |
|
STP/FSTP name | Dropdown | Internally pass this information: We have mapping between ULB and STP/FSTP. |
DSO name | Search | N - Auto-populate on typing a few letters. |
Vehicle number | Dropdown | Populate only if the DSO name is selected. |
From date | Date | Y |
To date | Date | Y |
Application number | DSO name /Vehicle number | Vehicle entry date | Vehicle in time | Vehicle out time | Volume of sludge dumped (L) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Field name | Type | Comments |
DDR (District name) | Dropdown |
|
ULB name | Dropdown |
|
Date range (From and to dates) | Date | Mandatory, auto-select for entire time period. |
Field Name | Type | Comments |
Denomination | Array | Choose the denominate between Cr, Lac and Unit. |
Chart name | Chart type | X Axis | Y Axis | Logic | Comments | Tooltip (if any) | Drilldown available (Y/N) |
Overview: Total requests | KPI | NA | NA | Sum of total the requests cumulated over a period of time. | Absolute number and percentage increase or decrease from previous year for the same time period. | NA | N |
Overview: Total sludge treated (in KL) | KPI | NA | NA | Sum of the total sludge deposited from registered and unregistered vehicles at the FSTP. | Absolute number and percentage increase or decrease from the previous year for the same time period. | NA | N |
Overview: Total collection | KPI | NA | NA | Sum of the total revenue collected against service delivery. | Absolute number and percentage increase or decrease from the previous year for the same time period. | NA | N |
Overview: SLA compliance | KPI | NA | NA | Average SLA compliance (percentage of requests completed within SLA). | Percentage number and percentage increase or decrease from the previous year for the same time period. | NA | N |
Overview: Citizen average rating | KPI | NA | NA | Average citizen rating (Total citizen rating/total number of applications with feedback). | Absolute number and percentage increase or decrease from the previous year for the same time period. | NA | N |
Total cumulative collection | Area chart | Month | Total collection | Cumulative collection over a period of time. |
| - Month name - Value | N |
Revenue by property type | Pie chart | NA | NA | Distribution of requests by property type. | The percentage of requests by each property type to be displayed on the chart. | Display percentage and absolute value. | N |
Top 3 performing ULBs (SLA achievement) | Percentage completion on line chart | NA | NA | Average SLA per ULB. | Top 3 to be displayed. View more options available to view the entire list of ULBs. |
| N |
Bottom 3 performing ULBs (SLA achievement) | Percentage completion on line chart | NA | NA | Average SLA per ULB | Bottom 3 to be displayed. View more options available to view the entire list of ULBs. |
| M |
FSTP - Capacity utilisation | Line chart | Percentage capacity utilisation | Time (Month) | Total waste disposed of or total capacity. | Total waste treated to be displayed below the chart heading. | - Month - Capacity utilisation (%). - Capacity utilisation (%) as compared to last year for the same month. |
|
Monthly waste collected versus monthly waste disposed off | Column chart | Waste collected and waste dumped | Time (Month) | - Sum of waste collected. - Sum of waste disposed of. |
| - Month - Waste collected (absolute number and % increase decrease as compared to last year for the same month). - Waste disposed (absolute number and % increase or decrease as compared to last year for the same month). |
|
Total request by region | Table | NA | NA | Fields: - Serial number. - District - # of open requests. - # of closed requests. - # of total requests. - Completion rate (Percentage completion). - SLA achieved: Percentage. - Total collection. | - Selection to display the number of rows in a table. - Option to move to the next and the previous pages, and display the current page number. - Search by district name. - Show filters applied, if any. |
| Drilldown on district name to ULBs mapped in the district. |
Vehicle log report | Table | NA | NA | Fields: - Serial number. - ULB. - Volume of waste collected. - Volume of waste dumped. - Capacity utilisation (percentage). - Show comparison to last year. | - Selection to display the number of rows in a table. - Option to move to the next and the previous pages, and display the current page number. - Search by district name. - Show filters applied, if any. |
|
|
Application type | Status | Roles | Action | Next state |
Desludging |
| Citizen FSM_CREATOR_EMP | Create application | Application created |
Desludging | Application created | Citizen FSM_CREATOR_EMP | Submit application | Pending for payment |
Desludging | Pending for DSO assignment | FSM_EDITOR_EMP | Reject application | Application created |
Desludging | Pending for payment | Citizen | Pay for the number of trips (may be 0 to full) | Pending for DSO assignment |
Desludging | Pending for DSO assignment | FSM_EDITOR_EMP | Assign DSO | Pending for DSO approval |
Desludging | Pending for DSO assignment | FSM_EDITOR_EMP | Return application | Application created |
Desludging | Pending for DSO assignment | FSM_EDITOR_EMP | Reassign DSO | Pending for DSO approval |
Desludging | Pending for DSO approval | DSO FSM_EDITOR_EMP | Assign Vehicle | DSO in progress |
Desludging | Pending for DSO approval | DSO FSM_EDITOR_EMP | Reject | Pending for DSO assignment |
Desludging | DSO in progress | FSM_EDITOR_EMP DSO | Update the number of trips or schedule trips | DSO in progress |
Desludging | DSO in progress | Citizen | Pay (full amount) | DSO in progress |
Desludging | DSO in progress | FSM_EDITOR_EMP DSO | Dispose | DSO in progress |
Desludging | DSO in progress | DSO FSM_EDITOR_EMP | Complete request (after collecting the total amount) | Pending citizen feedback |
Desludging | Pending citizen feedback | Citizen | Citizen provides feedback | Request completed |
Application Type | Status | Action | Roles | Next State |
VehicleTrip |
| Schedules trip | FSM_DSO | SCHEDULED |
VehicleTrip | SCHEDULED | Ready for disposal | FSM_DSO" "FSM_EDITOR_EMP | Waiting for disposal |
VehicleTrip | Waiting for disposal | Dispose | FSM_EMP_FSTPO | DISPOSED |
Application type | Status | Roles | Action | Next state |
Desludging |
| Citizen FSM_CREATOR_EMP | Create application | Application created |
Desludging | Application created | Citizen FSM_CREATOR_EMP | Submit application | Pending for DSO assignment |
Desludging | Pending for DSO assignment | FSM_EDITOR_EMP | Reject application | Application created |
Desludging | Pending for DSO assignment | FSM_EDITOR_EMP | Assign DSO | Pending for DSO approval |
Desludging | Pending for DSO assignment | FSM_EDITOR_EMP | Return application | Application created |
Desludging | Pending for DSO assignment | FSM_EDITOR_EMP | Reassign DSO | Pending for DSO approval |
Desludging | Pending for DSO approval | DSO FSM_EDITOR_EMP | Assign Vehicle | DSO in progress |
Desludging | Pending for DSO approval | DSO FSM_EDITOR_EMP | Reject | Pending for DSO assignment |
Desludging | DSO in progress | FSM_EDITOR_EMP DSO | Update the number of trips or schedule trips | DSO in progress |
Desludging | DSO in progress | Citizen | Pay (Full Amount) | DSO in progress |
Desludging | DSO in progress | FSM_EDITOR_EMP DSO | Dispose | DSO in progress |
Desludging | DSO in progress | DSO FSM_EDITOR_EMP | Complete Request (after collecting the total amount) | Pending citizen Feedback |
Desludging | Pending citizen feedback | Citizen | Citizen provides feedback | Request completed |
Application Type | Status | Action | Roles | Next state |
VehicleTrip |
| Schedules trip | FSM_DSO | SCHEDULED |
VehicleTrip | SCHEDULED | Ready for disposal | FSM_DSO" "FSM_EDITOR_EMP | Waiting for disposal |
VehicleTrip | Waiting for disposal | Dispose | FSM_EMP_FSTPO | DISPOSED |
Application type | Status | Roles | Action | Next State |
Desludging | - | Citizen FSM_CREATOR_EMP | Create application | Application created |
Desludging | Application created | Citizen FSM_CREATOR_EMP | Submit application | Pending for payment |
Desludging | Pending for DSO assignment | FSM_EDITOR_EMP | Reject application | Application created |
Desludging | Pending for DSO assignment | FSM_EDITOR_EMP | Assign DSO | Pending for DSO approval |
Desludging | Pending for DSO assignment | FSM_EDITOR_EMP | Return application | Application created |
Desludging | Pending for DSO assignment | FSM_EDITOR_EMP | Reassign DSO | Pending for DSO approval |
Desludging | Pending for DSO approval | DSO FSM_EDITOR_EMP | Assign vehicle | DSO in progress |
Desludging | Pending for DSO approval | DSO FSM_EDITOR_EMP | Reject | Pending for DSO Assignment |
Desludging | DSO in progress | FSM_EDITOR_EMP DSO | update No of trips / schedule trip | DSO in Progress |
Desludging | DSO in progress | FSM_EDITOR_EMP | Reassign DSO | Pending for DSO approval |
Desludging | DSO in progress | FSM_EDITOR_EMP DSO | Dispose | DSO in progress |
Desludging | DSO in progress | DSO FSM_EDITOR_EMP | Complete request (after collecting the total amount) | Pending citizen feedback |
Desludging | Pending citizen feedback | Citizen | Citizen provides Feedback | Request completed |
Application type | Status | Action | Roles | Next state |
VehicleTrip |
| Schedules trip | FSM_DSO | SCHEDULED |
VehicleTrip | SCHEDULED | Ready for disposal | FSM_DSO" "FSM_EDITOR_EMP | Waiting for disposal |
VehicleTrip | Waiting for disposal | Dispose | FSM_EMP_FSTPO | DISPOSED |
FSM home breadcrumb title all should align | Improvement | 2 | Done | Y | Y |
All text alignment should be left for FSM registry table | Improvement | 2 | Done | Disable button alignment, Figure our dropdown | Antriksh will share design |
The date of vehicle creation camel case needs to be fixed | Improvement | 0.5 | Done | Y |
Alignment of breadcrumbs and title should be out of the card and left | Improvement | 3 | Done | Y |
Vehicle details title and second card should be aligned | Improvement | 2 | Done | Y |
Remove the break line in the FSM details page | Improvement | 2 | Follow Design same as New Desludging Application | Done | Y | Spacing between section header, field above and field below |
(+91) in every mobile input field need to be added if it is not major changes | Improvement | 16 | 91 Should be every where there is mobile number field | Done | Some are in old format and some are in new format | Look at entire application and check where gaps are |
The rupee symbol needs to be removed from the left side and symbols should be left aligned | Improvement | 2 | Done | Rupee is still coming on the left hand side in application form | Also look at the entire application and check where gaps are |
Add vendor card need to be alligned for vehicle | Improvement | 3 | Done |
Add vendor pop-up close circle need to follow the Figma design, pop-up does not align for text properly | Improvement | 2 | Done |
Update trips, add driver, add vendor, add driver modal cancel icon need to be corrected | Improvement | 2 | Done |
Remove top padding in vendor/vehicle/driver details screen | Improvement | 2 | Done |
Vendor/driver/vehicle details screen title-breadcrumb-card should be aligned properly | Improvement | 4 | Done |
Vendor/driver/vehicle edit screen title-breadcrumb-card should be aligned properly | Improvement | Done |
Vendor/driver/vehicle edit screen title should be outside card | Improvement | Done |
Vehicle number search box in the vehicle tab should check the correct format | Improvement | 2 | Done |
HOME SCREEN REMOVE | Improvement | 2 | Done |
Pincode validation | Improvement | 16 | Done |
Roles permission for FSM inbox links are not proper | Improvement | 3 | Done |
In collector screen, error for incorrect phone number is showing as Payment_Invalid_Mobile | Localisation | 0.15 | Done |
Sorting FSM inbox should follow common inbox for vendor/driver/vehicle tab -backend | Improvement | 12 | Done |
Sorting FSM inbox should follow common inbox for vendor/driver/vehicle tab- UI | Improvement | 12 | Done |
The vendor name dropdown UI sould be according to the Figma link and align left | Improvement | 18 | Done |
Show only go back to home if has only go back to home else show take action + If only one action is present in take action, then show only the action name | Improvement | 12 | Done |
Redirection from SMS for payment, Showing as ES_PAYMENT_DETAILS_TOTAL AMOUNT and ES_PAYMENT_DETAILS_ADV_AMOUNT | Localisation | Done |
Wherever input text does not match validation, error message needs to show in real-time | Improvement | 40 | Blocker | Todo |
Change is redirected to a page in form and then the entire form restarts. Expected action: Change button should go to required page and then Next button should go back to the same page | Improvement | Common Issue in Every Module. Antriksh, Jagan and team is looking into it |
Different terminologies found for Payment Method. In the Generate Receipt page (Payment mode -> Cash, Cheque, Credit/Debit Card) where as In Complete Request Page (Payment Received -> Paid In Cash, Paid at Counter, Net Banking). | Improvement | Need Clarity on what method should be populated? |
Receipt capacity instead of type | Improvement | Dependency on Backend PDF Service | Todo |
Vehicly type and payment sections should be separate | Improvement | Dependency on Backend PDF Service | Todo |
Receipt needs to be redesigned | Dependency of Core Team. Since Receipt is a core services |
FSM registry table should be common component | Improvement | 16 | Already common component is using | Todo |
Either we can keep the option for the advanced amount and full amount in collect page for citizen, or remove the option <Tahera will get back on this | Improvement | Addressed in Frontendedback section of advance pay | Todo | Will be covering in Advance Pay Section |
Pay Now and Pay Later looks a little confusing. Check the localisation with other modules | Improvement | Addressed in Frontendedback section of advance pay | Todo | Will be covering in Advance Pay Section |
After clicking pay now, it is showing advance amount which looks a little confusing. Need to check with PO | Improvement | Addressed in Frontendedback section of advance pay | Todo | Will be covering in Advance Pay Section |
Login error message "This MobileNumber Already Register as UserName in System. Pls try Another UserName"/ Reword to "This Mobile Number Already Register in the System. Please try Another UserName" | Improvement | 1 | Core team work | Todo |
Test the entire product | Todo |
Scroll up to the field | Improvement | 12 | Todo |
Next button should be disabled when data is not filled; next button usage is currently inconsistent | Improvement |
View application screen for citizen should have data in the same format as the acknowledgement receipt | Improvement | new UI has to be developed on figma first |
