Translated Multi-Language Content Across the Platform

With the Multi-Language feature, you can create a single form and provide it to your field users in multiple languages. Different parts of the TrueContext platform use a variety of settings and translation files to display translated content. This topic describes how TrueContext displays Multi-Language translations on each part of the platform.

Available as an add-on to the Advanced and Enterprise tiers:

Essentials

Advanced +Add-on

Enterprise +Add-on

Contents

Translated Multi-Language Content Across the Platform

Translated content that you provide

Multi-Language Forms

A Multi-Language Form A Multi-Language Form is a form that’s set up with different translations so that field users can choose their preferred language. Translated content includes page and section names, question text, help text, and other form content. is a form that’s set up with different translations. Field users, dispatches, and App‑to‑App calls can select the language used to display the form content and output Documents. The languages available to the user depend on the form’s Languages settings and the translation files that the Form Designer uploads. The topic Set Up a Multi-Language Form describes these settings in detail.

Multi-Language Data Sources

A Data Source Data sources, also known as "Lookups", are external sources of data that you upload or connect to TrueContext. You can reference this data in a form to populate answers or answer options. Data sources save typing, reduce errors, and make it easy to provide mobile users with only the relevant, most current data. can provide a list of translated options for a Dropdown, Multiselect, or Radio Button lookup question.

We store Data Sources Data sources, also known as "Lookups", are external sources of data that you upload or connect to TrueContext. You can reference this data in a form to populate answers or answer options. Data sources save typing, reduce errors, and make it easy to provide mobile users with only the relevant, most current data. as tables (rows and columns) in the TrueContext system. To set up translated values in your Data Source, you must have a column that contains a language code for each row. The topic Data Source Translations describes how to set up your Data Source.

Multi-Language output Documents

A Multi-Language Document is a PDF, Microsoft Word, or HTML output document that’s set up with different translations. match the language selected when the form first opensThe output document renders in a Multi-Language Form’s selected language. For example, if a user chooses to display the form in Japanese, the system renders the Multi-Language Document in Japanese.

How translation files provide content for Forms and Documents

The following illustration shows how Form and Document translation files and Data Sources provide content in forms and output Documents.

Info:Form-level content and Document-level content each require different translation files. The topic How Multi-Language Translation Files Work provides detailed information about the translation files.

Where translated content is displayed

Translations for Forms, Documents, and Emails

The following table describes where translations come from for Forms, Documents, and Emails.

The…	Displays translated content for…	Based on…
Multi-Language Form	Page and section headings Question text Manually-defined display values in lists for options-based questions Options-based questions are questions that display a list of options for field users to choose from. These include Button Group, Card List, Dropdown, Multiselect, and Radio Button questions. Question help Custom validation messages Static text in a DREL Data Reference Expression Language (DREL) is used to get form data and metadata and add it to a string, such as dates, usernames, or answers to questions in forms. expression. For example, if the DREL expression is: `My Customer %r` You can translate the text “My Customer” but not the value returned by `%r`.	Translation files that you upload and activate for each form language.
Multi-Language Form	Lookup questions that use a translated Data Source, both the display and data (server) values	Translations that you include in the Data Source. Info:The topic Data Source Translations describes how to set up your Data Source.
Multi-Language PDF, Microsoft Word, or HTML Document	The Document itself: Output File Properties Header Title Additional information Footer Table column headers you set in your Table Layout Metadata labels (such as Reference Number) System-generated content (such as page numbering) Content from the submitted form: All content included in the form translation file (such as page, section, and question text) Submitted values for lookup questions that use a translated Data Source Note:Data that field users enter directly into a form, such as data typed into a text field, stays as entered.	The language selected for the submitted form. Active additional languages. Translation files for document details, such as header and footer.
JSON and XML Documents	JSON and XML documents have key-value pairs that contain the data from a submitted form. If an XML or JSON document is linked to a Multi-Language Form, the document displays form content in the form’s Selected Language. The document shows translated form content based on the form’s translation file. The key names and question Unique IDs don’t change. For your integrations, use the question Unique ID A Unique ID refers to the specific identifier of a question, form page, form section, or Data Destination. Unique IDs are used as reference points when pulling data for conditional logic, Analytics projects, Data Destinations, and Documents. and not the question text. The system also translates the standard XML and JSON files that you can download from the Form Submission Details page. Tip:You don’t need to set up translation files for XML or JSON files that you attach or download.	The language selected for the submitted form.
Email Data Destinations A Data Destination specifies where to send data from a submitted form. You can use Data Destinations to automate data sharing and storage, routing data to a specific service (such as email or cloud storage) in several different formats. that use a standard HTML body	If you linked an Email Data Destination A Data Destination specifies where to send data from a submitted form. You can use Data Destinations to automate data sharing and storage, routing data to a specific service (such as email or cloud storage) in several different formats. to a Multi-Language Form and chose a standard HTML body, the email shows translated form content.	The language selected for the submitted form.

Translations for Mobile App, Web Portal, and Customer Feedback forms

This table describes where Multi-Language translations come from for the Mobile App, Web Portal, and Customer Feedback forms.

Info: The topic Language Settings and Translations explains in detail the standard TrueContext language support options and how to set them up.

The…	Displays…	Based on…
Mobile App	Translated content for: Menus Settings Confirmation messages Error messages Notifications	The user’s device locale settings.
	Form names in Forms, Drafts, Inbox, Search, or Sent in the source language (not translated)	The names as defined by the Form Designer.
	Text embedded in Resource Images and Resource Documents as is (not translated)	Text embedded in the file.
Web Portal	Form details, such as question text, exactly as defined in the Form Builder (not translated). Submitted values exactly as submitted.	The source language used to build the form. Actual values submitted.
Customer Feedback forms	The Multi-Language feature is not available for Customer Feedback forms.	Not applicable