IP2017 – Key Benefits

Happy new year 2018 to all my blog readers!!!

Starting with a single slider highlighting the benefits of IP2017.


Get the best out of IP2017, which we all feel is one of the best Innovation releases from Siebel/Oracle!!!


Siebel – Outbound email Validation

Siebel by default does validation of the email addresses that are used in the outbound communication manager. Basic validations like having a “@” or a “.com” or “co.*” are present. Some times there might be an exception scenario where these validations needs to be overwritten to cater to the customer needs where they might encounter validation errors like :

Invalidate eMail address:****@abc.support.(SBL-EML-00050) 

To overcome these validations, you need to set system preferences. Following steps needs to be followed :

  1. Navigate to Administration – Application  –> System Preferences
  2. Query out “Enable EmailAddress Validation”
  3. Set its value to “FALSE”
  4. Bounce Siebel Service

When changing System Preferences (normally by the administrator), Siebel Application Object Manager component needs to be restarted to make it reload the new System Preferences settings.

Test and Deploy!!

Siebel OpenUI – List Applet Filter

Since the List applet in OpenUI uses the JQgrid frame work, it gives some very good capabilities of JQGrid. One of them is the “Filter Toolbar”, which gives us additional filtering options within the List Applet.


Additionally, you can now programmatically control the contents in list applet (Like filtering, Searching etc).

Following code in PR can get you the “Filter Toolbar” in your list applet:


To add a filter condition, you can try the below script:

$(“#gs_Location”).val(‘H’); // Setting the filter condition
this.GetGrid()[0].triggerToolbar(); // Trigger the Filter condition

Where “gs_Location” needs to be replaced with the correct List Column name. Here I have added a filter condition of “H”. Once you set a value, Trigger the toolbar to execute your filter condition.

Also, you can hide the toolbar, if you do not want your users to use it, or to have the filtering in the background.


Happy Filtering!!

Siebel Log analyzer

Recently I have been working on some of the Performance related issues in Siebel. The usual way is to get the OM logs with SQL logging level set to 4/5. Now the big task is to analyze these log files to find Long running queries which cause the performance degradation.

So, I have come up with my own “Siebel Log Analyzer” which will check for long queries pertaining to :

a) SQL Prepare Time

b) SQL Execute Time

c) SQL Fetch Time

Log analyzer1

You need to enter the Log File Path and give a value for Threshold (Threshold time above which all the values to be captured . Eg : 0.4 sec, 0.7 sec etc)

On clicking the “Analyze File”, the output is generated in a new excel sheet like this :

Log analyzer2

Now it’s some what easier to find where the issues are. This is especially helpful when the log file size is very huge.

Let me know if any of you need to try this. You can email me to get a copy!!

Simplified Debugging!!!

IP2015 -Custom JS Do not showup

Dear OpenUI Developers,

Those working with earlier version of OpenUI (, .10, .11) will see that the custom JS files/folder will not show up in the browser console anymore. (IP2015 onwards).

Open UI now loads scripts “as needed” as opposed to pre-load via direct includes. This prevents the script from showing up in a list with a named reference.


To Debug the  PMs, PRs files  use debugger call in the script and this will open the script in browser console and you can set breakpoints as and when needed. When keyword “debugger;”  is added to script which will make the browser stop the script that line for debugging.

Happy debugging!! 🙂



Siebel OpenUI – UPT – Usage Pattern Tracking

Sharing a very interesting and new feature added in 15.5 version. This will greatly help in designing the UI Flows. Thanks John!!

Usage Pattern Tracking

By John Bedford-Oracle

Siebel Usage Pattern Tracking, a feature introduced in 15.5 is a framework module that packs immense potential. This feature allows Siebel administrators with the ability to configure live systems to capture information on how end users are using the application without adding performance or response time overheads.

The information gathered via this feature is invaluable as it can be analyzed, sliced and diced in many different ways to extract information that can be used to improve the end user experience, lower total cost of ownership and/or personalize the application down to the smaller unit.

The feature is capable of capturing user patterns that can be analyzed to determine for e.g. the 10 most visited views in the system, number of login/logoff sessions in a period of time, how many fields are really used in an applet, top 5 views where users spend the most time, the entire set of views all users have accessed over time, what was the user doing when they hit an error and what steps were performed getting to that point, etc. The possibilities are endless.

Chart showing user login across applications


Chart showing which applications are being accessed


Chart showing the most access views in the application


Chart showing the most access views in the application


Chart showing the most active events in an applet


There was a lot of excitement when Usage Pattern Tracking (UPT) was announced and we think this is a great new feature for our customers to start to utilize.

Some Additional information :

When UPT module receives an event to track, the configured RTE triggers an action. The action is based on a Business Service “Usage Pattern Service” which is written to batch the events into groups of 100 events and write them into a file. The value of 100 is the default value of System Preference UPT Max Record Count and can be changed to a maximum value of 1000.
To process the data from the files, a job should be created. Through this job, UPT Process Workflow is invoked, which triggers Business Service “Usage Pattern BG Service”. This reads the information from the .csv files and moves it to the correspondent Siebel tabels. As the files are processed by the job, they are purged in order to manage efficiently the diskspace. The information in the Siebel tables is then used to populate Usage Pattern Tracking View. 

The only recommendation that exists regarding the UPT tables is the one in Bookshelf where the following is stated:

The number of records in the S_USER_EVENT table and the S_USER_EVT_DTL table depends on the events that you configure for usage pattern tracking. It is recommended that you periodically move data from these tables. Your movement frequency depends on available memory and the level of user activity.
For reporting purposes, you can click the cogwheel icon and select the Export option to export the data from the Usage Pattern Tracking view to another application, such as Microsoft Excel.