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.

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.

egovernments / Digit-Core

Missing Localization for MDMS Schemas Created via Postman #575

574