How to translate the section label for a custom view?

georgimavrodiev
Mega Guru

Hello,



Yesterday, I translated my custom application to Russian language.
I actually translated the Menu modules of it along with the Labels of the respective fields in the required forms, including the Section Headers.

Yet, I was not able to translate the Section Labels.

To achieve this, I tried the solutions mentioned into the Translating an Instance document in wiki plus the below Community threads:
https://community.servicenow.com/thread/157693;
&
https://community.servicenow.com/message/877702#877702;
However, nothing works. I am still not able to complete my goal.

Could anyone help me out by providing me with detailed steps how this can be achieved?

Thank you in advance!


Best Regards,

Georgi

1 ACCEPTED SOLUTION

kamals
Tera Contributor

Hi Georgi,



I too faced the same challenge and handled it successfully. Please follow the below steps to display translated Section Labels,



1. Navigate to System Localization > Translated Name / Fields.


2. Click New button.


3. Choose the following options,


        a. Table = "sys_ui_section"


        b. Element = "caption"


        c. Language = "ja" (ja denotes Japanese. Please use appropriate value for your requirement)


        d. Value = "Notes" (Provide the English name of the form section)


        e. Label(translate) = "ノート" (Translated Japanese text)


4. Click on Submit button.



Login / Impersonate using the user account with the desired language and open the form. Translated text will be displayed as section name.



Please mark this answer as correct, if it helps to solve your issue



Regards,


Kamal


View solution in original post

7 REPLIES 7

kamals
Tera Contributor

Hi Georgi,



I too faced the same challenge and handled it successfully. Please follow the below steps to display translated Section Labels,



1. Navigate to System Localization > Translated Name / Fields.


2. Click New button.


3. Choose the following options,


        a. Table = "sys_ui_section"


        b. Element = "caption"


        c. Language = "ja" (ja denotes Japanese. Please use appropriate value for your requirement)


        d. Value = "Notes" (Provide the English name of the form section)


        e. Label(translate) = "ノート" (Translated Japanese text)


4. Click on Submit button.



Login / Impersonate using the user account with the desired language and open the form. Translated text will be displayed as section name.



Please mark this answer as correct, if it helps to solve your issue



Regards,


Kamal


Hi Kamal,





Thank you for willing to help me out!


I have to admit that the steps you shared are exactly those that I used.
The problem is that they did not work for me.

For example, in order to translate the Menu modules, I used these steps, but instead of 'caption' I used 'title' on the Element field + Module [sys_app_module] as table.
Everything worked perfectly.
But performing the same steps for the Sections by just changing the Element to 'caption' + the table to sys_ui_section did not work.
Thus, I decided to raise this thread in order to check if there is another way for me to translate the Sections.

Here, I will add something which I have just found out and it definitely looks strange and also funny to me!
This morning, I enabled List v3 Plugin on my DEV instance in order to perform some tests in regards to a different task.
Now, after checking my system, I may confirm that the Sections have been translated

Strange, right?
It looks like List v3 made the translating visible.



Does anybody know why two users (me and Kamal), who performed the same translating steps on their instances, found themselves into a position in which — for one of them: Kamal — the used steps work, but for me they work only when List v3 Plug is in use?


Best Regards,
Georgi



IT Consultant
Do IT Wise




You can visit us in our Web Site:http://www.doitwise.com


Hi Kamal,





I made some additional tests, in order to translate the Section Labels.
It looks like the steps we used do work, but with a delay.
We simply need to wait for a while for the translate to happen and be shown in the system (the instance).



Anyway, I decided to mark your above reply as the "Correct Answer". Thank you for willing to assist, Kamal!




For the people that may visit this thread in future, I would like to share the below steps, which might be helpful to you if you are looking for a way via which to translate the: Application Modules (visible in the Navigator menu), Section Headers, Labels and Section Labels of a Custom Application of yours.



Please have in mind that the steps below describe how you can translate English to Russian.
If you are planning to use a language different than Russian, then you will have to active a different "I18N: ... Translations" Plugin, once you activate "I18N: Internationalization" Plugin first.



NOTE: Firstly, you need to activate the required plugins.


Navigate to Plugins > activate "I18N: Internationalization" & "I18N: Russian Translations" Plugins;



Translating the Custom Application Modules:


- log as System Administrator into the ServiceNow Instance;


- ensure that you are in the Global scope;
- use the Navigator and navigate to System Localization > Translated Name / Field;
- then, click on New. A form will appear. Fill it in like this:
* Label (translate) — add the Russian name of the Custom Application Module, which you want to translate from English to Russian;
* Element — type here 'title';
* Language — change it to Russian by typing down 'ru';
* Table — locate the Module [sys_app_module];
* Value — here add the English equivalent of the Custom Application Module, which you are currently changing to Russian.
NOTE: add it as it is in the system (shown in the Navigator, under the Custom Application);



Translating the Section Headers:


- log as System Administrator and go to the Custom (application) scope;
- go to Tables and locate the table which Section Header you want to translate from English to Russian.
For example: let's say that this is the Organizations module. So, we need to locate the x_bbt_pragmatic _organization table;
- once we are there, we need to go to the bottom of the form. Under the Related Lists, we need to click on the Label item. Currently, we are seeing it as: Label (1), as we have only one record there — the English;
- click on New and create a new record. Fill it in like below:
* Label —
Организации;
* Plural — Организации;
*
Language — ru;
NOTE: these are all the items you need to fill in;
- click Submit;



Translating the Labels:


- log as System Administrator and go to the required tables;
- select the label, which you want to translate from English to Russian;
For example: let's use the City Positions Table (x_bbt_pragmatic_city_positions):
- log into the table and go to its table columns; then specify each one of them that has to be translated, click on it and go to its "Label" item, below the Related Links.


There, add a new one but using 'ru' as Language and also add the Russian names of the column in the 'Label' and 'Plural' items of the form;



Translating the Section Labels:


- log as System Administrator;
- navigate to System Localization > Translated Name / Fields.
- click the button called: "New";
- choose the following options in the form:
Table = "sys_ui_section";
Element = "caption";
Language = "ru" (for Russian Language);
Value = add here the English name of the Section Label;
Label(translate) = add here the Russian name of the Section Label;
- click the Submit button;




In addition, you may use the following documents:


- Translating an instance - http://wiki.servicenow.com/index.php?title=Translating_an_Instance#gsc.tab=0
- Language Internationalization - http://wiki.servicenow.com/index.php?title=Language_Internationalization#User-Specific_Language&gsc....




Hope the above info will be useful!




Best Regards,


Georgi Mavrodiev



IT Consultant


Do IT Wise



You can visit us in our Web Site: http://www.doitwise.com.


Thanks to everyone!


This was the only piece I was missing for translating an app.



Cheers,


Lon