Siebel IP 2015 : Siebel Composer Overview

What would you say if you see your traditional Siebel Tools has turned into Web based Siebel Tools (Siebel Composer) ?

Well, that made me crazy!

But it’s true! With Siebel IP 2015, Oracle has released web based Siebel tools  – Siebel Composer.

After Siebel Open UI, this is another major feature introduced by Oracle to compete with other could based CRM applications.



Oracle recommends to use Siebel CRM Composer only in isolated developer mode as current release is not ready for production environment.

But, nevertheless this is a big step to make Siebel more popular and interesting among developers and business users.

In this article, we will discuss Siebel CRM Composer in details.

That’s enough intro…

Let’s start our discussion with Siebel Composer definition.

Siebel Composer is the web version of Siebel Tools that runs on server. You can access it in any browser using Siebel Open UI client.

Currently it includes some of the functionalities of Siebel Tools. For example, using Siebel CRM Composer, you can make a field read-only or change field label without Siebel Tools.

We will discuss these functionalities in the later part of this article.

Siebel CRM Composer interface:

To give users an inconsistent look, Oracle has built Siebel Composer interface same as Siebel Business Application user interface.

Siebel IP 2015 - Siebel CRM Composer

The items in the first level object explorer (ex: Applet, Business Component) in Siebel Tools are available as screens. You can select any object from side menu icon in the top left corner of the screen.

Lower level objects of the object explorer appears as views and sub views under the screens in Siebel Web Tools.

All attributes of Siebel objects come as fields in Siebel composer.

For example: Name property of Applet object appears as Name field under Applet screen.

In Siebel CRM Composer, you navigate between screens and views in the same way that you do in Siebel application. You can add, update or delete records in the same way you do in any Siebel Open UI business application.


You might be wondering:

Siebel Composer looks like any other Siebel application.

So, does that mean, lock or unlock object/s is not required anymore before doing any changes?

How to compile changes in repository?


Same as Siebel Tools, developers must lock an object before modifying it and unlock once modification is completed.

Steps to lock/unlock an object in Siebel Composer:

  • Select the object
  • Click on ‘Lock Object’ from applet menu
  • Modify the object
  • Click on ‘Unlock Object’ to unlock the object.

That simple!

But unlike Siebel Tools, you do not compile any object in repository file. Once objects are modified in Siebel Composer, navigate to Administration – Runtime Configuration > Publish view and publish all changes.

You can publish objects in two ways –

Siebel Composer - Publish

1. Click on ‘Publish All’ to publish all modified objects at a time

2. To publish individual object, select the record and click on ‘Publish’

Now all your changes will be available in repository metadata table.

To verify your changes –

Siebel composer

1. Either you can navigate to Administration – Runtime Configuration > ‘Published Version’ view and check the object record. Object with latest version must be available under ‘Published Version’ view.

2. Or log in to Siebel application and verify all changes. If you were already logged in to application before object modification, then log off and log in again to see changes.

You know about AOM (Application Object Manager), right?

Remember this:

Siebel Web Tools Object Manager (ENU) is the AOM component for Siebel CRM Composer. Currently this component is available only in U.S. English language.


You have fair idea about Siebel Web Tools.

But you must know other advantages of Siebel Composer as well.

Benefits of Siebel CRM Composer over Siebel Tools:

1. No compilation, no downtime


If you add or modify any object in Siebel Tools, you have to compile it into repository file. Then you down the server, replace .srf file and restart the server again to see changes in Siebel Application.


There are some exceptions where you do not need to compile objects ( like workflow) in Siebel Tools. But except few, almost all objects need compilation.

But in Siebel Composer, there is no need of object compilation. You just login into Siebel Web Tools, do required changes and publish it.

All changes will be available in server without any compilation and downtime.

Like Siebel Tools, you can lock/unlock objects in Siebel composer also to stop simultaneous update.

It expedites the overall Siebel configuration process as well.

2. Improved user interface with easy navigation

Like other Siebel applications, Siebel Web Tools has screens, views, applets and fields. It has a separate object manager that helps you to open it as a web client. Due to its enhanced user interface, navigation among objects is easier than Siebel Tools.

3. More efficient web page rendering


For Siebel Tools, Siebel web templates have deeper hierarchy structure in Siebel Business Application. It makes Siebel application difficult to render on different devices like desktop, mobile devices.

