Translated Lookup Meaning: Does not auto translate when application language is switched
Summary:
Hello,
Our implementation scope is to implement across geographies and to meet this compliance requirements we have designed -
- Lookup with their meanings in multi languages
- Used this lookup to build a table value set that is referenced in DFFs across HCM
Noticed when a French user selects a value in French and drafts the action but logs in back with English as the default language the French translated value stays as it is prompting the user to select its English translated value.
This is not only confusing from an user experience but is also impacting our conversions.
Has anyone face similar issue, if yes, what was the solution.
Tagged:
0