The function of this presentation is to explain the processes for adding translations to a Scoped Custom Application in ServiceNow. English to Spanish translations are covered, but the methods employed apply to all languages.

1. Language Translations
Tested in ServiceNow
Istanbul & Jakarta Releases
4/17/2018 1© 2018 DataIntent LLC

2. Purpose
The function of this presentation is to explain the processes for adding
translations to a Scoped Custom Application in ServiceNow.
English to Spanish translations are covered, but the methods employed
apply to all languages.
4/17/2018 2© 2018 DataIntent LLC

3. Language Internalization
4/17/2018 3© 2018 DataIntent LLC

4. Activating plugins and languages is performed by the purchaser of the custom
application for their Global ServiceNow production instance.
The same activations are performed in the custom application development
instance.
Language Internalization
ServiceNow plug-in activation writes to Global Application Scope.
4/17/2018 4© 2018 DataIntent LLC
Knowledge
Article

5. Facts About Global Scope:
• All custom app components must in the custom application scope.
• Typically, only applications provided by ServiceNow are in the global scope*
• However all custom apps created before application scope was implemented
are also in the global scope*
• Apps in the global scope are also not eligible for upload to the ServiceNow
Store*
• When language internalization is activated data is written to the global scope
• This data can be effected by ServiceNow updates
• This data should be confirmed by language expert although changes are made
in the global scope
* Quotes from ServiceNow documentation
4/17/2018 5© 2018 DataIntent LLC

6. Facts About Custom Application Scope
The only objects that can be imported into Scoped Custom Applications are records
written to the Scoped Custom Application, other objects are written to the global
application by default; And cannot be uploaded to the ServiceNow store.
4/17/2018 6© 2018 DataIntent LLC

7. Global VS. Custom Scoped Client Scripts
Client Scripts which are created as part of a Scoped Custom
Application, are executed slightly differently than their non-scoped
counterparts.
Inaccessible APIs for Scoped Custom Applications Modified APIs for Scoped Custom Applications
GlideRecord GlideAjax
window g_form
document GlideDialogWindow
$ (Prototype library)
$$ (Prototype library selector shortcut)
jQuery
$j (jQuery shortcut)
$F (Sizzle form element value shortcut)
This information was provided by Cory Seering, a ServiceNow Employee via the Developer Community.
Open attached .pdf for more details.
4/17/2018 7© 2018 DataIntent LLC

8. Translation Objects
The following slides explain the
process of inserting translations for:
• Modules
• Form sections
• Field labels
• Choices
• Translated text
• Using reference fields as an import
data workaround
• Client side scripts
• Server side scripts
4/17/2018 8© 2018 DataIntent LLC

9. Modules
4/17/2018 9© 2018 DataIntent LLC
Example of modules filtered
using the word “translate”

10. Modules — Structure
Module Created
in Studio
New Module
ServiceNow Browser
Module labels can
now be created /
edited via:
Translation Support >
Translated Name /
Fields
Exact match of
module label in
System
Localization
Application
menu?
New Module
Saved
Label
(en)
No
Yes
Label Translated
by System
New Label
(es)
Label
(es)
4/17/2018 10© 2018 DataIntent LLC

11. Modules — Inserting
1. Follow the menu path: Translation Support > Translated Name / Fields
2. Complete:
1. Label = (translated text)
2. Element = title
3. Language = “es”
4. Table = sys_app_module
5. Value = English label
3. Click submit button.
4/17/2018 11© 2018 DataIntent LLC

12. Modules — Workaround
If the steps on the slide labeled “Modules — Inserting “ fails
(as it occasionally does); the steps below provide a workaround.
1. Login to instance with the language required for the translation selected.
2. Change the Module title from ServiceNow browser.
3. Update.
4. The new label is saved in the language.
Notes:
The setting of Global is automatically applied to application usage.
(Not in Global ServiceNow app, but globally across the custom app)
ServiceNow
Browser
Module labels can
be edited via:
Translation Support
> Translated Name /
Fields
or
Translation Support
> Field Label
4/17/2018 12© 2018 DataIntent LLC

13. Disclaimer — Modules Workaround
4/17/2018 13© 2018 DataIntent LLC