But web templates for Siebel Composer have flatter hierarchy structure. It makes web templates flexible to render across wide range of devices.

Flatter hierarchy also helps to reduce server roundtrip to render web pages.

Unlike Siebel Tools, you do not modify .swt files to configure web template files here.

Now you just add or update records/fields in the Web Template Item view of Web Template screen. Also it is not necessary to use table tag to position fields in web template files.

4. More elements for building user interface

Siebel CRM composer includes all objects/properties of Siebel Tools as screens/views/fields. Plus it has few extra fields that are not available in Siebel Tools.

For example:

Template Item Holder Name field is available in Applet Web Template Item view, View Web Template Item view and Web Page Item view. This field captures the name of Item Identifier and helps to identify it easily.

To know the list of new fields available in Siebel Composer, click here.

5. Required less network traffic

Let me tell you how…

You know, Siebel composer has flatter hierarchy of web templates. Also it renders only the necessary elements in user interface. This needs less network bandwidth to deliver web pages in UI.

And last but not least…

6. Enhanced file loading

Besides existing presentation model and physical renderer for views or applets, PM and PR are available for web pages as well. In Siebel Composer, files for PM, PR or framework (required to start the Siebel application) are loaded from manifest.

Now you know what all extra benefits you can get from Siebel Composer (IP15).

Next let me explain:

Siebel Tools objects that are included in Siebel Composer Developer Preview (IP 15):

Integration Object
Symbolic String
Business Component
Business Object
Web Page
Business Service
Message Category
Web Template
Pick List


Siebel Tools objects that are not included in Siebel Composer Developer Preview (IP 15):

 Assignment Attribute  Icon Map  Server Component Type
 Assignment Criteria  Import Object  System Activity Object
 Bitmap Category  Pager Object  Task
 Content Object  Repository  Task Group
 Dock Object  Schema Maintenance Phase  Toolbar
 EIM Interface Table  Schema Maintenance Process  Workflow Policy Column
 Entity Relationship Diagram  Schema Maintenance Step  Workflow Policy Object
 Find  Search Category  Workflow Policy Program
 Help Id  Search Engine  Workflow Process
 HTML Hierarchy Bitmap  Search Index  

You know what?

Once you upgrade your Siebel application to IP15, all file based contents for Siebel web templates turn into table based contents. Due to this web template migration, Incremental Repository Merge for IP15 takes longer time than earlier version.

Also make sure that the ‘EnableResponsive‘ parameter is set to ‘TRUE‘ for all Siebel applications that use responsive web design feature. By default, value of this parameter is set to ‘FALSE‘. This parameter enables Siebel CRM Composer for that Siebel application.


How to modify this parameter value?

To change the parameter value, navigate to Administration – Server Configuration screen and search for the component of the Siebel application. Then you go to component parameter list and update the parameter value.

Now we are at the end of the discussion…

But wait a minute:

Before closing this article, let us tell you few features that would come in future releases.

As per Siebel Composer Bookself published by Oracle, below features will be included in future releases

  • WYSIWYG (What You See Is What You Get) display and drag-and-drop functionality in the user interface.
  • Drop-down lists of values for some fields to replace free form text fields in which you enter data.
    • Access to Siebel CRM Composer from within the Siebel application.
  • Management of a multi-user development environment for Siebel CRM Composer.
  • Publication of repository changes in a development, test, and production environment, where the changes are implemented without having to restart the server.

Just to summarize:

Siebel Composer is a good initiative to move Siebel application on the cloud. It also makes configuration process faster and easier.

To know more, please refer Siebel composer bookself.

You know, Siebel IP 2016 has been released recently. In out next article, we will discuss all new features of Siebel Composer – IP16.

What do you think? It is good for Siebel future or not?

Please leave your comment below!

Keep in touch, follow TechOneStop on Facebook / Twitter / LinkedIn / Google+.

Watch YouTube Video on Siebel CRM Composer (IP 15):

Error: Invoking service ‘Context Service’, method ‘GetRowSetData’ at step ‘Get Context Row Set’ (SBL-BPR-00162) (SBL-DAT-00215)”.

Have you seen below error message during Siebel configuration?

“Error invoking service ‘Context Service’, method ‘GetRowSetData’ at step ‘Get Context Row Set’.(SBL-BPR-00162)”.

