OBPS EDCR /OC-EDCR

Overview

To provide the facility for the stakeholder users to create and submit the eDCR Application. Stakeholders include Architects, Builders.....etc.

Workflow Details

File Path: https://github.com/egovernments/DIGIT-Dev/blob/develop/frontend/micro-ui/web/micro-ui-internals/packages/modules/obps/src/Module.js

Apply For eDCR Application

Users can generate and submit the eDCR application by clicking on the “Registered Architect Login”, through which only registered stakeholders (Stakeholders including Architect, Builder.....etc) can log in. Other users will not be able to proceed further.

Stakeholders can generate the eDCR scrutiny number by clicking on Plan Scrutiny For New Construction link. They can add all the information, according to the questions asked, after filling in the information in the eDCR form click on the Submit button. This triggers the Create API call. The success or failure of the API routes the user to the acknowledgement screen. If eDCR API is Success => it routes to the acknowledgement screen. Stakeholders can see the eDCR number, application number and download option. If eDCR API is Failure => it routes to the acknowledgement screen. Stakeholders can see the application number and download option but not eDCR number.

File Path: https://github.com/egovernments/DIGIT-Dev/blob/develop/frontend/micro-ui/web/micro-ui-internals/packages/modules/obps/src/pages/citizen/home.js

eDCR Scrutiny

Users need to provide their City, Applicant Name and Upload dxf file in order to generate the eDCR number.

File Path: https://github.com/egovernments/DIGIT-Dev/blob/develop/frontend/micro-ui/web/micro-ui-internals/packages/modules/obps/src/pageComponents/EDCRForm.js

Success Screen

The acknowledgement Page gets displayed after the success of eDCR creates call. Here stakeholders can see -

eDCR Number
Application Number
Download option for downloading the scrutiny report
Apply for the building plan permit button for creating the BPA application( OBPS BPA/OCBPA - ARCHITECT )
Go Back To Home button to navigate to the home page

File Path: https://github.com/egovernments/DIGIT-Dev/blob/develop/frontend/micro-ui/web/micro-ui-internals/packages/modules/obps/src/pages/citizen/EDCR/EDCRAcknowledgement.js

Failure Screen

The failure acknowledgement page gets displayed if the eDCR Create API call results in failure due to some reason. Here stakeholders can see -

Application Number
Download option for downloading the scrutiny report
Go Back To Home button to navigate back to the home page

File Path: https://github.com/egovernments/DIGIT-Dev/blob/develop/frontend/micro-ui/web/micro-ui-internals/packages/modules/obps/src/pages/citizen/EDCR/EDCRAcknowledgement.js

Applying for OC eDCR Application

Users can apply for the OC eDCR application by clicking on the Registered Architect Login link through which only registered stakeholders (Stakeholders including Architect, Builder.....etc) can log in. Other users will not be able to proceed further. Stakeholders can generate the OC eDCR scrutiny number by clicking on the OC Plan Scrutiny for new Construction link. They can add all the information, according to the question asked, and after filling in the information in the eDCR form steps clicking on the Submit button triggers the Create API call. Depending on the success or failure of the API call users are routed to the acknowledgement screen.

The Permit Date and Permit Number of BPA are required to generate the OC eDCR. The permit details enable the search for specific BPA records followed by a search for the OLD eDCR details (BPA eDCR). These details are used to generate the OC eDCR Number.

1. Data Required

Click on OC Plan Scrutiny for new Construction link. This routes the user to the Data Required screen and the screen provides information about the data required to generate OC eDCR number.

Clicking on the Next button routes the user to the OC eDCR scrutiny details screen.

File Path: https://github.com/egovernments/DIGIT-Dev/blob/develop/frontend/micro-ui/web/micro-ui-internals/packages/modules/obps/src/pageComponents/OCEDCRDocsRequired.js

2. OC eDCR Scrutiny Details

After entering the permit number and permit date, stakeholders need to click the Search button. Internally BPA and eDCR search fetches the required data.

The BPA and eDCR search results display all details regarding the application along with the proceed for OC scrutiny button on a separate card.

On clicking the Procced for OC scrutiny button users are redirected to the Upload OC Plan Diagram screen.

File Path:

https://github.com/egovernments/DIGIT-Dev/blob/develop/frontend/micro-ui/web/micro-ui-internals/packages/modules/obps/src/pageComponents/OCeDCRScrutiny.js

3. Upload OC Plan Diagram

Users have to upload the dxf file and click on the Submit button that triggers the Create API call.

File Path:

https://github.com/egovernments/DIGIT-Dev/blob/develop/frontend/micro-ui/web/micro-ui-internals/packages/modules/obps/src/pageComponents/OCUploadPlanDiagram.js

Success Screen

The Success Acknowledgement Page gets displayed after a successful eDCR create call. Here stakeholders can see -

eDCR Number
Application Number
Download option, for downloading the scrutiny report
Apply for OC For New Construction button, for creating the BPA application( OBPS BPA/OCBPA - ARCHITECT )
Go Back To Home button to navigate back to the home screen

Creating preview...

File Path:

https://github.com/egovernments/DIGIT-Dev/blob/develop/frontend/micro-ui/web/micro-ui-internals/packages/modules/obps/src/pages/citizen/OCEDCR/EDCRAcknowledgement.js

Failure Screen

The Failure Acknowledgement Page gets displayed in case the eDCR create call fails for some reason. Here stakeholders can see -

Application Number
Download option, for downloading the scrutiny report
Go Back To Home button to navigate back to the home screen

Creating preview...

File Path:

https://github.com/egovernments/DIGIT-Dev/blob/develop/frontend/micro-ui/web/micro-ui-internals/packages/modules/obps/src/pages/citizen/OCEDCR/EDCRAcknowledgement.js

Technical Implementation

All screens have been developed using the new-UI structure followed previously in FSM, PGR, PT and TL.

The link for the eDCR & OC eDCR Main Index is given below. It helps in understanding the starting point of the flow:

Config responsible for the routing of each flow

eDCR:

https://github.com/egovernments/DIGIT-Dev/blob/develop/frontend/micro-ui/web/micro-ui-internals/packages/modules/obps/src/config/edcrConfig.js

OC eDCR:

https://github.com/egovernments/DIGIT-Dev/blob/develop/frontend/micro-ui/web/micro-ui-internals/packages/modules/obps/src/config/ocEdcrConfig.js

MDMS Data

Throughout the flow, a few of the page data is imported from MDMS. Following is the list of pages that are using MDMS data. These pages .js files can be found under page components.

PageComponent

MDMS Detail

Module Details Name

Master Detail Name

EDCRForm

City list

tenant

citymodule

For calling the MDMS data React Hooks has been used, so that it can be shared across modules. Below is the little code snippet for the call used for MDMS.

  const { data:homePageUrlLinks , isLoading: homePageUrlLinksLoading } = Digit.Hooks.obps.useMDMS(stateCode, "BPA", ["homePageUrlLinks"]);

Localization

Localization keys are added under the ‘rainmaker-bpa’ locale module. In future, if any new labels are implemented in the OBPS - Architect (Citizen) they should also be pushed to the locale DB under rainmaker-bpa locale module. Below is an example of a few locale labels.