You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Locations form a large part of the translation workload of an app.
It is also possible that the translations are being done for a test organisation, and therefore location translations are not required. In such cases, it is possible that the user might want to skip this part when exporting translations.
Some orgs have around 7K locations and it keeps increasing. For such orgs, being able to translate all the locations is quite overwhelming, So to start with they dont want to export locations
But most orgs have comparitively lesser number of locations and do translations for locations as well.
Acceptance criteria
On the Translations page (Home-> translations), when downloading translations, an options section is added under the dropdown and Download buttin
A switch to "Exclude Locations" is added as an option during the download
The default value of the switch is "Off"
When the switch is "ON", locations are ignored in the downloaded file
Inputs:
Being able to understand what key has come from where
user names
Technical details
This includes changes in avni-webapp and avni-server
Change required in /translation endpoint to accept includeLocations=true|false
The text was updated successfully, but these errors were encountered:
Need:
Locations form a large part of the translation workload of an app.
Acceptance criteria
Inputs:
Technical details
The text was updated successfully, but these errors were encountered: