The Zurich release has arrived! Interested in new features and functionalities? Click here for more

How can I add language code to sys_languages table of PDI?

jiyoung ko
Tera Contributor

I'd like to test add new language which servicenow platform does not supported, such as arabic.

I think that I need to add language code to sys_languages table first of all.

but I've heard that it has been blocked to access this table since san-diego version.

So, How do I can add new language code to the sys_languages table? 

It would be appreciate that whoever prvide me a guide to add arabic language to the instance.

1 ACCEPTED SOLUTION

@Maik Skoddow,

So in the Tokyo release you can (manually) add new languages once again. In SanDiego we had to restrict it (via requests raised via NowSupport) because we were changing the functionality of the "id" field. 

Previously the length was only 2 chars long, which meant you could only add a "Language". However, there's a lot of use-cases and scenarios to support "locales" which follows the "BCP-47" format.

For those who don't know, is the idea of correlating a Language and a Country. An example is Mexican Spanish as it's not "es" it would be "es_MX", or Austrian German would be "de_AU" for example.

This type of requirement is very important for HR and CSM scenarios, depending on the Organisation and it's scale. Hence you will now see some new features on the [sys_language] once you've upgraded to Tokyo.
Side note - yes an English choice is automatically added to the sys_user.preferred_language field (which drives the language selectors across the instance) to make it easier, and if that choice isn't translated it will always show the English when in other languages just to be safe,

I'll talk more about all of this in my blog closer to the Tokyo release, because there's a whole bunch of interesting things to discuss,

Many thanks,
Kind regards

--------------------------------------------------------------------
Director of Globalization Deployment, Internationalization

View solution in original post

3 REPLIES 3

Maik Skoddow
Tera Patron
Tera Patron

Hi

Yes, you are right: ServiceNow has blocked access to the sys_language table. The only way to have a new entry in that tableis installing a language package.

If a language is not available please reach out to your ServiceNow sales rep to clarify how you can contribute to a new language package.

Maik 

@Maik Skoddow,

So in the Tokyo release you can (manually) add new languages once again. In SanDiego we had to restrict it (via requests raised via NowSupport) because we were changing the functionality of the "id" field. 

Previously the length was only 2 chars long, which meant you could only add a "Language". However, there's a lot of use-cases and scenarios to support "locales" which follows the "BCP-47" format.

For those who don't know, is the idea of correlating a Language and a Country. An example is Mexican Spanish as it's not "es" it would be "es_MX", or Austrian German would be "de_AU" for example.

This type of requirement is very important for HR and CSM scenarios, depending on the Organisation and it's scale. Hence you will now see some new features on the [sys_language] once you've upgraded to Tokyo.
Side note - yes an English choice is automatically added to the sys_user.preferred_language field (which drives the language selectors across the instance) to make it easier, and if that choice isn't translated it will always show the English when in other languages just to be safe,

I'll talk more about all of this in my blog closer to the Tokyo release, because there's a whole bunch of interesting things to discuss,

Many thanks,
Kind regards

--------------------------------------------------------------------
Director of Globalization Deployment, Internationalization

Hi Alex,

thanks for that insiight. Looking forward to the mentioned article!

Maik