siebel

"Mere color, unspoiled by meaning, and unallied with definite form, can speak in thousand different ways." -- Oscar Wilde Status bar is a common feature in siebel where color encoding depicts the status of record. I recently encountered similar scenario where i had to display different coloured text based on certain conditions on Form Applet. Browser script clicked me first. But finally this was achieved using configuration. As i struggle to achieve similar result in List applet we will discuss how on Form applet desired could be done. Lets take Service Request entity as an example (offlately this is becoming my favourite entity). Problem Statement : If SR has some related SR then it should display some text in Red else alternate text in green. Solution: a) Go to SR buscomp. Create following fields Name: PastSRRed Calculated: True Calculated Value: " < font color='red' > "+"This SR has related SR." + " < font > " Name: PastSR

Offlately i am working on SI application and being bombarded by lot of user acceptance issues. I am not sure whether God is really happy or its just a clearance sale that most of the time we are able to find the fix. Recently we were being asked to implement explicit write sort of scenario in standard interactivity portal. In the detail applet for service request user didn't want to click Save button to save the record instead it was required as soon as details in the Description are filled record should auto save. Again browser script comes to party. As browser script on standard events of Applet/BC doesn't work under SI architecture, only control level events are supported. Ever friendly Alex has beautifully explained the browser script architecture in his recent post . So idea here is to explicitly call the click event for "Save" button on the applet for OnChange event of Description column. Fortunately for us most of the fields on the applet were auto populated an

Whenever I am asked to work on siebel standard interactivity it feels like harry potter stranded in those wild mazes. But i can tell you if you play in Java/HTML you can really unearth hidden gems in SI application. Recenty while working on Siebel eSales portal we were asked to implement  typical requirement to control button's visibility conditionally.  For the Open status button should be visible on list applet and for other status values it should be hidden. Once again "WebApplet_ShowControl" server event is  critical to its implementation as other browser events of applet are not supported in SI architecture. The idea is to modify the HTML generated at run time to  achieve conditional visibility. Below steps are required for ultimate illusion. 1 - In the HTML attribute of the Button Control which we want to make conditionally visible add below property style='visibility:hidden' By default button will be hidden and we will only make it visible when status is Op