OpenUIThemes, a new company that creates themes for Siebel Open UI

Some days ago I received an email from a Company representative who wanted to introduce me to their concept around Siebel Open UI. Why not? I replied “Ok” and so I joined a video conference with the guy the next day.

Much to my surprise, they had decided to create packaged themes with various look & feel for Siebel Open UI to help other companies customize their Siebel CRM Open UI application.

The idea is very promising I think, as every company has corporate colors and branding that makes its visual identity.

I’ve seen in the past that it’s much easier to implement a new tool, make an upgrade to an existing tool and finally gain user adoption when the users feel that the software was made specifically for their company (visual identity, colors, display, etc… is part of it).

It also seems to go along with Oracle’s strategy with the Open UI (apart from the compatibility benefits).

Here is the URL: http://www.openuithemes.com

At the end of the video conference, I had a look at the code of one of their themes and they also offered me to test it… So I think I will!

Next post I will make a review of this test and share my thoughts.

Homepage EditLayout Issue

In Siebel 8.1.1.10, Edit layout is not working. As per their document, no Quick fixes are available for this issue & next version (8.1.1.11) may not fix this issue.

Fixing date field Jumbing in Siebel open UI

There might be some issue with date input field. We need to edit the css files to fix this problem.
I got the same problem in vanila SRF also.

Above image is before selecting/clicking calender Icon

After clicking calender icon. You can see its length is increased.


To solve this probelm, go to
theme-base.css file in your "files" folder.

.mceGridField input.siebui-input-popup {
        max-width: 119px;
    }

Here   max-width: 119px is given as our input filed. If you need more than this width, you can alter this.

GetProfileAttr/SetProfileAttr not Working in Siebel 8.1.1.10

In 8.1.1.10 version, SetProfileAttr() has been disabled for HTTP calls as a security fix.
That means if you have a browser scripts uses SetProfileAttr(), it won't work. No change to GetProfileAttr() access.
Oracle disable this "SetProfileAttr()" as a security fix. So enabling this is not recommended.

SetProfileAttr() access can be turned on by setting the server parameter “EditProfileAttr” value to TRUE

Siebel Business Applications Release 8.1.1.10

Oracle just released siebel version 8.1.1.10 . You can download this from edelivery cloud.

Hope that this version will be a solution for all issues that we faced in previous version (8.1.1.9)

adding voice input in siebel openUI :: Physical Render experiement

Please Note: Here we are using a webkit property. That means this feature will work only in google chrome.
Google chrome supports it's own voice search property. We can add this property to our application by adding "x-webkit-speech" in our input fields. Here we can create a physical render and implement this feature.


<!-------------------CODE Begins----------------------------!>

if( typeof( SiebelAppFacade.GoogleVoicePR ) === "undefined" ){
    SiebelJS.Namespace( "SiebelAppFacade.GoogleVoicePR" );
   
    SiebelApp.S_App.RegisterConstructorAgainstKey( "GoogleVoicePRenderer", "SiebelAppFacade.GoogleVoicePR" );
   
    SiebelAppFacade.GoogleVoicePR = ( function(){
       
       
        function GoogleVoicePR( pm ){
            SiebelAppFacade.GoogleVoicePR.superclass.constructor.call( this, pm );
            var controls = this.GetPM().Get( "GetControls" );
            var cntrl = controls[ "Last Name" ];   
            var lastNameCntrl  = cntrl.GetInputName();
            $('input[name="'+lastNameCntrl+'"]').attr("x-webkit-speech","x-webkit-speech");

        }
       
        SiebelJS.Extend( GoogleVoicePR, SiebelAppFacade.PhysicalRenderer );
       
        return GoogleVoicePR;
    }());
}


<!-------------------Code Ends------------------------------!>

Mapping & Finishing customization (Part – 4)

Part - 1

Part - 2

Part - 3

This is our final steps in this customization. Here we are going to Map our custom physical render & Physical Model.  We are validating the EmailAddress field in contact form applet.

We are mapping our Key. Hope you remember our key, that we used to register.

So in tools go to contact  form applet.

Expand Applet user property

1.       Create a new user property Name -> Physical_Render and Render Key as its value (Shown in fig)

Another user property Physical_Model and Model key as its  value.

Compile Object.

2.       Now Copy our code (Physical Render & Physical model )to SCRIPTS->Siebel->custom folder

3.       Open OBJECTS Folder. There you can see “manifest_extensions.map”. Open  this in a notepad or wordpad.  Map our Key with applet.

4.       Open “custom_manifest.xml” in the same folder.

Find  <PLATFORM_KEY_SPECIFIC>

                                <PLATFORM Name="Desktop">

Here we map our physical render

Open a new node and write our file name as shown in fig

Find <KEY_COMMON>

Here we map our physical Model

And map our new key as shown in fig.

Now we finished everything. Make sure that you compiled applet. Clear your browser cache.  And launch application and change your email. Hope everything works well.