Localization / Translation of HR (case or task) templates

[Christian Prob2]

Hi Community,

I think I know the answer, but would appreciate confirmation that I am not missing something:

If the same HR Service is to be offered and made requestable in multiple languages (in our case FQ and EN) I basically have to create separate services, case and task templates for each service as the templates don't really support any of the traditional means (translated text fields / gs.getMessage etc.) for Localization / Translation.

On a Lifecycle Event (LCE) level, I have the option to

1. either create an entire LCE per language or
2. use audiences and add one activity per language for each required activity,

is that roughly what it is?

Thanks,

Christian 

[michaelj_sherid · Accepted solution]

@Christian Probst To answer your question, this is something we are aware of and have this on our road map. There are things that can be done to achieve this. I have a document attached as an example to show how the Short Description can be translated to other languages within the portal. This does require some modification of code, so you will need to track this for upgrade purposes or until this is part of the HRSD Product. Remember modification of Tables, Script Includes and Widgets will "Invalidate" the Restricted Caller Access records so you would need to allow them appropriately. 

Regards,

Mike

[Hugo Tristant1]

Thanks for this post !
Hello @michaelj_sherid, Thanks for your answer and document attached. I guess this is no longer required in Tokyo release at least. The "Thing" in the roadmap is the global description isn't it ?
Unfortunately this is not compatible with the Now Mobile App (PRB1632438). 
So how would you see a Mobile compatible for Localization / Translation of HR (case or task) templates ?

@Christian Prob2 what was the direction you took back then and was it the good choice with experience until now ?