Apply TradeLicence

The trade license 'apply' is the major feature in TL Module. It allows Citizen or Counter Employee to create TL Applications for the current financial year.

Every application is a part of the workflow.

Stepper 1 :

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

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

All the drop down data are mapped through mdms response.

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

In Trade License : We used common container for Trade Category , Trade Type , Trade Sub Type , Structure Type and Sub Structure Type, Ownership , and Sub Ownership .

Sample JSON for Structure Type and Sub Structure Type :

dynamicMdmsStructureType : {
      uiFramework: "custom-containers",
      componentPath: "DynamicMdmsContainer",
      props: {
        dropdownFields: [
          {
            key : 'structureType',
            isDisabled:getQueryArg(window.location.href, "action") === "EDITRENEWAL"? true:false
          },
          {
            key : 'structureSubType',
            callBack : structureSubTypeChange
          }
        ],
        moduleName: "common-masters",
        masterName: "StructureType",
        rootBlockSub : 'structureTypes',
        callBackEdit: updateStructureTypes
      }
    }

Example :

jsonPath , sourceJsonPath are created as a dynamic in ( “DynamicMdmsContainer“ ) based on module name and rootBlockSub , Key .

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 :

Structure Type and Sub Structure Type field data is fetched from https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/common-masters/StructureType.json

Trade Category , Trade Type , Trade Sub Type field data is fetched from https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/TradeLicense/TradeType.json

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

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

Stepper 2 :

Source path: https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-tradelicence-dev/src/ui-config/screens/specs/tradelicence/applyResource/tradeOwnerDetails.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 URLs:

1. /egov-mdms-service/v1/_search

2. /tl-calculator/billingslab/_search

3. /egov-location/location/v11/boundarys/_search

4. /user/_search

5. /tl-services/v1/_create

6. /filestore/v1/files

7. /filestore/v1/files/url

8. /billing-service/bill/v2/_fetchbill

9. /tl-calculator/v1/_getbill

10. /tl-calculator/billingslab/_search

11. /tl-services/v1/_update