Apply BPA OC
- Phani Kiran (Unlicensed)
- Vamshikrishna Kole (Unlicensed)
The BPA OC 'apply' is the major feature in BPA OC Module. It allows Stakeholder to create BPA OC Applications .
Every application is a part of the workflow.
Stepper 1 :
https://egov-micro-qa.egovernments.org/citizen/oc-bpa/apply?tenantId=pb.amritsar
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 OC : We used common container for Application Type , Service Type , Risk Type , Occupancy Type and Sub Occupancy Type .
Sample JSON for Structure Type and Sub Structure Type :
applicationType: getSelectField({
label: {
labelName: "Application Type",
labelKey: "BPA_BASIC_DETAILS_APPLICATION_TYPE_LABEL"
},
placeholder: {
labelName: "Select Application Type",
labelKey: "BPA_BASIC_DETAILS_APPLICATION_TYPE_PLACEHOLDER"
},
jsonPath: "BPA.applicationType",
sourceJsonPath: "applyScreenMdmsData.BPA.ApplicationType",
required: true,
gridDefination: {
xs: 12,
sm: 12,
md: 6
}
}),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
Basic details is the first stepper of BPA OC:
The disable fields data is fetched once the Occupancy Certificate Scrutiny Number field is filled and made a search call on edcr-service.
Apply Footer
The Next and Previous buttons are configured this json file.
BPA OC create call is triggered on 1st stepper’s Next button onclick().
NOC Search call is triggered after success of BPA Create.
Â
Stepper 2 :
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 3:
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/oc-bpa/summary.js
Update BPA OC API - bpa-services/v1/bpa/_update and Update NOC API - /noc-services/v1/noc/_update is called on SEND TO CITIZEN.
Â
Success Screen :
Search-Preview :
To load search preview page egov-workflow-v2/egov-wf/process/_search?businessIds=PB-BP-2020-07-23-003480&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 OC Workflow :
Role | Action | Next State | Status |
|---|---|---|---|
BPA_ARCHITECT/BPA_ENGINEER/BPA_BUILDER/BPA_STRUCTURALENGINEER/BPA_TOWNPLANNER/BPA_SUPERVISOR | INITIATE | SEND_TO_CITIZEN | INITIATED |
BPA_ARCHITECT/BPA_ENGINEER/BPA_BUILDER/BPA_STRUCTURALENGINEER/BPA_TOWNPLANNER/BPA_SUPERVISOR | SEND_TO_CITIZEN | CITIZEN_APPROVAL_PENDING | CITIZEN_APPROVAL_INPROCESS |
CITIZEN | SEND_TO_ARCHITECT | INPROGRESS | INPROGRESS |
BPA_ARCHITECT/BPA_ENGINEER/BPA_BUILDER/BPA_STRUCTURALENGINEER/BPA_TOWNPLANNER/BPA_SUPERVISOR | APPLY | PENDING_APPL_FEE_PAYMENT | PENDING_APPL_FEE |
CITIZEN/BPA_ARCHITECT/BPA_ENGINEER/BPA_BUILDER/BPA_STRUCTURALENGINEER/BPA_TOWNPLANNER/BPA_SUPERVISOR/SYSTEM_PAYMENT/CEMP | PAY | DOC_VERIFICATION_PENDING | DOC_VERIFICATION_INPROGRESS |
BPA_VERIFIER | FORWARD | FIELDINSPECTION_PENDING | FIELDINSPECTION_INPROGRESS |
BPA_FIELD_INSPECTOR | FORWARD | NOC_VERIFICATION_PENDING | NOC_VERIFICATION_INPROGRESS |
BPA_NOC_VERIFIER | FORWARD | PENDINGAPPROVAL | APPROVAL_INPROGRESS |
BPA_APPROVER | APPROVE | PENDING_SANC_FEE_PAYMENT | PENDING_SANC_FEE_PAYMENT |
CITIZEN/BPA_ARCHITECT/BPA_ENGINEER/BPA_BUILDER/BPA_STRUCTURALENGINEER/BPA_TOWNPLANNER/BPA_SUPERVISOR/SYSTEM_PAYMENT/CEMP | PAY | APPROVED | APPROVED |
Â
API Call Role Action mapping:
S.No. | API | Action id | Roles |
|---|---|---|---|
1 |
|
|
|
2 |
|
|
|
3 |
|
|
|
4 |
|
|
|
5 |
|
|
|
6 |
|
|
|
7 |
|
|
|
Â
NOC Workflow :
Role | Action | Next State | Status |
|---|---|---|---|
BPA_ARCHITECT/BPA_ENGINEER/BPA_BUILDER/BPA_STRUCTURALENGINEER/BPA_TOWNPLANNER/BPA_SUPERVISOR | INITIATE | INPROGRESS | INITIATED |
BPA_VERIFIER/BPA_FIELD_INSPECTOR/BPA_NOC_VERIFIER | INPROGRESS | APPROVE | INPROGRESS |
FIRE_NOC_APPROVER | APPROVE | APPROVED | APPROVED |
API Call Role Action mapping:
S.No. | API | Action id | Roles |
|---|---|---|---|
1 |
|
|
|
2 |
|
|
|
3 |
|
|
|
4 |
|
|
|
Â