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:

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

<property name="rtf-checkbox-glyph">Wingdings2;0082;0163</property>

By going to "Administration" - > Parameters -> Characters Used for Checkbox,

In Siebel IP17 once you will open Weblayout editor to arrange controls on the template then you won't be able to see anything and if you look into the browser console, you will see below error:

Uncaught TypeError: this.GetUIWrapper(...).BuildPreview is not a function

 The issue is caused by the following setup: Customization added at JS level.
WebTools is the correspondent of Tools, and should, therefore, contain no customizations. This includes JS files. 

Manifest Safe Load : TRUE
Enable Safe Boot : TRUE

The printing of the current record in Siebel IP17 has been taken off. The Print menu option is there but when it is not working. Here is to reproduce the issue:
1. On an applet go to Menu
2. Click on the Print option
3. the print dialog appears
4. Click on Print button nothing happened
5. Clicking on Print Preview button nothing happened

In Siebel IP17 there is a major problem with the State Models that some of the business components will not appear in the State Model MVG Applet when you will search the business component.

Until all previous versions all the available business components are available in the MVG applet to be added in a State Model but in IP17 the underlying model got changed.

Now, in IP17+ the business component behind the applet used to show all the BCs to be selected for a State Model is replaced with a virtual business component and only those business components having a user property State Model = Y will be displayed but this is not how it is currently working. Despite the user property is mentioned, most of the business components do not appear in the applet to be selected for State Model. As per Oracle this bug will be fixed in Siebel 18.7.

Apparently Siebel IP17 has some problem for testing development related changes on local environment before pushing it to the server. Development related changes cannot be tested locally on the workspace also known as sandbox in IP17 but changes cannot be seen made in the objects until workspace get submitted and delivered the respository.

As per bookshelf, below are the steps to test changes/modifications locally:

1. Create a workspace 
2. Edit objects for example update the Applet control caption 
3. Checkpoint/versioned the workspace ( i suppose this is optional step) 
4. Modify the corresponding CFG file say "publicsector.cfg" cfg file as below: 

[Workspace]
Name = Main
Version = 41 -- The version of the workspace for which you wanted to test the changes

[InfraObjMgr]
RequestServerName = <SERVER_NAME>
RepositoryType = RUNTIME 

In one of our Siebel IP17 upgrade project we had to set an option for the end users cancel currently long running queries. In Siebel 8.1x if user executes a query in the application UI then if the result is taking longer time then a popup window appeared asking and informing user to wait as query is taking longer execute time or Cancel the current operation. In the meanwhile user do not have the option/permission to click anywhere else on the screen while the current operation is in progress.



 But in OpenUI (until IP17.5), in case of long running query a circle appears showing as system is busy but after certain amount of time it stop spinning and disappear and from here the user can click on other screens but as the current operation was not completed the next screen will not be loaded and system appears as stuck.

In case we set set CancelQueryTimeOut >=1 say 10 in the corresponding Object Manager and execute a long running query then a popup window starts appearing after 10 seconds but on clicking Cancel button it did not work and stays as below: