Mdms UI configurations

Menu Items :

Open

Each Items in the above screen is displayed by adding an object in egov-mdms-data/data/pb/ACCESSCONTROL-ACTIONS-TEST/actions-test.json at master · egovernments/egov-mdms-data

Eg:

  {

    "id": 1800,

    "name": "FIRE-NOC",

    "url": "url",

    "displayName": "Search",

    "orderNumber": 3,

    "parentModule": "",

    "enabled": true,

    "serviceCode": "FIRE-NOC",

    "code": "null",

    "navigationURL": "fire-noc/search",

    "path": "FIRE-NOC.Search",

    "leftIcon": "social:people"

  }

• id , url, displayName, navigationURL, path, leftIcon

  • Mandatory properties.

• The value of url  property should be “url” as shown above.

• path property specifies the levels to show the action items.

Employee/Citizen Landing Page service cards : 

Each Items in the above screen is displayed by adding an object in egov-mdms-data/data/pb/ACCESSCONTROL-ACTIONS-TEST/actions-test.json at master · egovernments/egov-mdms-data

Eg:

 {

    "id": 1778,

    "name": "rainmaker-common-tradelicence",

    "url": "card",

    "displayName": "Trade Licence",

    "orderNumber": 2,

    "parentModule": "",

    "enabled": true,

    "serviceCode": "",

    "code": "",

    "path": "",

    "navigationURL": "tradelicence/search",

    "leftIcon": "places:business-center",

    "rightIcon": "",

    "queryParams": ""

  }

• id , name, url, displayName, navigationURL

  • Mandatory properties.

• The value of url  property should be “card” as shown above.

• Citizen : name property should start with “rainmaker-citizen” prefix

Employee : name property should start with “rainmaker-common” prefix

• path property specifies the levels to show the action items.

Employee Inbox QUICK ACTIONs :

Each Items in the above dropdown is displayed by adding an object in egov-mdms-data/data/pb/ACCESSCONTROL-ACTIONS-TEST/actions-test.json at master · egovernments/egov-mdms-data

Eg:

 {

    "id": 1928,

    "name": "rainmaker-common-tradelicence",

    "url": "quickAction",

    "displayName": "Search TL",

    "orderNumber": 2,

    "parentModule": "",

    "enabled": true,

    "serviceCode": "",

    "code": "",

    "path": "",

    "navigationURL": "tradelicence/search",

    "leftIcon": "places:business-center",

    "rightIcon": "",

    "queryParams": ""

  }

• id , url, displayName, navigationURL

  • Mandatory properties.

• The value of url  property should be “quickAction” as shown above.

Mapping Roles to action objects :

Role-actions mapping is added in below file:

egov-mdms-data/data/pb/ACCESSCONTROL-ROLEACTIONS/roleactions.json at master · egovernments/egov-mdms-data

{

    "rolecode": "TL_CEMP",

    "actionid": 1928,

    "actioncode": "",

    "tenantId": "pb"

  }

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

rolecode will be the roles of Employee or citizen. 

Employee Inbox :

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

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

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

Note : Every id property in egov-mdms-data/data/pb/ACCESSCONTROL-ACTIONS-TEST/actions-test.json at master · egovernments/egov-mdms-data will be unique. 

As and when we add the object , the id counter should be incremented by 1 of the previous objects id.