SpagoBI - Uso de caracteres especiais como parâmetros (LOV)

Caso seja necessário o uso de caracteres especiais nos parâmetros dos LOV, como por exemplo um LOV para meses: Janeiro, Fevereiro, MARÇO, etc... e quando o valor MARÇO for selecionado, seu SpagoBI deixa de funcionar, siga as dicas abaixo:



the url string pattern is blocked by the spagobi's validator. You can find the pattern used by spagobi to validate the parameter's value in file SpagoBI/WEBINF/conf/tools/datasources/validation.xml In particular this is the block of configuration that specify the pattern... <field label="URL_CONNECTION" name="URL_CONNECTION"> <validator arg0="^([a-zA-Z0-9.:@\s\-\_\(\)\\\/])*$" validatorname="REGEXP"> <validator arg0="50" validatorname="MAXLENGTH"> </validator></validator></field> as you can see char ';' and '=' are not included in the pattern. For this reason your url parameter value is considered not valid. You can modify this block of configuration in order to include also ';' &amp; '=' chars in the pattern and then restart the server. With this work around you should be able to save your db url.

Contributed by Andrea Gioia (SpagoBI Team)

SpagoBI - Localization

Rough SpagoBI Translation Guide. Suppose adding pt_BR language:

========================
1) Configure the new language
• Log into SpagoBI as Administrator
• Go to Tools - Manage Configurations
• In the Select Category combo box, select "LANGUAGE_SUPPORTED"
• Add the language at the end of the existing string as follows: ,[pt,BR]
• Add the icon of the related flag into the file: SpagoBI\themes\sbi_default\css\analiticalmodel\execution\main.css , by
adding the following lines:
.icon-pl {
 background- url('../../../img/pt_BR.gif') !important;
}
• The image containing the new flag shall be added into the folder SpagoBI\themes\sbi_default\img .


2) Translate the titles, messages and labels
At this point, translate all the titles, messages and labels included in SpagoBI packages:
• SpagoBI\WEB-INF\classes\MessageFiles\
• SpagoBI\js\src\ext\sbi\messages e SpagoBI\js\src\ext\sbi\formats
• SpagoBIQbeEngine\js\spagobi\messages e SpagoBIQbeEngine\js\spagobi\formats
• SpagoBIGeoReportEngine\js\src\ext\sbi\messages e SpagoBIGeoReportEngine\js\src\ext\sbi\formats
• SpagoBIConsoleEngine\js\spagobi\messages e SpagoBIConsoleEngine\js\spagobi\formats
All .properties files must be copied and renamed as xxxxxx_pt_BR.properties, before making any changes inside.
Repeat the steps above to all engines you want to use


3) Translate the messages in the files above to your locale language and if the language uses non-latin characters run native2ascii on each file: (e.g. native2ascii messages_pt_BR.properties messages_pt_BR.properties)

4) Copy webapps/SpagoBI/js/src/ext/sbi/locale/en.js & webapps/SpagoBI/js/src/ext/sbi/locale/commons/en.js to your language code e.g. br.js and translate the messages in the files, run native2ascii if required.

5) Restart SpagoBI and you should see your language. Also clear browser cache to see the new modifications.

6) Contribute the message files etc back to SpagoBI


contribution from Hesham Ahmed (SpagoBI jira user)