14. Disclaimer — Modules Workaround
WARNING:
• Making configuration changes after switching to another language
may have unforeseen consequences, including wiping out 90% of
your translations for an entire table.
• When changing the language in the ServiceNow Navigator, Studio IDE
automatically changes to the newly selected language.
• When the language is set back to the original language in the
ServiceNow Navigator, Studio IDE does not change back to the
original language, a browser language change and refresh is required
to set Studio IDE back to English.
4/17/2018 14© 2018 DataIntent LLC

15. Scenario
1. A table is created in English.
2. Spanish labels and choices are applied to fields in the table.
3. Language settings are changed to another language.
4. A change is made to an object in the table using Studio IDE.
(example: an attribute is changed for one column)
5. The labels are changed to original English value while plurals for the
labels are not effected.
6. All other translated text, choices, etc. may also* be changed
to an English value.
*Results in testing varied
4/17/2018 15© 2018 DataIntent LLC

16. Scenario Example — Before & After
4/17/2018 16© 2018 DataIntent LLC

17. Form Sections
4/17/2018 17© 2018 DataIntent LLC
Example of form sections (tabs) from my personal instance

18. Form Sections — Structure
Translation Support >
Translated Name /
Fields table
New
Record
Created
(es)
System UI > Forms
(ServiceNow Browser)
Form Sections
Edits performed using
Translation Support >
Translated Name / Fields
table
Form
(Studio)
Form Section
(en)
Form Section
(en)
Form Section
(en)
Position Sys UI section Table
Position Sys UI section Table
Position Sys UI section Table
4/17/2018 18© 2018 DataIntent LLC

19. Form Sections — Inserting
1. Navigate to Translation Support > Translated Name / Fields.
2. Click New button.
3. Select the following options:
a. Table = "sys_ui_section"
b. Element = "caption"
c. Language = “es“
d. Value = "Notes" (Provide the English name of the form section)
e. Label(translate) = “Notas" (Translated Spanish text)
4. The ID field is used to identify a specific record.
5. Click Submit button.
4/17/2018 19© 2018 DataIntent LLC

20. Form Sections — Workarounds
The following problems related to form sections require workarounds.
Issues:
• Process stopped working for multiple tabs.
• The system only matches the first instance of the caption per Scoped Custom
Application.
• Broken relationship between sys_ui_section & sys_ui_form_section
documented in ServiceNow Developer’s Community.
• Show / Hide form sections is not possible because JavaScript / JSON
cannot recognize the full UTF-8 character set (including diacritics).
4/17/2018 © 2018 DataIntent LLC 20

21. Workaround — Displaying Form Sections
Show / hide a UI Action (form button) based on browser session language settings:
• Display a table of translations as a system message.
• Display a Knowledge Article with a table of translations in a new browser
window using a button.
• Display a Knowledge Article with a table of translations in a new browser
window using a check-box (true/false) via a UI Policy.
4/17/2018 21© 2018 DataIntent LLC

22. Hide / Show UI Action (form button)
Requirement:
A client script that hides or shows a button based on the user’s session browser
language settings.
Issue
The script contains the API g_lang which is not documented in any ServiceNow
materials and is not found in JavaScript, JSON, or Angular scripting.
Question for ServiceNow:
Is usage of the API g_lang, considered being within best practices for ServiceNow?
4/17/2018 22© 2018 DataIntent LLC

23. Hide / Show Button — Language Condition
Client Script
This script contains $$; A Prototype library selector
shortcut API.
The Prototype library selector shortcut API is Inaccessible
to Scoped Custom Applications with OOB settings.
Document Object Model (DOM) manipulation is required
to utilize the Prototype library selector shortcut API.
In the custom app, create an explicit system property to
allow DOM manipulation by creating the property
glide.script.block.client.globals set to false.
Issue
DOM manipulation is considered opting out of best
practices and avoided if possible, because of
maintainability issues when browsers are updated.
4/17/2018 23© 2018 DataIntent LLC

24. UI Action — System Message
Requirement: The form contains a UI Action (form button) that opens a URL
link in a new browser window leading to a Knowledge Article with a table
containing translations for the section labels. The button is shown or hidden
based on the current browser language settings.
Issue
A table containing section or field labels is a simple way to deal
with translations, but impedes a seamless UI experience.
4/17/2018 24© 2018 DataIntent LLC

