Clib.System function fails in Solaris 11

Clib.System functions are commonly used to invoke system process or batch/shell files etc. This function is having some compatibility issues with Solaris 11 or above.

When you migrate Clib.system is returning some error codes like 32512 or 9.
This is because of Siebel is referring some 64 bit libraries instead of 32 bit.

To over come this issue kindly follow below steps:

1. Make a backup copy of $SIEBEL_ROOT/bin/siebmtshw.

2. Edit siebmtshw file

3. Change LD_PRELOAD to LD_PRELOAD_32

4. export LD_PRELOAD_32

5. Save the file

6. Take clean bounce of siebel services and a machine bounce as well.

By this way the library would be preloaded for 32-bit binaries

for more information please refer:
Doc ID 2193193.1
Doc ID 2149311.1

View PR not working in IP 2014 ?

IP 2014 has a problem with its view PR. View PR cannot work alone :)

Oracle support web has already given a workaround for this issue.

Here is the solution part. 

For this matter a defect was created: BUG 23016729 - SIEBEL OPEN UI VIEW PR DOES NOT WORK WITHOUT A SPECIFIC PM

Workaround:

The PR the PM it is called, according to the documentation and if the PM is called, a PM should exist for this PR.
Life Cycle of a Physical Renderer: https://docs.oracle.com/cd/E14004_01/books/config_open_ui/architecture13.html#wp1246021

Added a PM along with the PR and the view loaded properly, with no errors in the browser console log.

Steps
----------------------
1. Copied the Java Script file EIMViewPR.js in SCRIPTS/siebel/custom
2. Login into Siebel Application
3. Added the file through Manifest Administration Screen
4. Log out of Siebel Application
5. Login again in Siebel Application
6. Go to Site Maps > Query for EIM
7. Go to EIM Tables screen

8. Created a Java Script file EIMViewPM.js in SCRIPTS/siebel/custom
9. Login again into Siebel Application and added the file in the Manifest Screen
10. Go to Site Maps > Query for EIM > Go to EIM Tables screen

Expected results
----------------------
The application should work properly.

Actual results
----------------------
The application is loaded properly, no errors in the browser console log

For More information Check doc ID: 2122937.1

Log In Undefined issue in Siebel Open UI

In some of our environment, we noticed that Login button is showing as Login Undefined.

Solution to this problem.
From support web

1. On "CC Login Page (Login Only)', locate the "LoginButton".
2. Remove the Caption String Override.
3. Open UI script need to have nothing but HTML code in the caption. Otherwise, it will returns "Undefined" condition.

This did not worked for me due to some reason. The alternate way I used is by editing LoginSWT.

<script language="javascript" src="23030/scripts/3rdParty/jquery.js?_scb="></script>

<script>

$(document).ready(function(){

            $(".loginButton a").text("Login");

     });

</script>​

started working perfectly ;-)

Siebel UI Innovations

Here is some amazing OpenUI experiments. 

is it windows 8?? no its siebel 

1. 

2. 

3.

4. 

5. 

6.

7. 

Siebel Open UI - How to fix Form applet display issue in Chrome

Open UI form applets have some issue, when it rendering in Google Chrome.The controls are overlapped as shown below.

Solutions
Fix without JS
-------------
Open a CSS file your application referring paste the below css

td {
    border: 1px solid transparent;
}

clear the cache and try :-)

-------------------------------------------------------------------------------------
Fix with JS (as per oracle doc)
As per oracle technical document we can fix this issue with a piece of code

if (typeof(SiebelAppFacade.ChromeSpaceFix) == "undefined") { Namespace('SiebelAppFacade.ChromeSpaceFix'); (function() { SiebelApp.EventManager.addListner("postload", ChromeTdSpaceFix, this); function ChromeTdSpaceFix() { try { $("#_svf0 table.GridBack").find("tr").children("td").each(function(index) { var regex = /(height)(\s*):(\s*)([^;]*)/, el = $(this), st = el.attr("style"), match = regex.exec(st); if (match && Number(match[4]) && el.is(":empty") && el.siblings().length != el.siblings(":empty").length) { st = st.replace("height", "x­height"); el.attr("style", st + "height:" + Number(match[4]) + "px;"); } }); } catch (error) { // Nothing to do. } } }()); }

Now you can add this file as Platform common (8.1.1.9 & 8.1.1.10) or Application -> common as (8.1.1.11)
you can see the above fix from here

Siebel OpenUI : Calender Issues

Siebel OpenUI : Calender Issues

Siebel OpenUI currently not supporting SI Classes and Applets referring to that type. That is why Salutation applets are shown with a "question mark". Open UI will not render these classes of applet.
Calender functionality is one of the main features of Siebel. Many Customers are using this feature to schedule their activities.In Siebel we have two kinds of Calenders. HI calender and SI type. Normally in home pages you can see SI calenders and that will not work in OpenUI. Even though OpenUI render this applets, that doesn't work properly.  Siebel Non OpenUI version needs SI applets in its home page. So we need to toggle these two applets in between OpenUI and Non OpenUI.

In order to do that, we can use Personalization.

In the home page view you can Include both Calenders. Now got to Administration- Personalization -> Applets.
Create two new records for two applets (HI & SI)

To display in HI: GetProfileAttr("IsOpenUI") < 1 OR GetProfileAttr("IsOpenUI") IS NULL
To display in OUI: GetProfileAttr("IsOpenUI") > 0


GetProfileAttr("IsOpenUI") will be 1 in OpenUI applications.

How to set your custom theme as Default theme

In Siebel Open UI, user can change theme from their user preferences.  If they did not choose any thing a default theme will get loaded. By default that is "Gray Tab".

Suppose you created a new theme called "Golden Tab" and you have to make it by default, Otherwise we have to force our clients to change their theme from their user preference and that is not recommended.
You can change this thing by using some tool level change.

In order to do that please follow the steps.


1. Using Siebel Tools, navigate to "User Preferences" BC.
2. Update the calculated value for field "Behavior/DefaultTheme" to "<custom theme>"
3. Update the Predefault value for field "Behavior/DefaultTheme" to "<custom theme>"
4. Compile the changes and re-test the behavior

You will need to remove the user pref file (spf) file to make the changes take effect.