Configuration to setup UI

Owned by Phani Kiran (Unlicensed)
Last updated: Aug 03, 2020 by Vamshikrishna Kole (Unlicensed)
2 min read

For applying BPA, we need EDCR and STAKEHOLDER setup.

BPA SETUP:

Mdmds configurations

  1. Map all BPA roles to respective API’s giving 403 status inhttps://github.com/egovernments/playground-mdms-data/blob/master/data/pg/ACCESSCONTROL-ACTIONS-TEST/actions-test.json and https://github.com/egovernments/playground-mdms-data/blob/master/data/pg/ACCESSCONTROL-ROLEACTIONS/roleactions.json

  • BPA_ARCHITECT

  • BPA_ENGINEER

  • BPA_BUILDER

  • BPA_STRUCTURALENGINEER

  • BPA_SUPERVISOR

  • BPA_TOWNPLANNER

  • BPA_VERIFIER

  • BPA_FIELD_INSPECTOR

  • BPA_NOC_VERIFIER

  • BPA_APPROVER

  • CEMP

  • To configure the module cards in the inbox use below Json.

  • { "id": 1936, "name": "search BPA application", "url": "card", "displayName": "Search Application", "orderNumber": 1, "parentModule": "", "enabled": true, "serviceCode": "", "code": "", "path": "", "navigationURL": "egov-bpa/search", "leftIcon": "communication:business", "rightIcon": "", "queryParams": "" },

    Refer https://digit-discuss.atlassian.net/l/c/9nu3H010 to know how to configure roles in mdms.

  1. All BusinessService details and BPA && BPA OC Specific mdms data.

3. Pdf configurations at UI.

4. Workflow configurations

  • { "id": 1766, "name": "rainmaker-common-workflow", "url": "", "displayName": "", "orderNumber": 2, "parentModule": "", "enabled": true, "serviceCode": "", "code": "", "path": "", "navigationURL": "", "leftIcon": "", "rightIcon": "", "queryParams": "" },

     

  • Assign above action to BPA and BPA_OC roles. This action is mainly to enable Workflow Inbox.

  • All the workflow API should be given access to all BPA and BPA_OC roles in

https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/ACCESSCONTROL-ROLEACTIONS/roleactions.json.

STAKEHOLDER SETUP:

Mdmds configurations

  1. Map all BPA roles to respective API’s giving 403 status inhttps://github.com/egovernments/playground-mdms-data/blob/master/data/pg/ACCESSCONTROL-ACTIONS-TEST/actions-test.json and https://github.com/egovernments/playground-mdms-data/blob/master/data/pg/ACCESSCONTROL-ROLEACTIONS/roleactions.json

  • CITIZEN

  • BPAREG_DOC_VERIFIER

  • BPAREG_APPROVER

  • To configure the module cards in the inbox use below Json.

  • { "id": 1879, "name": "BPAStakeHolderSearch", "url": "url", "displayName": "BPA Stakeholder Search", "orderNumber": 1, "parentModule": "rainmaker-bpa", "enabled": true, "serviceCode": "BPAREG", "code": "null", "path": "BPAStakeHolder.Search", "navigationURL": "bpastakeholder/search", "leftIcon": "communication:business", "rightIcon": "" }

    Refer https://digit-discuss.atlassian.net/l/c/9nu3H010 to know how to configure roles in mdms.

2. All BusinessService details and Stakeholder Specific mdms data.

3. Pdf configurations at UI.

4. Workflow configurations

  •  

  • Assign above action to Roles roles. This action is mainly to enable Workflow Inbox.

  • All the workflow API should be given access to all Stakeholder roles in

https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/ACCESSCONTROL-ROLEACTIONS/roleactions.json.

EDCR SETUP:

Mdmds configurations

  1. Map all BPA roles to respective API’s giving 403 status inhttps://github.com/egovernments/playground-mdms-data/blob/master/data/pg/ACCESSCONTROL-ACTIONS-TEST/actions-test.json and https://github.com/egovernments/playground-mdms-data/blob/master/data/pg/ACCESSCONTROL-ROLEACTIONS/roleactions.json

  • BPA_ARCHITECT

  • BPA_ENGINEER

  • BPA_BUILDER

  • BPA_STRUCTURALENGINEER

  • BPA_SUPERVISOR

  • BPA_TOWNPLANNER

  • To configure the module cards in the inbox use below Json.

  • Refer https://digit-discuss.atlassian.net/l/c/9nu3H010 to know how to configure roles in mdms.

2. All BusinessService details and EDCR mdms data.

3. Pdf configurations at UI.

 

Front End Configurations :

  • Change the state level tenantId in /frontend/web/rainmaker/packages/employee/.env

REACT_APP_DEFAULT_TENANT_ID=pb

  • Point to specific environment you want to test on.

"proxy": "https://egov-micro-qa.egovernments.org/",

Â