Configuring Master Data
Overview
Configuring Master Data for a new module requires creating a new module in the master config file and adding masters data. For better organizing, create all the master data files belongs to the module in the same folder. Organizing in same folder is not mandatory it is based on the moduleName
in the Master data file.
Pre-requisites
Before you proceed with the configuration, make sure the following pre-requisites are met -
User with permissions to edit the git repository where MDMS data is configured.
Key Functionalities
These data can be used to validate the incoming data.
Deployment Details
After adding the new module data, the MDMS service needs to be restarted to read the newly added data.
Configuration Details
Adding new module
The Master config file is structured as below. Each key in the Master config is a module and each key in the module is a master.
{
"<module1>":{
"<master1>":{},
"<master2>":{},
...
},
"<module2>":{
<master3>:{},
<master4>:{},
...
},
...
}
the new module can be added below the existing modules in the master config file.
2. Creating Masters data
Please check the link to create new master Adding New Master
Reference Docs
Doc Links
Title | Link |
Sample Master config file | https://github.com/egovernments/playground-mdms-data/blob/master/master-config.json |
Sample Module folder | https://github.com/egovernments/playground-mdms-data/tree/master/data/pg/TradeLicense |