...
| Code Block |
|---|
{
"tenantId": "uk" , //<ReplaceWithDesiredTenantId>
"moduleName": "common-masters",
"StateInfo": [ {
"name": "Uttarakhand",
"code":"uk" , //<ReplaceWithDesiredTenantId> "bannerUrl":https://amazonaws-url/foldername/file.jpg", <bannerimage file path>
"logoUrl":"https://amazonaws-url/foldername/file.jpg", <state logo image file path>
"hasLocalisation" : true, <if true, enables multilingual support mentioned below. Or else by default english>
"languages" : [ { <languages to be supported are listed here>
"label": "ENGLISH",
"value": "en_IN"
}, {
"label": "हिंदी",
"value": "hi_IN"
} ],
"defaultUrl" : {
"citizen" : "/user/register",
"employee" : "/user/login"
} } ]
} |
Integration
Integration Scope
Integration Benefits
Steps to Integration
5.Boundary Data Load :
Boundary is ULB specific master data. For Revenue modules we use Revenue boundary. It’s pushed under each ulb.
File Path would be : https://github.com/egovernments/state-mdms-data/tree/master/data/tenant/ulb/egov-location/boundary-data.json
Boundary Hierarchy : Zone -> Ward -> Locality -> Area
Boundary data json is generated using implementation Kit.
Reference Docs
Doc Links
Title | Link |
API List
...
Title
...
Link
...
tenant json file | https://github.com/egovernments/ukd-mdms-data/blob/master/data/uk/tenant/tenants.json |
citymodule json file | https://github.com/egovernments/ukd-mdms-data/blob/master/data/uk/tenant/citymodule.json |
stateinfo json file | https://github.com/egovernments/ukd-mdms-data/blob/master/data/uk/common-masters/StateInfo.json |
boundary-data json file |