As a user,
I want to see my previous version translations to the next version of a form2.0 form.
So that I don't need to write all my translations again in the new version
When a user clicks on translations in the form builder, he will be directed to adding translations page, where he can be able to add his translations to the respective concepts. Now, any time if I click on a new version of a form, the translations will be empty. I should be able to see my previous versions translations in that page. This will be useful, the user can be able to reuse his previous versions translations in his current version.
Translations from the last version should be copied to next version in the UI
User can edit the translation from UI where required
New translations will be copied to the next version
Translations, when imported, should be copied in the translations files - currently, they are in draft mode when imported and on publishing, the translation files are lost
If we are creating a new form, the translations file will be generated for that first version.
while you are editing a published version, it will create a new next version of that form, currently in which the published translations are getting lost and fresh translations file is created.
We implement in a way that, while clicking on edit for published we are storing that published version as reference version, which will be used to fetch the reference version translations and copy to the newly created version translation file.
bahmni ie apps:
bahmni ie apps PR should be merged first, and then implementer-interface PR has to be merged