Might be an easier task to create just 1 attribuut with the value and one for the language.
Then create multiple records one for each language and then by mean of xpath constraints or mircroflows make sure the right options are available by selecting the data based on the user’s language setting.
Theother option is, as the widgets are strongly related to the selected attribute, to create multiple fields that show the specific language value attribute and show the correct version with conditional visibility.
But I would consider using the first approach.
You can impliment this, but this can be a bit tricky.
First make a NPE(FeedbackNPE) with one attribute (eg. Lang)
associate it with your Feedback entity and the entity which is parent to feedback as well.
On the referrence selector(with FeedbackNPE_Parent-association)
you can call a microflow on the
selectable object tab, in the microflow, First add a retrieve activity and then
retrieve all your preferred objects from the database, and then retrieve the language from
current user, Now based on current language you can populate one NPE each(By using a loop) for feedback object with Lang attirbute
set based on Feedback object and selected entity.
Now you can return this list.
Hope It helps!