Sometime it is followed by another error message – “This operation is not allowed when there are no records displayed. Please execute a query that returns at least one record or add a new record.(SBL-DAT-00215)”.

Recently one of our readers dropped us a mail asking solution to fix this issue.

This error usually comes up when we are working on Signals or variable maps or pricing workflows in Siebel. There could be many reasons behind this error but most common mistakes are –

1) PSP driver Workflow is not active
– Verify that the PSP driver Workflow is in active status. If not, activate the workflow, restart server and verify it once again, issue should be resolved.

2) Business components are not based upon class CSSBCOrderMgmtBase, CSSBCPecBase and their subclasses
– Signals can be invoked only for that business component if it’s base class is either CSSBCOrderMgmtBase or CSSBCPecBase or their sub classes. Mainly signals call be called from all order management related objects like Quote , Order, Product BCs. If we try to invoke signal from any other business components which are not based upon these classes, Siebel will throw this error.

Please share your experience if you have faced this issue for any other reason or these two solutions were not sufficient to fix this error message.

To know more, follow ‘TechOneStop on Facebook / Twitter / LinkedIn / Goolge+ or join our website as follower.
Sharing is caring, so please share this article with your friends.

<< SBL-EAI-08032: WSDL cannot be generated               SBL-SCB-00014 / SBL-NET-01023 >>

Highlight required fields in Siebel Open UI

Highlight required fields in Siebel Open UI – sounds interesting?

Let us discuss in details.

We all know about required fields in Siebel, right?

It means, users can not save the record keeping such fields blank.

Also, we know that in Siebel, every required field on form applet comes with a red asterisk on right hand side.


What if we highlight all required fields beside red asterisk?

Does it look good?

Let’s take a look…

Highlight required fields in Siebel Open UI
No doubt, highlighted required field has better visualization than the other one.

In this article, we will discuss how to highlight required fields in Siebel Open UI.

Wait a minute,

Let us tell you few more real time scenarios as well except this one.

Highlight all required fields if users do not enter any value and try to save the record. But when the application loads, required fields come with a red asterisk only.

If users enter wrong value in a field, highlight that field with error message.

For example, if users enter numeric value in ‘Name’ field, highlight the name field.

There are n number of business requirements related to highlighted fields in Siebel.


Back to our topic…

Steps to highlight required fields in Siebel Open UI:

Step 1: Determine CSS tag (Optional step)

You know,

For any kind of visual requirements in Siebel Open UI, very first step is to find out the corresponding CSS tag for that particular element.

But why this step is optional for this requirement?

It is optional because we are not configuring our application for a particular field. We are going to highlight all required fields throughout application.

However, it is better to know the CSS tags behind required fields.

So, right click on the field and click on ‘Inspect element‘ to launch browser developer tool.

Browser developer tool is nothing but a vanilla tool provided by almost all modern browsers like Google Chrome, Mozilla Firefox, IE 8+.

To know more about browser developer tool, read our article onDebugging in Siebel Open UI‘.

Step 2: Build the new CSS file

You know about Cascading Style Sheet (CSS), right?

If not, try to get a basic idea about CSS. It is very much required to be Siebel Open UI developer.

To learn CSS, we would suggest you to go through w3schools – CSS tutorial.


We are going to use a simple notepad to write CSS rules. You could use any tool as per your choice.

CSS rules are –

input[aria-required=”true”], div.mceGridField input.siebui-ctrl-mvg[aria-required=”true”], input[aria-required=”true”] [readonly=”readonly”]


border-color: #CC0000 !important;

background: #FFCCCC !important;

color: red !important;

font-weight: bold !important;;


All CSS rules are self-explanatory except ‘!Important‘, isn’t it?

Purpose of using this CSS property is to override the default CSS priority rule. Any CSS property with ‘!Important’ will always be applied on the selector, no matter what all other rules appear in the CSS file.

Now save the file with .css extension. We have named our file – highlight_required_fields.css.

Remember, you must save the file with .css extension.

Step 3: Copy the CSS file

Did you go through our Siebel Open UI configuration best practices tutorial?

Yes! then you know,

According to Open UI configuration best practices, you should keep all custom CSS and JS files under custom folder/s.


Do you know why Oracle suggests to keep all custom CSS and JS files under custom folder/s?

This is to avoid any unnecessary conflicts during application upgrade.

If you follow this practice, all vanilla files will be migrated to upper version without affecting any custom file.


