What are considered not translated values in ServiceNow?

In the context of ServiceNow, not translated values refer to specific types of content that are typically presented in their original language rather than being localized for different languages. Field values, variables, logs, and debug messages are all examples of this.

These values often contain technical or contextual information that is meant for system administrators or developers, rather than end-users. Keeping them in the original language helps maintain clarity and consistency when troubleshooting or developing within the platform. For instance, if an administrator is looking at a log file or a debug message, having it in a translated form could lead to misinterpretation or confusion.

On the other hand, user-facing elements like buttons, labels, menu options, and system messages are meant to be experienced and interacted with by end-users, thus they are typically translated to ensure accessibility and usability across different languages. Likewise, translation keys and resource bundles are part of the localization process, which means they are specifically designed to be translated.