CRM & Cloud

Issues I faced in CRM & Cloud solutions

BIP 12C checkbox is appearing as rhombus

As a part of our Siebel Upgrade project, we had to upgrade Siebel Actuate reports as well. As Siebel Actuate is not compatible with Siebel IP17 so we decided to move on BIP 12C.

There were certain reports on which client was using check boxes and based on certain condition and value these check boxes are being filled with 'X' sign. In the Actuate reports all these were working perfectly until we moved our reports from Actuate to BIP 12C.

We notice that all the check boxes started appearing as rhombus sign or diamond sign. We looked into the issue fixed by doing using Wingdings2 font. The steps to fix the issues are:

  • Copy the Wingdings2.ttf file of your custom font (e.g. wingdings2.ttf) to the JRE home\fonts (e.g. C:\OraHome_1\jdk\jre\lib\fonts) folder on the BI Publisher Server
Log into the BI Publisher Server using the 'Administrator' login.
    • Click on the 'Administration' tab. 
    • Click on the 'Font Mappings' link under the 'Runtime Configurations' section on the right hand side. 
    • Click on 'Add Font Mapping' button under the 'RTF Templates' section. 
    • Set the following fields: 
Base Font - Wingdings
Style - Normal
Weight - Normal
Target Font Type - Truetype
Target Font - wingding2.ttf 
  • Go the the following location of your BIP 12C installation:
Lets suppose it is intalled in C dir,
C:\Oracle_Home\user_projects\domains\bip\bidata\components\bipublisher\repository\Admin\Configuration 

 Open the xdo.cfg file in textpad and add the entry:

<property name="rtf-checkbox-glyph">Wingdings2;0082;0163</property>
  • Copy the font file wingdings2.ttf  to: $BIP_INSTAL_HOME\user_projects\domains\bifoundation_domain
Please note that, you can also set following property:
<property name="rtf-checkbox-glyph">Wingdings2;0082;0163</property>
By going to "Administration" - > Parameters -> Characters Used for Checkbox,




When you are done with above steps, please bounce the BIP sever and test your reports.


No comments:

Post a Comment