How to use and configure localization screen
This screen used to add, update, search and delete localization key and value to the application
1. Feature
Bulk upload(Excel).
2. Bulk module search.
3. Module and language-wise search.
4. Table view with edit and delete.
5. Validation of duplicate data.
6. Global search.
7. Export as CSV.
2. Search localization
Users can search localization for any modules selecting search filters as mentioned screenshot.
2. Select Locale and click on Search.
3. Users can do a global search entering the specified search string.
3. Create Localization
Search for modules and Locale you want to add localization and click on search.
2. Click on + button right top of the result card, it will show fields to add localization, enter localization code, message, module, and Locale then clicks the OK icon.
4. Update Localization
Search for modules and Locale you want to add localization and click on search.
2. Search or go to a particular row on the table and click on edit. Update the values as needed for your requirement then click on the OK button.
5. Delete localization key
Search for modules and Locale you want to add localization and click on search.
Search or go to a particular row on the table and click on edit. Update the values as needed for your requirement then click on the OK button.
3. It will show confirmation message, click on Ok icon, and delete the record.
6. Filter the records
Search for modules and Locale you want to add localization and click on search.
2. Click filters in 1st row, select the related filters, click on other places, it will filter the record.
7. Bulk Upload
Click on + button top right of the localization screen, upload the document that is having the data in the form of the code, messages, module, and locale, then click on upload. It will take some time to upload wait for the same. If any error in the data it through the exception.
PFA of bulk upload template.
8. Export as CSV.
1. Top right of the result card click on the 1st icon, then click on export.
9. MDMS changes for this feature.
Need to add 2 properties as below to state info master.
JSON -
{
"languages":[
{
"label":"ENGLISH",
"value":"en_IN"
},
{
"label":"हिंदी",
"value":"hi_IN"
},
{
"label":"ಕನ್ನಡ",
"value":"kn_IN"
}
],
"localizationModules":[
{
"label":"rainmaker-abg",
"value":"rainmaker-abg"
},
{
"label":"rainmaker-common",
"value":"rainmaker-common"
},
{
"label":"rainmaker-noc",
"value":"rainmaker-noc"
},
{
"label":"rainmaker-pt",
"value":"rainmaker-pt"
},
{
"label":"rainmaker-uc",
"value":"rainmaker-uc"
},
{
"label":"rainmaker-pgr",
"value":"rainmaker-pgr"
},
{
"label":"rainmaker-tl",
"value":"rainmaker-tl"
},
{
"label":"rainmaker-hr",
"value":"rainmaker-hr"
},
{
"label":"rainmaker-test",
"value":"rainmaker-test"
},
{
"label":"finance-erp",
"value":"finance-erp"
},
{
"label":"rainmaker-receipt",
"value":"rainmaker-receipt"
}
]
}
2. Add iframe configuration in bellow URL
https://github.com/egovernments/ukd-mdms-data/blob/UAT/data/uk/common-masters/uiCommonConstants.json
"ui-localisation":{
"iframe-routes":{
"localization":{
"routePath":"/ui-localisation/#/egov-ui-framework/egov-localization/localization",
"isOrigin":true
}
}
}
3. Add a menu action
https://github.com/egovernments/ukd-mdms-data/tree/UAT/data/uk/ACCESSCONTROL-ACTIONS-TEST
{
"id": 1889,
"name": "rainmaker-localization-screen",
"url": "url",
"displayName": "Localization",
"orderNumber": 5,
"parentModule": "",
"enabled": true,
"serviceCode": "",
"code": "",
"path": "Localization",
"navigationURL": "integration/ui-localisation/localization",
"leftIcon": "places:business-center",
"rightIcon": "",
"queryParams": ""
}
4. Add role action mapping
Note: URL and number of actionid will depend on the environment to environment, please refer your environment id.
11. Build URL
https://builds.egovernments.org/job/builds/job/frontend/job/localization/
12. Branch
Rainmker-v1-uk-new