SiebelGuide.com/siebelblogs

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

Though scripting should be avoided, it is often common that scripting would become necessary to meet our requirements. So if scripted, it should be done the most efficient way. There are several optimization techniques. Below are some and I will post more in the future.

Tip 1:
Avoid repeated calling of a function if the results returned are the same. Instead cache the value in a variable. Especially avoid repeated calling of the API function like TheApplication().ActiveViewName() as shown below.


Tip2:
Delay Object Instantiation. If the object being used is under a conditional expression then wait till the conditional statement actually evaluates true. This reduces the cost and burden on the server. See the code below.

 

Make sure you leave some comments.

There are more Tips to come. So stay tuned.

 

Related posts(Auto Generated):

  1. eScripting Best Practices - Part4
  2. eScript Best Practices - Part6
  3. eScripting Best Practices - Part5
  4. eScripting Best Practices - Part1
  5. Count number of Child Records without Scripting

Posted by admin on Monday, December 3rd, 2007


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.

5 Responses to “eScripting Best Practices - Part2”

Post A Comment

Recent Posts 

Recent Comments:

  • Anonymous: Greate man greate….Very help ful
  • Sridhar: Did you check the BC Field User Properties? check and let me know.
  • Nishant: Hi, There are 2 controls -(fields) on applet level which are showing as read only though the Read Only property...
  • Sridhar: anonymous login is nothing but guest login.
  • Sridhar: How are you authenticating? if you dont want to authenticate make sure anonymous login has access to this view....