Administrative Utilities → About Localization → String Localization Categories → Design Object Strings
Once you select the Allow translation for MLS Runtime Objects and Design Objects check box on the Settings tab, you can translate strings for design objects that are created in SBM Composer into another language. Design object strings in a process app are available for translation in Application Administrator after you deploy the process app.
Once translation for design objects is allowed and a process app is deployed, each primary and auxiliary table in the process app appears as a category on the Localization page. Design object strings are organized by section within each category.
Design object strings that you can translate include:
You can select one or more language locales in Application Administrator under Predefined Locales on the Localization | Settings page, deploy a process app, and then translate the process app's design object strings into each defined locale. When translation is complete, users who select the locale for the translated version will see the translated strings. For details, refer to Settings Tab.
Translated design object strings appear throughout the end user interfaces, including the following areas:
When viewing items, translated strings appear for all form types (state, transition, printable) in the following:
Translated strings appear in the workflow diagram that users can view from an item.
In report results, translated field names appear in column headers and in results that include selection values. During report creation, translated field names appear for columns to display, filtering, and sorting. Sorting in report results does not use translated string names.
Translated strings appear in notifications when design object strings (such as Single Selection, Multi-Selection, and State field names and selections) are included in the e-mail template.
Copyright © 2007–2016 Serena Software, Inc. All rights reserved.