Page Comparison

...

The above json has each object for every BusinessService like PT, TL . When a new module is integrated a new object should be added in above json file.

Taking a example of PT - There are 2 pages in common-pay mocule.

...

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

Enabling state level configuration :

https://github.com/egovernments/egov-mdms-data/blob/master/master-config.json

"uiCommonPay": {
      "masterName": "uiCommonPay",
      "isStateLevel": true,
      "uniqueKeys": []
    }

statelevel configuration is added for newly added json.

UI Changes :

All downloadReceipt and downloadBill functions are refactored. So all module developers will have to update the calls respectively in the module screens .

download(receiptQueryString , "download"); is changed to download(receiptQueryString , "download" , receiptKey); - receiptKey specific to each modules is added as a 3rd param

download(receiptQueryString ,"print"); is changed to download(receiptQueryString ,"print" , receiptKey ,state); - receiptKey specific to each modules is added as a 3rd param

If configs are not added in mdms for any module then it fetches default keys :

Bill data-config - https://github.com/egovernments/configs/blob/master/pdf-service/data-config/consolidatedbill.json

Bill format config - https://github.com/egovernments/configs/blob/master/pdf-service/format-config/consolidatedbill.json

Receipt data-config - https://github.com/egovernments/configs/blob/master/pdf-service/data-config/consolidatedreceipt.json

Receipt format-config - https://github.com/egovernments/configs/blob/master/pdf-service/format-config/consolidatedreceipt.json