Missing Localization for MDMS Schemas Created via Postman
Description: Currently, MDMS schemas are being created through Postman, which bypasses the creation of necessary localization messages. This leads to several issues when users access the MDMS/Workbench UI:
-
Localization Absence:
- Users do not create localization when adding data via Postman. As a result, when they visit the MDMS or Workbench UI, they see fields displayed as code since the screen expects localized messages for every field name.
-
Non-Readable UI:
- The entire screen displays non-user-readable codes for fields, which impacts usability and clarity. This is because the UI assumes and expects localization messages for each field in the schema.
Attachment
-
Proposed Approach:
- We should implement an event-based approach or an alternative mechanism that ensures a localization message is automatically created for every property in a schema when it is created.
- This default localization message would provide a more user-friendly interface, displaying proper messages when users visit the screen.
-
Standardization for Localization:
- To ensure uniqueness and consistency, a prefix should be added to every field's localization key. This prefix should follow the format:
{schemaCode}_fieldName. This will help standardize how localization messages are created for each schema field.
- To ensure uniqueness and consistency, a prefix should be added to every field's localization key. This prefix should follow the format:
Steps to Reproduce:
- Create an MDMS schema via Postman without providing localization.
- Access the MDMS or Workbench UI.
- Observe that the screen displays non-localized codes instead of user-friendly messages.
Expected Behavior:
- Localization messages should automatically be generated for every property in the schema with a default message, ensuring that users see proper, user-readable fields on the UI.
Additional Notes:
- Implementing this approach will help improve the user experience and ensure that fields are localized appropriately across the MDMS and Workbench UI.
#574
We previously discussed this issue during the "Localization <> Master Data" meeting held on Wednesday, September 25, from 12:00 PM to 1:00 PM. The attendees were @jagankumar-egov @eGovMan @Rishabh-egov @varunreddy-egov Krishna
@Rishabh-egov , please add the discussion points and proposed approaches from the meeting here.
@jagankumar-egov - I thought we are calling it Admin Console and not Workbench. 😀
Hello Everone!! I am Zeel Darji , C4GT community Lead and Open source Lead of Development Wing of IIITN . I am organizing an open source event in my college's techfest which higlights the importance of DPGs and DPIs .
I wanted to ask you if participants could contribute to the repos of eGovernments for our Event ? Thank You!