Siebel Developers Life made easy – Script Assist new ST eScript Engine.

(8 votes, average: 4.50 out of 5)

Loading ...

Viewed : 6,434 times

Written on October 29, 2007 by neel in eScript, How To

Finally there is some good news for Siebel developers. We have always envied developers using sophisticated IDE’s having intelligence engine and dropdown support for object methods and functions but now Siebel too have it. A new scripting engine called ST eScript Engine provides us with all those functionalities we always wanted.

I came to know about it few days ago from a called “Notes on Siebel“ and this is what it had:

Siebel 7.7.2.3 and 7.8.2 introduced a new eScript engine called the ST eScript engine. The engine supports strong typing, which offers performance improvements at the cost of offending some weak-typing-fundamentalists. Even without rewriting script to define your variables, the new engine is supposed to offer performance and scalability advantages over the old T-eScript engine.

More importantly for the day-to-day life of a hard-coding Siebel developer, the new engine (finally!) offers method listing (known elsewhere as ‘typedown’). This is the feature common to all modern IDEs that pops up a list of child methods of a known-type object, so that the poor developer doesn’t have to remember the precise format of ‘PropertySet.InsertChildAt’. One of those little modern innovations that lets developers get on with concentrating on the flow of their script, rather than the irrelevancies of syntax. Now, Siebel’s implementation is hardly Visual Studio IntelliSense, but it’s useful nonetheless.

To switch on method listing, go to View > Options in Tools, then the Scripting tab, and tick the ‘Enable Method Listing’ checkbox: the associated IDE-improvements ‘Enable Auto Complete’, ‘Enable Warnings’ and ‘Deduce Types’ are also worth having. If you can set all these flags then you’re good to go.

If these settings are all disabled, then you’re not using ST eScript engine. This is an enterprise-wide setting that you might have to sell. Details of the whys and hows are on Support Web In brief: for 7.8 & 8, set the System Preference ‘Enable ST Script Engine’ to TRUE, for 7.7.2.4, change your cfg file to set EnableCLIScripting to TRUE.

I would just add few details that you might require if you don’t have access to Siebel Support Web.

In Siebel Tools you can access System Preferences by going through

Screen Menu » System Administration » System Preferences

In Siebel Application you can access System Preferences by going through

Site Map » Administration Application » System Preferences

*Make sure that all your environments (Tools and Client) have the same scripting engine enabled and if you have started your development via one scripting engine then you will need to recompile all you scripted objects.

And it is not recommended to disable ST eScript Engine once you have enabled it.

Ankit

Hi Neel,

Thats a great help to the siebel developer.
thanks for sharing such a good idea.

I have a doubt here,as currently we are using T- escript engine, supposing that it supports weakly typed, now when we change in the system preference and enable the ST Engine scripts.As ST engine is strongly typed, will it create problem for the previous code which has been developed using T script engine.

Thanks
Ankit

Hi Neel,

Thats a great help to the siebel developer.
thanks for sharing such a good idea.

I have a doubt here,as currently we are using T- escript engine, supposing that it supports weakly typed, now when we change in the system preference and enable the ST Engine scripts.As ST engine is strongly typed, will it create problem for the previous code which has been developed using T script engine.

Thanks
neel

Not really, You will need to recompile all your scripted obects and it should work fine. But you will have to ensure that all your enviornments have same scripting engine set in their system prefrences

Kanishka Sarangi

Hi Neel,

i have a requirement here, wherein i completely need the existing code to be migrated to be ST engine compatible. i mean i tried checking the deduce type flag and compile the object, this BS of mine worked fine and there were no errors since i used ST code format, but all the existing code started throwing errors, since they are not ST Typed. Kindly let me know the procedure of how to make the existing code ST compatible.

neel

Not really, You will need to recompile all your scripted obects and it should work fine. But you will have to ensure that all your enviornments have same scripting engine set in their system prefrences
http://slemos.com.ar/ Sebastian