If you don’t have a custom folder already, create one and keep all custom CSS and JS files under that folder only.

Now, copy the .css file under ‘custom‘ folder and register it in theme.js file.

For dedicated client, copy the custom CSS file under ..Client/PUBLIC/<lang>/files/custom.

For Webclient, copy the file under ..webserver/PUBLIC/<lang>/files/custom.


Do you know how to register .css file in theme.js file?

Read the next step…

Step 4: Register the file in Theme.JS file

Once your .css file is ready, next step is to register the file in theme.js file.

You’re probably wondering…

Why theme.js file?

It is because we are doing this customization for ‘GRAY_TAB‘ theme only. This ‘GRAY_TAB’ theme is based on theme.js file.


Where do you find theme.js file in Siebel Open UI?

For dedicated client, navigate to  ..Client/PUBLIC/<lang>/<ver no>/SCRIPTS/siebel

For Webclient, navigate to ..webserver/PUBLIC/<lang>/<build>/SCRIPTS/siebel

Now open the theme.JS file in any text editor, register the CSS file and save it.

Script to register –

var ua=navigator.userAgent;

var re=new RegExp(“MSIE ([0-9]{1,}[.0-9]{0,})”);



var IE8inc=”files/ie8-compat.css”;

var IE8incTangerine=”files/ie8-compat-tangerine.css”




var IE8inc=””;var IE8incTangerine=””









Step 5: Register theme.js file (Optional step)

Another optional step to highlight required fields in Siebel Open UI application…

You may have theme.js registered already but it is better to verify!

To do so, login into application and navigate to Sitemap > Administration-Application > Manifest Files.

Here, query for theme.js file.

Customize Siebel Open UI

If the file is already there, no need to do anything.

But if not, create a new record to register theme.js file like below screenshot..

Now navigate to Administration-Application > Manifest Administration and create new UI objects, Object expression and add the file.

siebel open ui customization - highlighted required fields

Step 6: Verify changes


Clear browser cache and reload the application…

You should see all required fields highlighted on Form applet.


If you have any question, please let us know.

Also if you want us to discuss any business scenario in this ‘Configuring Siebel Open UI‘ series, please leave your comment below.

Don’t forget to leave your feedback in the comment section!

Keep in touch, follow TechOneStop on Facebook / Twitter / LinkedIn / Google+.

<< Change screen tabs icons                                       Customize the Server Busy error in Siebel >>

Watch our YouTube Video on how to configure Siebel Open UI to highlight required fields:

Change icons on screen tabs in Siebel Open UI

Have you ever tried to add or change icons on screen tabs in Siebel HI application?

Before that,

Do you think, we can configure screen tab icons in Siebel HI at all?

And what about Siebel Open UI?

Configuring Siebel Open UI

Answer is YES!

We can add or change icons on screen tabs in Siebel HI as well as Open UI application.

There are two ways to change screen tab icons in Siebel –

1. Repository Dependent Process – Configure Bitmap category and Bitmap in Siebel Tools

2. Repository Independent Process – Find out the image name and replace it with custom image

We all like fast and non srf solution, isn’t!

Here, we will discuss about repository independent process in details. Though we will brief you about srf dependent process also but main focus will be on non srf solution.

You may think, what is the use or business value of changing screen tab icons?


It’s not like that it does not have any business value. Better user experience is also a business value, right?

You know, image can engage users more than just a text.

Even we have seen a customer who asked to replace all texts from screen tabs with images completely just for better user experience.


Steps for non srf solution to change icons on screen tabs in Siebel HI or Open UI:

Step 1. Find out the image name, responsible to display icon on screen tab

You already know how to find out any element or object in Siebel Open UI, right?

If not, you must go through our Open UI training articles, particularly Siebel Open UI theme customization.

Here we will change screen icon for ‘Account‘ tab.

So, right click on ‘Account‘ screen icon and click on ‘Inspect Element‘ to launch inspector.

change icons on screen tabs in Siebel Open UI

Under Elements tab, you should see highlighted ‘img‘ html tag. Once you keep the cursor over that highlighted script, you will see a popup of that image and icon on screen tab will also be highlighted.

Modify screen tab icons in Siebel Open UI

Now seeing the image, you can tell the image file name and size.

For ‘Account‘, image file name is ‘accounts_icon.gif‘ and size is ‘16X16‘ pixels.