25. UI Action — System Message
UI Action Settings:
• Active — true
• Show insert — true
• Show update — true
• Client — false
• Form button — true
• Condition —
onClick()
4/17/2018 25© 2018 DataIntent LLC

26. UI Action — Script
UI Action Script
4/17/2018 26© 2018 DataIntent LLC
Issue
The code “current.setAbortAction” is utilized to avoid the user “losing” new entries on the form; this
workaround adds an error message to the info message and could cause confusion for the end-user.

27. UI Action — System Message
System message displayed following mouse click.
4/17/2018 27© 2018 DataIntent LLC

28. UI Action — System Message Without Error
System message displayed following mouse click.
Issue
If current.setAbortAction is not utilized the user exists the record returning to list view new while new
entries on the form are cleared.
4/17/2018 28© 2018 DataIntent LLC

29. UI Action — Open URL In A New Window
Requirement:
Open a URL linking to a Knowledge Article in new browser window using a UI
Action (form button) with a table containing translations for the section labels.
4/17/2018 29© 2018 DataIntent LLC

30. UI Action — Open URL In A New Window
4/17/2018 30© 2018 DataIntent LLC
Requirement (continued):
The button is shown or hidden based on the current browser language settings.

31. UI Action — Open URL In A New Window
4/17/2018 31© 2018 DataIntent LLC

32. UI Action — Open URL In A New Window
Requirement (continued):
The button is shown or hidden based on the current browser language settings.
4/17/2018 32© 2018 DataIntent LLC
When the Traducir
button is clicked a
Knowledge Article is
opened in a new
window

33. UI Action — Open URL In A New Window
4/17/2018 33© 2018 DataIntent LLC
Issue:
A table containing section or field labels is a simple way to deal with translations, but impedes
a seamless UI experience.

34. UI Action — Open URL In A New Window
UI Action Settings:
• Active — true
• Show insert — true
• Show update — true
• Client — true
• Form button — true
• OnClick — viewPortal()
• Condition — !(new KBCommon().isStackNameDialog())
4/17/2018 34© 2018 DataIntent LLC

35. UI Action — Open URL In A New Window
UI Action Script
4/17/2018 35© 2018 DataIntent LLC

36. UI Policy — Open URL In New Window
Requirements:
• A UI Policy that opens a URL linking to a Knowledge Article in new browser
window containing translations for the section labels.
• The check-box is shown or hidden based on the current browser language
settings.
4/17/2018 © 2018 DataIntent LLC 36

37. UI Policy — Open URL In New Window
UI Policy script:
4/17/2018 © 2018 DataIntent LLC 37

38. Form section:
Technical metadata - Metadata técnica
Form Sections With Diacritics
This workaround is required for tabs containing text with diacritic accents.
Examples: á, è, í, ú, etc.
Issue
Intrusive — the workaround mentioned here, requires changes to the
Scoped Custom Application.
4/17/2018 38© 2018 DataIntent LLC

39. Workarounds — Displaying Form Sections
Show / hide form view containing new fields (other language), based on browser
session language settings:
• The new fields are creating in the existing English table with corresponding fields.
• The data is copied from newly created fields to the corresponding English fields in
the application.
• The data is cleared from the new language field when the form is closed. If an
existing record is opened the fields auto populate with data from the server.
4/17/2018 39© 2018 DataIntent LLC

40. New Sections and Views
Form Section
(en)
Form
(Studio)
Original View
(en)
Form Section
(es) New View (es)New Section
Original Section
Form Section
(pb)
New View (pb)
New Section
4/17/2018 40© 2018 DataIntent LLC

41. Tables & Fields
Form Section
fields
(en)
Form Section
fields
(es)
Form Section
fields
(pb)
Form
(Studio)
Original Field
(en)
4/17/2018 41© 2018 DataIntent LLC

42. Tables & Fields
Form Section
fields
(en)
Form Section
fields
(es)
Form Section
fields
(pb)
Form
(Studio)
Original Field
(en)
4/17/2018 42© 2018 DataIntent LLC
Form Section
fields
(en)
Form Section
fields
(es)
Form Section
fields
(pb)

43. Copying & Clearing Data
4/17/2018 43© 2018 DataIntent LLC
Form Section
fields
(en)
Form Section
fields
(es)
Form Section
fields
(pb)
Form
(Studio)
Original Field
(en)
Form Section
fields
(en)
Form Section
fields
(es)
Form Section
fields
(pb)

