Bookshelf Home | Contents | Index | PDF |
Siebel SmartScript Administration Guide > Fundamentals of SmartScript Creation > Releasing ScriptsOnce 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. Scripts should only be released when you are ready for production, otherwise you must rerelease scripts after each change made in order for the change to be visible when testing. Releasing a script saves (or more properly, caches) a precompiled version of the SmartScript definition and all associated code (VB or JavaScript). Releasing 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 to create a pointer to the release file in its server location. When a user invokes a released script, the SmartScript engine will look 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 will copy a release copy of the script from the file system to the server and then execute 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 raised. If a script is not released, SmartScript must compile and execute the script from the server, which causes the script to load slower. When you release a script, you must select the translation of the script you want to release. If a script has multiple translations, you must release each translation individually. The following is an overview of the release process and how it will work in your environment:
CAUTION: If you change a released script, be sure to rerelease it. Otherwise, SmartScript will continue to use the previously released version of the script, which will not include the most recent changes.
NOTE: When you release a script, only the translation you selected is released. |
Siebel SmartScript Administration Guide |