Propose new features

Fingerprint

The piece of text below is a shortened, hashed representation of this content. It's useful to ensure the content hasn't been tampered with, as a single modification would result in a totally different value.

Value: aa49a1472398ed9242573c848d1c4abbedd1991cedc48867dfe5187df05ea18b

Source: {"body":{"en":"<p><strong>**Is your feature request related to a problem? Please describe.**</strong></p><p>The current solution for multi-languages fields works well when the organization has 3, 4 or 5 languages, but we'll be working with a client that has a much higher number of languages, and the current solution does no escale</p><p><strong>**Describe the solution you'd like**</strong></p><p>We propose improving the UX for these fields and we have two suggestions:</p><ol><li>Use a dropdown per each field. This wouldn't change much of the current behavior, only that locales would be hidden in the dropdown.</li><li>Use a dropdown for the whole form. On top of each form, show a dropdown that will change the fields shown to use the selected language version. Non-translatable fields will be shown anyway. This implies a bigger change of behavior and more work, dev-wise.</li></ol><p>We're not sure about what's the best approach, or if we should find even another approach to this problem.</p><p><strong>**Describe alternatives you've considered**</strong></p><p>None.</p><p><strong>**Additional context**</strong></p><p>None.</p><p><strong>**Does this issue could impact on users private data?**</strong>\r\n</p><p>No.</p>"},"title":{"en":"Improve the UX for multi-lingual fields when the organization has multiple languages"}}

This fingerprint is calculated using a SHA256 hashing algorithm. In order to replicate it yourself, you can use an MD5 calculator online and copy-paste the source data. ×