Contents Now Platform Administration Previous Topic Next Topic Language internationalization support Subscribe Log in to subscribe to topics and get notified when content changes. ... SAVE AS PDF Selected Topic Topic & Subtopics All Topics in Contents Share Language internationalization support The ServiceNow system supports multiple languages, using UTF-8 for international characters. When a user logs in, the language for the instance session is determined by the following logic: If the language selection at login is enabled, that language is used. If not, the language preference selected using the language picker in the header bar is used. If not, the user's language setting in the User [sys_user] table is used. If none of the above are true, the system default language is used. Some areas of the system are not translated, including journal fields, report titles, and any field that stores free-form text. These fields remain in the language used to create them. When creating a custom field, you must add the labels in the Field Label table because they are not added automatically. Table 1. FAQ Question Answer Will my custom fields be translated? When you create a field, it does not create a translated label. Labels for custom fields are created with a language of English (en). You can, however, translate the fields manually. I am not seeing journal fields translated. User-defined string fields, such as short description, additional comments, and report titles are not translated. They appear in the language they were created in. Set default language for an instanceYou can set the default language for an instance. Do this after activating the plugin for the desired language.User specific languageThe user has several choices for identifying the language to be used for the instance, as described here.Translation tablesServiceNow stores translation information in these tables.Translate new customizationsWhen using one of the Internationalization plugins, most of the fields in the instance are automatically translated. However, customizations are not translated automatically, and need to be translated by hand. In this case, it is best to locate the individual untranslated strings, and insert those translations manually.Service catalog buttonsYou can specify language-specific messages for buttons in these service catalog screens: Cart, Edit Cart, and Check Out (including workflows and approvals). On this page Send Feedback Previous Topic Next Topic
Language internationalization support The ServiceNow system supports multiple languages, using UTF-8 for international characters. When a user logs in, the language for the instance session is determined by the following logic: If the language selection at login is enabled, that language is used. If not, the language preference selected using the language picker in the header bar is used. If not, the user's language setting in the User [sys_user] table is used. If none of the above are true, the system default language is used. Some areas of the system are not translated, including journal fields, report titles, and any field that stores free-form text. These fields remain in the language used to create them. When creating a custom field, you must add the labels in the Field Label table because they are not added automatically. Table 1. FAQ Question Answer Will my custom fields be translated? When you create a field, it does not create a translated label. Labels for custom fields are created with a language of English (en). You can, however, translate the fields manually. I am not seeing journal fields translated. User-defined string fields, such as short description, additional comments, and report titles are not translated. They appear in the language they were created in. Set default language for an instanceYou can set the default language for an instance. Do this after activating the plugin for the desired language.User specific languageThe user has several choices for identifying the language to be used for the instance, as described here.Translation tablesServiceNow stores translation information in these tables.Translate new customizationsWhen using one of the Internationalization plugins, most of the fields in the instance are automatically translated. However, customizations are not translated automatically, and need to be translated by hand. In this case, it is best to locate the individual untranslated strings, and insert those translations manually.Service catalog buttonsYou can specify language-specific messages for buttons in these service catalog screens: Cart, Edit Cart, and Check Out (including workflows and approvals).
Language internationalization support The ServiceNow system supports multiple languages, using UTF-8 for international characters. When a user logs in, the language for the instance session is determined by the following logic: If the language selection at login is enabled, that language is used. If not, the language preference selected using the language picker in the header bar is used. If not, the user's language setting in the User [sys_user] table is used. If none of the above are true, the system default language is used. Some areas of the system are not translated, including journal fields, report titles, and any field that stores free-form text. These fields remain in the language used to create them. When creating a custom field, you must add the labels in the Field Label table because they are not added automatically. Table 1. FAQ Question Answer Will my custom fields be translated? When you create a field, it does not create a translated label. Labels for custom fields are created with a language of English (en). You can, however, translate the fields manually. I am not seeing journal fields translated. User-defined string fields, such as short description, additional comments, and report titles are not translated. They appear in the language they were created in. Set default language for an instanceYou can set the default language for an instance. Do this after activating the plugin for the desired language.User specific languageThe user has several choices for identifying the language to be used for the instance, as described here.Translation tablesServiceNow stores translation information in these tables.Translate new customizationsWhen using one of the Internationalization plugins, most of the fields in the instance are automatically translated. However, customizations are not translated automatically, and need to be translated by hand. In this case, it is best to locate the individual untranslated strings, and insert those translations manually.Service catalog buttonsYou can specify language-specific messages for buttons in these service catalog screens: Cart, Edit Cart, and Check Out (including workflows and approvals).
