• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Siebel eScript

Siebel eScript



The slides for introducing how to use Siebel eScript and some best practies

The slides for introducing how to use Siebel eScript and some best practies



Total Views
Views on SlideShare
Embed Views



5 Embeds 247

http://gosiebel.com 117
http://www.gosiebel.com 97
http://www.slideshare.net 24
http://naveensprai.blogspot.com 8
http://www.linkedin.com 1



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • Declarative alternative strong typing Support strong type and typeless variable Strong type –- compile time  performance Typeless -- runtime
  • ECMA-262 Edition 4 You should regard coding as a last resort. Siebel Tools provides many ways to configure your Siebel application without coding, and these methods should be exhausted before you attempt to write your own code, for the following reasons: ■ Using Siebel Tools is easier than writing code. ■ More important, your code may not survive an upgrade. Customizations created directly in Siebel Tools are upgraded automatically when you upgrade your Siebel application, but code is not touched, and it may need to be reviewed following an upgrade. ■ Finally, declarative configuration through Siebel Tools results in better performance than implementing the same functionality through code.

Siebel eScript Siebel eScript Presentation Transcript

  • Siebel eScript
  • Agenda
    • What’s Siebel E-Script
    • Why to use
    • Where to use
    • When to use
    • How to use
    • Tips and Tricks
  • What’s Siebel E-Script
    • A scripting language
    • The core language is javascript
    • Siebel eScript provides access to local system calls through two objects, Clib and SElib,
  • Siebel Script --outlying
    • Types of Scripts: There are two types of scripting available:
      • Server Scripts (eScript or SiebelVB)
        • Execute on the server for web clients or on the client machine for mobile or dedicated web clients
      • Browser Scripts (JavaScript)
        • Downloaded to the client and are executed within the browser
  • Where to Use
    • Siebel Tools
    • Web
  • When to use
      • Data Validation: Complex and business object/component data relationship rules can be written
      • User Interaction: Specific messages to users based on specific inputs – string concatenation is supported
      • Integration: Transfer the data to and from the external system ,uses include calling a business service, workflow, etc
  • When to use
  • How to Use
    • Siebel eScript Guidelines
    • Siebel eScript Commands
  • Siebel eScript Guidelines
    • Declare your variables
    • Consider case sensitivity
    • Use parentheses () with functions
    • Use four-digit years in dates
    • Use the this object reference
  • Siebel eScript Commands
    • Applet Object Methods
    • Application Object Methods
    • Business Component Objects
  • Tips and Tricks
    • Scripts are always interpreted (all text in the script is parsed), use compact notation where possible (for example):
        • if(foo == bar)
        • doSomething();
        • Instead of
        • if(foo == bar)
        • {
        • doSomething();
        • }
      • Use “ elimination ” code to short circuit functions when not needed:
        • if(isInDoItList(myval)) {
        • longChunkOfCode();
        • }
  • Tips and Tricks
      • When querying for a business component, activate all fields via the ActivateField() method prior to executing the query (this is well documented in Siebel Bookshelf).
      • When querying for BCs try to use a “ForwardOnly” flag in the ExecuteQuery() method, this forces Siebel to create a forward only cursor which is more efficient than a bi-directional cursor.
      • Be very careful with using “SetFieldValue” within a “PreSetFieldValue” event due to possible undesired recursion.
      • You can’t throw an error message during the “OnLoad” logic of an applet, (the error goes nowhere).