OBPS EDCR /OC-EDCR
- Vamshikrishna Kole (Unlicensed)
Objective
To provide the facility for the user which allows to create eDCR Application by the stakeholder (Stakeholder includes Architect, Builder.....etc).
Apply for eDCR Application:
User can apply for eDCR application by clicking on the “Registered Architect Login”, through which only registered stakeholder (Stakeholder includes Architect, Builder.....etc) can login other user will not be able to proceed further.
Stakeholder will generate eDCR scrutiny number by clicking on “Plan Scrutiny For New Construction” link, can add all the information, according to the question asked, after filling the information in the eDCR form submit button will enable and click on submit button create API will be called. after success/failure of api, it will route to acknowledgement screen.
If eDCR API is success => it will route to acknowledgement screen. there stakeholder can see eDCR number, application number and download option.
If eDCR API is Failure => it will route to acknowledgement screen. there stakeholder can see application number and download option but not eDCR number.
eDCR Scrutiny
User need to provide city, applicant name and upload dxf file in order to generate eDCR number.
Success Screen:
Acknowledgement Page will get displayed after success of eDCR create call, here stakeholder able to see,
eDCR Number
Application Number.
Download option for downloading the scrutiny report.
Apply for building plan permit button for creating the BPA application( OBPS BPA/OCBPA - ARCHITECT ).
Go Back To Home button for go to home.
Failure Screen:
Acknowledgement Page will get displayed after success of edcr create call, here stakeholder able to see,
Application Number.
Download option for downloading the scrutiny report.
Go Back To Home button for go to home.
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:
User can apply for OC eDCR application by clicking on the “Registered Architect Login”, through which only registered stakeholder (Stakeholder includes Architect, Builder.....etc) can login other user will not be able to proceed further.
Stakeholder will generate OC eDCR scrutiny number by clicking on “OC Plan Scrutiny for new Construction” link, can add all the information, according to the question asked, after filling the information in the edcr form steps, submit button will enable and click on submit button create API will be called. after success/failure of api, it will route to acknowledgement screen.
For creating OC eDCR, we need permit date and permit number(approval number) of BPA. by using the permit date and permit number we are calling the bpa search, after success of that bpa search we are calling the eDCR search for OLD eDCR details (BPA eDCR), by using those details we are creating the OC eDCR Number.
1.Data required:
Click on OC Plan Scrutiny for new Construction link, it will route to Data required screen and the screen will be visible which will specify what all data required to generate OC eDCR number.
onClick on next, it will route to OC eDCR scrutiny details screen.
2. OC eDCR scrutiny details
After entering the permit number and permit date, stakeholder need to click the Search button. internally bpa and eDCR search will call for required data.
After success of BPA search and eDCR search, all the details regarding the application along with “proceed for OC scrutiny” button will display after search button with separate card.
onClick of procced for OC scrutiny, it will route to Upload OC Plan Diagram screen.
3.Upload OC Plan Diagram
After uploading the dxf file, submit button will enable and on click of submit button, create api will call.
Success Screen:
Acknowledgement Page will get displayed after success of eDCR create call, here stakeholder able to 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 for go to home.
Failure Screen:
Acknowledgement Page will get displayed after success of eDCR create call, here stakeholder able to see,
Application Number.
Download option, for downloading the scrutiny report.
Go Back To Home, button for go to home.
Technical Implementation Details:
All the screen has 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 can be used to understand the starting point of the flow:
eDCR and OC eDCR is the part of OBPS (OBPS DIGIT-UI ).
Config responsible for routing of each flow
MDMS data:
Throughout the flow, few of the pages data are being imported from MDMS, Following are the list of pages which 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 |
|
|
For calling of MDMS data React Hooks has been used, so that it could be shared throughout the 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) that should also be pushed in the locale DB under rainmaker-bpa locale module. Below is the example of few locale labels.
API Call Role Action mapping:
S.No. | API
| Action id | Roles |
|---|---|---|---|
1 |
|
|
|
2 |
|
|
|
3 |
|
|
|
4 |
|
|
|
5 |
|
|
|
6 |
|
|
|