I strongly support incorporating this functionality because, currently, the only workaround involves hardcoding values based on the selected eng values. This approach not only slows down the process when creating new templates, but also complicates value management significantly. Each time there's a change in translation or the addition of a new value, the template itself needs to be updated, which is both time-consuming and error-prone.
I strongly support incorporating this functionality because, currently, the only workaround involves hardcoding values based on the selected eng values. This approach not only slows down the process when creating new templates, but also complicates value management significantly. Each time there's a change in translation or the addition of a new value, the template itself needs to be updated, which is both time-consuming and error-prone.