As of Lumira 2.1 the Designer uses the following URL parameter when starting an app via Execute Locally (not for Execute on BIP):
This will have the effect that locale settings will not be correctly set, only EN-US will be taken as it is the default.
Simple workaround: after choosing execute locally remove the above parameter from the URL and refresh in the browser whenever you need to load the changed application again.
Important: this parameter is not used on the platform in BI launchpad or OpenDoc, therefore this symptom will not occur on the platform.
The date picker e.g. in the variable dialog did not show the correct format. This is fixed with Lumira 2.3 SP 2. (Jul 3rd: Updated to SP 2)
3. Translation Management Tool bug
After Saving As (in the Designer) of an application inside a LUMX the translation management tool does not show the duplicated texts.
This is fixed at least with translation management tool 4.2 SP 5 Patch 2.
4. Designer Save As
5. Chrome Setting without country => default texts in Lumira
In case your chrome language setting does not show a country this result in an HTTP accept-language header where the country is missing e.g. de instead de-DE. The Lumira addon will show the default application texts then.
Lumira Applications can be have three types of multilingual text source categories:
Bellow settings can be defined in the BI Launch Pad in order to fulfill user requirements (unchecked box means setting does not interfere in the text source category).
Preferences -> Preferred Viewing Locale (PVL)
OLAP Connections -> Save Language
Each of the three Texts Source Categories can have error/warning messages during Application Runtime. The messages locale respect the text categories locale.
&LANGUAGE=xx&COUNTRY=xx is the recommended way for the language selection.
"Allow Language to be set as an OpenDocument" should be activated in the CMC Lumira Server Settings.
In order to have the BI Launch Pad settings applied to Lumira applications, select BI Platform User Settings‘ in the Lumira Client Preferences.
The format for numbers, dates and times varies according to the defined Locale.
Interval Filters : Setting a interval variable via script is only possible with setVariableValueExt - but this is language dependent. If the application is intended to be used by a multi-lingual group of users, this method can bring system limitations.
- Right menu lumx file has no dutch translation in right mouse menu
- in IE the language setting of NW PORTAL is not respected for french language. - fixed in 2.2 release
- Lumira shows comma for decimal operator for turkish language.
If you test in the Designer do not choose the red setting. Otherwise the Designer will overwrite the browser language settings with these URL parameters: &LANGUAGE=en&COUNTRY=US
Browser Locale determine language specifics
A typical use case for English language but European date/time formats using the UK locale instead of English-US. The browser locale (PVL) determines all translated texts, the backend texts from the data source (e.g. "Flight Date") and product texts from the Lumira UI element (e.g. "Show Filterbar").
BIP user locale determine language specifics
Another typical scenario where the user locale configured on BIP determines all translated texts and formats.
Browser Locale as well as OLAP connection determine language specifics
An untypical mixed language scenario with a language specified in the OLAP connection of the BIP (German in this case) and the EN-UK browser locale. As you can see backend texts (yellow) are determined by the OLAP conection setting. All backend texts (green) are determined by the browser locale.