This screen enables employees to update consumer details.

Users are redirected to this screen/page when they click on the Update Consumer Details card.

Link

→ {base url}/mgramseva/home/consumersearchupdate?Mode=update

→ {base url}/mgramseva/home/consumersearchresult

It redirects to Search Connection Page in update mode where users enter specific consumer details to search for consumers. The search result screen has the Edit Consumer button. Clicking on this button navigates the users to the Update Consumer screen.

Field Validations

Note: All fields are validated on Submit apart from the phone number which gets validated on change.

API Details

Components utilised from Widgets Library

Enables employees to create new Consumers or Connections - The process of onboarding the end-users.

Link

→ {base url}/mgramseva/home/consumercreate

The Create Consumer card is available on the home screen as per the defined user role.

Click on the Consumer Create card navigates the user to the consumer creation screen.

Users enter the required details for the creation of a consumer.

If a user logs in for the first time then a walkthrough is populated following the same logic as in the home screen.

File Path

Primary Files -

punjab-mgramseva/WalkFlowContainer.dart at develop · egovernments/punjab-mgramseva

punjab-mgramseva/walkthrough.dart at develop · egovernments/punjab-mgramseva

Note: All fields are validated on Submit except the Phone number which gets validated on change.

API Details

Process Details

Consumer creation involves 2 sequential processes

1. Property Creation

2. Water connection Creation

After creating a property, the Property ID is linked to the WaterConnection Request JSON.

Water connection creation is of two types:

A metered connection that requires Meter ID and meter installation Date/ Last Meter Reading Date and an optional field to capture meter reading.

Non-Metered Connection which requires the last billing cycle as mandatory params captured in the field as shown below.

Users can switch between connection types by selecting a desired value from the Service Type DropDown.

Advance and Penalty

• For consumers, users can give either Advance or Arrears along with a Penalty by selecting the respective option using the radio buttons. If a user selects Advance, the field is shown or else Arrears and Penalty will be shown where the user can enter the required amount.

• The radio button “Advance” will be displayed only if the config flag “Advance enabled” is activated in the MDMS billing service.

• The “Penalty” field (displayed along with arrears) on selecting the Arrears radio button, will be displayed only if the config flag “Penalty enabled” is activated in the MDMS billing service. The user will be able to see the arrears field and can enter the arrears amount.

Logic Implemented For Advance

billing-service/demand/_search API is used for calculating the advance amount for the current bill. We can get the advance amount if taxHeadMasterCode contains 'WS_ADVANCE_CARRYFORWARD'. Here we have two properties - collection amount and tax amount. The tax amount is the advance amount that is added to the system and the collection amount is how much we utilised from the total advance amount. We can get the current advance from the taxAmount - collectionAmount

Logic Implemented For Time Penalty

billing-service/demand/_search API is used to calculate the Penalty amount. We can get the penalty amount if taxHeadMasterCode contains 'WS_TIME_ADHOC_PENALTY'. We get the penalty amount from the tax amount property.

The due date is calculated by adding the billexpirtyDate days with the demand generation date.

Logic Implemented For First Demand Penalty

If it is the first demand and it has the taxHeadMasterCode 10201, we show the Penalty placeholder in the bill details.

Role Access Mapping

    case Routes.CONSUMER_CREATE:
        return ['GP_ADMIN', 'SUPERUSER'];

File Path

Model →

View →

Controller →

Components utilised from the Widgets Library