Standard change templates - how to translate fields ?

mathieu_brule
Kilo Sage

Hi all 🙂

 

I have a requirement from my customer, who wants to be able to translate fields in a standard change template.

 

For example :

a standard change template purpose the implementation plan to be pre filled

I set the implementation plan in English

I would like to be able to set it in French, and then other languages

 

As a result :

If a user has his language set in English, he selects the standard change template, and the implementation plan of the change is filled in the english value of the template

If a user has his language set in French, he selects the same template, and the implementation plan of the change is filled in the french value of the template

and so on for any other languages...

 

I'm afraid there is no any solution, I've tried following things :

- in the template, with my profile in english, set the value in english, set my profile in french, translate the value, then the template keeps the french translation, whatever my profile language

- try to create a translated field in the change, and try to set it in my template, same result...

 

I'm surprised there could be no any solution for this kind of requirement...

 

 

Could you please help me to find a solution ? Has anyone worked on this ?

1 ACCEPTED SOLUTION

Mark Manders
Mega Patron

Template fields aren't translatable. Do you have dynamic translation on the instance, because then you could use that to update the fields to the viewer's language.

If not, I think there is no other solution than create them in all languages and use user criteria based on language to make them available.
Just one question: who is resolving the changes? Because I think that an in French created change isn't understood by an Englishman.


Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark

View solution in original post

4 REPLIES 4

Mark Manders
Mega Patron

Template fields aren't translatable. Do you have dynamic translation on the instance, because then you could use that to update the fields to the viewer's language.

If not, I think there is no other solution than create them in all languages and use user criteria based on language to make them available.
Just one question: who is resolving the changes? Because I think that an in French created change isn't understood by an Englishman.


Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark

Hi Mark,

 

Thanks for your feedback !

 

No, my customer doesn't have Dynamic translation, but it could be great to talk about it with him, thanks for the proposal 😉

Moreover, if I well understood, I have no other solution, except implementing a custom "thing", which could be difficult to set up and make it effective, or using user criteria that i had already in mind, indeed...

 

Concerning your question, I'm not really aware about who resolve the changes, I'm only wondering on my customer's need 😉

 

 

 

Without any dynamic translation, this is an essential question to ask before you fulfill your customer's need. Great that a French user can select a standard change in French, but without dynamic translation, the English resolver does not know what he needs to do.


Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark

Hi Mark,

 

So he will have to learn french language 😛

 

More seriously, yes you're right, and that's why my customer would need to translate templates. But I don't think he will be ok for using Dynamic translation, as it uses Integration hub.

Btw, I have all information thanks to you 😉