LogicNets Multi-Language Support Module (LN-MLS)
License: per user of multi-language-enabled applications
Notes:
- Supports use of both named and concurrent user licenses
- ASF and SAF only
- Requires customer to take full responsibility for translatingand validating all primary language content elements into targeted additional languages
LN-MLS Description
The LogicNets Multi-Language Support (“MLS”) module allows LogicNets based applications to be designed and executed so that they selectively present content and functionality in any one of a range of possible languages in the user interface. It makes specialized functionality available both in the Designer environment and the runtime behavior of any of the Frameworks with which it is integrated. Note that the MLS is NOT a translation system. For each language it enables in addition to the primary language, the LogicNets Customer will need to provide accurate content translations and other information for the system to generate the appropriate interface content. This information is managed in a language table which is imported into the system and allows for alternative text to display in: 1) modeled content and content controls and 2) Framework text displays. This functionality also complements the Knowledge Centers’ ability to organize content in multiple language folders.
The effect of using the Multi Language Support Module for end users of a LogicNets application is to make it possible for an application to either 1) be dynamically presented in one of any number of supported languages at the initial point of access based on the language “preference” set in the user’s profile or (when available) 2) allow a user to dynamically select a language from a languag e selector dropdown list from the Starter App as a session is initiated.
Services and Deployment Considerations
The Multi-Language Support Module requires Deployment Services (LN-DS) for integration into any user environment. Services can include:
- Configuration of/integration with Frameworks
- Configuration of language control tables and association of users with language preference settings
- Structuring of Knowledge Center content and configuration of tagging to match framework language selection/preference
- Configuration of exportable/importable data model for data interchange with translation services
- Designer training on functionality
These services usually require development and acceptance by customer of a formal SoW.