SiebelGuide.com/siebelblogs

Siebel Blogs, News, Events, Tips and Tricks
Filed under Tips&Tricks, eScript, All

Scripting often gets complicated with heavily customized applications. Not every business requirement can be met with just configuration. So developers resort to scripting. But if not properly implemented, this could cause a lot of mess. Below are some more Siebel recommended best practices.

Tip3:
Use SetSearchSpec only on Indexed column. Before we do ExecuteQuery in the script, we use SetSearchSpec to retrieve only relevant records. SetSearchSpec also limits the number of records retrieved which makes the ExecuteQuery faster. But on what type of column we do SetSearchSpec on is also very important. We should always do a SetSearchSpec on indexed column so that the records are retrieved very fast. This saves a lot of burden and time on both application and database servers. Look at the code below.

Tip4:
When we use ExecuteQuery, we need not do execute query again on child BC. ExecuteQuery on parent BC also forces a query on all active child BC defined using Links. For example in the screenshot below, consider Account Object. There is Link defined between Account and Action BC. So if a query is executed on Account BC, only relevant Activity records pertaining to the records Account BC are retrieved. This behavior is very similar to searching in the Siebel application UI where if you have Account –Action view and if you query on Account applet, only activities relevant to are shown in the bottom list applet.

Also, if you need to do a use SetSearchSpec on child BC, do it before the ExecuteQuery. This way, ExecuteQuery is done only once. Again this is similar to searching in the Siebel Application UI. Below is the screenshot with a simple code to demonstrate this.

I will be posting few more tips again very soon. So do check back or subscribe to RSS.

Also, if you think that this post makes sense and is helpful, leave a comment.

 

Related posts(Auto Generated):

  1. eScript Best Practices - Part7
  2. eScripting Best Practices - Part4
  3. eScript Best Practices - Part6
  4. Siebel Predefined Queries (PDQs)
  5. Unlock a Project

Posted by admin on Thursday, January 3rd, 2008


Page copy protected against web site content infringement by Copyscape
You can follow any responses to this entry through the magic of "RSS 2.0" and leave a trackback from your own site.

11 Responses to “eScripting Best Practices - Part3”

Post A Comment

Recent Posts 

Recent Comments:

  • Sridhar: LDAP mechanism should be handled by Siebel Server. So I dont know why this would matter. I havent tested with...
  • Nitin: Hi, Nice post, however i think this will not work in the case where we are using any aunthentication methods like...
  • Nitin: Hey, Its a nice post but this cannot work if you are using any authetication method like LDAP or something…or...
  • Sridhar: Check Siebel Book Shelf. Siebel Business Process FrameWork workflow guide->Invoking Workflow processes page...
  • Nitin Kumar Jain: Can I control whether the Workflow invoked by the RTE is Synchronous or Asynchronous call. If yes, how?...