Localized Text

As shown in the XML fragment above, the activity name and description are not just text fields, but are defined in terms of a localized-text element. This is general purpose element used throughout the process definition metadata where ever text is required to be localizable.

A valid localized-text element must have at least one locale child element. This ensures that there is always some text for display for a particular field. In the process definition tool any localizable text that is entered in most user interface screens other than the localization screen is saved under the default sever locale as specified by the application property: curam.environment.default.locale.

<localized-text>
    <locale language="en">ApproveCase</locale>
    <locale language="en" country="US">ApproveCase</locale>
    <locale language="fr">ApprouverAffaire</locale>
    <locale language="fr" country="CA">ApprouverAffaire</locale>
  </localized-text>

locale: This contains the text for the locale specified by the language and country attributes. Note: A locale is uniquely identified by both the language and the country meaning that en, en_US and en_GB all represent different locales.
language: This is mandatory and is the two letter ISO language code.
country: This is optional and is the two letter ISO country code.