Fire NOC - Create

Objecticve

This feature is developed to apply for new NOC certificate. User has to provide various information regarding property and the owner and the location of the property, build type etc. User has to upload supportive documents. Once the application registered successfully it goes through various phases such as Verification, Field Inspection, Pay etc.

Technical Implementation Details

When user tries to create new NOC application, a popup comes upfront before navigating to the creation form. This popup tells about documents required to upload in the process so that user can collect those in advance.

This popup data is configurable in MDMS. On clicking Apply(citizen application) or New Application(employee application) a MDMS call is made to get the required document information. This information is passed to the Popup.

An Apply button is located at the footer of this popup. User can proceed to filing new NOC application on clicking of this apply button. The code related to this popup is written in search.js file. below is the link of the file.

https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-firenoc-dev/src/ui-config/screens/specs/fire-noc/search.js

showHideAdhocPopup method is responsible for making the required Document MDMS call and opening popup.

AdhocDialog Configuration for the required documents is as shown below. This is the component is present in the UI framework

Below is the MDMS call configuration is in the beforeInitScreen method of the search page you have to import the common util method of getRequiredDocData from the common.js file and has to call from the beforeInitScreen with the required document as mention in the image below.

For More details please refer to the required documents popup implementation documents file.

Link: Required documents dialog implementation


Apply for Fire NOC application divided into four forms. The configuration related to all these forms is written in apply.js file.

https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-firenoc-dev/src/ui-config/screens/specs/fire-noc/apply.js

NOC Details

NOC details is the first step. It has a card which displays two options: New and Provisional. User has to select atleast one option out of these two. Below is the link of configuration for NOC Details card.

https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-firenoc-dev/src/ui-config/screens/specs/fire-noc/applyResource/nocDetails.js

Property Details

Property details is the second step where user has to fill all the required details related to property for which Fire NOC application is being created. This step has two cards i.e. Property Details and Property Location Details.

Property Details card has requires information to fill like

Single Buildings / Multiple Buildings

Name of building

Building Usage Type

etc.

The configuration for this card is written in below file.

https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-firenoc-dev/src/ui-config/screens/specs/fire-noc/applyResource/propertyDetails.js

Property Location details asks the details about the city, street, mohalla, pincode etc where property is situated. The configuration for this card is written in below file.

https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-firenoc-dev/src/ui-config/screens/specs/fire-noc/applyResource/propertyLocationDetails.js

Applicant Details

This is the third step in the process of applying Fire NOC certificate. Applicant details basically asks information about the owner of the property. Below is the file for configuration of this step.

https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-firenoc-dev/src/ui-config/screens/specs/fire-noc/applyResource/applicantDetails.js

Before navigating to the next step i.e. Document upload screen, the NOC application create request has been made and after successful creation of NOC file user is being navigated to documents upload screen.

Documents

Documents screen is the fourth step in the process. User can upload all the relevant documents asked while applying for the certificate. Identity proof and address proof documents are mandatory and rest of the documents are configurable and can be made mandatory or optional as per requirement. Below file holds all the required configuration for this screen.

https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-firenoc-dev/src/ui-config/screens/specs/fire-noc/applyResource/documentDetails.js

After successfully uploading the documents, the next step is summary page. User can see all the information entered while applying along with total amount that user has to pay for this application process. User has options to edit the information of each section. Upon clicking of edit icon user will navigate to respective section with all the data pre-filled. Below is the file contains all the required configuration of this screen.

https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-firenoc-dev/src/ui-config/screens/specs/fire-noc/summary.js

Submit

Once user clicks on submit button, user navigates to acknowledgement screen stating that the application submitted successfully. Below is the acknowledgement configuration file.

https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-firenoc-dev/src/ui-config/screens/specs/fire-noc/acknowledgement.js

 

Sendback to Citizen ( from Release V2.4)

Sendback Feature from the workflow was enabled in firenoc applications , so Employees get an option from the Workflow for a particular state to sendback to citizen .
so citizen gets a notification to resubmit the application .

Citizen edits the Application and resubmits the same Application. so it goes into regular workflow.

 

API Call Role Action mapping:

S. No.

API

Action id

Roles

S. No.

API

Action id

Roles

1

/egov-mdms-service/v1/_search

954

CITIZEN

2

/localization/messages/v1/_search

1531

CITIZEN

3

/egov-location/location/v11/boundarys/_search

1429

CITIZEN

4

/firenoc-services/v1/_create

1797

NOC_CEMP,CITIZEN,

5

/filestore/v1/files/url

1528

,CITIZEN

6

/billing-service/bill/v2/_fetchbill

1862

CITIZEN

7

/firenoc-services/v1/_update

1798

NOC_CEMP,CITIZEN,NOC_DOC_VERIFIER,NOC_FIELD_INSPECTOR,NOC_APPROVER,

 

Â