Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

List of configurations need to updated so that BPA && BPA OC UI can display the information / provide access to the logged in User.

  1. Types of Roles & Access Details

  2. MDMS configurations

  3. PDF Configurations

  4. WorkFlow Configurations

  5. Egov-Searcher Configurations

  1. Type of Roles & Access Details

For BPA & BPA OC:

Citizen Level:

  1. BPA_ARCHITECT

  2. BPA_ENGINEER

  3. BPA_BUILDER

  4. BPA_STRUCTURALENGINEER

  5. BPA_SUPERVISOR

  6. BPA_TOWNPLANNER

Employee Level:

  1. BPA_VERIFIER

  2. BPA_FIELD_INSPECTOR

  3. BPA_NOC_VERIFIER

  4. BPA_APPROVER

  5. CEMP

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

...

Role-actions mapping is added in below file:

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

{

"rolecode": "BPA_APPROVER",

"actionid": 1931,

"actioncode": "",

"tenantId": "pb"

}

For every action object added in actions-test.json , we have to add specific roles who can access those added items inroleactions.json, where id will become the mapping key.

role code will be the roles of Employee or citizen. 

Employee Inbox :

For any Employee, Inbox will be visible only if its configured in mdms.

https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/ACCESSCONTROL-ACTIONS-TEST/actions-test.json

2. MDMS Configuration

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

https://github.com/egovernments/egov-mdms-data/tree/master/data/pb/BPA

https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/BPA/ApplicationType.json

https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/BPA/CalculationType.json

https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/BPA/CheckList.json

https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/BPA/DeviationParams.json

https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/BPA/DocTypeMapping.json

https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/BPA/OccupancyType.json

https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/BPA/ProposedLandUse.json

https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/BPA/RiskTypeComputation.json

https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/BPA/ServiceType.json

https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/BPA/SubOccupancyType.json

3. PDF Configurations at UI

https://github.com/egovernments/configs/tree/master/pdf-service/data-config

https://github.com/egovernments/configs/tree/master/pdf-service/format-config

4. Workflow Configurations

...

  • 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

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-dev.egovernments.org/",