Form name translations with Forms 2.0

Description

As a Bahmni User, I would like to have an interface to enter form name translations, based on the locale selected, so I can see the translated form names on consultation and display controls in the language I want.

 

Acceptance Criteria

  • Capture the form name translations using the current UI for form data translation, add a Translation key called ‘FORM_NAME’ as seen in image below:

  • The ‘FORM_NAME’ translation key should be the first row on the screen.

  • When other locales are selected we should be able to enter value for form name for it.

  • The default value should be same as the form name, for all locales.

  • When the save button in clicked this data should be persisted in DB, so that we can retrieve it again.

  • When I revisit the form translation screen, it should show me the value I entered and saved the last time.

  • Translate the form name in obs to obs, form 2 edit/view etc. display controls (normal & extended view)

  • Show translated form names when ‘Add new obs form’ is clicked

  • Show translated form names when pinned forms are displayed on the consultation screen

  • Show translated form name, when form is rendered to be filled on consultation

  • Show translated form name, when form is rendered to be edited using display control

  • Show translated form name, when form is rendered to be viewed on display control

  • Show translated form name for retrospective entry, covering all the above scenarios

  • Existing display controls should not break.

  • The translated form name should appear correctly on consultation, after imported form is published

  • When I export the form, the form name translation should also get exported

  • When I import a form with form name translation it should work fine

  • When I import a form without form name translation it should work fine

  • Above should also work with bulk export and import

  • For an imported(already existing and export) and then published form we should be able to change translations.

Technical Requirements

  • Store the form translations in the form resource table

  • If required, create a custom data type for storing this value

  • The structure of the the data stored should be

Assignee

Unassigned

Reporter

Mohit Kaustubh Dhamdhere

Units

None

PercentDone

None

DueTime

None

Clients

None

External issue ID

None

UAT Assignee

None

Reviewer

None

Components

Sprint

Configure