 |
Fact expressions given by domain users are usually in a domain language locale. CaseTalk should determine the value types, and store them in a locale-neutral manner. And when regenerating expressions, the user may choose according to which format/locale. Currently CaseTalk only treats it as text in text out. This may become a problem for generating sql dml scripts. Therefor registering some sort of locale code for expressions is a requirement to properly determine the datatypes, and parse and store values. |
|
|
Version 9.1 will contain the option to specify the Locale at IG level, this allows the population to be converted into system-neutral values when needed. And allow the population be treated as text-in and -out while in CaseTalk. |
|
|
Environment contains default Locale setting, which can be overridden in the IG property dialog. |
|
|
Closing automatically, stayed too long in resolved state. Feel free to re-open with additional information if you think the issue is not resolved. |
- Anonymous
