For an example that follows, the library name is myLibrary, and the library includes declarations of strings named entryForInputRequired and entryForOthers. Those variable names are case sensitive.
name STRING {inputRequired = yes, lowercase = yes, inputRequiredMsgKey = "entryForInputRequired", typeChkMsgKey = "entryForOthers", validationPropertiesLibrary=myLibrary };
The validationPropertiesLibrary field is used only when you are overriding validation and formatting messages.
entryForInputRequired=You must specify a value entryForOthers=Your input is incorrect someText=Not mentioned
The properties file is a text file. The entry names are case sensitive and are useful only if they match a string declaration in the Rich UI properties library.
The override relies on one of the following three "MsgKey" fields: inputRequiredMsgKey, minimumInputMsgKey, and validValuesMsgKey.
That single override also relies on the typeChkMsgKey field.
myButton.text = myLibrary.someText;
Alternatively, you can reference myLibrary in a use statement, in which case you do not need to reference the library name in the assignment.
You can also use the library function getMessage to provide inserts to a string inside your code.
A displayable value comes from a properties file whose name has a root (for example, myLibrary) and includes a locale, which is a code that identifies a human language, For example, en is the locale that represents English, and the file name myLibrary-en refers to a properties file that provides English text.
Each file name has a root name and the extension .properties. The locale is indicated at the end of the root name, before the extension. Locales consist of one to three identifiers, the first preceded with a hyphen and the others (if any) preceded with an underscore. Each additional identifier after the first enables you to indicate a more specific language; in particular, you can specify the dialect, variety, or geographic location of a language.
<a href="www.example.com/MyApplication-de.html">German version</a>
You store properties files in the WebContent/properties folder of your project. The root of the property file name (for example, myLibrary) must be the name specified in the propertiesFile annotation in the Rich UI properties library.
Deployment fails if no properties file is available for a given Rich UI properties library. To avoid the failure, you might want to include a default properties file for each library.