Siebel SmartScript Administration Guide > Fundamentals of Creating SmartScripts >

About Releasing SmartScripts

After you have completed and tested your script, you are ready to release it. Though it is optional to release a script, it is recommended to release it to improve its loading speed. It is also recommended that you release scripts if you intend to save a script during execution and resume its execution at a later time. If you do release the script, it will not be possible to resume it from a saved session.

Release scripts only when you are ready for production. Otherwise, you must release scripts again after each change made so that the change is visible when testing.

Releasing a script saves a precompiled version of the SmartScript definition and all the associated code (VB or eScript). Releasing a script saves the release-compiled script to a file on the file system. It also updates the SmartScript definition to indicate that a release file exists and creates a pointer to the release file in its server location.

When a user invokes a released script, the SmartScript engine looks for a release copy of the script on the server. If the SmartScript engine does not find a release copy of the script on the server, it copies a release copy of the script from the file system to the server and then executes the script from there. If a released version of the script does not exist on either the server or the file system, an error is generated. If a script is not released, Siebel SmartScript must compile and execute the script from the server, which causes the script to load more slowly.

When you release a script, you must select the translation of the script that you want to release. If a script has multiple translations, you must release each translation individually.