Image size is important because we have to replace this image with same size image. Otherwise Siebel will not display the icon properly.

For this tutorial, we have got a custom image with 16X16 pixels.

If you want to increase the size for screen tab icons, then you have to modify CSS rules.

You can test it by updating CSS properties inline using browser developer tool.

Update icons on Screen tab in Siebel Open UI

On the right hand side, you can see few CSS properties from theme-base.css file, right?

Just change the height parameter from 16px to any other value and see, icon size is changed. Likewise you can test font size, padding, line height also. To know more about theme related configuration, read our article on Siebel Open UI theme.

Anyway, back to our topic.

So far, we know what is the image name and where to find it.

Step 2. Verify custom image

Same as application loading image, screen tab icon also has size limit. From the previous step, we have got to know that best fit image size is 16X16 pixels.

To resize custom image, you can use any third party tool like Microsoft Office picture ManagerPicresize.

Also don’t forget to save it with .gif format.

Step 3. Replace the out of box image


Copy your custom image file under ‘IMAGES‘ folder.

For dedicated client, copy the image under ..Client\PUBLIC\<lang>\IMAGES.

For web client, copy it under Siebel Web Server\PUBLIC\<lang>\images.

Do not delete the out of box image!

Before copying the custom image, rename the vanilla one. So that, if it requires, you can always get the vanilla image.

Change screen tab icons in Siebel Open UI

Step 4. Verify Siebel Open UI application

Now clear browser cache and relaunch Siebel Open UI application, you should see the new icon.

Customize icons on screen tabs in Siebel Open UI

Simple and easy!!


It has a drawback 🙁

What will happen if the same vanilla image has been used in other place/s as well?

In this scenario, vanilla image will not appear in any other place as you have changed the name.


Good thing is that, we have never faced such issue but it may occur. In this case, you have to go for srf dependent process to change icons on screen tabs.

So, just a brief about Repository Dependent Process.

First, find out the ‘Bitmap Category’ and ‘Bitmap’ responsible to display the icon.

If the screen tab has icon, it will have ‘Bitmap Category’ also.

So navigate to Siebel Tools -> Screen and search for the screen.

From ‘Bitmap Category’ property in Screen object, you will get the category name.

If there is no category associated, you have to create a new one.

So copy the category name and query for the category under ‘Bitmap Category’ object.

Come down to the ‘Bitmap‘ child object and query with Name = Screen Tab Icon. If it is not there, then we have to create a new one with image name.

Name: Screen Tab Icon
Filename: Custom image file name

Do not forget to copy the custom image under ‘IMAGES’ folder as specified in step 3.

Compile all changes and launch the application. You must see the custom icon instead of vanilla.

Good enough!

If you have any question, please let us know.

Also if you want us to discuss any business scenario in this ‘Configuring Siebel Open UI‘ series, please leave your comment below.

Don’t forget to leave your feedback in the comment section!

Keep in touch, follow TechOneStop on Facebook / Twitter / LinkedIn / Google+.

<< Change application default loading image       Highlight required fields in Siebel Open UI >>

Watch our YouTube Video on how to configure Siebel Open UI to change icons on screen tabs:

Configuring Siebel Open UI – Change application loading image

Configuring Siebel Open UI‘ is our next series where we will discuss how to customize application as per business requirements.


Have gone through all Siebel Open UI training articles?

If not, we would suggest you to read Open UI tutorials first and then start configuration. 

Now its time to customize Siebel Open UI application.

We will start with few easy and interesting configuration requirements. Later we will discuss actual business scenarios.


You must follow best practices as much as possible during Siebel Open UI configuration.


Lets start with a simple requirement – change the application default loading image.

Though it does not have much business impact but we have seen many customers to change default loading images.

By default Siebel Open UI loading image looks like this – Siebel open ui default loading image(spinning wheel).

We will change it to this – Siebel open ui custom loading image(running man).

Though our custom image looks like static image but actually it is an animated image 🙂

Configuring Siebel Open UI -Change application default loading image

Sounds interesting?

Lets look configuration steps.

Steps for configuring Siebel Open UI loading image:

1. Verify custom image size

2. Rename out of box loading image (loadingAjax.gif)

3. Copy custom image

4. Verify Siebel Open UI application

Step 1: Verify custom image size

