<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0"><channel><atom:id>tag:blogger.com,1999:blog-8531650369937741306</atom:id><lastBuildDate>Sat, 21 Apr 2012 03:37:33 +0000</lastBuildDate><category>Siebel Server Admin</category><category>Where is IT going?</category><category>Tom Siebel</category><category>Siebel Tips</category><category>Siebel Configuration</category><category>Siebel eScript</category><category>Siebel 8 Presentations</category><category>Product Configurator</category><category>Miscellaneous</category><category>Basics</category><category>Siebel Errors</category><category>Siebel EAI</category><category>Downloads</category><category>Screencasts/Videos</category><category>Siebel Presentations</category><category>Best Practices</category><title>Exploring Siebel</title><description /><link>http://exploringsiebel.blogspot.com/</link><managingEditor>noreply@blogger.com (Tejeshwer)</managingEditor><generator>Blogger</generator><openSearch:totalResults>38</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/ExploringSiebel" /><feedburner:info uri="exploringsiebel" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:emailServiceId>ExploringSiebel</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8531650369937741306.post-221275584965637148</guid><pubDate>Sat, 20 Nov 2010 05:52:00 +0000</pubDate><atom:updated>2010-11-20T11:36:30.820-08:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Siebel EAI</category><title>Fetching value of Oracle Sequence from External DB</title><description>Fetching value of external Oracle Sequence in Siebel is one of the typical business requirement in integration of Siebel applications. In case of windows environment solution is quite straight forward, we just need to create ADODB object in script and execute sql on external database. &lt;br /&gt;&lt;br /&gt;But in case of Unix environment this is not possible as ADODB is not supported in Unix.&lt;br /&gt;&lt;br /&gt;&lt;a name='more'&gt;&lt;/a&gt;&lt;br /&gt;For this requirement we can use External Business Component or "EBC" to fetch the next value of an external sequence.&lt;br /&gt;&lt;br /&gt;Solution:&lt;br /&gt;1. Create external table in Siebel database using the External Table Schema Import Wizard.&lt;br /&gt;2. Create additional column in table and set Alias property of the column with concatenation of external column name and the external oracle sequence like:&lt;br /&gt;&lt;br /&gt;&lt;div class="separator" style="clear: both; text-align: center;"&gt;&lt;a href="http://4.bp.blogspot.com/_mJfGtfR_Zdc/TObW1JimP4I/AAAAAAAAAG4/p1opB65q0LM/s1600/EBC.JPG" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="86" ox="true" src="http://4.bp.blogspot.com/_mJfGtfR_Zdc/TObW1JimP4I/AAAAAAAAAG4/p1opB65q0LM/s400/EBC.JPG" width="400" /&gt;&lt;/a&gt;&lt;/div&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Siebel will use this Alias property of the columns to build SQL for external tables. So when building SQL in this case it will concatenate the column value with the nextvalue of the specified sequence.&lt;br /&gt;&lt;br /&gt;After this, compile all the changes and query on BC based on this table and process the field value to fetch next value of the sequence of external database.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8531650369937741306-221275584965637148?l=exploringsiebel.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ExploringSiebel/~4/xQT7Ui-wT7w" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/ExploringSiebel/~3/xQT7Ui-wT7w/fetching-value-of-oracle-sequence-from.html</link><author>noreply@blogger.com (Tejeshwer)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/_mJfGtfR_Zdc/TObW1JimP4I/AAAAAAAAAG4/p1opB65q0LM/s72-c/EBC.JPG" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://exploringsiebel.blogspot.com/2010/11/fetching-value-of-oracle-sequence-from.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8531650369937741306.post-4406171967241218038</guid><pubDate>Tue, 31 Aug 2010 09:10:00 +0000</pubDate><atom:updated>2010-08-31T02:10:06.116-07:00</atom:updated><title>Sending email from eScript</title><description>Sending email updates from Siebel is quite easy, we just have to call Outbound Communication Manager, an OOB Business Service to trigger emails. &lt;br /&gt;&lt;br /&gt;&lt;a name='more'&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;We can call this service from any of the events available or just call this service from a Workflow.&lt;br /&gt;Found this simple code on IT-toolbox :&lt;br /&gt;&lt;br /&gt;&lt;pre class="js" name="code"&gt;var mailBS = TheApplication().GetService("Outbound Communications Manager"); &lt;br /&gt;var psInput = TheApplication().NewPropertySet(); &lt;br /&gt;var psOutput = TheApplication().NewPropertySet(); &lt;br /&gt;&lt;br /&gt;psInput.SetProperty("CommProfile", "Communication profile name"); &lt;br /&gt;psInput.SetProperty("MsgToList", "email ids to whom you want to send email"); &lt;br /&gt;psInput.SetProperty("MsgBody", "email content"); &lt;br /&gt;psInput.SetProperty("MsgSubject", "subject"); &lt;br /&gt;mailBS.InvokeMethod("SendMessage", psInput, psOutput); &lt;br /&gt;&lt;/pre&gt;&lt;br /&gt;&lt;br /&gt;Coming up Next: Steps to configure Communication Profile.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8531650369937741306-4406171967241218038?l=exploringsiebel.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ExploringSiebel/~4/bTsFXonbcj8" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/ExploringSiebel/~3/bTsFXonbcj8/sending-email-from-escript.html</link><author>noreply@blogger.com (Tejeshwer)</author><thr:total>0</thr:total><feedburner:origLink>http://exploringsiebel.blogspot.com/2010/08/sending-email-from-escript.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8531650369937741306.post-4931636295334610352</guid><pubDate>Fri, 27 Aug 2010 18:06:00 +0000</pubDate><atom:updated>2010-08-27T11:14:43.891-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Siebel eScript</category><category domain="http://www.blogger.com/atom/ns#">Product Configurator</category><title>Get Attribute Value - Product Configurator</title><description>There is no method out of the box available in Siebel Product Configurator that can be used to get attribute value. For this one of my team member have written this code which traverses the product structure and return the attribute value as string.&lt;br /&gt;&lt;a name='more'&gt;&lt;/a&gt;&lt;br /&gt;I am sharing the code here, it helped us in solving lots of complex business requirements.&lt;br /&gt;&lt;br /&gt;&lt;pre class="js" name="code"&gt;function GetAttr (AttribName)&lt;br /&gt;{&lt;br /&gt;  var ps = TheApplication().NewPropertySet();&lt;br /&gt;  var ps2 = TheApplication().NewPropertySet();&lt;br /&gt;&lt;br /&gt;  GetCPInstance(ps);&lt;br /&gt;  ps2 = ps.GetChild(0).GetChild(0).GetChild(0).GetChild(0).GetChild(0).GetChild(0);&lt;br /&gt;&lt;br /&gt;  var count = ps2.GetChildCount();&lt;br /&gt;  for(var i = 0; i&amp;lt; count; i++)&lt;br /&gt;  {&lt;br /&gt;             var curr_node = ps2.GetChild(i);&lt;br /&gt;             var name = curr_node.GetProperty("Name");&lt;br /&gt;             if (name == AttribName)&lt;br /&gt;             {     var value = curr_node.GetProperty("Value");&lt;br /&gt;                   ps=null;&lt;br /&gt;                   ps2=null;&lt;br /&gt;                   curr_node = null;&lt;br /&gt;                   return(value); &lt;br /&gt;             }&lt;br /&gt;   }&lt;br /&gt;&lt;br /&gt;}&lt;br /&gt;&lt;/pre&gt;&lt;br /&gt;Note: This code will return the attribute value of root product only, for other child products code needs to be modified accordingly.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8531650369937741306-4931636295334610352?l=exploringsiebel.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ExploringSiebel/~4/K6ATPo1ewD8" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/ExploringSiebel/~3/K6ATPo1ewD8/get-attribute-value-product.html</link><author>noreply@blogger.com (Tejeshwer)</author><thr:total>0</thr:total><feedburner:origLink>http://exploringsiebel.blogspot.com/2010/08/get-attribute-value-product.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8531650369937741306.post-7706473605353738423</guid><pubDate>Tue, 10 Aug 2010 16:53:00 +0000</pubDate><atom:updated>2010-08-10T09:57:54.930-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Siebel Tips</category><title>Automatic login to Siebel thin client</title><description>While in development, I used to get bugged up by entering credentials every time application needs to be accessed. Out of&amp;nbsp;frustration&amp;nbsp;I have found way to bookmark the credentials in IE favorites so that it directly takes the user to application home screen.&lt;br /&gt;&lt;br /&gt;&lt;a name='more'&gt;&lt;/a&gt;&lt;br /&gt;&lt;b&gt;&lt;span class="Apple-style-span" style="font-weight: normal;"&gt;&lt;br /&gt;&lt;/span&gt; &lt;/b&gt;&lt;br /&gt;&lt;b&gt;Step 1&lt;/b&gt;: Add application URL to IE favorites&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Step 2&lt;/b&gt;:&amp;nbsp;Edit&amp;nbsp;the target URL&amp;nbsp;from :&lt;br /&gt;&lt;br /&gt;&lt;div class="separator" style="clear: both; text-align: center;"&gt;&lt;a href="http://2.bp.blogspot.com/_mJfGtfR_Zdc/TGGELdnpvbI/AAAAAAAAAGo/WC3nRV-fkkg/s1600/favorites.bmp" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="200" src="http://2.bp.blogspot.com/_mJfGtfR_Zdc/TGGELdnpvbI/AAAAAAAAAGo/WC3nRV-fkkg/s200/favorites.bmp" width="145" /&gt;&lt;/a&gt;&lt;/div&gt;&lt;br /&gt;http://&lt;b&gt;[host name]&lt;/b&gt;/fins_enu/start.swe?SWECmd=Start&amp;amp;SWEHo=&lt;b&gt;[hostname]&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;to :&lt;br /&gt;&lt;br /&gt;http://&lt;b&gt;[host name]&lt;/b&gt;/fins_enu/start.swe?SWECmd=ExecuteLogin&amp;amp;SWEUserName=&lt;b&gt;[username]&lt;/b&gt;&lt;strong&gt;&lt;user name=""&gt;&lt;/user&gt;&lt;/strong&gt;&amp;amp;SWEPassword=&lt;b&gt;[password]&lt;/b&gt;&lt;br /&gt;&lt;b&gt;&lt;span class="Apple-style-span" style="font-weight: normal;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;/b&gt;&lt;br /&gt;&lt;b&gt;Step 3&lt;/b&gt;: Save URL.&lt;br /&gt;&lt;br /&gt;Now this bookmark will directly take you to the home screen of the application,without showing the login screen..&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8531650369937741306-7706473605353738423?l=exploringsiebel.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ExploringSiebel/~4/PuUmwP0fEG8" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/ExploringSiebel/~3/PuUmwP0fEG8/automatic-login-to-siebel-thin-client.html</link><author>noreply@blogger.com (Tejeshwer)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/_mJfGtfR_Zdc/TGGELdnpvbI/AAAAAAAAAGo/WC3nRV-fkkg/s72-c/favorites.bmp" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://exploringsiebel.blogspot.com/2010/08/automatic-login-to-siebel-thin-client.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8531650369937741306.post-3433552409876718170</guid><pubDate>Tue, 10 Aug 2010 16:36:00 +0000</pubDate><atom:updated>2010-08-10T09:36:07.578-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Downloads</category><title>Excellent Siebel EAI / Web services training Material</title><description>&lt;div class="MsoNormal"&gt;Really Excellent Siebel EAI training material is available for download on &lt;a href="http://4shared.com/"&gt;4 shared &lt;/a&gt;and &lt;a href="http://esnips.com/"&gt;esnips&lt;/a&gt;.&lt;/div&gt;&lt;div class="MsoNormal"&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="MsoNormal"&gt;1. &lt;a href="http://www.4shared.com/file/dQL7Ak3K/Siebel_EAI_PPT.htm"&gt;http://www.4shared.com/file/dQL7Ak3K/Siebel_EAI_PPT.htm&lt;/a&gt;&lt;/div&gt;&lt;div class="MsoNormal"&gt;Contents: Oracle Siebel Trainging Material of may 2004 and Hands on Labs &lt;/div&gt;&lt;div class="MsoNormal"&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="MsoNormal"&gt;2. &lt;a href="http://www.4shared.com/file/_vf9wkvH/web_service_ppt.html"&gt;http://www.4shared.com/file/_vf9wkvH/web_service_ppt.html&lt;/a&gt;&lt;/div&gt;&lt;div class="MsoNormal" style="mso-layout-grid-align: none; text-autospace: none;"&gt;Content: Web services PPTs and Hands on Labs + SOAP fundamentals &lt;/div&gt;&lt;div class="MsoNormal"&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="MsoNormal"&gt;2. &lt;a href="http://www.esnips.com/doc/a904d5b4-46db-4d95-b698-3d5c217085c2/Integrating_Siebel_Web_Services_Aug2006"&gt;http://www.esnips.com/doc/a904d5b4-46db-4d95-b698-3d5c217085c2/Integrating_Siebel_Web_Services_Aug2006&lt;/a&gt;&lt;/div&gt;&lt;div class="MsoNormal"&gt;Content: 146 Slides explaing Integrating Siebel 7.8 x CRM using Web Services&lt;/div&gt;&lt;div class="MsoNormal"&gt;with WAS 6 and RAD 6&amp;nbsp;&lt;/div&gt;&lt;div class="MsoNormal"&gt;&lt;b&gt;Source: IBM&lt;/b&gt;&lt;/div&gt;&lt;div class="MsoNormal"&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="MsoNormal"&gt;3. &lt;a href="http://www.4shared.com/file/e11fSFF3/Siebel_EAI_on_1025122.htm"&gt;http://www.4shared.com/file/e11fSFF3/Siebel_EAI_on_1025122.htm&lt;/a&gt;&lt;/div&gt;&lt;div class="MsoNormal"&gt;Siebel EAI PPT and labs + Siebel EAI Web Services Lab Guide + &lt;span style="color: black; font-family: Verdana; font-size: 10.0pt;"&gt;Concepts of WSDL, UDDI and SOAP&lt;/span&gt;&lt;span style="color: black; display: none; font-family: Verdana; mso-hide: all;"&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/div&gt;&lt;div class="MsoNormal"&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="MsoNormal"&gt;&lt;b&gt;Source Cognizant&lt;/b&gt;&lt;/div&gt;&lt;br /&gt;&lt;div class="MsoNormal"&gt;Happy learning &lt;span style="font-family: Wingdings; mso-ascii-font-family: &amp;quot;Times New Roman&amp;quot;; mso-char-type: symbol; mso-hansi-font-family: &amp;quot;Times New Roman&amp;quot;; mso-symbol-font-family: Wingdings;"&gt;&lt;span style="mso-char-type: symbol; mso-symbol-font-family: Wingdings;"&gt;J&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8531650369937741306-3433552409876718170?l=exploringsiebel.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ExploringSiebel/~4/xZk6zMp-yps" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/ExploringSiebel/~3/xZk6zMp-yps/excellent-siebel-eai-web-services.html</link><author>noreply@blogger.com (Tejeshwer)</author><thr:total>0</thr:total><feedburner:origLink>http://exploringsiebel.blogspot.com/2010/08/excellent-siebel-eai-web-services.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8531650369937741306.post-4243052517458105787</guid><pubDate>Tue, 10 Aug 2010 10:40:00 +0000</pubDate><atom:updated>2010-08-10T03:40:36.040-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Siebel Tips</category><category domain="http://www.blogger.com/atom/ns#">Siebel EAI</category><title>Generate Random Number (Cont..)</title><description>In continuation of my earlier &lt;a href="http://exploringsiebel.blogspot.com/2009/09/how-to-generate-random-number-in-siebel.html"&gt;post&lt;/a&gt; , I am sharing another way of generating random number in siebel using&amp;nbsp; vanilla SIS OM PC Service.&lt;br /&gt;&lt;br /&gt;SIS OM PC Service is a vanilla service which provides a method to get new system generated row id as output.&lt;br /&gt;The output can be utilised to generate random number by calling&amp;nbsp;RowIdToRowIdNum() in expression.&lt;br /&gt;&lt;br /&gt;Workflow:&lt;br /&gt;&lt;div class="separator" style="clear: both; text-align: center;"&gt;&lt;a href="http://4.bp.blogspot.com/_mJfGtfR_Zdc/TF2n3rE2NtI/AAAAAAAAAGg/7G84j6KC_YI/s1600/Random+Number.bmp" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" src="http://4.bp.blogspot.com/_mJfGtfR_Zdc/TF2n3rE2NtI/AAAAAAAAAGg/7G84j6KC_YI/s320/Random+Number.bmp" /&gt;&lt;/a&gt;&lt;/div&gt;&lt;br /&gt;Step 1 : Service :&lt;b&gt;SIS OM PC Service&lt;/b&gt; Method:&amp;nbsp;&lt;b&gt;Get Next RowId&lt;/b&gt;&lt;br /&gt;Output: &lt;strong&gt;Next Row Id&lt;/strong&gt;&lt;br /&gt;&lt;br /&gt;Step 2: Service: &lt;strong&gt;Workflow Utilities&lt;/strong&gt;&lt;br /&gt;Output : Random Num [Type Expression] : &lt;b&gt;RowIdToRowIdNum&lt;/b&gt;([&amp;amp;Next Row Id])&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Thanks to &lt;a href="http://exploringsiebel.blogspot.com/2009/09/how-to-generate-random-number-in-siebel.html"&gt;Sebestian&lt;/a&gt; for sharing this.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8531650369937741306-4243052517458105787?l=exploringsiebel.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ExploringSiebel/~4/WXhDXheGQog" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/ExploringSiebel/~3/WXhDXheGQog/generate-random-number-cont.html</link><author>noreply@blogger.com (Tejeshwer)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/_mJfGtfR_Zdc/TF2n3rE2NtI/AAAAAAAAAGg/7G84j6KC_YI/s72-c/Random+Number.bmp" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://exploringsiebel.blogspot.com/2010/08/generate-random-number-cont.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8531650369937741306.post-7208461355925028038</guid><pubDate>Mon, 02 Nov 2009 16:20:00 +0000</pubDate><atom:updated>2010-05-08T12:08:27.146-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Siebel eScript</category><category domain="http://www.blogger.com/atom/ns#">Product Configurator</category><title>Debugging Siebel eScript - Write Property Set to file</title><description>This is one of the tricks that i use to debug Siebel scripts. It is really useful if you are working on the product configurator. As most of the events in configurator have property set as argument to it, and there is no debug window to see runtime property values for the events.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a name='more'&gt;&lt;/a&gt;For configurator i use&amp;nbsp;&lt;span style="font-weight: bold;"&gt;WritePropSet &lt;/span&gt;method of&amp;nbsp;&lt;span style="font-weight: bold;"&gt;EAI XML Write to File&lt;/span&gt; business service. This method prints out the property set to a file on the siebel server. here is the code for the configurator:&lt;br /&gt;&lt;br /&gt;&lt;pre class="js" name="code"&gt;var ps = TheApplication().NewPropertySet();&lt;br /&gt;var ps1 = TheApplication().NewPropertySet();&lt;br /&gt;GetCPInstance(ps);&lt;br /&gt;var bs = TheApplication().GetService("EAI XML Write to File");&lt;br /&gt;var op = TheApplication().NewPropertySet();&lt;br /&gt;&lt;br /&gt;ps.SetProperty("FileName" , "C:\\temp.xml");&lt;br /&gt;bs.InvokeMethod("WritePropSet", ps, op);&lt;br /&gt;&lt;/pre&gt;similarly for business services and workflows we can have following snippet:&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;pre class="js" name="code"&gt;function Service_PreInvokeMethod (MethodName, Inputs, Outputs)&lt;br /&gt;{&lt;br /&gt;var ps = Inputs.Copy();&lt;br /&gt;var bs = TheApplication().GetService("EAI XML Write to File");&lt;br /&gt;var op = TheApplication().NewPropertySet();&lt;br /&gt;ps.SetProperty("FileName" , "C:\\temp.xml");&lt;br /&gt;bs.InvokeMethod("WritePropSet", ps, op);&lt;br /&gt;return (ContinueOperation);&lt;br /&gt;}&lt;br /&gt;&lt;/pre&gt;&lt;br /&gt;Above code can be use as code sniffer. Provided you use some naming sequence of the file.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8531650369937741306-7208461355925028038?l=exploringsiebel.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ExploringSiebel/~4/SRTR6NRZA7Q" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/ExploringSiebel/~3/SRTR6NRZA7Q/debugging-siebel-escript-write-property.html</link><author>noreply@blogger.com (Tejeshwer)</author><thr:total>0</thr:total><feedburner:origLink>http://exploringsiebel.blogspot.com/2009/11/debugging-siebel-escript-write-property.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8531650369937741306.post-5782871058625573970</guid><pubDate>Fri, 30 Oct 2009 18:58:00 +0000</pubDate><atom:updated>2009-11-02T08:03:55.186-08:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Siebel Tips</category><category domain="http://www.blogger.com/atom/ns#">Siebel Server Admin</category><title>How to see the SADMIN / SIEBEL password un-encrypted!</title><description>Today i have seen a very strange data in Siebel database that actually shouldn't be there just as a un-encrypted free text. I think people from Siebel Admin would know that which table i am talking about. &lt;br /&gt;&lt;br /&gt;&lt;a name='more'&gt;&lt;/a&gt;&lt;br /&gt;Usually all user details in Siebel database are kept in S_USER table and passwords are never stored in Siebel Database. Whenever there is a need to store the password either the value is masked or is stored in database after encryption. &lt;br /&gt;&lt;br /&gt;Even in siebns.dat file the password is not stored. All the name subsystems in server manager and on UI use masking to show password. But at one place, as I know the password is kept as clear string. This happens on the Server Manager Job Parameter table i.e. &lt;b&gt;S_SRM_REQ_PARAM&lt;/b&gt; table. &lt;br /&gt;&lt;br /&gt;I don’t know what was the reason the data on this table was kept unencrypted. If you want to get the password you just need to query the VALUE column of the parameter table and you will find the password in next row where SADMIN or SIEBEL user name is stored.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;select VALUE from SIEBEL.S_SRM_REQ_PARAM&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;This happens because to run certain jobs like Generate Triggers database user and password are required as arguments but due to some limitation of the jobs this data is not encrypted. So if your server administrator use SADMIN as the password for generate trigger command you can see the SADMIN password by querying the database.&lt;br /&gt;&lt;br /&gt;Gud luck :)&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8531650369937741306-5782871058625573970?l=exploringsiebel.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ExploringSiebel/~4/IpAZ57MI6ic" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/ExploringSiebel/~3/IpAZ57MI6ic/how-to-see-sadmin-siebel-password-un.html</link><author>noreply@blogger.com (Tejeshwer)</author><thr:total>0</thr:total><feedburner:origLink>http://exploringsiebel.blogspot.com/2009/10/how-to-see-sadmin-siebel-password-un.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8531650369937741306.post-613344100643622445</guid><pubDate>Tue, 27 Oct 2009 19:05:00 +0000</pubDate><atom:updated>2009-10-28T13:21:07.922-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Siebel EAI</category><title>In-process reentrance is NOT supported for JMS, MSMQ and MQ Series transports</title><description>Process re-entrance refers to calling of same method of the business service again before the first call has not been completed.&lt;br /&gt;&lt;a name='more'&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Some of the code in Siebel is written to work on shared pool of resources, thus if same code is called again the shared pool either release the lock that is made by the first call or the second call creates deadlock between them.&lt;br /&gt;&lt;br /&gt;This behavior is very much prominent when a receiver component executes workflow on receiving xml message from queue, and this workflow process again executes Receive method of the same business service. This doesn't halts the execution but it start listening to queue for which last Receive method was called. &lt;br /&gt;&lt;br /&gt;So if second call passes arguments to receive message from different queue then receiver component will also start listening to this new queue. I was completely unaware of this behavior until one of the JMS receiver component stopped listening to messages from one queue, but started listening on the other. It was also clearly visible in the log of the component.&lt;br /&gt;&lt;br /&gt;Oracle support web &lt;a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;amp;type=NOT&amp;amp;id=845247.1"&gt;article &lt;/a&gt;confirms this behviour.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8531650369937741306-613344100643622445?l=exploringsiebel.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ExploringSiebel/~4/Rrt-5IDkHd0" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/ExploringSiebel/~3/Rrt-5IDkHd0/in-process-reentrance-is-not-supported.html</link><author>noreply@blogger.com (Tejeshwer)</author><thr:total>0</thr:total><feedburner:origLink>http://exploringsiebel.blogspot.com/2009/10/in-process-reentrance-is-not-supported.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8531650369937741306.post-4313753238267625450</guid><pubDate>Mon, 26 Oct 2009 19:03:00 +0000</pubDate><atom:updated>2009-10-28T13:22:11.001-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Siebel Tips</category><category domain="http://www.blogger.com/atom/ns#">Siebel Server Admin</category><title>How to change default location of logs on Siebel Server !</title><description>Location of Siebel Server logs is set while installation of the server. And most of the time Administrator keeps it to the default location i.e.. sea77\siebsrvr\logs directory.  But sometimes the installation location of siebel server is kept on very small and faster disk drives to improve performance, thus there is no or very less space is left on the drive for the extended log levels.&lt;br /&gt;&lt;br /&gt;&lt;a name='more'&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Specially for the EAI log files that can grow as fast as 1 gb per hour or more, it becomes very difficult to manage the log files, and debug the issue. And there is no direct way to changing this log directory path either.&lt;br /&gt;&lt;br /&gt;There is only one hidden parameter &lt;span style="font-weight: bold;"&gt;logdir&lt;/span&gt; for every server is&amp;nbsp;available&amp;nbsp;that can contains the location of log directory, but this parameter not visible on the UI and nor on Advance object lists. The only way to change this parameter is through server manager command prompt.&lt;br /&gt;&lt;br /&gt;Excerpt from support web:&lt;br /&gt;&lt;br /&gt;Problem Description: The Siebel Server Log Directory parameter - LogDir is not visible anywhere.&lt;br /&gt;Resolution:&lt;br /&gt;Currently, the Server Log Dir can be set by using the following srvrmgr command:&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;srvrmgr&amp;gt; change param logdir=&amp;nbsp;&lt;/span&gt;&lt;span style="font-family: Arial; font-size: 13px;"&gt;&lt;span style="font-weight: bold;"&gt;&amp;lt; new path &amp;gt;&amp;nbsp;&lt;/span&gt;&lt;span style="font-family: 'Times New Roman'; font-size: 16px;"&gt;&lt;span style="font-weight: bold;"&gt;for server &amp;lt; server name &amp;gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;However, the parameter "LOGDir" cannot be seen anywhere. After setting the param, the new server logs starts going into a new location, but there is no way to see this parameter in the Admin screen or through the server mgr. This happens despite having "ShowAdvancedObjects" parameter set to TRUE&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8531650369937741306-4313753238267625450?l=exploringsiebel.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ExploringSiebel/~4/qsU1wXsMcK8" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/ExploringSiebel/~3/qsU1wXsMcK8/changing-log-directory-of-siebel-server.html</link><author>noreply@blogger.com (Tejeshwer)</author><thr:total>0</thr:total><feedburner:origLink>http://exploringsiebel.blogspot.com/2009/10/changing-log-directory-of-siebel-server.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8531650369937741306.post-2449224423973210913</guid><pubDate>Thu, 15 Oct 2009 10:40:00 +0000</pubDate><atom:updated>2009-12-31T02:01:23.681-08:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Siebel Tips</category><category domain="http://www.blogger.com/atom/ns#">Siebel eScript</category><title>Date functions in Siebel eScript</title><description>If you have worked on any date field then you would be knowing that some of the standard date functions are not available in Siebel escript, like converting date from one format to another, adding number of business days to a particular date, comparing two dates etc., &lt;br /&gt;&lt;br /&gt;Here are some methods built in eScript that perform these operations.&lt;br /&gt;&lt;br /&gt;&lt;a name='more'&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;1. AddDays &lt;br /&gt;This function serves the purpose of DateAdd function available in other languages. Basically, when we need to add x days to a date, we can use this function.&lt;br /&gt;&lt;br /&gt;&lt;pre class="js" name="code"&gt;function AddDays(myDate,days) &lt;br /&gt;{&lt;br /&gt;/* Adds the number of Days specified in the input parameter ‘days’ &lt;br /&gt; *  to the input parameter mydate and returns the new date&lt;br /&gt; * @param myDate,days&lt;br /&gt; * @return new Date&lt;br /&gt;*&lt;br /&gt; */&lt;br /&gt;&lt;br /&gt;    return new Date(myDate.getTime() + days*24*60*60*1000);&lt;br /&gt;}&lt;br /&gt;&lt;/pre&gt;&lt;br /&gt;2. SubtractDays&lt;br /&gt;&lt;br /&gt;This function helps in finding a backdated date.&lt;br /&gt;&lt;br /&gt;&lt;pre class="js" name="code"&gt;function SubtractDays(myDate,days)&lt;br /&gt;{&lt;br /&gt;/**&lt;br /&gt; * Will subtract ‘days’ number of &lt;br /&gt; * days from the input date and return the new date&lt;br /&gt; * @param myDate,days &lt;br /&gt; * @return date &lt;br /&gt; * @modified &lt;br /&gt; */&lt;br /&gt; return new Date(myDate.getTime() - days*24*60*60*1000);&lt;br /&gt;}&lt;br /&gt;&lt;/pre&gt;&lt;br /&gt;&lt;br /&gt;3. IsFutureDate&lt;br /&gt;This function is used to find if any date is greater than today. &lt;br /&gt;&lt;br /&gt;&lt;pre class="js" name="code"&gt;function IsFutureDate(mydate)&lt;br /&gt;{&lt;br /&gt;/*&lt;br /&gt; *  Function to check if a date is greater than today&lt;br /&gt; *  Returns 0 if Current Date is larger&lt;br /&gt; *  1 if Passed Variable is larger&lt;br /&gt;*/&lt;br /&gt;&lt;br /&gt;var istoday = new Date();   &lt;br /&gt;var myM = ToInteger(mydate.getMonth()+1);&lt;br /&gt;var myD = ToInteger(mydate.getDate());&lt;br /&gt;var myY = ToInteger(mydate.getFullYear());&lt;br /&gt;var toM = ToInteger(istoday.getMonth()+1);&lt;br /&gt;var toD = ToInteger(istoday.getDate());&lt;br /&gt;var toY = ToInteger(istoday.getFullYear()); &lt;br /&gt;if ((myY &amp;lt; toY)||((myY==toY)&amp;amp;&amp;amp;(myM &amp;lt; toM))||((myY==toY)&amp;amp;&amp;amp;(myM==toM)&amp;amp;&amp;amp;(myD &amp;lt; = toD)))&lt;br /&gt; { &lt;br /&gt;  return(0);&lt;br /&gt; }&lt;br /&gt;else &lt;br /&gt;{ &lt;br /&gt;  return(1);&lt;br /&gt;}&lt;br /&gt;}&lt;br /&gt;&lt;br /&gt;&lt;/pre&gt;4. CompareDates  This function is used to compare two dates and to find if one date is greater than or lesser than the other date.  &lt;br /&gt;&lt;pre class="js" name="code"&gt;function CompareDates(dte_from,dte_to)&lt;br /&gt;{&lt;br /&gt;/* Function to compare two dates.. will return 1 if dte_from is greater than dte_to else will return 0 */&lt;br /&gt;&lt;br /&gt;var myM = ToInteger(dte_from.getMonth()+1);&lt;br /&gt;var myD = ToInteger(dte_from.getDate());&lt;br /&gt;var myY = ToInteger(dte_from.getFullYear());&lt;br /&gt;var toM = ToInteger(dte_to.getMonth()+1);&lt;br /&gt;var toD = ToInteger(dte_to.getDate());&lt;br /&gt;var toY = ToInteger(dte_to.getFullYear()); &lt;br /&gt;if ((myY &amp;lt; toY)||((myY==toY)&amp;amp;&amp;amp;(myM &amp;lt; toM))||((myY==toY)&amp;amp;&amp;amp;(myM==toM)&amp;amp;&amp;amp;(myD &amp;lt; = toD)))&lt;br /&gt; { &lt;br /&gt;  return(0);&lt;br /&gt; }&lt;br /&gt;else &lt;br /&gt;{ &lt;br /&gt;  return(1);&lt;br /&gt;}&lt;br /&gt;}&lt;br /&gt;&lt;/pre&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8531650369937741306-2449224423973210913?l=exploringsiebel.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ExploringSiebel/~4/i8AxhlMpf9k" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/ExploringSiebel/~3/i8AxhlMpf9k/date-functions-in-siebel-escript.html</link><author>noreply@blogger.com (Tejeshwer)</author><thr:total>0</thr:total><feedburner:origLink>http://exploringsiebel.blogspot.com/2009/10/date-functions-in-siebel-escript.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8531650369937741306.post-3523109246538722944</guid><pubDate>Wed, 14 Oct 2009 18:38:00 +0000</pubDate><atom:updated>2009-10-28T13:23:07.058-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Siebel Tips</category><category domain="http://www.blogger.com/atom/ns#">Siebel eScript</category><title>Case Insensitive Query in Siebel by using LIKE operator !</title><description>I think most of the readers would know how to perform an case&amp;nbsp;insensitive&amp;nbsp;search/query in Siebel. Those who don't read on!&lt;br /&gt;&lt;br /&gt;Case&amp;nbsp;insensitive query in Siebel means to query the database records using the LIKE operator in SQL. This type of SQL tends to be slow as they return more records than the equal (=) operator.  &lt;br /&gt;&lt;br /&gt;&lt;a name='more'&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Case&amp;nbsp;insensitive&amp;nbsp;query&amp;nbsp;can only be controlled by editing the Application level parameter &lt;span style="font-weight: bold;"&gt;DSCaseInsensitiveFlg &lt;/span&gt;in the Data source named subsystem. For thick clients it can be done setting &lt;span style="font-weight: bold;"&gt;CaseInsensitive &lt;/span&gt;parameter in cfg file.&lt;br /&gt;&lt;br /&gt;But this is rarely&amp;nbsp;activated as it&amp;nbsp;severely&amp;nbsp;hampers the application performance. &lt;br /&gt;&lt;br /&gt;Now what if this parameter is set and we need to execute an&amp;nbsp;insensitive&amp;nbsp;query on BC using script? &lt;br /&gt;&lt;br /&gt;For this we can use tilda operator and LIKE operator in the search expresion of the query ~ LIKE . Like operator along with tilda &lt;span style="font-style: italic;"&gt;forces case&amp;nbsp;insensitive query on the bc field even if the application level&amp;nbsp;sensitivity&amp;nbsp;is turned off!&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;This can also verfied by quering on the UI using this operator:&lt;br /&gt;&lt;br /&gt;&lt;div class="separator" style="clear: both; text-align: center;"&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="separator" style="clear: both; text-align: center;"&gt;&lt;br /&gt;&lt;/div&gt;&lt;a href="http://2.bp.blogspot.com/_mJfGtfR_Zdc/StYYy_ou2dI/AAAAAAAAAFs/6KAk6-uaxPE/s1600-h/1.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" src="http://2.bp.blogspot.com/_mJfGtfR_Zdc/StYYy_ou2dI/AAAAAAAAAFs/6KAk6-uaxPE/s320/1.JPG" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;div class="separator" style="clear: both; text-align: center;"&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="separator" style="clear: both; text-align: center;"&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="separator" style="clear: both; text-align: center;"&gt;&lt;a href="http://2.bp.blogspot.com/_mJfGtfR_Zdc/StYY0MXBnoI/AAAAAAAAAF0/zobx0Dczqgs/s1600-h/2.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" src="http://2.bp.blogspot.com/_mJfGtfR_Zdc/StYY0MXBnoI/AAAAAAAAAF0/zobx0Dczqgs/s320/2.JPG" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8531650369937741306-3523109246538722944?l=exploringsiebel.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ExploringSiebel/~4/T4thSPvVpZQ" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/ExploringSiebel/~3/T4thSPvVpZQ/case-insensitive-query-in-siebel-by.html</link><author>noreply@blogger.com (Tejeshwer)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/_mJfGtfR_Zdc/StYYy_ou2dI/AAAAAAAAAFs/6KAk6-uaxPE/s72-c/1.JPG" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://exploringsiebel.blogspot.com/2009/10/case-insensitive-query-in-siebel-by.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8531650369937741306.post-7571483640583176158</guid><pubDate>Wed, 07 Oct 2009 20:29:00 +0000</pubDate><atom:updated>2009-10-28T13:24:07.560-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Siebel Tips</category><category domain="http://www.blogger.com/atom/ns#">Basics</category><category domain="http://www.blogger.com/atom/ns#">Miscellaneous</category><category domain="http://www.blogger.com/atom/ns#">Siebel EAI</category><title>Get Workflow Instance Id from the process property value!</title><description>Workflow Instance monitor is one of the best out of the box&amp;nbsp;debugging&amp;nbsp;techniques available in&amp;nbsp;Siebel. But this also lacks in some aspects. &lt;br /&gt;&lt;br /&gt;As most of developer would know that there is no way in instance monitor view to identify the workflow instance for&amp;nbsp;specific&amp;nbsp;object id or process property value. &lt;br /&gt;&lt;br /&gt;&lt;a name='more'&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;We usually have to rely on the time and keep switching between the tabs to find the correct instance. And this becomes really cumbersome in production or acceptance environment, or when workflow executes very frequently.&lt;br /&gt;&lt;br /&gt;Same problem we were facing, until we wrote this small sql. This sql queries the instance&amp;nbsp;monitor&amp;nbsp;table that stores all the workflow steps and returns the &lt;span style="font-weight: bold;"&gt;W&lt;/span&gt;&lt;span style="font-weight: bold;"&gt;orkflow Instance Id's&amp;nbsp;&lt;/span&gt;where ever it finds the field value in the input property set.&lt;br /&gt;&lt;br /&gt;&lt;pre class="sql" name="code"&gt;select EXEC_INST_VAL from siebel.S_WFA_INST_LOG &lt;br /&gt;where row_id in( &lt;br /&gt;select distinct INST_LOG_ID from siebel.S_WFA_INSTP_LOG where row_id in(&lt;br /&gt;select step_log_id from siebel.S_WFA_STPRP_LOG where PROP_VAL ='PROPVALUE'))&lt;br /&gt;&lt;/pre&gt;&lt;br /&gt;You can&amp;nbsp;substitute&amp;nbsp;any process property value in place of &lt;span style="font-weight: bold;"&gt;PROPVALUE&lt;/span&gt; in above sql, and it will return all the workflow instance id where the property was found.&lt;br /&gt;&lt;br /&gt;njoy!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8531650369937741306-7571483640583176158?l=exploringsiebel.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ExploringSiebel/~4/F3Si_svwcGQ" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/ExploringSiebel/~3/F3Si_svwcGQ/get-workflow-instance-id-from-process.html</link><author>noreply@blogger.com (Tejeshwer)</author><thr:total>0</thr:total><feedburner:origLink>http://exploringsiebel.blogspot.com/2009/10/get-workflow-instance-id-from-process.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8531650369937741306.post-9021871290261269366</guid><pubDate>Tue, 06 Oct 2009 20:53:00 +0000</pubDate><atom:updated>2009-10-30T12:04:41.957-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Siebel Tips</category><category domain="http://www.blogger.com/atom/ns#">Best Practices</category><category domain="http://www.blogger.com/atom/ns#">Siebel EAI</category><title>Alternate use of List Of Values</title><description>&lt;div&gt;&lt;/div&gt;&lt;div&gt;Most common use of list of values comes in implementation&amp;nbsp;of multilingual siebel applications. But its global&amp;nbsp;presence&amp;nbsp;all over the applications objects makes them extremely useful for writing switches in codes/workflows. I saw one&amp;nbsp;great&amp;nbsp;use in creating the stubs for the real time interfaces in Siebel EAI.&lt;br /&gt;&lt;br /&gt;&lt;a name='more'&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;It usually happens in development phase of the application is that the external interfaces are not ready to test while siebel processes needs some&amp;nbsp;inputs&amp;nbsp;to test rest of the application. In such cases building&amp;nbsp;separate&amp;nbsp;dummy workflow&amp;nbsp;temporarily doesn't look like a&amp;nbsp;good solution.&lt;br /&gt;&lt;br /&gt;Instead of creating&amp;nbsp;separate&amp;nbsp;workflow, we added another branch to the workflow along with the decision step which used to read XML message from the file instead of the interface.&lt;br /&gt;&lt;br /&gt;This&amp;nbsp;decision&amp;nbsp;was taken depending upon the value of the &lt;span style="font-weight: bold;"&gt;STUB_LOV&lt;/span&gt;, if it is set to Y then XML from the file was read otherwise the real interface was called.&lt;br /&gt;&lt;br /&gt;So whenever the interface was down or we need specific data only we just used to set this LOV to get the XML from file.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;There can be lots more uses of LOV like this in Siebel, please feel free to share anything that comes up in your mind.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8531650369937741306-9021871290261269366?l=exploringsiebel.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ExploringSiebel/~4/MwY2Knivw9A" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/ExploringSiebel/~3/MwY2Knivw9A/alternate-use-of-list-of-values.html</link><author>noreply@blogger.com (Tejeshwer)</author><thr:total>0</thr:total><feedburner:origLink>http://exploringsiebel.blogspot.com/2009/10/alternate-use-of-list-of-values.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8531650369937741306.post-9053012758157662510</guid><pubDate>Mon, 07 Sep 2009 18:14:00 +0000</pubDate><atom:updated>2009-10-03T12:09:58.562-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Siebel 8 Presentations</category><category domain="http://www.blogger.com/atom/ns#">Best Practices</category><category domain="http://www.blogger.com/atom/ns#">Basics</category><category domain="http://www.blogger.com/atom/ns#">Downloads</category><category domain="http://www.blogger.com/atom/ns#">Siebel Presentations</category><title>Download Siebel 8.0 Essentials Training Presentation!</title><description>Most of siebel developers don't undergo siebel core consultant training because of the high cost of the course. I have undergone through such classroom training and found that there is nothing special in that training except the training material that they use.&lt;br /&gt;&lt;br /&gt;Their content is well organised to teach siebel from scratch. In my opnion they are much - much better from bookshelf that veterans suggests. Now the good thing is that the same content is available online for download!&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Download Link for Siebel 8.0 training presentation:&lt;/strong&gt;&lt;br /&gt;&lt;a href="http://www.esnips.com/doc/47d61d24-b55e-473e-aa37-7c94ac3841cb/Siebel-8.0-Essentials"&gt;http://www.esnips.com/doc/47d61d24-b55e-473e-aa37-7c94ac3841cb/Siebel-8.0-Essentials&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;It is worth reading even if you have gone through the 7.8 core consultant training, in siebel 8.0 they have added plenty of things like Workflow Policies and new stuffs like Task base UI and Audit trail.&lt;br /&gt;&lt;br /&gt;There are plenty of more content is available in &lt;a href="http://www.esnips.com/"&gt;esnips &lt;/a&gt;- a public content sharing website. I think it favorite among the siebel developers.Check it out!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8531650369937741306-9053012758157662510?l=exploringsiebel.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ExploringSiebel/~4/CCES9pOKy2o" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/ExploringSiebel/~3/CCES9pOKy2o/download-siebel-80-essentials-training.html</link><author>noreply@blogger.com (Tejeshwer)</author><thr:total>0</thr:total><feedburner:origLink>http://exploringsiebel.blogspot.com/2009/09/download-siebel-80-essentials-training.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8531650369937741306.post-6694647594279821800</guid><pubDate>Sat, 05 Sep 2009 19:01:00 +0000</pubDate><atom:updated>2009-10-28T13:26:08.210-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Siebel eScript</category><title>How to generate random number in Siebel eScript?</title><description>Recently I had a requirement to generate &lt;strong&gt;non-repetitive random numbers &lt;/strong&gt;in siebel escript. I searched the siebel tools help and found Clib.rand() function to the rescue. And using it was also very simple.&lt;br /&gt;&lt;a name='more'&gt;&lt;/a&gt;&lt;br /&gt;&lt;pre class="js" name="code"&gt;var temp = Clib.rand();&lt;br /&gt;TheApplication().RaiseErrorText(temp);&lt;/pre&gt;&lt;br /&gt;&lt;br /&gt;But this function do not guarantee the non-repetitive output. Instead of building any complex algorithm, to get non-repetitive random number i used &lt;strong&gt;Date object &lt;/strong&gt;and &lt;strong&gt;getTime &lt;/strong&gt;method. As time is allways incrementing and it never looks back :) i used this as my random number.&lt;br /&gt;&lt;br /&gt;This method returns the date-time, in milliseconds, of the Date object.&lt;br /&gt;&lt;br /&gt;&lt;pre class="js" name="code"&gt;var aDate = new Date().getTime();&lt;br /&gt;TheApplication().RaiseErrorText(aDate);&lt;br /&gt;&lt;/pre&gt;&lt;br /&gt;Try it out it never fails.&lt;br /&gt;One point to note here is that if requirement is to get series of random number in loop, then you have to add some delay of about a millisec so that system time is updated. njoy!!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8531650369937741306-6694647594279821800?l=exploringsiebel.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ExploringSiebel/~4/TEcLcgUjAPU" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/ExploringSiebel/~3/TEcLcgUjAPU/how-to-generate-random-number-in-siebel.html</link><author>noreply@blogger.com (Tejeshwer)</author><thr:total>0</thr:total><feedburner:origLink>http://exploringsiebel.blogspot.com/2009/09/how-to-generate-random-number-in-siebel.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8531650369937741306.post-8632926447273260875</guid><pubDate>Sat, 22 Aug 2009 15:33:00 +0000</pubDate><atom:updated>2009-08-31T10:25:58.792-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Siebel eScript</category><category domain="http://www.blogger.com/atom/ns#">Siebel Configuration</category><title>Accessing Field in Siebel Browser Script</title><description>Accessing a field in browser script can a bit pain, for someone who is new to the browser scripting. There is no direct way to access the field in browser scripts that are not shown on the applet at run time.&lt;br /&gt;&lt;br /&gt;This is because the browser script works on the DOM elements not the Siebel Objects. Siebel to support its syntax, publishes some of the objects and methods in the browser script.&lt;br /&gt;&lt;br /&gt;There is a workaround to access field in the browser script:&lt;br /&gt;&lt;strong&gt;1. Add a control in the applet with the required field.&lt;/strong&gt;&lt;br /&gt;&lt;strong&gt;2. Set the HTML Type of control to Hidden.&lt;/strong&gt;&lt;br /&gt;&lt;strong&gt;3. Add this control on the list applet as column or on the header (where buttons are placed) of the form applet.&lt;/strong&gt;&lt;br /&gt;&lt;strong&gt;4. Create usual script to GetFieldValue. Now you will be able to get the value inside the script.&lt;/strong&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;There are also lots of restriction in the browser script as compared to Server Script, some of them being:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;TheApplication() in eScript is converted to theApplication() in JavaScript.&lt;/strong&gt;&lt;/li&gt;&lt;li&gt;&lt;strong&gt;We can not use theApplication().GetBusObject(), can only use theApplication().ActiveBusObject();&lt;/strong&gt;&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Cannot Get and Set Field values that are not shown on the UI.&lt;/strong&gt;&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Cannot use InvokeMethod("LookupValue") (this creates lots of troubles in developing multilingual prompts.)&lt;/strong&gt;&lt;/li&gt;&lt;/ul&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8531650369937741306-8632926447273260875?l=exploringsiebel.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ExploringSiebel/~4/uqlzWH0DX24" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/ExploringSiebel/~3/uqlzWH0DX24/accessing-field-in-siebel-browser.html</link><author>noreply@blogger.com (Tejeshwer)</author><thr:total>0</thr:total><feedburner:origLink>http://exploringsiebel.blogspot.com/2009/08/accessing-field-in-siebel-browser.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8531650369937741306.post-1516502574857486982</guid><pubDate>Sat, 22 Aug 2009 07:46:00 +0000</pubDate><atom:updated>2009-08-22T13:16:17.828-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Basics</category><category domain="http://www.blogger.com/atom/ns#">Siebel EAI</category><title>Siebel Message Property Set</title><description>The Next buzz word that we hear in Siebel EAI is Siebel Message or IO Hierarchy. It appears to be very similar to XML hierarchy, but it is not!&lt;br /&gt;&lt;br /&gt;&lt;div&gt;&lt;/div&gt;&lt;br /&gt;&lt;div&gt;Siebel Message or IO Hierarchy is an instance of an Integration Object in form of property set. It is mostly used in EAI workflows, but it can also be very useful in scripting and business processes.&lt;/div&gt;&lt;br /&gt;&lt;div&gt;&lt;span class="Apple-style-span" style="FONT-WEIGHT: bold"&gt;&lt;/span&gt;&lt;/div&gt;&lt;br /&gt;&lt;div&gt;&lt;span class="Apple-style-span" style="FONT-WEIGHT: bold"&gt;What is Integration Object? : &lt;/span&gt;It is an structure that defines the Siebel Data that is needed to be integrated with Other applications. &lt;/div&gt;&lt;br /&gt;&lt;div&gt;An IO defines Business Object whose data will be integrated, BC whose fields will be updated, and the fields that will be used.&lt;/div&gt;&lt;br /&gt;&lt;div&gt;&lt;span class="Apple-style-span" style="FONT-WEIGHT: bold"&gt;&lt;/span&gt;&lt;/div&gt;&lt;br /&gt;&lt;div&gt;&lt;span class="Apple-style-span" style="FONT-WEIGHT: bold"&gt;What is Integration Object Instance? : &lt;/span&gt;&lt;/div&gt;&lt;div&gt;When an Integration Object is used to query siebel database it results in an property set that contains the data in the structure represented in the Integration Object.&lt;/div&gt;&lt;div&gt;This output property set is called &lt;span class="Apple-style-span" style="FONT-WEIGHT: bold"&gt;Siebel Message.&lt;/span&gt;&lt;span class="Apple-style-span" style="FONT-WEIGHT: bold"&gt;&lt;br /&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="FONT-WEIGHT: bold"&gt;&lt;/span&gt;&lt;/div&gt;&lt;br /&gt;&lt;div&gt;&lt;span class="Apple-style-span" style="FONT-WEIGHT: bold"&gt;How Siebel Message is different from a Property Set?&lt;/span&gt;&lt;/div&gt;&lt;div&gt;Siebel Message is actually a property set whose type is set to "&lt;strong&gt;SiebelMessage&lt;/strong&gt;".Most common method to create a Siebel Message is by calling &lt;strong&gt;Query &lt;/strong&gt;Method of &lt;strong&gt;EAI Siebel Adapter Service&lt;/strong&gt;.&lt;/div&gt;&lt;div&gt;This service creates the properties with Name specified in the Integration Components Fields. &lt;/div&gt;&lt;br /&gt;&lt;p&gt;On the other hand &lt;strong&gt;XML Hierarchy &lt;/strong&gt;contains property name from the Integration Component XML Tag.&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8531650369937741306-1516502574857486982?l=exploringsiebel.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ExploringSiebel/~4/iSX048CLcDc" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/ExploringSiebel/~3/iSX048CLcDc/siebel-message-property-set.html</link><author>noreply@blogger.com (Tejeshwer)</author><thr:total>0</thr:total><feedburner:origLink>http://exploringsiebel.blogspot.com/2009/08/siebel-message-property-set.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8531650369937741306.post-2713601507055791160</guid><pubDate>Fri, 21 Aug 2009 16:14:00 +0000</pubDate><atom:updated>2009-08-21T10:36:51.290-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Basics</category><category domain="http://www.blogger.com/atom/ns#">Siebel EAI</category><title>Mapping between Siebel Property Set and XML</title><description>I think first problem that we face in EAI is understanding the mapping between the &lt;strong&gt;Siebel Property Set&lt;/strong&gt; and the &lt;strong&gt;XML&lt;/strong&gt;. But once this mapping is clear Siebel EAI becomes lot more easier module to work on.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;XML as we all know is the structured data trasfer language, and property set is set of variables contain values in form of string name value pairs. There are lots of vanilla services available in siebel tools that converts the property set in to an XML or write the property set to a file.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Let see how the property set is converted into an XML.&lt;br /&gt;&lt;div align="justify"&gt;A Property set contains four parts which we can get and set by eScript methods. &lt;/div&gt;&lt;div align="justify"&gt;&lt;br /&gt;&lt;/div&gt;&lt;a href="http://4.bp.blogspot.com/_mJfGtfR_Zdc/So7WqfkCIjI/AAAAAAAAAD0/5vC2H7-1kA0/s400/1.JPG"&gt;&lt;img id="BLOGGER_PHOTO_ID_5372467431015064114" style="DISPLAY: block; MARGIN: 0px auto 10px; WIDTH: 400px; CURSOR: hand; HEIGHT: 96px; TEXT-ALIGN: center" alt="" src="http://4.bp.blogspot.com/_mJfGtfR_Zdc/So7WqfkCIjI/AAAAAAAAAD0/5vC2H7-1kA0/s400/1.JPG" border="0" /&gt;&lt;/a&gt; &lt;div align="justify"&gt;Note : A property set can contain child elements , which can themselves be a Property Set, and can have Type , Property and a Value.&lt;br /&gt;&lt;/div&gt;&lt;br /&gt;Similarly an XML contains:&lt;br /&gt;&lt;br /&gt;&lt;img id="BLOGGER_PHOTO_ID_5372455141523227106" style="DISPLAY: block; MARGIN: 0px auto 10px; WIDTH: 400px; CURSOR: hand; HEIGHT: 110px; TEXT-ALIGN: center" alt="" src="http://3.bp.blogspot.com/_mJfGtfR_Zdc/So7LfJo2geI/AAAAAAAAADs/MPDVeIhBtq8/s400/xml.JPG" border="0" /&gt;&lt;br /&gt;&lt;br /&gt;Siebel converts&lt;br /&gt;&lt;strong&gt;Type&lt;/strong&gt; of property set to XML &lt;strong&gt;Element&lt;/strong&gt; ,&lt;br /&gt;&lt;strong&gt;Properties&lt;/strong&gt; are added as &lt;strong&gt;Attrbutes, &lt;/strong&gt;&lt;br /&gt;&lt;strong&gt;Value &lt;/strong&gt;is kept as &lt;strong&gt;Value of the Element &lt;/strong&gt;&lt;br /&gt;and child properties are added as child elements in XML.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;This can be demonstrated by following code:&lt;br /&gt;&lt;br /&gt;&lt;a href="http://2.bp.blogspot.com/_mJfGtfR_Zdc/So7W2TtkP8I/AAAAAAAAAD8/hGkoImg26G0/s1600-h/coed.JPG"&gt;&lt;img id="BLOGGER_PHOTO_ID_5372467633992253378" style="DISPLAY: block; MARGIN: 0px auto 10px; WIDTH: 400px; CURSOR: hand; HEIGHT: 218px; TEXT-ALIGN: center" alt="" src="http://2.bp.blogspot.com/_mJfGtfR_Zdc/So7W2TtkP8I/AAAAAAAAAD8/hGkoImg26G0/s400/coed.JPG" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;It will produce an XML output like this:&lt;br /&gt;&lt;br /&gt;&lt;div&gt;&lt;/div&gt;&lt;br /&gt;&lt;a href="http://3.bp.blogspot.com/_mJfGtfR_Zdc/So7XGtvUblI/AAAAAAAAAEM/8prOJBu53YA/s1600-h/untitled.JPG"&gt;&lt;br /&gt;&lt;img id="BLOGGER_PHOTO_ID_5372467915856834130" style="DISPLAY: block; MARGIN: 0px auto 10px; WIDTH: 400px; CURSOR: hand; HEIGHT: 79px; TEXT-ALIGN: center" alt="" src="http://3.bp.blogspot.com/_mJfGtfR_Zdc/So7XGtvUblI/AAAAAAAAAEM/8prOJBu53YA/s400/untitled.JPG" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;div&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8531650369937741306-2713601507055791160?l=exploringsiebel.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ExploringSiebel/~4/5aMn4d3fm6I" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/ExploringSiebel/~3/5aMn4d3fm6I/mapping-between-siebel-property-set-and.html</link><author>noreply@blogger.com (Tejeshwer)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/_mJfGtfR_Zdc/So7WqfkCIjI/AAAAAAAAAD0/5vC2H7-1kA0/s72-c/1.JPG" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://exploringsiebel.blogspot.com/2009/08/mapping-between-siebel-property-set-and.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8531650369937741306.post-3916744308580270734</guid><pubDate>Sat, 15 Aug 2009 07:34:00 +0000</pubDate><atom:updated>2009-08-15T05:31:35.435-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Siebel Errors</category><category domain="http://www.blogger.com/atom/ns#">Siebel EAI</category><title>Workflow Revision Failed : SBL-DAT-00393: An end of file error has occurred.</title><description>Recently I faced a strange bug in my Siebel Tools. Whenever i tried to revise an workflow, i was getting this error :&lt;br /&gt;&lt;br /&gt;&lt;a href="http://1.bp.blogspot.com/_mJfGtfR_Zdc/SoZmTMFMC3I/AAAAAAAAADk/khksT4eDTqc/s1600-h/1.JPG"&gt;&lt;img id="BLOGGER_PHOTO_ID_5370092085532429170" style="DISPLAY: block; MARGIN: 0px auto 10px; WIDTH: 400px; CURSOR: hand; HEIGHT: 217px; TEXT-ALIGN: center" alt="" src="http://1.bp.blogspot.com/_mJfGtfR_Zdc/SoZmTMFMC3I/AAAAAAAAADk/khksT4eDTqc/s400/1.JPG" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;div&gt;&lt;strong&gt;An end of file error has occurred. Please continue or ask your system administrator to check your application configuration if the problem persists. (SBL-DAT-00393).&lt;/strong&gt;&lt;/div&gt;&lt;div&gt;&lt;strong&gt;&lt;/strong&gt;&lt;/div&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;div&gt;And after i press Ok button, tools hangs and every time i have to restart the tools. &lt;p&gt;&lt;/p&gt;&lt;p&gt;&lt;/p&gt; Even when i tried to connect directly to the database server the error was re-occurring. And this was happening with a specific workflow only. I was very much bugged up at that time.&lt;/div&gt;&lt;br /&gt;&lt;div&gt;I searched support web but still couldn't find any reason behind this in Siebel Tools. &lt;p&gt;&lt;/p&gt;&lt;/div&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;div&gt;Then one of colleague suggested me to delete excess versions of workflows in tools to get it done. &lt;/div&gt;&lt;div&gt;At first i thought it wouldn't help, but yes it worked!! &lt;/div&gt;&lt;div&gt;&lt;/div&gt;&lt;div&gt;&lt;/div&gt;&lt;div&gt;&lt;/div&gt;&lt;div&gt;&lt;/div&gt;&lt;div&gt;&lt;/div&gt;&lt;div&gt;&lt;/div&gt;&lt;div&gt;&lt;/div&gt;&lt;div&gt;&lt;/div&gt;&lt;div&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;I must say, Siebel has got mind of his own! Thanks to &lt;strong&gt;Manuj&lt;/strong&gt;, who helped me to get this thing done. &lt;/div&gt;&lt;div&gt;&lt;/div&gt;&lt;div&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8531650369937741306-3916744308580270734?l=exploringsiebel.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ExploringSiebel/~4/UBkTPWiidvA" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/ExploringSiebel/~3/UBkTPWiidvA/workflow-revision-failed-sbl-dat-00393.html</link><author>noreply@blogger.com (Tejeshwer)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/_mJfGtfR_Zdc/SoZmTMFMC3I/AAAAAAAAADk/khksT4eDTqc/s72-c/1.JPG" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://exploringsiebel.blogspot.com/2009/08/workflow-revision-failed-sbl-dat-00393.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8531650369937741306.post-5033136998603203708</guid><pubDate>Fri, 14 Aug 2009 08:36:00 +0000</pubDate><atom:updated>2009-08-14T03:24:29.906-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Best Practices</category><category domain="http://www.blogger.com/atom/ns#">Screencasts/Videos</category><title>Extending Column in Siebel : Video Tutorial</title><description>I haven't came across any siebel implementation till yet, that doesn't requires extension of siebel base tables. &lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;This usually required when siebel table doesn't have any column that can support the required data type or when there is additional data required at the business layer.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Although it can be achieved by using the extension table, but it is recommended that fields that are shown on UI or used frequently in the script should exists in the base column. &lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;This is because that extension column requires an additional join in the sql query. And every time BC based on the base table will be queried, extension table will also be called into the memory. &lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;div&gt;&lt;div&gt;Here is one video from you tube that explain the whole process of extending column as a screen cast.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div style="text-align: center;"&gt;&lt;object width="425" height="344"&gt;&lt;param name="movie" value="http://www.youtube.com/v/l-h3_ySGCPc&amp;amp;hl=en&amp;amp;fs=1&amp;amp;"&gt;&lt;param name="allowFullScreen" value="true"&gt;&lt;param name="allowscriptaccess" value="always"&gt;&lt;embed src="http://www.youtube.com/v/l-h3_ySGCPc&amp;amp;hl=en&amp;amp;fs=1&amp;amp;" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="425" height="344"&gt;&lt;/embed&gt;&lt;/object&gt;&lt;/div&gt;&lt;br /&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8531650369937741306-5033136998603203708?l=exploringsiebel.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ExploringSiebel/~4/cYMbn_Gou48" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/ExploringSiebel/~3/cYMbn_Gou48/extending-column-in-siebel-video.html</link><author>noreply@blogger.com (Tejeshwer)</author><thr:total>0</thr:total><feedburner:origLink>http://exploringsiebel.blogspot.com/2009/08/extending-column-in-siebel-video.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8531650369937741306.post-4963329155271753938</guid><pubDate>Tue, 11 Aug 2009 18:08:00 +0000</pubDate><atom:updated>2009-08-14T03:40:45.130-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Where is IT going?</category><category domain="http://www.blogger.com/atom/ns#">Siebel Presentations</category><category domain="http://www.blogger.com/atom/ns#">Tom Siebel</category><title>Tom Siebel at Stanford University: Glory Days Long Gone for I.T.?</title><description>Here are some videos of &lt;strong&gt;Entrepreneurial Thought Leader Lecture at &lt;/strong&gt;Standford University by &lt;strong&gt;Tom Siebel &lt;/strong&gt;who started siebel systems and sold it to oracle.&lt;br /&gt;&lt;br /&gt;Have a look what he has to say to new entrepreneurs @ stanford. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;embed id="single" src="http://ecorner.stanford.edu/swf/player-ec.swf" width="500" height="302" type="application/x-shockwave-flash" flashvars="config=http://ecorner.stanford.edu/embeded_config.xml%3Fmid%3D2178"&gt;&lt;/embed&gt;&lt;br /&gt;&lt;strong&gt;Description&lt;/strong&gt;&lt;br /&gt;Tom Siebel, Chairman of First Virtual Group, paints a picture of the dramatic explosion of the dot-com boom; an era, he recalls, where "risk was a business problem, and not an anathema." With a 17 percent growth rate - an increase unprecedented before or since, says Siebel - the business opportunities of the 1980's era appeared to be unlimited. Changes in technology were total replacements, rather than incremental, meaning that every client had to buy and keep buying or find themselves lagging into obsolescence. He credits this free market flow with conjuring a revolution in computing and communications.&lt;br /&gt;&lt;br /&gt;&lt;embed id="single" src="http://ecorner.stanford.edu/swf/player-ec.swf" width="500" height="302" type="application/x-shockwave-flash" flashvars="config=http://ecorner.stanford.edu/embeded_config.xml%3Fmid%3D2179"&gt;&lt;/embed&gt;&lt;br /&gt;Description&lt;br /&gt;Most of the promise of post-industrial society has been realized, says Tom Siebel, Chairman of First Virtual Group, and all of the great technological advances and development of great companies are behind us. The tech sector is hovering around a mere three percent annual growth rate, says Siebel; keeping it just on par with the rate of current economic growth.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;embed id="single" src="http://ecorner.stanford.edu/swf/player-ec.swf" width="500" height="302" type="application/x-shockwave-flash" flashvars="config=http://ecorner.stanford.edu/embeded_config.xml%3Fmid%3D2180"&gt;&lt;/embed&gt;&lt;br /&gt;&lt;strong&gt;Description &lt;/strong&gt;&lt;br /&gt;The globe's human population is currently around six-and-a-half billion, and it is slated to reach nine billion people in the next twenty years. Tom Siebel, Chairman of First Virtual Group, points out that this sharp increase will propel a worldwide demand for food, water, energy, and healthcare. And, he adds, the business opportunities in providing these essentials are unparalleled.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;embed id="single" src="http://ecorner.stanford.edu/swf/player-ec.swf" width="500" height="302" type="application/x-shockwave-flash" flashvars="config=http://ecorner.stanford.edu/embeded_config.xml%3Fmid%3D2181"&gt;&lt;/embed&gt;&lt;br /&gt;Description&lt;br /&gt;Facing the likelihood of carbon reporting and carbon tracking that will be necessary with upcoming cap and trade legislation, Tom Siebel, First Virtual Group Chairman, announces a new initiative to help reduce the cost of reporting on an enterprise's carbon footprint - a tool that he foresees will serve a $3 trillion market in 2020.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;embed id="single" src="http://ecorner.stanford.edu/swf/player-ec.swf" width="500" height="302" type="application/x-shockwave-flash" flashvars="config=http://ecorner.stanford.edu/embeded_config.xml%3Fmid%3D2182"&gt;&lt;/embed&gt;&lt;br /&gt;&lt;strong&gt;Description &lt;/strong&gt;&lt;br /&gt;Forward-thinking entrepreneurs should consider government restrictions in their long-term business planning, says First Virtual Group's Chairman Tom Siebel. They should also be aware of the opportunities that exist through population growth and a growing demographic of the aged. And they should be thinking about solving the energy problem, and the provision of clean food and water for the planet.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8531650369937741306-4963329155271753938?l=exploringsiebel.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ExploringSiebel/~4/VHDszcDaP3g" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/ExploringSiebel/~3/VHDszcDaP3g/tom-siebel-at-stanford-university-glory.html</link><author>noreply@blogger.com (Tejeshwer)</author><thr:total>0</thr:total><feedburner:origLink>http://exploringsiebel.blogspot.com/2009/08/tom-siebel-at-stanford-university-glory.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8531650369937741306.post-512685806699640229</guid><pubDate>Sat, 08 Aug 2009 17:16:00 +0000</pubDate><atom:updated>2009-08-14T03:43:08.424-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Siebel Configuration</category><category domain="http://www.blogger.com/atom/ns#">Best Practices</category><title>Adding Button on Applet – Part 2</title><description>&lt;div&gt;In&lt;a href="http://exploringsiebel.blogspot.com/2009/08/siebel-adding-button-on-applet-part-1.html"&gt; part one&lt;/a&gt; of this post I have discussed how we can enable a button on applet and call workflow or service from it using scripting.&lt;/div&gt;&lt;div&gt;But Siebel user properties provides us the way to achieve the same behaviour without scripting. There are two or more solutions to it.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;span class="Apple-style-span" style="font-weight: bold;"&gt;Solution 1 &lt;/span&gt;: Using &lt;span class="Apple-style-span" style="font-weight: bold;"&gt;CanInvokeMethod &lt;/span&gt;User Property&lt;/div&gt;&lt;div&gt;1.&lt;span class="Apple-tab-span" style="white-space:pre"&gt; &lt;/span&gt;Create control on applet with method invoke property set to required method name.&lt;/div&gt;&lt;div&gt;2.&lt;span class="Apple-tab-span" style="white-space:pre"&gt; &lt;/span&gt;Create an applet user property “&lt;span class="Apple-style-span" style="font-weight: bold;"&gt;CanInvokeMethod&lt;/span&gt;”&lt;span class="Apple-style-span" style="font-weight: bold;"&gt; &lt;/span&gt;to activate this button conditionally.&lt;/div&gt;&lt;div&gt;3.&lt;span class="Apple-tab-span" style="white-space:pre"&gt; &lt;/span&gt;Add an “&lt;span class="Apple-style-span" style="font-weight: bold;"&gt;NamedMethod&lt;/span&gt;” User Property on BusComp or Applet to invoke Business Service or Workflow of your choice.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;span class="Apple-style-span" style="font-weight: bold;"&gt;Solution 2&lt;/span&gt; : Using &lt;span class="Apple-style-span" style="font-weight: bold;"&gt;EventMethodMethodName&lt;/span&gt; User Property&lt;/div&gt;&lt;div&gt;1.&lt;span class="Apple-tab-span" style="white-space:pre"&gt; &lt;/span&gt;Create Control applet with method invoke property as : &lt;span class="Apple-style-span" style="font-weight: bold;"&gt;EventMethodMethodName&lt;/span&gt;. Where Method Name is your orignal method.&lt;/div&gt;&lt;div&gt;2.&lt;span class="Apple-tab-span" style="white-space:pre"&gt; &lt;/span&gt;Add “&lt;span class="Apple-style-span" style="font-weight: bold;"&gt;EventMethod Enabled&lt;/span&gt;” user property on Buscomp to conditionally activate the button.&lt;/div&gt;&lt;div&gt;3.&lt;span class="Apple-tab-span" style="white-space:pre"&gt; &lt;/span&gt;Create a runtime event on PreInvoke of the Buscomp to invoke service or workflow.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Both of these solutions are suitable for our basic requirement of adding buttons on Siebel Applets. &lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Please note that these user properties works on &lt;span class="Apple-style-span" style="font-weight: bold;"&gt;CSSBCBase &lt;/span&gt;BusComp class and&lt;span class="Apple-style-span" style="font-weight: bold;"&gt; CSSFrameListBase &lt;/span&gt;applet class&lt;span class="Apple-style-span" style="font-weight: bold;"&gt;. &lt;/span&gt;These are not defualt classes when you create new objects.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8531650369937741306-512685806699640229?l=exploringsiebel.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ExploringSiebel/~4/-DLrI4_IP0w" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/ExploringSiebel/~3/-DLrI4_IP0w/adding-button-on-applet-part-2.html</link><author>noreply@blogger.com (Tejeshwer)</author><thr:total>0</thr:total><feedburner:origLink>http://exploringsiebel.blogspot.com/2009/08/adding-button-on-applet-part-2.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8531650369937741306.post-4666348440430873080</guid><pubDate>Mon, 03 Aug 2009 19:18:00 +0000</pubDate><atom:updated>2010-08-27T11:05:23.108-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Product Configurator</category><title>How to restrict length of an attribute - Part 2</title><description>In Continuation of my earlier &lt;a href="http://exploringsiebel.blogspot.com/2009/08/siebel-product-configurator-how-to.html"&gt;post&lt;/a&gt;, for constraining the length of attribute, in this post i am explaining what other solution is available in out of the box Siebel application for this problem. &lt;br /&gt;&lt;span class="Apple-style-span" style="font-weight: bold;"&gt;Attribute selected&lt;/span&gt; is an event which gets triggered before any attribute's value is updated, this events sends the information of the attribute and the value as property set argument.&lt;br /&gt;&lt;div&gt;XML representation of property set would look something like :&lt;/div&gt;&lt;a href="http://2.bp.blogspot.com/_mJfGtfR_Zdc/Snc7nvqSLgI/AAAAAAAAADc/h7JcvRyQUQ0/s1600-h/1.JPG" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"&gt;&lt;img alt="" border="0" id="BLOGGER_PHOTO_ID_5365823035029990914" src="http://2.bp.blogspot.com/_mJfGtfR_Zdc/Snc7nvqSLgI/AAAAAAAAADc/h7JcvRyQUQ0/s400/1.JPG" style="cursor: hand; display: block; height: 120px; margin: 0px auto 10px; text-align: center; width: 364px;" /&gt;&lt;/a&gt;&lt;span class="Apple-style-span" style="font-style: italic;"&gt;*from bookshelf&lt;/span&gt; &lt;span class="Apple-style-span" style="font-style: italic;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;br /&gt;Now if this property set is available as argument then i think writing script to constrain its value is not a big task. &lt;br /&gt;&lt;br /&gt;I have created this snippet, it worked in my case hope it works for others also.&lt;br /&gt;&lt;br /&gt;&lt;pre class="js" name="code"&gt;&lt;br /&gt;function Cfg_AttributeSelected (SelectedAttribute)&lt;br /&gt;{&lt;br /&gt; var temp = SelectedAttribute.GetChild(0);&lt;br /&gt; var sStr =  temp.GetProperty("NewVal");&lt;br /&gt; TheApplication().RaiseErrorText("Error");&lt;br /&gt;}&lt;br /&gt;&lt;br /&gt;&lt;/pre&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8531650369937741306-4666348440430873080?l=exploringsiebel.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ExploringSiebel/~4/GY2tEOksFcM" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/ExploringSiebel/~3/GY2tEOksFcM/how-to-restrict-length-of-attribute.html</link><author>noreply@blogger.com (Tejeshwer)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/_mJfGtfR_Zdc/Snc7nvqSLgI/AAAAAAAAADc/h7JcvRyQUQ0/s72-c/1.JPG" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://exploringsiebel.blogspot.com/2009/08/how-to-restrict-length-of-attribute.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-8531650369937741306.post-1982311046385889208</guid><pubDate>Mon, 03 Aug 2009 18:33:00 +0000</pubDate><atom:updated>2010-06-12T09:26:42.950-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Product Configurator</category><category domain="http://www.blogger.com/atom/ns#">Miscellaneous</category><title>Siebel Product Configurator: How to restrict attribute length?</title><description>&lt;div&gt;&lt;span style="font-weight: bold;"&gt;Requirement&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;div&gt;&lt;div&gt;&lt;div&gt;We have one requirement in our project, that we need to restrict the value of one attribute to five characters only.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;In Siebel vanilla application we tried to implement this without doing scripting, but failed.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;span class="Apple-style-span" style="font-weight: bold;"&gt;Solution we used:&lt;/span&gt;&lt;/div&gt;&lt;div&gt;This requirement can be achieved in two ways:&lt;/div&gt;&lt;div&gt;&lt;span style="font-weight: bold;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span style="font-weight: bold;"&gt;1. By Scripting in Attribute Selected event. &lt;a href="http://exploringsiebel.blogspot.com/2009/08/how-to-restrict-length-of-attribute.html"&gt;update&lt;/a&gt; or&amp;nbsp;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span style="font-weight: bold;"&gt;2. Creating Custom User Properties for product configurator.&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;I will be discussing the second solution in this post. It will involve editing of cfgui.js . For more info my older&lt;a href="http://exploringsiebel.blogspot.com/search/label/Product%20Configurator"&gt;&amp;nbsp;posts&amp;nbsp;&lt;/a&gt;&lt;/div&gt;&lt;div&gt;&lt;span style="font-weight: bold;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;1. Find the following code in cfgui file.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;/div&gt;&lt;a href="http://1.bp.blogspot.com/_mJfGtfR_Zdc/Sncvxp5xB7I/AAAAAAAAADE/ngvIjTuW6k8/s1600-h/1.JPG" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"&gt;&lt;img alt="" border="0" id="BLOGGER_PHOTO_ID_5365810011143473074" src="http://1.bp.blogspot.com/_mJfGtfR_Zdc/Sncvxp5xB7I/AAAAAAAAADE/ngvIjTuW6k8/s400/1.JPG" style="cursor: pointer; display: block; height: 132px; margin-bottom: 10px; margin-left: auto; margin-right: auto; margin-top: 0px; text-align: center; width: 400px;" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;div&gt;try to find text: function showtextbox.&lt;/div&gt;&lt;div&gt;&lt;b&gt;Updated Section:&lt;/b&gt;&lt;/div&gt;&lt;div&gt;2. Replace the code with :&lt;/div&gt;&lt;/div&gt;&lt;div&gt;&lt;div class="separator" style="clear: both; text-align: center;"&gt;&lt;a href="http://4.bp.blogspot.com/_mJfGtfR_Zdc/TBO0pYYNd9I/AAAAAAAAAGY/Y689-jUtkQ8/s1600/code.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" src="http://4.bp.blogspot.com/_mJfGtfR_Zdc/TBO0pYYNd9I/AAAAAAAAAGY/Y689-jUtkQ8/s320/code.JPG" /&gt;&lt;/a&gt;&lt;/div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;3. Create user property on the root product like:&lt;br /&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;/div&gt;&lt;a href="http://4.bp.blogspot.com/_mJfGtfR_Zdc/SncxFO9eYOI/AAAAAAAAADU/s-LgZmp1c-U/s1600-h/1.JPG" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"&gt;&lt;img alt="" border="0" id="BLOGGER_PHOTO_ID_5365811447020282082" src="http://4.bp.blogspot.com/_mJfGtfR_Zdc/SncxFO9eYOI/AAAAAAAAADU/s-LgZmp1c-U/s400/1.JPG" style="cursor: hand; cursor: pointer; display: block; height: 158px; margin: 0px auto 10px; text-align: center; width: 400px;" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;div&gt;and you are done!&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Now clear cache of browser and restart the client.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Attribute on which you have defined the property will automatically be constrained by the number of characters that you have provided in property.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;div&gt;&lt;span style="font-weight: bold;"&gt;Hope its is understandable.&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;For more info how it worked, look at the maxlength property&lt;a href="http://www.w3schools.com/htmldom/prop_text_maxlength.asp"&gt; here.&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8531650369937741306-1982311046385889208?l=exploringsiebel.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/ExploringSiebel/~4/_MtPbchrVpo" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/ExploringSiebel/~3/_MtPbchrVpo/siebel-product-configurator-how-to.html</link><author>noreply@blogger.com (Tejeshwer)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/_mJfGtfR_Zdc/Sncvxp5xB7I/AAAAAAAAADE/ngvIjTuW6k8/s72-c/1.JPG" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://exploringsiebel.blogspot.com/2009/08/siebel-product-configurator-how-to.html</feedburner:origLink></item></channel></rss>

