Overview

To provide users with the bill details and the options to cancel the bill.

Workflow Details

Implementation Details

The screen development file is available in the egov-abg-dev folder within the below link:

The details of the Bill are fetched by calling BillingService fetchBill API and the Consumer.No is used in the query param.

FetchBill API returns the Bill Object which contains all the details about the bill including Billing Period, Due Amount, Due Date, and information about the Tax, Cess, Rebate, and Penalty applied to this bill.

NextStep - On clicking on the next step, the screen navigates to the cancel bill screen. The user must select the option that best states the reason for bill cancellation. More details for the cancel bill screen is available on this page - Cancel Bill

API Call Role Action Mapping

Overview

Once the user logs in with WS_CEMP or SW_CEMP roles the BillGenie tree option is available on the left panel of the screen.

Workflow Details

Clicking on the BillGenie displays two options as seen in the screenshot below.

Click on the Bill Cancellation option. This routes the user to the search bill screen.

Search Bill

Objective: This option allows employees to search for active bills, download bills, or cancel bills.

For instance, a bill can be cancelled if the tax head information is entered wrong in a bill.

Route - mSeva

Technical Implementation

• Initial MDMS call is made on page load

Example:

{
   "code": "WS",
   "headerBandLabel": "PAYMENT_COMMON_CONSUMER_CODE",
   "pdfModule":"WNS",
   "receiptKey": "ws-onetime-receipt",
   "cancelReceipt":false,
   "cancelBill": true,
   "billKey": "ws-bill",
   "arrears": true,
   "buttons": [
    {
      "label": "COMMON_BUTTON_HOME",
      "citizenUrl": "/wns-citizen/home",
      "employeeUrl": "/wns/search"
    }
  ]
}

Table Structure

• MUIDataTable is used to implement the table component.

• Every column entry is treated as an object.

{
   labelName: "Bill No.",
   labelKey: "ABG_COMMON_TABLE_COL_BILL_NO"
}

• Any customizations at column level are done through the customBodyRender hook available with the option property of the columns.

Data fetch, load and render

Once the data is fetched using egov-searcher/bill-genie/billswithaddranduser/_get API, the returned data is formatted and dispatched to redux.

As seen in the above screenshot, the data is assigned to a specific path inside props.

The table component now fetches the data from its props as shown below.

To cancel bills, employees have to click on the Cancel Bill option. The system navigates to the Bill Details page that displays the bill amount and other details. The bill can be cancelled from this page.

For bill details refer to the document here - Bill Details.

API Used

1. egov-mdms-service/v1/_search,

2. egov-searcher/bill-genie/billswithaddranduser/_get

Role Action Mapping

Overview

To provide users with the option to select cancel reasons and the options to cancel the bill.

Workflow Details

Implementation Details

The screen development files are available in the egov-abg-dev folder within the below-mentioned link.

The reasons for bill cancellation options are fetched from the MDMS service.

PREVIOUS STEP: Clicking on the Previous Step option redirects users to the bill details screen.

Cancel Bill

Clicking on the cancel bill option triggers the cancel bill API (billing-service/bill/v2/_cancelbill ). Once the API call is successful it routes to the acknowledgement screen.

The Next Step button file is available in the below-mentioned file path.

Acknowledgement Screen

Localisation

For localisation, the “rainmaker-ws” and “rainmaker-abg” modules are re-used. In case they are any new keys, these are added under “rainmaker-abg”.

API Call Role Action Mapping