AMPATH Form Translations domain to track form version changes.

[Ruhanga]

Currently when an AMPATH form version changes, its name-identifier (UUID) changes and so a new form with a different UUID identifier is loaded. Form translation changes loaded using the associated translation file update the form translation resource associated with the previous version of the form, hence the new form looses its translations.

Proposed Solution
AMPATH Form Translation's domain should void the previously loaded translations file associated to previous form version and create a new translations file to be associated with new version of AMPATH form.

[mks-d]

@Ruhanga is this still current or we can close this issue?

[Ruhanga]

Yes this is till current @mks-d.

[Ruhanga]

Closing this as duplicating this other one: #244