...
Every application is a part of the workflow.
Stepper 1 :
https://egov-micro-qa.egovernments.org/citizen/egov-bpa/apply?tenantId=pb.amritsar
...
In BPA : We used common container for Application Type , Service Type , Risk Type , Occupancy Type and Sub Occupancy Type, Ownership , and Sub Ownership Owner Type and Type of owner-Subtype .
Sample JSON for Structure Type and Sub Structure Type :
Code Block |
---|
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 } }), |
Example :
jsonPath is used to store the data in specified path when clicking event triggers or on handleFieldChange.
...
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 :
...
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 :
Here all details are fetched from the EDCR data ( calling edcr service in stepper 1).
Stepper 3 :
...
Owner Type of Ownership and Type of Subownership 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 fetchedd 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-tradelicencebpa-dev/src/ui-config/screens/specs/tradelicenceegov-bpa/applyResource/footer.js
The Next and Previous buttons are configured this son file.
Tradelicence BPA create call is triggered on 2nd 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-tradelicencebpa-dev/src/ui-config/screens/specs/tradelicenceegov-bpa/applyResource/documentListdocumentDetails.js
...
Mdms data : https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/TradeLicenseBPA/documentObjDocTypeMapping.json
The data formatting logic is as shown below. getDocListprepareDocumentsUploadData(state, dispatch);
in https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-tradelicence-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/indexcommons.js
...
Stepper
...
5:
This is the Review/Summary screen - https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-tradelicencebpa-dev/src/ui-config/screens/specs/tradelicence/applyResource/tradeReviewDetailsegov-bpa/summaryDetails.js
...
Update TradeLicence BPA API - bpa-services/v1/bpa/_update
and Update NOC API - tl/noc-services/v1/noc/_update
is called on SUBMITSEND TO CITIZEN.
Success Screen :
Souce path : https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-tradelicencebpa-dev/src/ui-config/screens/specs/tradelicenceegov-bpa/acknowledgement.js
...
Search-Preview :
Source Path : https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-tradelicencebpa-dev/src/ui-config/screens/specs/tradelicenceegov-bpa/search-preview.js
To load search preview page egov-workflow-v2/egov-wf/process/_search?businessIds=PB-TLBP-2020-0507-23-006604003475&history=true&tenantId=pb.amritsar
API should return workflow history.
...
View History Buttons gives the list of workflow actions performed on the application.
...
...
BPA Workflow :
Role Credentials | Action | Next State | Status | ||||
---|---|---|---|---|---|---|---|
Citizen/Counter Employee/TL_CEMP | EMP1 / Citizen / TLCEMP01 | INITIATE | INITIATED | INITIATED | |||
Citizen/Counter Employee/TL_CEMP | EMP1 / Citizen | APPLY | Applied/ DOCUMENTVERIFICATION | Pending for Document Verification | |||
TL_DOC_VERIFIER | EMP1 | FORWARD | FIELDVERIFICATION | Pending for Field Verification | |||
TL_FIELD_VERIFIER | EMP1 | FORWARD | PENDINGAPPROVAL | Pending for APproval | |||
TL_Approver | EMP1 | APPROVE | PENDINGPAYMENT | Pending for Payment | |||
Citizen/Counter Employee/TL_CEMP | EMP1 / TLCEMP01 | PAY | Approved | ApprovedBPA_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 |
| 1684 |
|
|
|
|
43 |
|
|
| ||||
4 |
|
|
| ||||
5 |
|
|
| ||||
6 |
|
|
| ||||
7 |
|
|
| ||||
8 |
|
|
| ||||
9 |
|
|
| ||||
10 |
|
|
|
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 |
|
|
|