44. Labels
4/17/2018 44© 2018 DataIntent LLC
Examples of form labels from my personal instance

45. Labels — Structure
(ServiceNow Studio)
Language
Label
Hint
Plural
Help / URL
Column label
(ServiceNow Studio)
Language
Label
Hint
Plural
Help / URL
Table label
Translation Support >
Field Labels
Data Dictionary
sys_documentation.list
ServiceNow Browser
Translated
label
4/17/2018 45© 2018 DataIntent LLC

46. Labels — Inserting
1. Follow the menu path: Translation Support > Language file or
enter sys_documentation.list in the ServiceNow browser and press the Enter key.
2. Complete:
1. Table = x_table
2. Label = (translated text)
3. Plural = (plural of translated text)
4. Language = “es”
5. Help text
6. Hint text
3. Click submit button.
4/17/2018 46© 2018 DataIntent LLC

47. 4/17/2018 47© 2018 DataIntent LLC
Choices
Examples of a choice lists from my personal instance

48. Choices — Structure
(ServiceNow Studio)
Column labelTable Choice
Hint
Language
Label
Value
Sequence
Translation Support >
Choices
sys_choice.list
Data Dictionary
ServiceNow Browser
Translated
choice
4/17/2018 48© 2018 DataIntent LLC

49. Choices — Inserting
The following works with Choice & String fields.
1. Navigate to Translation Support > Choices.
2. Click New button.
3. Choose the following options,
a. Table = “x_table"
b. Element = “u_field"
c. Language = “es“
d. Value = “a" (choice value must match translation)
e. Label(translate) = Translated text
f. Sequence = “0” (sequence much match translation)
g. Hint
4. Click on Submit button.
Translated choices are not
listed in alphabetical order
like the English choices.
This may be fixed with a
Business Rule…
4/17/2018 49© 2018 DataIntent LLC

50. Translated Text
Translated text entered into records
4/17/2018 50© 2018 DataIntent LLC
Examples of translated text from my personal instance

51. Facts — Translated HTML / Text
• Translated Text & Translated HTML have the
same structure and function
• Translated HTML / Text is applied to one record
• The text displayed depends on the user’s
language settingRecord no. 001
Translated Text
English
Translated Text
Spanish
One Record
4/17/2018 51© 2018 DataIntent LLC

52. Non-Translated Field Data
Non-translated field data is not effected by translated text in the
record. All users have the same view of non-translated field data
regardless of their language setting.
Translated HTML
or Text
Record no. 001 String True / False
Non-translated field data is not effected by
language settings
4/17/2018 52© 2018 DataIntent LLC

53. Editing Translated HTML / Text Fields
Editing:
• Translated HTML & Translated Text can be edited
directly within a record
or via the menu path:
Translation Support > Translated Text.
• Only the translated HTML / Text is displayed or edited
using Translated Texts table; the non-translated fields
for the record are not available in this table.
Record no. 001
Translated Text
English
Translated Text
Spanish
One Record
Translated Texts Table
Translated Text
Spanish
4/17/2018 53© 2018 DataIntent LLC

54. Translated Text / Translated HTML
Three useful functions for working with translated text:
• User Entry
• Reference field
• Redirect to another table*
*Not actually translated text but requirement of displaying translated
text to user is achieved
4/17/2018 54© 2018 DataIntent LLC

55. User Entry — Structure
HTML / Text
English
ServiceNow Browser User language setting is English
Record no. 001 String True / False
HTML / Text
English
Record no. 002 String True / False
HTML / Text
Spanish
ServiceNow Browser User language setting is Spanish
Record no. 001 String True / False
HTML / Text
Spanish
Record no. 002 String True / False
Attachment
English
Attachments can be
viewed by all users
Attachment
Spanish
4/17/2018 55© 2018 DataIntent LLC

56. HTML / Text — Record Viewed in English
Attachment
English
Attachment
Spanish
HTML bar
Translated
Text
String
String
True/False
Choice
Reference with
translated text
Choice
String
Translated
HTML
Number
Reference
Decimal
4/17/2018 56© 2018 DataIntent LLC

