Importing, Exporting, and Deploying SmartScripts

This chapter describes how to import, export, and deploy SmartScripts. It covers the following topics:

Siebel SmartScript allows the exporting and importing of SmartScripts in a binary format between the development, testing, or production environments. A file that can be imported or exported is referred to as a Siebel SmartScript file or SSS file.

If you have a large number of SmartScripts to deploy to another environment, consider using the Application Deployment Manager. For more information, see About SmartScripts and the Application Deployment Manager.

Exporting SmartScripts

You can export SmartScripts using a menu option available in the Scripts view of the Administration - SmartScript screen. When you export a SmartScript, all the elements required for a SmartScript are copied to the destination file. When this file is imported into another Siebel database, the SmartScript must have all the elements required to execute successfully. Any conflicts with existing elements in the new database are resolved during the import process.

To export a SmartScript

Navigate to the Administration - SmartScript screen > Scripts view.
Select the SmartScript you want to export, and choose Export Script from the Menu button.
The SmartScript Export Results view appears.
Click the hyperlink that displays the name of the SmartScript to export the SmartScript.
The File Download dialog box appears.
Click Save to download the SmartScript.
The Save As dialog box appears.
Specify a location to save the SmartScript, then click Save.
The SmartScript is exported to the location that you specify.

Importing SmartScripts

You can import SmartScripts using a menu option, which is available in the Scripts view of the Administration - SmartScript screen. The import process checks many characteristics of the SmartScript elements for error conditions. For example, it checks references to make sure that questions specified as branch destinations have been defined. When the import process has finished, you can view a log file listing any errors by clicking a link.

The import process transfers everything that does not cause an error or a conflict from the SSS file into the database. When you import a SmartScript, the SmartScript that you want to create or update is based on the SmartScript name for the exported SmartScript, not the file name of the SmartScript or the name of the selected SmartScript when the Import button is selected.

Note: When you import a SmartScript into a local SQL Anywhere Database in which the pages for the importing SmartScript already exist, delete the existing pages to make sure that duplicate page branches are not created. This is necessary only when importing into an SQL Anywhere Database.

Note: For Siebel Innovation Pack 2015, the local database for the Siebel Mobile Web Client uses SAP SQL Anywhere. SAP SQL Anywhere is not available for new deployments after September 2015. For more detailed information on how this change affects Siebel Tools and Siebel Remote, see Siebel Release Notes on My Oracle Support for Innovation Pack 2015 (Doc ID 1996273.1).

After a SmartScript has been imported, verify it by using the Verification Wizard, and then perform normal testing. For information about the Verification Wizard, see About the Verification Wizard.

To import a SmartScript

Navigate to Administration - SmartScript > Scripts.
Click Menu, and choose Import Script.
The SmartScript Import Intro view appears.
In the File Name field, click the Select button to display the Add Attachment dialog box.
Navigate to where the SmartScript is stored, then select it.
From the In case of error drop-down list, select how you want to handle conflict resolution.
For more information, see Resolving Conflicts Encountered During an Import.
Click Import File.
The SmartScript is imported. A list of the different elements that were processed as part of the import appears in the Processing Steps list applet. The import process also generates a log file that you can view when you click the hyperlink that displays the name of the log file.

Resolving Conflicts Encountered During an Import

If Siebel SmartScript encounters conflicts during the import process, it refers to the options you select in the In case of error field. You can select from the following options: Update, Skip, or Add.

These options determine how Siebel SmartScript handles the conflict or error. You can add the element, skip the import of that element, or update the existing element in the database. If you choose the Add option, a duplicate version of the elements in the SmartScript is created (Script, Page, or Question). This duplicate version of the SmartScript has a different name. For example, if you import a SmartScript entitled Revenue Schedule Script with the Add option selected, the application creates a duplicate version of this SmartScript entitled, Revenue Schedule Script_1. The script references within the SmartScript continue to reference the original element name.

If Siebel SmartScript encounters any errors or conflicts, it creates a log file. You can view this log file when the import process has finished by clicking a link. Review the conflicts and errors reported in the log file, and correct each element as necessary, using the appropriate Administration - SmartScript view.

If the contents of a picklist are different in both the exporting and importing databases, a conflict occurs. Update the contents of the picklist before exporting the SmartScript, so that the contents are consistent in both databases.

About SmartScripts and the Application Deployment Manager

SmartScripts are one of the data types that the Application Deployment Manager (ADM) supports. Using ADM, you can import or export SmartScripts between different environments (for example, between development and production). For more information about Application Deployment Manager, see the Siebel Application Deployment Manager Guide.