DIGIT Workbench
PlatformDomainsAcademyDesign SystemFeedback
  • 👋Introducing DIGIT Workbench
    • Release Notes
      • Service Build Updates
      • MDMS & Configuration Updates
      • Test cases
      • Schema Collection
  • Understanding Workbench
    • Workbench Concept Note
    • Approach
  • Specifications
    • Master Data Management Process Flow
    • User Stories
  • Platform
    • Architecture
      • High Level Design
      • Low Level Design
    • Source Code
  • Setup
    • Configurations
      • Services
        • MDMS V2 (Master Data Management Service)
          • Adopt New MDMS - Steps
      • Workbench UI
        • Configurations
          • MDMS Configurations
          • DevOps Configuration
          • FAQ :: On Localisation Screens
        • Manage Master Data
          • Search Master Data
          • Add Master Data
          • View Master Data
          • Update Master Data
        • Manage Localisation Data
          • Search Localisation Data
            • Add Localisation Data
          • Edit Localization Messages
          • FAQ :: Add localisation if screens are not localised.
        • Create New Master
      • MDMS V2 Migration Guide
  • Community
    • Issues
Powered by GitBook

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

On this page
  • Overview
  • Steps
  • Search API For Localisations

Was this helpful?

Export as PDF
  1. Setup
  2. Configurations
  3. Workbench UI
  4. Manage Localisation Data

Search Localisation Data

PreviousManage Localisation DataNextAdd Localisation Data

Last updated 10 months ago

Was this helpful?

Overview

This page provides the steps to search localisation data.

Steps

Navigate to the Manage Localisation screen from the home screen card. This opens the search localisation screen.

The following parameters are available for searching localizations

  1. locale -> this field is mandatory. This dropdown is populated based on this mdms

  2. module -> list of modules present in this mdms

  3. keycode -> code of a specific message. It is a string-type parameter

Search Results

We have the following columns for localisation search results:

  1. Module name

  2. Key code

  3. Default value -> message stored in default locale

  4. Text -> message stored

  5. Action -> Edit action to update message in that particular localisation

A note on the default value in the results

While adding localisations, by default all the messages will be updated in the locale mentioned by the user as well as in the "default" locale. The message updated in this locale is considered the default message. While updating the message default locale message remains unchanged.

Search API For Localisations

Localisation search API is an open API. Refer to the curl given below:

curl --location 'https://qa.digit.org/localization/messages/v1/_search?locale=en_IN&tenantId=pb' \
--header 'Content-Type: application/json' \
--data '{
     "RequestInfo": {
       "apiId" : "emp",
       "ver" : "1.0",
       "ts" : "10-03-2017 00:00:00",
       "action" : "create",
       "did" : "1",
       "key" : "abcdkey",
       "msgId" : "20170310130900",
       "requesterId" : "rajesh",
       "authToken" : "{{authToken}}",
       "userInfo" : {
         "id" : 1
       }
   }
}'
  • Search for the desired language and module using the provided search functionality. The language and module are derived from MDMSv2.

  • For example, if you are searching for the language ‘English’ and the module ‘rainmaker-common’, Once you perform the search, all relevant results will be displayed below.

Refer to the screenshot below:

Adding a new Localisation Message

To add a new language, provide a locale name and a keycode, then click ‘Add’ to include it in the system.

https://github.com/egovernments/egov-mdms-data/blob/UNIFIED-UAT/data/pg/common-masters/StateInfo.json
https://github.com/egovernments/egov-mdms-data/blob/UNIFIED-DEV/data/pg/common-masters/StateInfo.json