Very first step is to check custom image size. Image size must be less than or equal to 32 X 32 pixels. Otherwise Siebel will display only part of the image during application load.

To resize custom image, you can use any third party tool like Microsoft Office picture Manager, Picresize .

If you are using animated image, then don’t forget to save it with .gif format.

Step 2: Rename out of box loading image (loadingAjax.gif)

Do you know that loadingAjax.gif is responsible to display spinning wheel during application load?

So, before copying the custom image, rename ‘loadingAjax.gif’ file to keep the out of box image.

To rename the file, go to IMAGES folder under ..Client\PUBLIC\enu\IMAGES (for dedicated) or ..webserver\PUBLIC\enu\images (for web client), search for the file ‘loadingAjax.gif’ and rename it.

Step 3: Copy custom image

Now copy-paste your custom image file under IMAGES folder and rename it as loadingAjax.gif.

Step 4: Verify Siebel Open UI application

Delete browser’s cookies / history and launch the application. You should see your custom loading image instead of default image.

Simple and easy, isn’t it!!

If you have changed the default loading image in Siebel HI, then you are already familiar with these steps.

We have followed almost similar approach for Open UI also.

Do you want us to discuss any business scenario in this ‘Configuring Siebel Open UI’ series? please write us.

Also dont forget to leave your feedback in the comment section below.

Keep in touch, follow TechOneStop on Facebook / Twitter / LinkedIn / Google+.

                                                                                                                 Change icons on screen tabs >>

Watch our YouTube Video on how to configure Siebel Open UI to change application default loading image:

How to remove ‘Case Required’ prompt from all fields, displayed on home page search applet

Fixing issues in Siebel Open UI is really fun. Well, let me explain you why so. Have you noticed such behavior in Siebel Open UI where ‘Case Required’ prompt is displayed for all fields on home page search applet? In SupportWeb, Oracle has reported this symptom as ‘There is inconsistent UI behavior between home page search applets and regular form/list applets when the field is reconfigured to support case insensitive searches’. Now see the below screenshot, you can see ‘‘ prompt for Opportunity name and Account name field but expected behavior is that there will not be any such prompt as those are not case sensitive search at all.

Case Required on home page in SIebel Open UI -

Oracle has taken this one as product bug (BUG #19001914) and stated like ‘This is a cosmetic issue as searching against the fields in the home page search applet will still be case insensitive, Until a fix for this is available there is no workaround’. But do not wait for their work around, we can fix it within few minutes. Follow below steps to fix it.

Step 1: Do ‘Inspect Element’
– Login into Siebel Open UI application and navigate to home page of any entity (Opportunity or Account or Contact) 
– Right click on any field from search applet and click on ‘Inspect Element’ option to launch inspector window

Inspect Element in Siebel Open UI -

Step 2: Locate CSS and file name

– Inspector window will keep the corresponding script highlighted under Elements tab. If it is not highlighted, then again right click on the field and choose ‘Inspect Element’ option.
From the script, you get to know that class ‘siebui-watermark-text‘ is responsible to display ‘‘ tag in watermark.
– From right hand side window, locate the CSS class ‘siebui-watermark-text‘ and change the color from ‘#C0C0C0’ to ‘#FFFFFF’. Can you see ‘Case Required’ tag now? You have just changed the color to White (:D)
– For us, CSS file name is ‘theme-gray.css’. This CSS file could be different based upon the theme that you are using
– Now refresh your application, it will display ‘Case required’ again
CSS in Siebel Open UI -

Step 3: Change theme-gray.css file

– Open the file ‘theme-gray.css’, located under ..Client_1PUBLICenuFILES (for dedicated client) or ..SWEAppPUBLICenufiles (for web client)
– Find the string ‘siebui-watermark-text’ and change the color code from ‘#C0C0C0’ to ‘#FFFFFF’.
  It should look like below:
                           color: #FFFFFF !important;


– Save and close the file

Step 4: Verify changes
– Restart web server service (For Windows environment, web server service name is IIS Admin Service)
– Clear browser cache and launch Siebel Open UI application
‘<Case Required>‘ is gone from search applet!! Same way, you can change field text color, font, background color and many more. To get more details, read our article on Siebel Open UI theme.
If you face any problem, please let us know. For more updates on recent activities, follow ‘TechOneStop‘ on Facebook / Twitter / LinkedIn or join our website as follower.

To know more, watch our YouTube video: