Page Comparison

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, Ownership , and Sub Ownership .

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
      }
    }),

Example :

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)

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.

Image Added

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

...

Type of Ownership and Type of Subownership - 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 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-tradelicence-dev/src/ui-config/screens/specs/tradelicence/applyResource/footer.js

The Next and Previous buttons are configured this son file.

Tradelicence create call is triggered on 2nd stepper’s Next button onclick().

...

Stepper 3 :

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

...

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

The data formatting logic is as shown below. getDocList(state, dispatch); in https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-tradelicence-dev/src/ui-config/screens/specs/utils/index.js

...

Stepper 4 :

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

...

Update TradeLicence API - tl-services/v1/_update is called on SUBMIT.

Success Screen :

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

...

Search-Preview :

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

To load search preview page egov-workflow-v2/egov-wf/process/_search?businessIds=PB-TL-2020-05-23-006604&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.

...

TradeLicence Workflow :

API Call Role Action mapping: