Apply BPA

The BPA 'apply' is the major feature in BPA Module. It allows Stakeholder to create BPA Applications .

Every application is a part of the workflow.

Stepper 1 :

https://egov-micro-qa.egovernments.org/citizen/egov-bpa/apply?tenantId=pb.amritsar

Source path : https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-bpa-dev/src/ui-config/screens/specs/egov-bpa/apply.js

All the drop down data are mapped through mdms response.

For to display MDMS data we have common container in UI Framework ( “getSelectField“ ).

In BPA : We used common container for Application Type , Service Type , Risk Type , Occupancy Type and Sub Occupancy Type, Owner Type and Type of owner-Subtype .

Sample JSON for Structure Type and Sub Structure Type :

jsonPath is used to store the data in specified path when clicking event triggers or on handleFieldChange.

sourceJsonPath is the path where the data is fetched to populate in the dropdown.

Mdms data :

Application Type data is fetched from https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/BPA/ApplicationType.json

Service Type data is fetched from https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/BPA/ServiceType.json.

Occupancy Type data is fetched from https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/BPA/OccupancyType.json

Sub Occupancy data is fetched from https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/BPA/SubOccupancyType.json

Mohalla Data - https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/amritsar/egov-location/boundary-data.json (For Amritsar)

Basic details is the first stepper of BPA :

Source Path: https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-bpa-dev/src/ui-config/screens/specs/egov-bpa/applyResource/basicDetails.js

Open

The disable fields data is fetched once the Building Plan scrutiny number field is filled and made a search call on edcr-service.

Stepper 2 :

Source Path: https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-bpa-dev/src/ui-config/screens/specs/egov-bpa/applyResource/scrutinyDetails.js

Here all details are fetched from the EDCR data ( calling edcr service in stepper 1).

Open

Stepper 3 :

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

Owner Type and Type of owner-Subtype - https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/common-masters/OwnerShipCategory.json https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/common-masters/OwnerType.json

The owner data is fetched once the Mobile Number field is filled and made a search call on user-service.

Apply Footer

https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-bpa-dev/src/ui-config/screens/specs/egov-bpa/applyResource/footer.js

The Next and Previous buttons are configured this son file.

BPA create call is triggered on 3nd stepper’s Next button onclick().

NOC Search call is triggered after success of BPA Create.

Stepper 4 :

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

Mdms data : https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/BPA/DocTypeMapping.json

The data formatting logic is as shown below. prepareDocumentsUploadData(state, dispatch); in https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-bpa-dev/src/ui-utils/commons.js

NOC Section :
Source Path : https://github.com/egovernments/frontend/blob/develop/web/rainmaker/dev-packages/egov-bpa-dev/src/ui-config/screens/specs/egov-bpa/noc.js

MDMS Date: https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/NOC/DocumentTypeMapping.json

The data formatting logic is as shown below.

prepareNOCUploadData(state, dispatch) and prepareNocFinalCards(state, dispatch) in https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-bpa-dev/src/ui-utils/commons.js

Stepper 5:

This is the Review/Summary screen - https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-bpa-dev/src/ui-config/screens/specs/egov-bpa/summaryDetails.js

Update BPA API - bpa-services/v1/bpa/_update and Update NOC API - /noc-services/v1/noc/_update is called on SEND TO CITIZEN.

Success Screen :

Souce path : https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-bpa-dev/src/ui-config/screens/specs/egov-bpa/acknowledgement.js

Search-Preview :

Source Path : https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-bpa-dev/src/ui-config/screens/specs/egov-bpa/search-preview.js

To load search preview page egov-workflow-v2/egov-wf/process/_search?businessIds=PB-BP-2020-07-23-003475&history=true&tenantId=pb.amritsar API should return workflow history.

The topmost card is mainly rendered using the workflow response.https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-workflow-dev/src/ui-molecules-local/TaskStatusComponents/index.js

View History Buttons gives the list of workflow actions performed on the application.

BPA Workflow :

API Call Role Action mapping:

NOC Workflow :

API Call Role Action mapping: