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
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.
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:
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
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]