The following points should be considered when specifying field or file level rule and triggers:
Error Message Text
When specifying multilingual error message text, use multilingual variables to specify the text. This way the textual content of the message will be determined at execution time and thus issued in the correct language.
Error Message Numbers and Message Files
When specifying error messages by message number and message file, use only a message file that has been defined at the partition level as a user defined message file for the default development language. This will ensure the correct multilingual message file will actually be used at execution time, ensuring that the message appears in the correct language.
Refer to The Handling of System Messages Issued by LANSA for details of how this feature works.
List of Values Check
Where a field can have a value that is language dependent, use multilingual variables in the list of values rather than literals.
Range of Values Check
Where a field can have a value that is language dependent, use multilingual variables in the ranges of values rather than literals.
Code File Lookup
Multilingual variables can be used as key fields in a file look-up check.
Simple Condition Check
Multilingual variables can be used in an expression as replacements for alphanumeric literals.
Call a Program Check
Multilingual variables can be used as parameters to dictionary checking programs.
Date Checking
There does not appear to be any requirements for multilingual support in date and date range checking validation rules.