57. HTML / Text — Record Viewed in Spanish
Attachment
English
Attachment
Spanish
HTML bar
Translated
Text
String
String
True/False
Choice
Reference with
translated text
Choice
String
Translated
HTML
Number
Reference
Decimal
4/17/2018 57© 2018 DataIntent LLC

58. Reference Field Workaround
Using reference fields as an import data workaround
4/17/2018 © 2018 DataIntent LLC 58

59. Use reference fields
containing translated
text to import
multiple translations.
The text displayed
depends on the user’s
language setting.
Reference Field — Structure
Reference Field
Form
Record no.
Translated
Text or
HTML
Reference Table
Fields
ServiceNow
Generated
columns
4/17/2018 59© 2018 DataIntent LLC

60. A script in the UI
policy shows
the relevant
field based on
logged-in
language
settings.
Create as many
tables as
required table
using one table
per language.
Reference Field Redirect — Structure
Reference Field
Spanish
Form
Countries
(Table with records in English)
Record no. 001
Record no. 002
Afghanistan
Algeria
Albania
Record no. 003
Países
(Table with records in Spanish)
Record no. 001
Record no. 002
Afganistán
Albania
ArgeliaRecord no. 003
Fields
Reference Field
English onLoad Client Script
setDisplay fields True/False
4/17/2018 60© 2018 DataIntent LLC

61. UI Policy Script
function onLoad() {
//Use g_lang to retrieve language settings from browser session
//(this is not the user language setting stored on server)
//Use g_form.setDisplay with field set with value of true / false
//Use g_lang para recuperar configuraciones de idioma de la sesión del navegador
// (esta no es la configuración de idioma del usuario almacenada en el servidor)
// Usa g_form.setDisplay con el campo establecido con el valor de verdadero / falso
if(g_lang == 'en'){
g_form.setDisplay('u_colores', false);
g_form.setDisplay('u_colors', true);
g_form.setDisplay('u_cor', false);
}
else if(g_lang == 'es'){
g_form.setDisplay('u_colores', true);
g_form.setDisplay('u_colors', false);
g_form.setDisplay('u_cor', false); }
else if(g_lang == 'pb'){
g_form.setDisplay('u_colores', false);
g_form.setDisplay('u_colors', false);
g_form.setDisplay('u_cor', true);
}
}
This script shows the user
one of three fields based
on session browser
language settings.
4/17/2018 61© 2018 DataIntent LLC

62. Translated Text — Inserting
Translated text
Edit the Record directly or:
1. Follow the menu path: Translation Support > Translated Text.
2. Required fields:
1. Document (match to record)
2. Field name
3. Language
4. Table name
5. Value (translated text)
3. Click the Submit button.
Issue
The Attributes for Reference Auto Complete Fields
do not work with translated text (numbers work
though...) There may be a way to use a client
script to facilitate this process.
4/17/2018 62© 2018 DataIntent LLC

63. Client / Server Development
4/17/2018 63© 2018 DataIntent LLC
Jelly : Executable XML

64. Client / Server Development Suggestions:
• It is recommended to only change scripts manually; The dangers
presented by importing this data outweighs any benefits, also data is
written to the Global Application by default.
• If an existing script references a field label and not a field value, the
script must be changed to reference the value.
• Having labeled tables allows users logged in with other languages to
view actions more clearly.
4/17/2018 © 2018 DataIntent LLC 64

65. Client Scripts:
• Provide description in both languages ex.:
• Display u_book_language or u_book_idioma based on session language — en
• Muestra u_book_language o u_book_idioma porque en el idioma de la sesión —
es
• Messages:
• Create a message and a translated message
or
• Insert messages directly into code
• if(g_lang == 'en’){ g_form.addInfoMessage('The Language field has "English"
values.’)
• Script: Add translated notes if helpful
• // English note
• //nota en español
4/17/2018 65© 2018 DataIntent LLC

66. UI Policies
• The Short description field contains limited space probably not helpful to
store translations here. A Knowledge Article can be used to display a
cross walk with translations.
• The Description field can be use to enter details in multiple langueges.
• Ex. Data info. — en
Información sobre los datos — es
• When to Apply conditions & UI Policy Actions are saved by ServiceNow as
code containing the u_field references, no changes are required for
translations.
4/17/2018 66© 2018 DataIntent LLC

67. END OF PRESENTATION
4/17/2018 © 2018 DataIntent LLC 68