Employee Center Portal Translation for HR Journeys

[Hardik10]

Hi @Alex Coope - SN ,

First, thank you for your post on enabling translation for the portal—it was incredibly helpful!

We’re currently facing a major localization challenge in the HRSD module, specifically with Journeys used for onboarding and employee lifecycle events. Here's the issue:

• We’ve enabled translation for Activity Sets and Activities using the dynamic translation and localization framework.
• However, when users access their Journey records in non-English languages via Employee Center Pro, everything still appears in English.
• The translations exist and are working in the backend, but they’re not reflected on the Employee Center UI.

Additionally, we’re struggling with translating HR Tasks within the Journey:

• These tasks originate from HR Core Task, and translating their short descriptions would mean duplicating translations.
• We’re unsure if it’s advisable to change the field type of description and short_description on the Task table to translated_text.

We also want to enable dynamic translation on-demand for fulfillers in modules like Incident and Request. This functionality is already enabled, but we’re unsure whether changing the field type to translated_text would impact dynamic translation. For these modules, we don’t want to store translated values in sys_translated_text, and we’re trying to understand the best approach.

We’ve opened a ServiceNow Case for this and attached a screenshot of the Journey detail page from Employee Center Pro for reference.

In summary:

• Localization framework works for Activity Sets and Activities, but translations are not visible on Employee Center.
• HR Task translation is unclear—especially regarding duplication and field type changes.
• Need guidance on dynamic translation for fulfillers without storing translations in sys_translated_text.

Any insights or suggestions would be greatly appreciated!
@barveaparna , @Madhu123 @swaghosh 

[Hardik10]

@Alex Coope - SN , looks like we are able to solve the translation issue for majority of the page. 

Activity Set - it supports translation framework, so with artifact or direct translation (change lang and add translated text) helped us to solve this. 

Activities/HR Template - with "use global description" field and translation framework, we are able to translate the values, and it is now visible to end-user in their preferred language. 

So, from ESC portal perspective, I think we are good with this translation capability. Just wanted to let you know the progress.