Apply Stakeholder Registration Through Openlink

NOTE: Difference between Openlink and normal link

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

1. Citizen no need to login into page

2. Citizen needs to login after submitting the application only.

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

1. Citizen needs to logic into https://egov-micro-qa.egovernments.org/citizen/
   then only Citizen able to route to Normal link

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/openlink/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

Open

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

Open

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

From here, Citizen needs to login into https://egov-micro-qa.egovernments.org/citizen/

After success login, Citizen needs route to https://egov-micro-qa.egovernments.org/citizen/bpastakeholder-citizen/my-applications

Open Citizen application:

Click on VIEW DETAILS, it will route to

https://egov-micro-qa.egovernments.org/citizen/bpastakeholder/search-preview?applicationNumber=PB-SK-2020-08-03-008058&tenantId=pb

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-008058&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.

Stakeholder Registation Workflow :

API Call Role Action mapping: