Language Translation Service Overview
- 20 Apr 2021
- 1 Minute to read
- Print
- DarkLight
This documentation version is deprecated, please click here for the latest version.
Language Translation Service Overview
- Updated on 20 Apr 2021
- 1 Minute to read
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Overview
As part of the host of Localization features, Decisions offers the ability to translate Text based on defined Language Settings. These Settings are established by Adding a Language in the System > System Data > Languages Folder. After establishing the Language, users will then add their desired String to the Master Translation list. Then, back in the Language Folder for the newly established Language, a Translation is added for that String.
For additional information on how to establish a new Language for Translation in Decisions, see: Setting Up a New Language.
Whereas many steps and Services in Decisions are designed to alter dynamically populated data or change the experience within the Design Studio, through use of the Translation Services, Designers are able to fulfill the Service's intended use of affecting the End User UI experience.
Note that Decisions' Translation Services are only presently able to translate static elements.
Dynamically populated objects such as Activity Panel data and States involved in Process Logic are not translatable. Therefore, it is encouraged that if this data needs to be translated for a user, that it is done so by mapping the Translated Text into the desired Inputs.
Dynamically populated objects such as Activity Panel data and States involved in Process Logic are not translatable. Therefore, it is encouraged that if this data needs to be translated for a user, that it is done so by mapping the Translated Text into the desired Inputs.
This process is executed by establishing the Translation at Design Time on a static element such as a Form Label or a Report Title. This allows Decisions the ability to swap the String for the translated at runtime.
The section below details some of the objects that can be translated via the Translation Services in Decisions as well as some sources for additional information.
Note that Translation in Decisions is a manual process and a translator should be involved in specifying a translated String.
Additional Resources
The following links below are links to additional documentation on Decisions Translation Services.
Translatable Objects
After establishing a String for Translation in the Master Translation List, Adding a New Language, and establishing a Language for a User, the String may be applied to the following objects at Design Time.
- Static Form Labels
- Report Column Titles
- Help Messages
- Constant Strings in Flows
Non-translatable Objects
Note: Chart and Report Titles are translatable objects as of versions 6.17.0.704489+, and version 7.2.0.67491+.
- Dynamically populated Flow Data
- Activity Panel Content
- Chart Titles
- Report Titles
Was this article helpful?
