There are generally two scenarios to use NLS: in XUI file and in transaction file.
In XUI file
Widget properties
NLS can help user to update the language for text or hint properties of widgets, including
▪ Label, Button, and Link widgets which possess the text and hint properties.
▪ Text and Table column when the data name is set as string type, and TextArea.
Note Normally, the latter group is not recommended to bundle NLS. In some specific scenario which need to bundle NLS with these widgets, it is only recommended to use NLS for message display. Otherwise, submission, validation or other data management would lead to logical contradiction.
Choices
▪ Double-click the widget that has the NLS.
▪ Right click the project in the UDTT Project Explorer, and then click UDTT Tools > NLS editor.
▪ Click the widget and turn to the Properties view. Click Browse in the Value column.
ECA rules
When defining Condition in an ECA rule, you could use NLS to define the left and right value in Expression as well as the multilanguage string value in Global Function.
If select Constant, select NLS as Type of Constant and then click Browse to define the value:
In transaction file
Condition State
In transaction files, users can use NLS when defining condition state. Compared with defining Condition in an ECA rule, the procedure is generally alike. You could also define the left and right value in Expression as well as the multilanguage string value in Global Function.
Input/output mapping
Users can also use NLS when defining input/output mapping for a transition. Compared with defining Condition in an ECA rule, the procedure is generally alike.
