Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.

Use the translate and learn property

Log in to subscribe to topics and get notified when content changes.

Use the translate and learn property

When the glide.translate.learn system property is set to true, the instance creates stub records in the translation tables when it encounters strings that have only an English version.

Before you begin

Role required: admin

About this task

The instance creates stub translation records for strings only in forms and records that ServiceNow provides or that have been opened at least once. In practice, you need to know which modules contain untranslated customer-created strings to use this approach with customer-created content.
Note: Using this method prevents the use of the Export Untranslated Strings method. This method creates stub translation records and the method of exporting untranslated strings identifies only missing translation records.

Procedure

  1. Navigate to System Properties > System Localization.
  2. Activate Display translation prefix on translatable strings.
    Translation property
  3. Activate the Translate and Learn property.
    System property entry 'Add the labels, messages, or choices to the appropriate table in English with an ending of the language code for newly added customizations that are missing translations (Translate and Learn) Yes | No'
  4. Change your user language to one of the non-English languages installed on your instance.
  5. Open each of the customer-created or customer-modified UI forms.
    The instance creates stub translation records for each untranslated but translatable string. These records are marked with the target language in the Label (translate) field, such as [fr].
  6. Open each translation table and find the stub translation records.

Example: Untranslated customer-created HR modules

For example: A user switches to the French language and opens a record. When loading the form, the instance looks at the Translated Field table to find the French translation for each field. If an appropriate translation record is not found, the instance automatically generates a stub record for that missing data, which can be manually translated.

The following HR application is missing translations for two modules:

Figure 1. HR application missing translations
HR missing translations
The suffix [fr] indicates that there is a French translation missing.
Note: These modules have been opened at least once already. Otherwise, the [fr] suffix would not appear.

Because translation prefixes are enabled, the prefix TRF: indicates that the entry can be found in the Translated Name / Fields table. The following image shows untranslated modules, located using the filter [Label (translate)] [contains] [fr]:

Figure 2. Example untranslated modules
Untranslated modules
Feedback