Table of Contents
Advertisement
Note that some languages have multiple variants or 'locales' (for example, US English, UK
English) which are pronounced differently. When you specify a language with multiple locales,
ensure that you use the complete language ID, including the correct locale, for example, "en-
US" (for US English), or "en-GB" (for GB English).
multiple personae
•
The list of personae handled is specified by the user in the Administration resource (see
below, and page 93). This, in effect, sets up a separate directory structure for each persona.
When you define a prompt, you specify its persona by selecting from a drop-down list, and
SAB labels the file accordingly. This mechanism allows you to define multiple sets of prompts
(each set using a different persona) that use the same prompt names but are automatically
stored in different directories. This, in turn, allows you to create a single application that uses
multiple personae. Persona is discussed on page 90.
The SAB database
SAB stores all components, all dialog flows, and all prompts in a database called the SAB database.
A default database is created when the SAB Configurator is installed. New or updated components
can be imported into the SAB Configurator via the Component Workbench, at any time, and SAB
provides mechanisms for updating existing dialog flows in the Tools environment.
For more information about the Component Workbench, see page 92.
When the SAB Configurator is updated, both the Configurator and the SAB database are uninstalled. It is
therefore essential to export all dialog flows to file (see page 77) before uninstalling SAB. The dialog flows can
be re-imported after the Configurator has been upgraded.
Debugging facilities
The Speech Applications Builder provides facilities for analyzing and debugging a dialog flow. Dialog
Analysis lists and describes every path through the selected dialog flow. The data it provides can be
used to build test cases.
Run/Debug allows you to "run" a dialog, telephone it, and watch the call flow as it happens. You can
open an individual dialog step and check its configuration as you hear it being executed.
Version control
The SAB Configurator provides the following version control mechanisms:
SAB automatically adds a version number (1.0) to a new dialog flow and provides both a copy
•
with same version number facility (see page 74) and a copy with an incremented version
number facility (see page 74). All versions of a dialog flow are stored in the SAB database,
and are displayed in the Dialogs tree, in the Dialog version index and following a search.
SAB is a multi-user development environment. To prevent more than one developer
•
simultaneously editing a dialog flow, SAB automatically opens it in a read-only version. The
developer cannot edit the dialog flow until he or she checks it out (see page 37). Whilst a
dialog flow is checked out, no other developer can edit it (though he or she may open another
read only version). The dialog flow should be checked in when the developer has finished
editing.
Speech Applications Builder Configurator User Guide • May 15, 2004 • page 14 of 116
Advertisement
Table of Contents
