Apply Stakeholder Registration

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

Every application is a part of the workflow.

Stepper 1 :

Route - https://egov-micro-qa.egovernments.org/citizen/bpastakeholder-citizen/apply

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

Licensee details is the first stepper of Stakeholder Registration :

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

Stepper 2 :

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

 

 

Apply Footer

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

The Next and Previous buttons are configured this json file.

Stakeholder 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-bpa-dev/src/ui-config/screens/specs/bpastakeholder/applyResource/documentList.js

Mdms data : https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/TradeLicense/TradeType.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-bpa-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-bpa-dev/src/ui-config/screens/specs/bpastakeholder/search-preview.js

Update BPA API - /tl-services/v1/BPAREG/_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/bpastakeholder/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/bpastakeholder/search-preview.js

To load search preview page egov-workflow-v2/egov-wf/process/_search?businessIds=PB-SK-2020-08-03-008053&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 :

Role

Action

Next State

Status

Role

Action

Next State

Status

CITIZEN, ANONYMOUS

INITIATE

APPLY

INITIATED

CITIZEN, ANONYMOUS

APPLY

PENDINGPAYMENT

PENDINGPAYMENT

CITIZEN, SYSTEM_PAYMENT

PAY

PENDINGDOCVERIFICATION

PENDINGDOCVERIFICATION

BPAREG_DOC_VERIFIER

FORWARD

PENDINGDOCVERIFICATION

PENDINGDOCVERIFICATION

BPAREG_APPROVER

APPROVE

APPROVED

APPROVED

 

API Call Role Action mapping:

API

Action id

Roles

API

Action id

Roles

1

/egov-mdms-service/v1/_search

954

LOA_CREATOR,SUPERUSER,WO_CREATOR,AE_CREATOR,WORKS_MASTER_CREATOR,

2

/egov-location/location/v11/boundarys/_search

1429

EMPLOYEE,CITIZEN,GRO,PGR-ADMIN,CSR,TL_APPROVER,TL_CEMP,SUPERUSER,DE_CREATOR,

3

/tl-services/v1/BPAREG/_create

1924

CITIZEN

4

/tl-services/v1/BPAREG/_update

1876

BPAREG_APPROVER, CITIZEN, BPAREG_DOC_VERIFIER

5

/filestore/v1/files/url

1528

SUPERUSER,EMPLOYEE,CITIZEN,GRO,DGRO,

6

/billing-service/bill/v2/_fetchbill

1862

EMPLOYEE,CITIZE

Â