Hi, Ankit. The only problem you can face with this new engine is if you are running Siebel 7.7.2.x, in which some standard BS doesn’t compile. Here’s the list:

Business Service
Alert Online Email Notification
CyberSource Adapter Service
EAI Create SearchSpec IntObj
Order – SAP 4x Maps
Taxware Adapter Service (eScript)
WorkFlow Patcher

If you need more info about this problem you can search for Alert 1176, or ask us

Regards!
http://slemos.com.ar Sebastian

Hi, Ankit. The only problem you can face with this new engine is if you are running Siebel 7.7.2.x, in which some standard BS doesn’t compile. Here’s the list:

Business Service
Alert Online Email Notification
CyberSource Adapter Service
EAI Create SearchSpec IntObj
Order – SAP 4x Maps
Taxware Adapter Service (eScript)
WorkFlow Patcher

If you need more info about this problem you can search for Alert 1176, or ask us

Regards!
Noone

Please note that there are very valuable scripting improvements in version 8.0.
1- Repository based ScriptAssist and compilation support. Accelerates development and upgrade.
Eg:If you type
var oSvc = TheApplication.GetService (
ScriptAsist displays the list of services (and this appliies to all similar functions,
GetBusObject, GetBusComp, SetFieldValue etc).
The compiler will also generate warnings if you have such incorrect names.
2- Fix & Go debugging: Greatly accelerates dbugging by eliminating .srf compilation. You make changes to the script and when you save it it applies immediately. You dont need to restart the client.
3- Services as Script libraries: Enables modular development and upgrade, accelerates development.
You can now see a script method on a Service via ScriptAssist and directly call it (w/o InvokeMethod).
Eg;
Suppose you have a method on Service Service1
function my_concat (left : chars, right : chars) : chars
{
var sReturns : chars = left + “_” + right;
}
Then you cann call this method from another place like this.
var oSvc = TheApplication ().GetService (”Service1″);
var sConcat : charr = oSvc.my_concat (”Hello”, “World”)
Thge ScriptAssist will also display that function in the drop down.

Please refer to the latest documentation on how to use these features. These features are available for ST engine only.

You need to set the External Use & Cached flag in the very first version of 8.0 to make #3 work. In later versions, you only need to set External Use flag.
Noone

Please note that there are very valuable scripting improvements in version 8.0.
1- Repository based ScriptAssist and compilation support. Accelerates development and upgrade.
Eg:If you type
var oSvc = TheApplication.GetService (
ScriptAsist displays the list of services (and this appliies to all similar functions,
GetBusObject, GetBusComp, SetFieldValue etc).
The compiler will also generate warnings if you have such incorrect names.
2- Fix & Go debugging: Greatly accelerates dbugging by eliminating .srf compilation. You make changes to the script and when you save it it applies immediately. You dont need to restart the client.
3- Services as Script libraries: Enables modular development and upgrade, accelerates development.
You can now see a script method on a Service via ScriptAssist and directly call it (w/o InvokeMethod).
Eg;
Suppose you have a method on Service Service1
function my_concat (left : chars, right : chars) : chars
{
var sReturns : chars = left + “_” + right;
}
Then you cann call this method from another place like this.
var oSvc = TheApplication ().GetService (”Service1″);
var sConcat : charr = oSvc.my_concat (”Hello”, “World”)
Thge ScriptAssist will also display that function in the drop down.

Please refer to the latest documentation on how to use these features. These features are available for ST engine only.

You need to set the External Use & Cached flag in the very first version of 8.0 to make #3 work. In later versions, you only need to set External Use flag.
Pingback: PS Pad Editor – making Siebel eScript easier | Siebel Unleashed
Pingback: T Script engine VS ST Script Engine. | Siebel Unleashed
Pingback: T Script engine VS ST Script Engine. | Siebel Unleashed

Siebel Developers Life made easy – Script Assist new ST eScript Engine.

Related Posts

Visitors to this post, also read: